Originally Posted by MrEvil
Power down your system and hold the Fn key while you power up. This will bring you into the built-in diagnostic utility. Let it run tests (you won't have a utility partition to run 32bit diag though) and see if there's not some other hardware problem.
I'd also low level format that drive, I've had so many problems with specialized partitions on drives for either recovery or from just Linux. XP just can't deal with them.
Well, there wasn't any Linux on it when the problem started. Nothing about the initial problem changed when installing Linux.
I don't think there's a real hardware problem here since Linux runs like a charm.
I also have to remind people that this very Windows XP on the very harddrive doesn't show this problem when connecting it to a random desktop. It only appears when in the D620.
I am sure now that what we see here is a repetition of the old phenomenon that BIOSes would limit the harddrive size for Windows but that Linux and FreeBSD would run the large drives fine if you just restricted the boot partition to be within the size limit. Once up, in Linux and FreeBSD the disk controller drivers take over ignoring the BIOS. In Windows the disk controller drivers inherit the bad size information from the BIOS and won't do even if you limit the partition size to be within the limit.
As a matter of fact, Dell seems to have managed to buy a BIOS that has a 128 GB hard drive size limit:http://techrepublic.com.com/5208-623...237829&start=0
This also says "up to 100 GB":http://www.dell.com/us/en/dfb/notebo...n=specs#tabtop
I think for a Core Duo generation business laptop that is very embarrassing.
I ordered both a regular HD caddie and a bay caddie. That will allow me to run XP off the 60 GB drive and either dual-boot by swapping harddrives or do dual-disk dual-boot. Not what I had in mind when I picked the Latitude.
I'll check whether I have the newest BIOS, though. You'd think I'm not the first one to find that a Notebook of that age shouldn't have a 128 GB limit, so maybe they fixed it in an update.