• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2k problems/questions...Win2k gurus please take a look.

M

moocat

Platinum Member
Win2k keeps finding problems with whatever zip disk I have inserted each time it boots. I know the simple solution is to just not have the disk in the drive at boot time but there must be a way to keep windows from checking it.

Also, any idea why all my IDE devices (Kenwood 42x cdrom, Yam 8x8x24 cdrw, Zip100, and 30gb ata66 HD) are showing up as SCSI devices?

I have looked for information pertaining to these issues on Win2k sites but haven't found anything yet. This stuff is driving me nuts and I would really appreciate any help that I can get with this. I've installed and used Win2k on a couple other systems and didn't come even close to having these types of difficulties. I would just go back to '98 but the person I'm putting this together for is insistent on 2000.

ADDED...

YET more problems. For god sake...someone throw me a lifeline. This is the single most frustrating install I've ever done. I'm almost ready to just part this system out and be finished with it. I think I finally see why some builder have such a strong anti VIA bias. I installed the aux usb ports this morning (I was waiting for Antec to send me the correct ext cable). I plugged it all up and enabled USB in bios then rebooted. I get the following error about a missing or corrupt file < /WINNT/SYSTEM32/CONFIG/SYSTEMced >

I try to repair it using the cd I installed from (as is suggested by the text message displayed with the error) but it doesn't allow me to do the repair and insists I have a Win2k repair diskette (which I foolishly don't have).



system:

TBird 1.4ghz
Iwill KK266-R kt133a chipset (not using raid but drivers were loaded during install)
Win2k Pro (sp2, compatibility patch, dx8.1, 4in1s, via ide tool)
384mb ram
V3 2k in pci 1
linksys lne100 in pci 3
onboard audio


 
added a question and some sys info. Here's hopin' someone will spare my sanity and answer these questions.
 
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! 🙂
 
Screw it 🙂 I'm back to Win98 for this system. 2K and VIA 133A is apparently not a good combo. I don't know...I just don't have time to mess with this any longer. Thanks to anyone who looked in on this thread.
 
moocat, 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, and here, too.
 
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.
 
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?
 
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....
 
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.



 
You must log in or register to reply here.

TRENDING THREADS

Back
Top