Just wanted to ring in and say my HP pentium III 800 Mhz with 256 MB RAM..ect... WinMe runs just fine on here about 99% of the time regardless of how much crap I have running.
I also here it's not a great idea to keep switching OS's and to be careful about installing and removing certain programs. Blue screen of death comes up alot because of .dll errors missing and wrong versions installed.
Edited by - Scooter on April 28, 2001 10:16:40 PM
We are here just like this,It really doesn't matter why.The world is here like it is,'We could laugh we could cry.Is it good or is it bad,Wright or maybe wrong?There's no use of being sad,Without a purpose within a song.
I started my machine (P3 550 w/256MB and TNT2) with 98SE, and I got ME as soon as it came out. Personally, I was happy with it, until it wouldn''t let me load stuff into high memory because of a memory lockout. After talking to someone who prodded Microsoft into investigating it, I was able to get more free conventional RAM and then got everything running. I actually found a few of my DOS games that RAN under WinME that didn''t under 98SE (The REALLY old DOS games).
I never really had many problems with ME, but I dual boot with Win2k now because I can lock my computer, and it is more stable, and I can run web and ftp server stuff, which ME doesn''t support (at least through PWS). I run 2000 for pretty much everything, except for a couple games that just don''t like it, such as Recoil (never heard of it? Not surprised...).
My only major preference of 2000 over ME is the security and the built-in web services. It''s kinda fun using Movie Maker from 2000, though. Just link to it from ME and it runs perfectly.
Anyway, I prefer 2000 over ME, even though they have the same stability for me. 2000 just has a few more features. And about the reboot thing...I''ve actually experienced that before, but it was 2000 that was doing it, and I''ve had 2000 to the point that every time I went into my mixer for my SBLive! card and clicked on the recording device (or the speaker change button, for that matter) it would immediately reboot. Go figure. This time around it works perfectly. It''s only my third install on this machine. ME has never done that rebooting problem for me, though.
I''ve actually experienced that before, but it was 2000 that was doing it, and I''ve had 2000 to the point that every time I went into my mixer for my SBLive! card and clicked on the recording device (or the speaker change button, for that matter) it would immediately reboot. Go figure.
Win2K will reboot as its default action when it reaches a system hault (a crash that it intercepts, but can''t recover from). You can change the default action in the control panel under "System->Advanced->Startup and Recovery." I''ve only ever seen it do that due to a driver problem, so that''s probably what was/is causing it.
Well, finally Oni is working with zero problems-- and I have no idea why. It''s running perfectly all of a sudden, but it''s been giving me problems all week. Still, if I play it, quit and immediately shut down, the blue screen pops up again and I have to push the power button down for ten seconds to turn it off.
Also, the suspend mode is working smoothly, so what I do is just suspend the machine immediately after I quit Oni, leave it like that for a few minutes, then move the mouse and shut it down.
I guess after learning about the problems and seeing what causes and prevents them. So I just work around them. Are there honestly any fixes or something for Windows ME? Honestly.
Scenario #1 I go to START>SHUT DOWN>SHUTDOWN, and it-- gasp-- restarts!!!
I had the same problem, but --gasp-- Micro$$ realised and have fixed it. If you go to Windows Update you should be able to find the fix.
Scenario #2 I dial up on my 56K, and after a while I disconnect and shut down my computer. The screen turns blue and says "Windows Protection Error... System Halted".
Once again I had the same problem and once again --gasp-- micro$$ relised and released another fix, that can also be found on Windows Update.
Scenario #3 Oni crashes constantly. Even on my AMD Athlon 128MB-RAM with an nVidia Vanta DDR. What. The. Hell...
I aint got a clue, but you claim to have fixed this.
Scenario #4 I hit "Sleep" on my 1-touch keyboard to put the computer in Suspend mode. I move the mouse to "wake it up." Nothing happens.
This sometimes happens to me to, but if the mouse doesn''t work bashing the keyboard usually works. You''ve probably tried this but if this doesn''t work you might be able to find a fix on Windows Update. As you appear to be missing alot of the fixes from there (The first two fixes I mentioned came out within a month of Windows ME being released), that should really fix this.
Crash,
We Must Move Forwards NOT Backwards, Sideways NOT Forwards And Always Twirling Twirling Towards Success
"We Must Move Forwards NOT Backwards, Sideways NOT Forwards And Always Twirling Twirling Towards Success." - 2000"If You Keep Looking Forward Your Gonna End Up Looking Backwards At Yourself Running Sideways!" - 2001
Scenario #4 I hit "Sleep" on my 1-touch keyboard to put the computer in Suspend mode. I move the mouse to "wake it up." Nothing happens.
This sometimes happens to me to, but if the mouse doesn''t work bashing the keyboard usually works. You''ve probably tried this but if this doesn''t work you might be able to find a fix on Windows Update. As you appear to be missing alot of the fixes from there (The first two fixes I mentioned came out within a month of Windows ME being released), that should really fix this.
What I meant was suspend mode can crash Windows ME. Actually happened to me only once, so I''m weary about using it unless it solves some problems. I called up tech support at Micron (my computer''s manufacturer), and they told me this is a bug in Windows ME. If suspend mode crashes your computer, simply hold the power button on the front down for ten seconds or switch it off in the back to turn it off. Then unplug the power chord to your tower and plug it back in. Now turn the computer back on and it should run fine. If it helps, put it on Safe Mode and run Scandisk, then reboot; though I didn''t have to do that.
And I''ll check out Windows Update for this stuff. Thanks for the tip.
I''ve had zero problems with Windows ME, running an Athlon based system. Windows 98 would lock up on me and Win2k would lock up as well and even reboot itself whenever it felt like it. Since I''ve installed WinMe it''s only crashed once and that was an issue with the crappy soundcard playing to much stuff at once.
WinME is a huge improvement over Windows 98, its faster, more stable, has less 16Bit code, and boots faster The blue screens are usually from bad drivers, as is with the shutdown problem. As with all new OS''s you have to give device manufacturers time to update their drivers to suit the new OS. When I installed my GeForce256 in WinME it was slow-ish and caused graphical glitches but when the updated drivers were installed everything was fine.
Ill stick with WinME until WinXP is released. Win2000 is ok for Business purposes and its more stable though I dont like the fact that it takes ages to load and shutdown.. this can be very annoying when you are trying to crash-debug your app, lets hope MS gets things right with WinXP.