Please read my earlier post Installing Linux on the IBM ThinkPad T43 for background information.
The setup so far: Windows XP Pro & SUSE Linux Professional 9.3 (with GRUB installed in the MBR). Although I had a perfectly functioning dual-boot system at this point in time, the fact that the Access IBM button did not work irritated me.
After a few unsuccessful attemtps at getting it to work, I decided to restore the MBR to it’s original state, to check if that would get the Access IM button working. When GRUB was installed, SUSE kept a backup copy of the MBR. I booted into Linux, invoked YaST2 and followed the instructions. The system told me that the MBR was restored successfully. However, after rebooting, there was no operating system found. No Linux, no Windows. And… the Access IBM key still didn’t work. Okay, it is possible that something may have gotten messed up during the experimenting and so the restore original MBR did not fix it. But I can’t say for sure.
Back to Linux. I rebooted using the SUSE DVD into rescue mode, and reinstalled GRUB. Came back to square one - a perfectly functioning dual boot system, minus the Access IBM functionality.
Since it looked like I would have to get into possibly more “destructive” experimentation, I decided to make me a set of system rescue and recovery disks, which would enable me to restore WinXP as well as the factory installed software provided by IBM. (You can do this within WinXP from: Start -> All Programs -> Access IBM -> Create Recovery Disks) It took six CDs.
Next, I did a cursory search on the web to see if anyone else had faced the issues on hand, but the results were not encouraging. So, I decided to take the easy way out and call IBM. Calling the IBM helpline didn’t help because their lines were always busy. I sent them an email describing the problem. Their response was to ask me for the serial number on my machine, which I sent and then waited… (Tip: If you have to ever communicate with IBM regarding your laptop, always include its serial number. It’ll save you the time of an email roundtrip.)
Getting impatient, the next day I sent them a reminder and about an hour later got a call from one of their Support Executives. After describing the problem to him, his response was: “If you want to install Linux and have a dual boot system, the Access IBM funtionality will be lost. Sorry sir…” I wanted to discuss in a little more technical detail stuff about the MBR, boot partitions, etc., but he couldn’t help and that clearly was getting nowhere. It was then that I decided I wanted to move back to square zero. To get the machine back into factory shipped state and start afresh. The executive was not at all confident that the rescue disks I had made would restore the system to the factory state and said that if it didn’t work, I’d need to take the notebook to their tech center. He promised to call me back in half an hour (and he did) to tell me what settings I should keep for the IBM Predesktop area in the BIOS. FYI, while restoring I kept the setting at “Normal”. The restore process obviously destroyed my Linux installation, but two and ahalf hours later I had the system in the state in which it was shipped to me… with the Access IBM button working.
Okay… it was time to get to work. My fundamentals were rusty and if I wanted to refresh my knowledge of how things work under the hood (which I very much did), I knew I would need to brush them up. So back it was to the web and good old Google. Seek and you shall find. I covered up disk architecture, partitioning, the boot process, MBR and boot sectors, boot loaders, Microsoft’s way of dealing with booting, the rest of the world’s way of dealing with booting, etc., etc.
It was fun, but I couldn’t do as much justice to the knowledge revision process as I’d have liked to, given the constraints of running a company and having to do everyday “real” work. The research and the experimentation resulted in some eye-opening, a lot of memory jogging and even a couple of tips and tricks - stuff that I’ll present in other postings.
To come down to it, there is more than one way to address the current challenge. This is what I did. It’s childishly simple - I almost felt cheated ;)
Important: Set the IBM Predesktop Area (in the BIOS) to “Secure”.
Boot using the SUSE DVD. Shrink the Windows partition as required. Follow the instructions and go through the regular installation process. Create a primary partition for /boot (the other stuff can go into the extended partitions) and when the time comes to install GRUB (you do prefer GRUB to LILO, don’t you?), make sure you install it into the boot sector of the boot partition. Set this partition as active. Leave the MBR alone.
That’s it.
Continue and complete the install. Reboot. If all has gone well, the system starts up and you have a choice of booting into SUSE (the default) or WinXP. They both startup fine.
Finally, try the Access IBM button when the machine is starting up. It works just fine… :)