ASUS A7V266E Users, Need your Help Please.

[Nebakanezzar]

hey all,

Hmm..seems the cause my be my memory, motherboard or Bios settings(see below). since i am able to install winme with np in a non RAID setup, i dont think it would be the memory. so maybe a bios setting or maybe i need to upgrade the promise bios? So all you A7V266e users that have a RAID array..could you tell me if you changed any settingsd in your bios when installing win. Does anyone know if there is a updated bios for the onboard promise card?


Edit: I have been having a hard time installing Win ME on a RAID Array with the ASUS A7V266E. im using Win ME cuz i dont got WIN98SE. its not the HD as i first suspected. I fixed the drive using the IBM utility. resetup the raid array and got the same error when installing winme "suwin.exe at 000C:195A" so i set it up non-raid and installed win with np..so its not the drive or the win disk so maybe the mobo?
End Edit

what a frigin pain in the booty! ok, so i got my new stuff (a7v266e, amd xp1600, ibm 60gxp 20gig) and i wanted to set it up in a raid array using my new 20gig gxp and my old 20gig gxp. i read the instructions and didnt see anything about having to format or fdisk my old hd..so i didnt. was that my 1st mistake? setup the raid array, np. booted up, fdisk'd the array 1 10gig 2 15gig partitions,np. formated the 10gig partition and went to load winme. scan disk was fine started to load windows and got a error "suwin.exe" i think it was. so not knowing what the problem was, i spent several hours trouble shooting..finaly found out the old hd wasnt working. if it was hooked up i couldnt even bootup with a boot didk to try to fdisk it. i finaly managed to bootup puting the old drive as a slave and the new one master. when i try to fdisk it..it says drive not accessable (old drive..new drive np)..it shows as a 20 gig drive with 1 10 gig partition. i was able to formate the 10gig partition..didnt help any.

is there anyway to fix my HD?

thanx for help

 

[Nebakanezzar]

Anyone have any Ideas?

 

[BrunoPuntzJones]

im sure you've done this, but just to make sure. rip everything out hd/cable wise
put the bad hd as master on IDE primary (not the raid)
boot with a floppy and try fdisking the drive like that

and from what i read you have done that already. have you tried running any diagnostics programs on the drive? cant think of the names off-hand but i know IBM has one and Maxtor has one. may give those a shot.

 

[Muadib]

It's been a while, but I'm pretty sure both HD on my array had to be set for master. I'm using a promise controller though, and I don't know what I did with the instuctions, so I can't check.

 

[Nebakanezzar]

Yeah, i tried diff cables tried both ide and the promise controllers...i am able to see the drive by putting it as a slave and the good drive as master. but when i try to FDISK it says cant access the drive. ill have to try those diagnostics programs..i assume i can find them on IBM's website? i am able to format a 10gig portion of the drive from a a: prompt...but their isnt another 10gig drive...and after i formated that, i still couldnt get access to the drive from FDISK. this seems REALY wierd to me! when i setup the array i had each drive on sep controllers both as masters..it was all going fine till i tried to install windows..but its not the windows disk cuz i can install it on the lone good drive.

any ideas?

GO DUCKS!

 

[Nebakanezzar]

WTF? i downloaded a IBM diagnostic utility and there were no problems. yet i bootup with a win98 boot disk and run FDISK and i cant access that drive still!! anyone know why that would happen?

 

[Nebakanezzar]

so here is a update: fixed the drive using the IBM utility. resetup the raid array and got the same error when installing winme "suwin.exe at 000C:195A" so i set it up non-raid and installed win with np..so its not the drive or the win disk so maybe the mobo?

 

[Jiggz]

In my experience, everytime there are unformatted section on the HD there always seems a problem arising from it. If you want to try to setup the raid again you need to fdisk each individual hdd and then set up an array. Fdisk again as a raid setup and then format all the partitions. If the same problem exists, you may have to copy the WinMe installation files on the HDD and do the setup from there. You can also check this link for other ideas. WinMe

 

[Nebakanezzar]

found this on the MS web site:

SYMPTOMS
When you try to install Windows 95 or Windows 98 in a new folder or a clean hard disk, you may receive one or more of the following error messages:

SUWIN
An error has occurred in your application. If you choose ignore you should save your work in a new file. If you choose close, your application will terminate. -This is my Problem!

CAUSE
This behavior can occur when any of the following conditions exist:

There are incorrect basic input/output system (BIOS) settings for a built-in peripheral device on your motherboard (for example, cache settings, CPU timing, hard disks, and so on).

Your computer has bad or mismatched random access memory (RAM) or cache (for example, if you are using EDO and non-EDO RAM, or you are using different RAM speeds).

The motherboard in your computer is not working properly.

RESOLUTION
To work around this behavior, try to slow down your computer by changing the BIOS settings. For information about how to change these settings, consult the documentation that came with your computer or contact the hardware manufacturer.

Modify the bus mastering setting.

Modify the externalor internal cache setting.

Modify your RAM setting.

Modify other settings that are specific to your BIOS and that contribute to the speed at which your computer runs.

Disable the Level 1 and Level 2 cache from the BIOS Setup tool for the duration of Setup.

Disable the Ultra DMA setting (if applicable) for the hard disk or CD-ROM drive. For information about how to change these settings, consult the documentation that is included with your computer.

If the error message still occurs after you perform these steps, the hardware may be damaged. Contact your hardware manufacturer for assistance.