can't winflash k7vza36a bios to detect 120G harddisk

running xp pro, already have a 30G drive.
current k7vza bios is ver 3.2 3/14/2001
it detects my 120G maxtor as a 33.8G drive.

which bios version should I get?

I saw 3.6a "support to 137G HD", intuitively, I
went to elitegroup website & downloaded winflash & vza36a.bin
once I entered the bin file in winflash, it says bios id error.

also tried flashv73 from a floppy, after entering the bin file,
monitor would get random flashes of '_' continuously. Another thing
is the utility displayed Flash Type -
I had to turn off my computer.

also tried awd822a, but it didn't support XP.

What should I do from here?

Thanks and much appreciated.

"ETSUN" <> wrote in message
news: om...
> running xp pro, already have a 30G drive.
> current k7vza bios is ver 3.2 3/14/2001
> it detects my 120G maxtor as a 33.8G drive.
>
> which bios version should I get?
>
> I saw 3.6a "support to 137G HD", intuitively, I
> went to elitegroup website & downloaded winflash & vza36a.bin
> once I entered the bin file in winflash, it says bios id error.
>
> also tried flashv73 from a floppy, after entering the bin file,
> monitor would get random flashes of '_' continuously. Another thing
> is the utility displayed Flash Type -
> I had to turn off my computer.
>
> also tried awd822a, but it didn't support XP.
>
> What should I do from here?
>
> Thanks and much appreciated.

You need something like a windows 98 boot floppy, containing just the files
command.com and io.sys. Copy the BIOS file and the flash utility to the
floppy and boot from it. At the command prompt use the following syntax
a:\awd822a vza36a.bin.

Incidentally, you may prefer to use the latest BIOS which is ver. 3.7.

guess what, I pulled the cylinder limitation jumper out from the harddrive
and my version 3.2 bios was able to auto detect 122.9GB.
I'm happy now.

before pulling out the jumper, I tried setting cylinder 1024, heads 16,
sector 63, as the harddrive manual suggested, but that only added up to be
528MB. I was only able to set these values in Manual-CHS mode,
other modes such as Manul-LBA/Large didn't let me change those values.
no idea why this was the case.

bottomline is bios ver 3.2 can support 120G byte harddrive, just
pull that stupid cylinder limitation jumper out.

Thanks.

"Mr. Slow" <> wrote in message news:<bu399h$5g7$>...
> "ETSUN" <> wrote in message
> news: om...
> > running xp pro, already have a 30G drive.
> > current k7vza bios is ver 3.2 3/14/2001
> > it detects my 120G maxtor as a 33.8G drive.
> >
> > which bios version should I get?
> >
> > I saw 3.6a "support to 137G HD", intuitively, I
> > went to elitegroup website & downloaded winflash & vza36a.bin
> > once I entered the bin file in winflash, it says bios id error.
> >
> > also tried flashv73 from a floppy, after entering the bin file,
> > monitor would get random flashes of '_' continuously. Another thing
> > is the utility displayed Flash Type -
> > I had to turn off my computer.
> >
> > also tried awd822a, but it didn't support XP.
> >
> > What should I do from here?
> >
> > Thanks and much appreciated.
>
> You need something like a windows 98 boot floppy, containing just the files
> command.com and io.sys. Copy the BIOS file and the flash utility to the
> floppy and boot from it. At the command prompt use the following syntax
> a:\awd822a vza36a.bin.
>
> Incidentally, you may prefer to use the latest BIOS which is ver. 3.7.

see www.bootdisk.com



On 13 Jan 2004 09:55:51 -0800, (ETSUN) wrote:

>running xp pro, already have a 30G drive.
>current k7vza bios is ver 3.2 3/14/2001
>it detects my 120G maxtor as a 33.8G drive.
>
>which bios version should I get?
>
>I saw 3.6a "support to 137G HD", intuitively, I
>went to elitegroup website & downloaded winflash & vza36a.bin
>once I entered the bin file in winflash, it says bios id error.
>
>also tried flashv73 from a floppy, after entering the bin file,
>monitor would get random flashes of '_' continuously. Another thing
>is the utility displayed Flash Type -
>I had to turn off my computer.
>
>also tried awd822a, but it didn't support XP.
>
>What should I do from here?
>
>Thanks and much appreciated.