Pigsaw Blog
All the pig that’s fit to saw

L 99 99 99…

Well that was far more difficult than it should have been. This weekend I switched my laptop back from Linux to Windows XP. Strangely, each time I install WinXP it’s more difficult than the time before.

In case you’ve found this page via Google, here’s one answer to the L 99 99 problem, which stumped me for hours…

The problem: After booting your PC it stops, saying simply “L 99 99 99…”, with about half a screen full of the 99s.

The explanation: This is actually an error message from the Linux LILO bootloader, reporting hex error 0×99. Despite removing Linux the Microsoft-recommended way — and wouldn’t you think they’d give you a foolproof method to do that? — I still had a trace of Linux stubbornly clinging on. It seems that removing partitions won’t remove the MBR, which is where the bootloader lives.

The solution: The safest solution is to replace LILO with a Windows bootloader — this assumes you want to restore Windows, as I did. The Microsoft way of doing this (article 247804) is to boot with a Windows XP installation disk, choose the recovery console and run the Windows fdisk /mbr command. Unfortunately my OEM recovery disks from IBM didn’t give me that option, so I had to borrow a Windows 2000 disk and use that instead. Once the Windows bootloader had been reinstalled I was able to continue my XP installation. If you don’t have access to a retail edition of Windows you might try bootdisk.com, but that looked a bit too Wild West for me.

I stumbled across another solution, too, specific to IBM Thinkpads. This involves changing a BIOS setting to so that LILO correctly reads the disk geometry (mismatching geometry is what gives error 0×99). However, when I tried this the BIOS flashed up a big scary warning telling me that this could expose the special IBM Pre-Desktop area of the disk, and make it vulnerable to overwriting by the operating system. I duly retreated, and am glad I did.

The fdisk solution above was right for me because I wanted to restore Windows. If you want to keep Linux you’ll have to try something else.

Apart from the Windows 2000 disk, the indispensible tool I used was a Knoppix CD — a real work of genius. Oh yes, and Google. Never forget Google.

Tags: , , ,

5 Responses to L 99 99 99… »»


Comments

  1. MC
    Comment by MC | 2006/02/20 at 09:49:21

    Sounds like removing linux didnt clear the MBR. I would have gone for a DBAN set to quick wipe under these circumstances. I think I have found before that Fdisk does not clear the MBR area of the disk.

  2. Nik
    Comment by Nik | 2006/02/20 at 12:39:25

    You’re right. I used the Linux version of fdisk to remove the partitions, courtesy of Knoppix. But that doesn’t touch the MBR. However, that’s the Microsoft recommended way of doing it. Even if it hadn’t, I’d have thought installing Windows would have installed its own MBR — or given me the option. The retail Windows install disks allow this, but not the OEM version that I had.

  3. Comment by Kirk | 2007/04/06 at 16:12:16

    I had the same exact issue after re-partitioning my Linux install. I have a DELL Precision M65 and I did have a tough time trying to fix this problem with Fdisk, as when I booted from the DELL recovery disk. Basically as you mentioned, Fdisk is no longer “there” in windows xp, but the command fixmbr should be threre and worked perfectly.

  4. Comment by Robert | 2008/07/03 at 06:46:39

    The way to wipe out all partitions on a disk and the boot program unconditionally from linux for and ide disk is

    dd count=1 if=/dev/zero of=/dev/hda

    for a scsi or sata drive

    dd count=1 if=/dev/zero of=/dev/sda

    This will remove EVERYTHING and the installers will see it a brand new disk.

    If you do the same without the count=1 it will wipe the whole disk, a very minimal security wipe. This may not stop anyone determined to recover data but it will stop them seeing anything without spending lots of money.

  5. Comment by freeformlife | 2008/10/10 at 17:43:42

    same problem, also oem’s couldn’t get me any further than a diagnostics tool which found no problems. Thank you for the fdisk/mbr solution worked like a charm.
    (I found an old windows 98 disk to run it!!! glad my mom is a pack rat!)


Leave a Reply »»