Windows 2000 on MX7515 models

Hi. I have the Gateway MX7515 and i have tried over and over again to get my Windows 2000 installation to work on it. Its driving me CRAZY!!!!!! see what happens is when i start the computer up and choose windows 2000 from the boot menu it loads into the windows 2000 splash screen. the progress bar loads to the top and the splash screen disappears like its supposed to and then once the backlight goes off and comes on again which is when you should see the cursor and background for the desktop all i see is black, nothing. it works fine on VGA mode and in safe mode as well. I have yet to encounter one person with this problem and i have asked around to see if anyone has loaded Win2K on ther MX7515 system but noone ever responds. Please someone tell me you have Windows 2000 running on your MX7515 system properly so i know its possible. I have SP4 installed as well as the rollup 1. I have tried default drivers, Omega drivers, and even just installing random drivers with no change. some people tell me it might work if i hit fn and F4 but that never works and neither does chaning the backlight. It has to be drivers or software errors but im not sure what they might be.


What im looking for is someone out there that has the Gateway MX7515 and has successfully installed windows 2000 SP4 onto their MX7515 system and is able to use it with full video accelaration. thanks

 

and why would anyone want to put 2000 on there when the big thing it 64-bit windows? just wondering

 

Why does everyone think we all want to run 64-bit windows? An OS that's not finalized and many drivers/applications have issues running on? Perhaps some of us would like to use a more stable OS, like 2000. Granted, XP is generally on an equal footing now, but there are applications that run better on Win2K than XP, so it's not unheard of for me.

As someone who was on a beta team for Win2K many years ago and ran various versions up until 18 months ago(when I finally switched to XP), I certainly understand why many people still prefer Win2K over XP in some circumstances.

 

first of all i have x64 loaded on my computer (with no sound, seeing posts everywhere about work arounds with dead links to drivers). for one reason its GUI reminds me of my days playing around in the DLL hell of windows ME and second its not a resource hog like xp pro is. It may be an older operating system, but it is very reliable and is compatible with most of todays games, applications, and other software. I've used windows 2000 for a long time and just got this system like a month ago. For this month i have tried nearly every day in some way to fix this problem, searching the internet, guess and checking drivers, disabling and enabling hardware, and even reinstalling the whole OS twice without change. If i don't run windows 2000 for any of these reasons above, i will fix it for all the time ive wasted just trying to get it to work. I've got nothing against x64 and am looking forward to it when it has been updated and all the bugs and drivers are fixed, but right now i want 2000

and for the recent post, thank you for understanding why i want to load windows 2000. Do you have it on an MX7515 notebook? I'm actually beginning to wonder if its not my particular system this problem is isolated to. i mean after searching for weeks for anyone who has had this problem on and MX7515 and turning up absolutly no results, its a little strange and of course frustrating

In fact i have like 30 favorites sites dedicated to forums where i have asked this same question. I've gotten about 3 responses to this question and none of these three have 2000 loaded onto an MX7515

 

I don't have an MX7515(I have an 8510GZ and haven't even bothered to do a clean install of XP yet, still running the machine as it was new, just cleaned some stuff off).

My guess would lean towards chipset drivers being the culprit. Win2K is very particular about that and does not have the same detection routines that XP has. There's so many manual driver installs that are necessary on Win2K installs with some components that I wouldn't be surprised if that's where the problem lies.

 

So.... thats what everyone else is doing with the 64 bit stuff... "beta" testing it.

 

Yes. But I was also not dependant on my machine when I was testing Win2K. If someone is utilizing a machine they need to keep working, they'll prefer something with a more stable history. It's all a matter of priorities.

Plus, I know a number of companies who still use Win2K because it's working and they don't see hte point in inviting trouble by upgrading software just for upgrading's sake. So many people I've met still run Win2K cause they like to keep their personal computer compatible(in all ways) with their work setup, in the instance that they need to use their personal computer for work related tasks.

 

I'm also having the same problem with a Gateway 7527 that after the splash logo of windows the screen goes black. Did you ever get a solution for this problem. I also need to use my Win2k Server OS.