Soltek SL-63AV+ Problem

Hot-swapping and Boot-Block flash & Boot block flash and floppy support
Post Reply
New visitors - please read the rules.
Posts: 12
Joined: Mon Dec 23, 2002 9:00 am
Location: UKRAINE

Today I try to update BIOS in the Soltek SL-63AV+ mobo:
date: 11/23/1999
version: 02.10
OEM: Soltek
Chip: SST 39SF020 /5V.
Utility: AwardFlash 7.88 (Awdfl788.exe).
New Bios: 63av+-e5.bin.

This utility made well old copy. Then I try to restore BIOS from this old copy (well done too). However when I try to upgrade the new BIOS PC stop runnidg at half time programming. Now my PC is dead! The floppy drive don't work too. No POST bipping too.
I use the following autoexec.bat at second case:
@echo off
if exist oldbios.bin goto old
awdfl788.exe newbios.bin oldbios.bin /py/sy/cc/cp/cd/sb/r
goto end
awdfl788.exe oldbios.bin /py/sn/cc/cp/cd/sb/r
Where is my fault? I didn't change the boot block, however PC don't booting at all. CPU fan is running, so supply source is good?
The UniFlasher
Posts: 3122
Joined: Wed Mar 20, 2002 4:16 pm
Location: Slovakia

Awdflash crashes sometimes...
Try using the hot-flash method to restore your BIOS.
Patched and tested BIOSes are at
UniFlash - Flash anything anywhere
New visitors - please read the rules.
Posts: 12
Joined: Mon Dec 23, 2002 9:00 am
Location: UKRAINE

I know the similar method, which used the soldering process for BIOS chips (Russian site). However I don't know which pins should be activated?
#31 (WE#), #24 (OE#) or #22 (CE#). Note that in that case we insert BOTH good (old) and bad (new) BIOS chips in the same soket at the same time.
New visitors - please read the rules.
Posts: 8
Joined: Sat Nov 23, 2002 6:01 pm

If the following doesn't help give the folks at a try....they're very helpful.

A. Lots of things go wrong with bios upgrades:

1. The exact right file must be used. Most often the wrong file was used for the upgrade. Being off by a single revision is often enough to kill the board. If the flash seemed to go perfectly but try as you might the board remains dead, suspect having used the wrong file.

2. Sometimes all you need to do is clear the CMOS and then go into SETUP and set things back they way they should be. You clear the CMOS by using the appropriate jumper or shorting points on the motherboard. This is usually called CL CMOS or CLRTC. The jumper is used with power removed or the shorting points are shorted with a wired or screwdriver. If you can't find either of these then remove power, remove the CMOS battery. Short the terminals that the battery plugs into on the motherboard, and replace the battery.

3. Many Upgrades will require the use of a "smart fan" plugged into the right header on the motherboard. Modern CPU's can overheat and burn out in under 5 seconds. To protect them they put protection into the bios requiring you to have the fan spinning at 2000RPM in under 5 seconds or the board will power down. If you power up the board and it turns back off after about 5 seconds, suspect this problem.

4. You flashed in a Window or over the internet. This is computer Russian Roulette. It is only safe to flash from a bootable floppy with no drivers, autoexec.bat, and no config.sys. Even this is not risk free. You should ALWAYS save the old file to floppy.

5. You have a defective chip. You can just about bet on it if you peel back the sticker on your chip and find it is made by MX or ASD or marked with an H.T and then a string of numbers. Only about 1 out of 10 of these chips will take a reflash due to their poor quality. It is the failure of this chip that likely caused your flash to fail, unless you know you used the wrong file. If the flash utility properly detected your BIOS chip and gave you a verification error or a write error part way through it is very likely your chip is bad. If your flash utility can not identify the chip, suspect the chip is bad. If your flash went normally, gave no errors, but your machine no longer works, suspect a wrong or corrupted file.

6. Your flash utility is too old or too new for your board. New chips and chipsets are added all the time to flash utilities. They are also removed. You may need and older or a newer flash utility than the one you have.


Q. I flashed with the wrong file. Is there any way to recover?

A. If your floppy drive seeks on power up and then stops after a short period of time, you may have a chance to recover. The following information was obtained from Wim's Bios FAQ's. Corrections on AWARD Bios by Terry McGuire.

Award: The boot-block BIOS will execute an AUTOEXEC.BAT file on a bootable diskette. Copy an Award flasher & the correct BIOS *.bin file on the floppy and execute it automatically by putting AWDFLASH *.bin /sn /py /cc /r in the AUTOEXEC.BAT file. The * would be the correct bios .bin file and there must be spaces between the slash marks. Put it in the floppy and turn on the computer when the floppy seeks it will load the correct bios and reboot by itself. When it finishes you have to remove the floppy and enter the cmos SETUP and modify the CMOS for your configuration.

AMI: The AMI boot-block BIOS will look for a AMIBOOT.ROM file on a diskette. Copy and rename the correct BIOS file on the floppy and power up the PC. The floppy doesn't need to be bootable. You will see the PC read the floppy, after about 4 minutes you will hear 4 beeps, this means the transfer is done.

Kill Power to the PC. Clear the CMOS or RTC. Reboot the PC and modify the CMOS for your configuration.

New visitors - please read the rules.
Posts: 12
Joined: Mon Dec 23, 2002 9:00 am
Location: UKRAINE

The Problem is solved!
First I restore the crush process:
1. I copied the new BIOS image on the floppy with BAD sector within this file! The floppy should be scandisk'ed before programming!
2. So during programming the floppy drive couldn't read this sector and crushes!
3. UPS was loaded with 3 mashines and beeing overloaded crushes too!
Now I restore my BIOS with new update and my mobo has better memory access.

Happy New Year to all!
Post Reply