I'm getting a trap 00000006 error wile trying to install windows 2000 pro on a new machine. I have looked around on the net for solutions to the error, but have only found suggestions to repair the installation because a system file is corrupt. This cannot be, as there are no system files copied.... I have tried re seating the ram, and ran through a ram test program with no errors. It will sometimes go past this error, and start installing but then stop with a stop c0000221 unknown hard error\systemroot\system32\ntdll.dll Any help? Please!!

Ok I think I may have an Idea of Something that it may be,,,, After looking around for awhile ,,,, In Trying to install you may Have some hardware that is not entirely supported by win 2000 and the emulation drivers are the cause of the conflict Supposedly in boot up you should be able to "a fairly obscure cmd is during the promt for flppy based drivers... Press F6 screen, if you press F7, supposedly a different (more compatible) set of hardware drivers are used. Windows 2000 may be having problems with whatever mix of real and emulated hardware you have." (found this elsewhere ,,, May be out of context) So! after that ,,,, Have you tried some different bios... settings... Sometimes fiddling around with some of them may help resolve the issue,,,, Other than that ,,,, At the moment can't think of anything,,, Good Luck Huh!!! MSI 845e mb 768 mb ram and a p4 2.4n running xp ,win 2000 advanced server and win 98 SE alot to learn and I know so little !!!!

Ok, well I tried a few different bios settings, but this is i also tried a few different os's as well, windows ME, 95 etc and none of them were at all happy, so I took it back to the shop assuming it was something bad hardware wise. They changed the channel everything was plugged into on the mobo, and the cable and it's up and going now, I'm a little suspect that both the channel and cable were changed, with the guy saying it was just the cable having a pinch or somehting in it.....but because both the cable AND channel were changed at the same time.......could have been either.... But I'm holding my breath that it was just the cable, sure won't be impressed if it was the controller..... Thanks for your help, you found more than I did on the subject!