Best Answer: it is not the bios that's causing the problems it is the systems hardware drivers. you need to install.
any way you need to go to Gateways customer service website and download the drivers and if need be the bios updates at the same time click on the link below where you will find what your looking for
windows 2K is well out of date and is not being supported any more by MS,
you could move up in the world and come into the year 2009 by installing any version of Linux which puts windows in the shade for security and speed
Linux is free to download and use with all the software you will ever need also free
Re:If the system had been behaving properly I probably wouldn't have given the fact that all IDE devices were being reported as SCSI a second thought…but since the install has been problematic from the very beginning it makes sense to take note of any abnormalities. I'm sure this is not just a KT133A problem, but more a combination of the VIA chipset, the ATAPI Zip100 (there is a known IDe performance issue), and the AMI raid controller. I did the install 6 times. I guess I could have missed some step along the way but at this point I doubt it.
By the way, I don't know what "problem" win2k found on my zip disk. What I know is that until I let it complete a scan it nagged me about it every time I booted. It wouldn't have been a big deal but the dang scan took forever (because of the zip100/via problem?). I eventually allowed it to complete the scan and then it stopped bugging me about it. No big deal really, just another Windows annoyance. I just assumed there would have been a way to tell it to ignore that drive since it was a removable, non-bootable disk.
I appreciate all the input but I've kinda put this install behind me. I had win98 up and running in an hour or so…no problems at all. I would have rather run 2k but since this system is getting sold I needed to be very confident in it's stablity.
I forgot to mention one other problem; Nero 5.0 refusing to do a burn due to SCSI errors.
Since getting Win98 up and running I've been doing some testing with Sandra and the Simmtester ram diag loops. I haven't found any problems with my ram or cpu. I thought when I got the missing or corrupt file error that I might have had a flakey stick of ram…not so though.
Re:are your drives performing badly? if not, then quit worrying about the scsi thing, if you're using an extra IDE controller like a promise or something, that is probably the reason. and even if you're not, if its not affecting anything then why worry so much about it?
what "problems" is windows "finding" with your zip disk?
and as for a repair of win2k…booting from the cd and hitting "R" when prompted should work fine….
Re:I am using win2000 with via kt133A, (Epox 8kta3) and I have no problems. Using sb pci128, old nasty vid card (TNT2 16mb), 30gb HDD, ide 4X4X32 cdrw, 50x cd, 512MB Corsair ram. Did I just get lucky or what?
Re:I did the routine described on the MS site but then the system would freeze at the splash screen. It just wouldn't boot. I have win98 installed and running already. I'm sure it's something about my particular configuration of hardware. Thanks again.
Re:guy, that system.ced error is a real dog! I've been hit with it no less than four times! As a result I have had to become somewhat well versed in it. Here are a few links which might help:
from MS (http://support.microsoft.com/default.aspx?scid=kb;EN-US;q269075), and here, too. (http://www.helpfromtechs.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=4&t=000208&p=)
Re:Screw it
Re:Missing or corrupt systemced usually means filesystem corruption. Search the KB and you'll get answers to that.
What kinds of problems does W2K find with your ZIP disk? Are you talking about chkdsk? Sounds like there's something wrong with your hardware if this happens every boot.
As for the IDE devices showing as SCSI devices, you got me. I dunno! ![]()
Re:added a question and some sys info. Here's hopin' someone will spare my sanity and answer these questions.
0 Comments.