Sorry if this problem has been resolved a thousand times before...

I’ve been having problems with my linux install and, as of yet, I haven’t been able to find any threads pertaining to similar problems (I have no idea what I’m really searching for in the first place). I’m currently running Win2k on my primary hdd & would like to install a linux distribution on my second hdd.

When installing Mandrake 9.0, I complete the setup & allow LILO to be the boot loader since I don’t mind LILO. I am able to successfully boot into Mandrake with full usability. The problem occurs when I reboot into Win2k. Win2k startup time increases dramatically to around 7 minutes to load my profile & initialize. Then, Windows Explorer reacts very, very sluggish and non-responsive sprinkling in the occasional “Program not responding” messages.

OK, so I can then go back and delete my linux partitions on my second drive & reboot into Win2k and everything is kosher. What is causing this response?? If Explorer doesn’t recognize the file system, doesn’t it usually ignore the drive?? I would really like to explore Linux, but I’m also tied to Windows for programs that I need for school. Does anyone have any ideas on how to resolve this.

NOTE: I’ve also installed debian 3.0 with the same results.

Maybe this post will help.

hi, i have exactly the same problem. i'm dual booting win2k and rh7.3 using grub. before installing linux, win2k booted really fast. but now it takes more than 8 minutes to boot and almost locks up when i login.
the problem , i think, is that win2k is trying to "MOUNT" my linux partition through a service called "Logical Disk Manager" but of course fails to do so! i tried to diable the service, same result.
i tried to pass the "hide (hd0,6)" in grub when booting win2k, but win2k insists on accessing the partition.
any ideas??

ps. the post above isn't really helpful, since i only have one hard disk and i can't disable a partition from win2k!

Thanks for the link linuxcool . It works!!

I had tried going into Device Manager to check if the drive was running in compatibility mode, but saw no problems & didn't even think to disable Windows from attempting to read from the drive.

You're welcome acidmoon.