GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After installing Suse 8.1 the explore.exe from win2k opens and works very slow! What could be the problem? Has anybody an idea? Windows 98 works fine! So do Suse 8.1 too!
You have win98/win2k and suse on the same system? if so, do they reside on the same HD? have you defragmented both windows partitions before partitioning for suse? is it possible that the suse install has taken a chunck off the win2k swap space?
Moved: Not a Linux Success Story and certainly not geared towards a Linux question.
There have been threads regarding this problem with a small fix. Can't think of it off top of my head but a search on the forums might find your resolution as its been mentioned before. It has to do something regarding Win2k trying and detecting the Linux partition, etc as its own drive or something along those lines.
I had a similar problem not to long ago when I moved my /home to a different partition. The partition was previously formatted as fat32 and was recognized by win2k. Without thinking, I blew away the partition and formatted as ext3. When I booted back into win2k it slowed to a crawl, almost as if it was looking for that drive to be there. What I ended up doing was re-formatting it as Fat32, and then using computer management to delete the partition. This way, Win2k wont freak out when it boots up and all of a suddent the drive isn't there. I then went in and reformatted the partition as ext3 and moved my /home to it.
Of course, if you have a linux install on this partition, then fixing it as I did above might not be an option, but its the best I can do for ya.
I had the same problem on Windows 98 when I used a separate HDD for Linux. To fix it I created a 10 meg Fat32 partition on the separate drive then used the rest for linux.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.