Can not boot with ECS k7s5a. :(

[dodo]

I just bought ECS k7s5a and AMD XP1800. But after I install everything I can not boot my computer. After system finished detect Win2K seems to start. But after second screen I got the error message,

STOP: 0X0000007B (..., ..., ..., ....) <- "some other address"
INACCESSIBLE_BOOT_DEVICE

Before it flash to second screen I think I saw one error message about I/O error. But it flashed too quickly I am not quite sure what exactly it said.

While I can use boot disk to boot without any problem.

After I use the installed the new board do I have to reinstall the operating system? Can I directly boot into my previously installed win2k?

The user guide also mentioned that I should not install any driver before I run their setup utility. Because my old OS already have all drivers installed. From this point of view I thought I may need to reinstall a new OS. Am I right?

One more question. If I have PC100 RAM can I set CPU to 133/133?

Thanks a lot.

dodo

 

[bowie71]

You need to do clean install, just plugging in the OS installed hardisk would give you problems here and there. There is a small number of peoples gets no problem though, but it sure is not the problem from your ECS K7S5A.


I don't think you can set your cpu/fsb setting to 133/133 if you have PC100 SDRAM. Good Luck

 

[Buz2b]

You need to reinstall the OS on your HDD. That is most likely why you are getting the errors. The drivers for the previous board are incompatible with the ECS board. Make sure to go into the BIOS and set the boot device order also. Go to this page to see what drivers you need to install. This information is part of the OC Workbench ECS Forum FAQ's. An excellent source of info on your board.
As to your question about the RAM, well, you can try it but don't hold your breath. Also you had better familiarize yourself with the procedure on resetting the CMOS on your board. If you have excellent quality RAM you have a slight chance of setting it that high successfully. Better to just spend the $$ for PC133 or DDR though.

 

[skriefal]

<< After I use the installed the new board do I have to reinstall the operating system? >>



Just do a "repair install". That'll fix everything up and get your system running, and all of your applications and settings will be preserved.

 

[dodo]

Buz2b, Thanks for the link! The guide mentioned,

"4. What drivers should I install for Windows 2000?

Install your video card drivers first, followed by the AMD AGP Patch. Then install AGP 1.07 using setup.exe or the .inf method. You also need to run SISIDE.EXE to make sure that all of the drives are in the correct DMA mode. Siside.exe does not produce any output when executed. Be aware that It's not enough to set "DMA if Available" in the device manager, you need to use the utility.

At this point if you need to, install theAudio Drivers, and/or the LAN Drivers...."

If I want to install my own sound card do I still need to install Audio Drivers? Is this driver for onboard Audio or for any Sound Card?

 

[dodo]

skriefal,

The user guide also mentioned that I should not install any driver before I run their setup utility. I think repair installation will use the old driver. Do you think that will work? Or I can apply those driver after I installed my old driver?

Thanks.

 

[Buz2b]

You do not need to install the onboard sound driver if you are going to use a sound card. In fact make sure you don't do that and have the onboard sound disabled in the BIOS.
You can try the "repair installation" method. Nothing really to lose. If it gets you "up and running" ok then you can go back and install the specific drivers that you need for Win2000. Those are separate from the "repair" of the OS. However, most likely it will not repair the installation. You really do need to do a fresh install.

 

[skriefal]

dodo, I'm not really certain what you're asking.

However, I just went through these steps a few days ago after installing a K7S5A. Did a "repair install" of Windows XP, and everything worked once again. Had to re-install all of the patches and fixes from WindowsUpdate, of course, since the "repair install" wiped them out.