The Webmechs Press

I just realized tonight why my internet usage billing on the iPhone seems excessive compared to, say, when I was using my Nokia XpressMusic 5800. I’ve seen a lot of complaints on the internet about such incidents and contrary to what many are suspecting it is most probably NOT the telecom carrier’s sneakiness/dishonesty, nor is it exactly the iPhone hardware’s fault.

The most likely reason you are getting billed for internet usage that you don’t believe you’re using is actually rather simple but easily overlooked, and it is: ADVERTISEMENT SERVED BY FREE APPS! Whenever an application shows an ad it loads it from the net and if you do not have wifi turned on, it will do a data connect using either 3G or GPRS (so turning off 3G will not help).  One way to make sure you don’t connect is to just stick an invalid Access Point Name (APN) in Settings -> General -> Network -> Cellular Data Network. If you have SBSettings, you can enable toggling of 3G and EDGE and toggle both off which is a more elegant of turning your data connection off as well as making it faster to turn on as well.

One of the greatest frustrations I have had with using the Apple Wireless Bluetooth Keyboard with my Modbook is that it sometimes gives out inexplicable error messages when trying to pair with Windows 7 and refuses to go forward with the process.

I was able to find an article on the net (forgot the link, unfortunately), explaining why and how to deal with the problem.  It turns out that if the Apple Wireless Keyboard got paired with OS X, it needs to be unpaired from OS X first.  Otherwise, for some reason (it keeps wanting to be with OS X ?)  it will fail to pair with Windows 7.  Remember, this means that the Apple WIreless Keyboard not only needs to be disconnected but also unpaired.  You should be able to do this by clicking on Bluetooth in the System Preferences, selecting the Apple Wireless Keyboard and clicking on the “-” button at the bottom.  This should both disconnect and unpair the Apple Wireless Keyboard.

Driver-wise, you should ensure that you use “Apple Built-in Bluetooth” under “Bluetooth Radios”, and then install the Apple Keyboard Driver from Boot Camp in that order.  If you can’t get them work, uninstall these drivers and reinstall them in the proper order.

The iPhone is a very nice device, but one of its many flaws are that it sucks up battery juice like there’s no tomorrow (which there literally won’t be if you don’t charge it every chance you get).  For someone who has lots of music videos and who may just want to listen to the audio to conserve battery power, here’s how to do it:

1. Play the video
2. Press the power button.  The screen will go blank.
3. Double click the Home Button.  You will get the iPod controls onscreen.
4. Press play to start playing the video’s audio track only.
5. Wait for the screen to go blank automatically or…
6. Click the power button to make the screen go blank, but this time the audio will continue playing.

When installing Windows and OS X side by side using Apple’s recommended Boot Camp technique, you can only use one partition for Windows.  If, like me, you need multiple partitions for Windows, you have to do it another way.  The first thing to understand is that Boot Camp Assistant is not at all necessary for installing Windows 7.

The other thing to understand are that the interaction between GPT/MBR (the new and old style partition tables) and EFI/BIOS (the new/old style firmware) makes things very tricky if you don’t understand the issues.

Several issues to know:

1) Windows 7 (and Vista too I believe) WILL install on a GPT partitioned drive and can also be booted from EFI firmware.

2) When the Windows 7 install DVD boots on a Macbook though, it actually boots in BIOS mode(!), this is because the Macbook will switch to BIOS mode when it sees that a DVD has a BIOS-based bootloader, which a Windows 7 install DVD of course will have.

3) When booted in BIOS mode, Windows 7 refuses to install on a GPT partitioned drive (this is what leads people to mistakenly think that Windows 7 does not support GPT installation)

4) However, and this is the kicker, even if you get the Macbook to boot Windows 7 (whether the installer DVD or the OS itself) in EFI mode, things will not work properly because the EFI version on Macbooks is the older version which Windows does not want to work with!  #$%@#$#@^@@….!!!!!  Windows 7, etc… *need* UEFI 2.0 to properly work with GPT partitions.

These 2 pages have more to say on the issue:

http://darobins.spaces.live.com/blog/cns!C188BEF79F825945!529.entry

http://www.insanelymac.com/forum/index.php?showtopic=186440

So how then do we install the 2 OSes side-by-side?  We’re left with two ways:

1) Hybrid GPT-MBR partitioned disk

or

2) MBR partitioned disk

From a Windows-centric viewpoint, method 2 is probably the cleanest and lets you deal with your partitions with standard tools like Partition Manager.  In this case, you will need to hack your OS X install DVD to install on an MBR disk.  The two links below explain how:

http://blog.netnerds.net/2009/10/easily-install-mac-os-x-leopard-on-an-mbr-formatted-disk/

http://www.insanelymac.com/forum/index.php?showtopic=181287

But because they involve extensive tweaking on the Mac command line which I don’t currently wish to involve myself in, I will go with method 1 instead which this blog article will explain further.

Firstly, a hybrid GPT-MBR disk is one looks like an MBR drive to older non-GPT supporting OSes but which GPT-supporting OSes sees as GPT.  As far as I understand, only the Disk Utility that comes with the OS X install DVD to create a hybrid GPT-MBR table correctly (if gParted can do this, drop me a comment…)

In my case, I needed 4 partitions, 3 for Windows and one for OS X.  In Disk Utility, I did the following steps:

1) Create 4 partitions in the partition editor, 3 as FAT and 1 as an OS X filesystem.  IMPORTANT: Make the OS X partition the last one.

