Re: [PLUG] OT: UDMA Problem

[Mike Leone <turgon@mike-leone.com>]

gyoza@comcast.net (gyoza@comcast.net) had this to say on 03/23/05 at 09:35: 
> I have a new drive that was working well.  Now, I can't get it to boot
> with UDMA enabled in the BIOS.  Specifically, I can't get WinXP to
> boot.  SuSE still boots fine, even with UDMA enabled.  SuSE can also 
> read the NTFS partition.
> 
> WinXP reports "UNMOUNTABLE_BOOT_VOLUME" and "STOP 0xED" on a nice, blue
> screen.  It does boot with UDMA turned off, or in Safe Mode.

You did read this, right?

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q297185

CAUSE
This behavior can occur if either of the following conditions is true: 
. Your computer uses an Ultra Direct Memory Access (UDMA) hard disk
controller, and the following conditions are true: 

. You use a standard
40-wire connector cable to connect the UDMA drive to the controller instead
of the required 80-wire, 40-pin cable. 
. The basic input/output system (BIOS) settings are configured to force the
faster UDMA modes. 
 
 . The file system is damaged and cannot be mounted 
 
> 
> The only thing I changed was that I used the "convert" utility to switch
> from FAT32 to NTFS.  (I did that because I didn't like the cluster size
> used by FAT32.)
> 
> Does anyone happen to have a solution?
> 
> ___________________________________________________________________________
> Philadelphia Linux Users Group         --        http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug