Well, I booted back into XP Pro, and both those problem devices work fine. So, I must conclude that when XP Pro went down, it damaged the lindows partition, even though lindows resides on a different drive and this drive was removed from the device list in XP.
Joel Sat, Jul 26, 2003 at 08:00:14AM -0400, Joel Hammer wrote: > I burned a CD at work and could not read it at home on any computer. > (XP home, XP pro, Caldera 2.4, lindows 3.0, lindows 4.0). Everytime the > first big jpeg file gets accessed (6 million bytes), everybody just hangs. > Windows explorer won't even shut down, requiring a reboot. > > I dual boot lindows 3.0 and windows XP pro. So, after a hang reading > this CD in XP pro and a reboot into lindows, booting lindows results > in no eth0 device detected, and the cdrom isn't detected. In the bios > setup up the eth0 is enabled and the cdrom is detected. The cdrom problem > is especially bad since I can't run any of the diagnostic software I > think might be on the motherboards's CD. > > Is this just a new motherboard going bad? Could XP crashing have damaged > the linux partition? I had the linux partition disabled in XP before the > problem began. > > Any suggestions appreciated. > > > Joel > > _______________________________________________ > Linux-users mailing list > [EMAIL PROTECTED] > Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