2) (VERY IMPORTANT) Select GUID Partition table instead of MBR type using the Options button.

3) Apply changes and then reboot into the Windows 7 install DVD.

4) When the Windows 7 installer shows the available partitions you will see one extra 200MB partition at the beginning.  DO NOT DELETE THIS!  This is the GPT protective partition, deleting it will prevent Windows 7 from booting correctly afterwards.

5) The free space you allocated for OS X will show up as “unallocated free space”.  Do not panic.  This is because MBR only allows 4 primary partitions and they will already have been taken up by the GPT protective partition and the 3 primary FAT 32 partitions.  OS X uses GPT aand will see this last partition correctly, however, MBR cannot show it.

6) A side effect of pre-partitioning this way is that the 200MB (for Win7 RC) and 100MB (for Win7 RTM) “System Reserved Partition” will no longer get created.  Some people consider this an annoyance so this would be a good thing for them.

7) You can now proceed to format one or all 3 partitions via the Windows 7 installer.  This will turn them into NTFS, and allow install of Windows 7 on them.

8 ) NOTE: If you had installed OS X in Step 3, before booting into the Windows 7 Install DVD, the machine will default to booting in OS X, so you should hold down the Alt/Option key to see the Windows partition and boot from it instead.

My Modbook from OCW took less than five days to arrive.  Less than five days after receiving it, it also saw a ~USD100 price drop.  Lol!  Can’t win ‘em all.

So anyway, one of the priorities was to get Windows working on this machine.  Since the Modbook has 4GB on it, I elected to install a 64-bit Windows OS on it to make full use of the RAM.  Even though some of the info out there may lead you to think that only 64-bit Vista is supported, it turns out that Windows 7 x64 RC installs and works great on the Modbook (and of course on the Macbook as well).

Just so we’re clear on the hardware environment, the Macbook base for this machine I have is the 2Ghz Core 2 Duo with the Nvidia 9400M graphics chipset and it comes with the Leopard OS X 10.5.6 DVD.  Following are the steps I took to get things working.  Steps 1-3 are covered in the Boot Camp Setup and Install Guide although Step 3 will be a bit different.

Step 1. Use Boot Camp Assistant to create the partition for Windows 7

Step 2. Boot from the Windows 7 DVD and install Windows 7 in the usual manner

At this point, after the stock Windows 7 install, the modbook’s digitizer and WiFi actually work without worrying about drivers, a very pleasant surprise!  However, there are certain glitches you may encounter.  The optical out on the left side of the modbook will turn on which may be a battery drain.  No sound even if sound drivers seem to be installed already.  These two are easily fixed it turns out by installing the drivers from the Mac OS X Install DVD - Step 3.

Step 3. At this point, if you were installing one of the “supported” OSes (e.g. Vista or XP), you just have to click on Boot Camp\setup.exe in the Install DVD.  Under Windows 7 however, the setup.exe refuses to run complaining about incompatibility.  You can be sneaky about it and just directly run \Boot Camp\Drivers\Apple\BootCamp64.msi which will work.

Step 4. For my particular Modbook model, I also had to separately run \Boot Camp\Drivers\NVidia\NvidiaMobileSetup64.exe and \Boot Camp\Drivers\NVidia\NvidiaChipset64.exe to get the graphics and chipset drivers installed.  If you want even newer graphics drivers, you can download the latest Nvidia mobile drivers from nvidia.com itself.

At this stage, everything should be pretty much working except in my case, I had one additional important hurdle to overcome.  By clicking on the Boot Camp icon in the notification tray, you will be able to boot back to OS X from Windows 7.  The reverse was, however,  sadly not possible.

You are supposed to boot back to Windows 7 from OS X by clicking on System Preferences | Startup Disk, but in this case, the Windows partition wouldn’t show up there.  You can still choose which OS to boot by plugging in a USB keyboard and holding down the Option key (equivalent to Alt on a PC keyboard) or using rEFIt, but these are very suboptimal solutions for a keyboard-less tablet.  It turns out the way to get around this and have essentially the same function as Startup Disk is to manually bless the Windows partition instead via the command line:

sudo bless --mount /Volumes/NameOfWindowsHD --setBoot --legacy

You should be able to put this in a clickable script (haven’t figured out how to do that in OS X yet).  Now we are in computing nirvana.

Gout Herbal Treatment

FPGAs or Field Programmable Gate Arrays are essentially programmable/reconfigurable hardware. A particular CPU architecture can be thought of as hardcoded whereas in contrast, FPGAs let you change the processor “architecture” any time you like. The trade-off is performance versus flexibility. While their gate configurations are reprogrammable, the different process utilized to make FPGAs mean that their switching speeds are going to be far slower than with dedicated gate designs.

On the other hand, the fact that you can tailor the “hardware” for a particular task or algorithm means that it has the potential to execute way way faster than implementing that algorithm in terms of a fixed assembly language instruction set. The caveat is that assembly language is pretty cumbersome as it is and programming at the gate level is going to be an even lower-level task.

The apparent return you get for having to endure the much more difficult programming task is that you effectively get much more computing power for the same amount of energy/power consumed. The analogy would be that of using a lower-level language to wring more performance out of less powerful hardware.

http://www.fhpca.org/
http://www.forbes.com/2003/03/25/cz_dl_0325star2.html
http://www.newscientist.com/article.ns?id=dn7448

A great, aptly-named FPGA site that discusses fun FPGA projects:
fpga4fun.com