Win2K + A7V's_ATA100 Installation Guide

G

Guest

Guest
Before anyone installs Win2K on A7V, copy the Promise100-ATA driver from the ASUS's Drivers CD-rom into a Floppy Disk. The files you need are the first 3 in the Promise100-ATA folder + the Win2000 folder with its 3 files inside. You need to keep the Win2000 folder intact.

Keep the HDD connection on the Promise100-ATA, you do not need to change it to the usual ATA66.

In BIOS remember to set the SCSI/RAID bootable.

Boot using the Win2K CD-rom (much faster) or make the Win2k Boot-Up disk (4 needed) [loading time very slow at 30 mins running on A7V Duron 900Mhz].

When Win2K installation CD boots, it will display a choice at the bottom of the screen asking "Press F6 to add additional SCSI/RAID IDE controller" Do it fast, or else start again if you missed the train.

So Press F6, it then asks you to press if you have additional disk or [ENTER] to skip/continue. And so you press and place the driver disk into A: and [ENTER]

After reading it will say "Win2000 Promise bla bla bla loaded"

After this, all will run smooth, when Win2K installation completes, you do not need to reinstall the Promise100 driver because it is already done.

This way you also do not need to unplug the Promise100 connection to ATA66 everytime you need to re/install Win2K

One perculiar thing I noticed on my machine. Mass Storage Device is support to use IRQ=10, WinME stated 10, but in Win2k it state IRQ=09, why? can anyone explain?

Extra advice
Remember to immediately create an "Emergency Repair Disk"
Immediately install "Recovery Console"
Read Win2k help files for instructions.

If Win2k crashes, never wants to boot up ever, clogged performace, which ever case that you need to reinstall the whole thing. NO!!! don't do it.

Restart the computer using the installation CD, select Repair Win2k installtion, select replace all files to original state.

Use either [M]anual replace to [A]ll replace, which ever you prefer.

I used the Manual replace and it tells me the exact file that was changed since original state, the folder it was in and so on.

For my case around 25 files was replaced and the entire process was around 1 min.

Win2k restarts and like new, better still all drivers are intact. It replaces all the .ini files and etc.

The only down sides are that residual files of other stuffs are still around. I also do not know if the registry is new, perhaps not.

No matter what it worked very well for me, I hope this option is available on Win9x as well.


Best regards
Fa Cheng CHIN<P ID="edit"><FONT SIZE=-1><EM>Edited by fcchin on 11/27/00 08:10 AM.</EM></FONT></P>
 
G

Guest

Guest
hi. what can i say, this post is the greatest!
i menaged to install Win2k by installing it on the ATA66, installing the Promise drivers and then switching back to ATA100.
i have just one problem:
now, the time from turning on the computer till Win2K is fully loaded is 2:10 Min (i tried it also on the ATA66 - the same time). Is it normal?? (i have A7v with T-bird 1.1Ghz).
Thanx again, hope you will reply this soon.
Jus.
 
G

Guest

Guest
Dear Jus

Glad you like the post, 2:10 Min looks like 2 hours 10 mins to me, is that right? If yes then obviously it is not normal, and I don't know how to fix it. Sorry

Perhaps if you provide more detail? if you plan to reinstall the whole thing, don't use my advice from previous post. Make sure you either format or properly delete everything that has to do with Win2k SYSTEMs

If it is just 2 mins 10 sec then it is faster than mine. Mines around 3 mins.

However, I do have a problem and can't seem to find the correct answer anywhere else.

After 3days Win2K will die and cannot be started. Repair using automatic option failed, repair using Emergnecy Disk failed. Repair using reinstallation pass, but takes long time and don't like it.

Does yours happen like this?

I have noticed it says
"Can't load c:\WINNT\SYSTEM32\config\SYSTEMced"

Now I have used my dual boot WinME to copy the entire folder in hope to replace it when it happens again.

Even if this method manage to safe it, I am still not satisfied because I want to find out the real problem.


Best regards
Fa Cheng CHIN
 
G

Guest

Guest
hi.
i meant 2 min and 10 sec, and now i see it is fast, thanx.
about your problem:
i used all of microsoft windows versions, and i learned just one thing - never upgrade a version, nor try to fix a fatal error - just reinstall the full version.
i use Hebrew Enabled versions, here it is much more buggy, so the most stable and relieble windows is by full installations.
that advise i give to you: never try to fix a fatal error.
thanx again,
Jus.
 
G

Guest

Guest
Get the latest Promise controller driver from Promise Website.
 
G

Guest

Guest
I already have the latest promise driver

Best regards
cx5
 
G

Guest

Guest
Have you disabled ByteMerge in the bios? I had the same problem until i disabled the ByteMerge in the Bios.