DriverGuide
English Português Español Deutsch Français 中国 Italiano 日本語 Translate
  




Go Back   Free Drivers Download | Request and Support Forums > Computer Hardware Forums > CPUs & Motherboards


 


  #1  
Old 03-18-2006
Jan
 
Posts: n/a
Default How backup BIOS

I downloaded ROM file for my MB, I wil try to upgrady my BIOS.
How can I backup current BIOS to have possibility return to my original BIOS if the new BIOS Vers. fail.
I have this MB BXi98-ATX: http://www.zida.com/vctboard/eng/dwnld/bios.htm

Thanks
Reply With Quote
Sponsored Links
    
  #2  
Old 03-18-2006
Unregistered
 
Posts: n/a
Default Re: How backup BIOS

This board has a AMI bios and during the flash process it will ask you if you want to save the old bios, just follow the directions!
Reply With Quote
  #3  
Old 03-18-2006
flasher
 
Posts: n/a
Thumbs up Re: How backup BIOS

most flashers have this feature.
you may trust the Uniflash from RainbowSoftware if the Amiflash supplied with the rom you downloaded isn't good enough for you..> http://www.rainbow-software.org
Reply With Quote
  #4  
Old 03-18-2006
Unregistered
 
Posts: n/a
Post Re: How backup BIOS

Quote:
Originally Posted by flasher
most flashers have this feature.
you may trust the Uniflash from RainbowSoftware if the Amiflash supplied with the rom you downloaded isn't good enough for you..> http://www.rainbow-software.org
UniFlash version 1.40 documentation
-----------------------------------
(C) 2005 Rainbow Software (Ondrej Zary)
Original version by Pascal Van Leeuwen and Galkowski Adam
" http://ping.be
UniFlash is licensed under GNU GPL v2 since UniFlash v1.4.
| Don't forget to disable "Flash write protect" - either in system BIOS or |
| using a jumper on the motherboard. |
`----------------------------------------------------------------------------'
If your chipset is marked BXCel, VXPro, TXPro or something like that, it's a
relabelled chipset (ALi, SiS or VIA) on a PC Chips board, with the exception
of VXPro-II which is Utron.
------------------------------------------

5.1 Making an emergency disk
---------------------------------------
It is always nice to have an emergency disk handy in case something goes wrong. You see, most flash BIOS's incorporate something called a 'boot block' and UNIFLASH will not normally overwrite it so it remains intact. The boot block contains just enough code to boot up your computer with basic peripheral support to enable you to flash in a working BIOS in case something went wrong. To make an emergency disk one would do the following:
-make a DOS (or Win95/Win98, NOT ANY OTHER) system disk using "format a: /S"
-copy uniflash to that disk
-copy a working bios image (preferably a backup that was made while the system was still a-ok) to the disk
-make an AUTOEXEC.BAT containing: @UNIFLASH -E <name of BIOS image file>
NOTE: Whatever you do, do *NOT* load HIMEM.SYS. The boot block lacks support routines that HIMEM.SYS requires, resulting in very nice crashes. And I know from experience ... !! In general, keep the boot disk as clean as possible, remove drvspace.bin and dblspace.bin. Make sure UNIFLASH and the BIOS image are on the disk as the boot block only supports the floppy drive, you won't be able to access any harddrive !! When you boot from this emergency disk the working BIOS image will automatically (without any intervention by you) be flashed into the flash ROM by UNIFLASH. This is very convenient as the boot block has no support for PCI or AGP video cards, so you won't be able to SEE anything in the process unless you replace your PCI videocard with an old ISA one (hint!). If you have motherboard with i815(E) chipset and you're using onboard video, it will probably not work in boot block mode (because graphics BIOS is stored in main Flash ROM chip) - try to put an AGP card in (there are no ISA slots). UNIFLASH will give you some audible feedback, though:
first short beep: UNIFLASH invoked, reading BIOS image
second short beep: done reading BIOS image, starting to flash
chime sound: done flashing, reset your system
long continuous beep: some error occured, press any key to retry operation

5.2 Command-line parameters
--------------------------------------
UNIFLASH [-H|-?|[-PCIROM [B D F]|-AMI|-ASUS|-BASE xxxxx|CTFLASH [xxx]]
[-E fname][-SAVE fname|-CHIPLIST|-FORCE xxxx][-REPAIR][-LOG][-MONO]
[-CMOSS fname][-CMOSR fname][-CMOSC]][-UNLOCK][-QUIT][-REBOOT]
-H or -? Shows this help screen
-E fname Flashes fname to Flash ROM with no prompts
-LOG Enables auto-logging to UNIFLASH.LOG
-MONO Use if you have problems with colors on monochrome monitor
-CTFLASH Flash ROM in c't Flasher 8-bit ISA card [xxx=port]
-PCIROM Flash ROM on a PCI card instead of system ROM
[BUS DEV FUN] Manually specify PCI device (decimal numbers)
-AMI, -ASUS Use AMI Flash Interface, Use Asus Flash Interface
-CHIPLIST Show list of supported flash chips with their numbers
-FORCE xxxx Force using routines for chip xxxx (4 hex digits)
-BASE xxxxx Set ROM Base to address xxxxx (at least 5 hex digits)
-REPAIR Repair erased chip ID (Winbond and SST chips)
-SAVE fname Write current bios image to file fname
-CMOSS/R fname Save/restore CMOS settings to/from file fname
-CMOSC Clears CMOS settings
-UNLOCK Unlock locked bootblocks (e.g. on W29C020)
-QUIT Quits (e.g. UNIFLASH -SAVE BACKUP.BIN -QUIT)
-REBOOT Reboot after flashing (use together with -E)
Parameters are executed in the same order as they are entered on the command line - so you can use e.g. "uniflash -cmoss cmos.bak -cmosc" to save CMOS settings to file called cmos.bak and then clear the CMOS.
Some parameters can't be used together - e.g. -AMI can't be used with -PCIROM.
-E: Flashes BIOS image from file fname including bootblock without any user input
-LOG: Enables logging of all important events into file UNIFLASH.LOG. Use this
when you are sending bug reports and attach this file. -CTFLASH: Selects ROM on c't Flasher 8-bit ISA card. This card supports Flash ROMs up to 512KB. Port is autodetected or can be specified manually as optional parameter (hex 200-3FC).
-PCIROM: Selects ROM on a PCI device instead of system ROM. Works only with some cards. You can optionally specify the device you want to use.
(e.g. -PCIROM 0 3 1 = BUS 0, DEVICE 3, FUNCTION 1)
-AMI: Uses interface supported by some AMI BIOSes instead of detecting the
chipset and writing to chipset registers to disable write protection. (I haven't seen this working anywhere yet...)
-ASUS: Uses interface supported by newer Asus BIOSes. This one really works
(tested on A7V133-C, A7V266 and A7V8X-X)
-CHIPLIST: Displays a list of supported chips with their IDs which are needed
for use with -FORCE parameter.
-FORCE: Disable Flash ROM autodetection and set chip type to the one specified by following ID (4 hex digits) - see -CHIPLIST parameter.
-BASE: Set ROM base address manually and allow running without PCI bus.
Useful for memory-mapped flash programming cards with old systems.
-REPAIR: ID on some Winbond and SST chips can be changed which can cause the chip not being recognized by any software (including BIOS - AMI BIOS does not work in that chip, Award BIOS displays Unknown Flash Type). This option can change the ID on these chips. Because UniFlash does not know the correct ID, you must specify it using -FORCE parameter.
-SAVE: Save current BIOS to file fname.
-CMOSS: Save current CMOS settings to file fname. CMOS memory size is detected automatically.
-CMOSR: Restore CMOS settings from file fname. CMOS memory size is detected automatically.
-CMOSC: Clear CMOS memory.
-UNLOCK: Bootblock lock can be disabled on some chips (tested on W29C020) by using this parameter.
Ondrej Zary (Rainbow Software) - Continues to develop this program after the
authors stopped the development. Done all that is new after v1.17b.
Added tons of Flash ROMs and chipsets, fixed a lot of bugs, got datasheets
from ALi.
You can contact me (Rainbow Software) by:
web : http://www.uniflash.org - UniFlash ONLY
web : http://www.rainbow-software.org
(new versions should be at all the addresses above)
e-mail : noemailaddysallowed@dot.com
When sending reports that something doesn't work, always send the log file!
9.0 Revision history
-------------------------------
1.40 -changed license to GNU GPL v2
Note: [-ASUS] means that Asus flash interface (-ASUS parameter) must be used UniFlash does NOT work on boards made by Intel. They use custom BIOS write protection and have soldered Flash ROM chips (often in TSOP package) - so there's nothing to hot-flash. They have recovery mode (activated by jumper) in case something goes wrong with the BIOS.

Last edited by Jerry K : 03-19-2006 at 08:55 PM.
Reply With Quote
Reply [Upload Driver/Firmware]



Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
BIOS Upgrade.. Helpme!! NewMan CPUs & Motherboards 4 04-04-2008 04:11 AM
Wanting to Upgrade My BIOS Unregistered CPUs & Motherboards 3 01-06-2006 07:13 PM
MANUAL for the following:MB694 ver 1.01 socket PGA370 ODDBALL9237 CPUs & Motherboards 4 11-06-2005 11:31 PM
Award bios update rahul CPUs & Motherboards 3 05-30-2004 04:20 PM
Description of Seven Major BIOS Limitations: Peter Storage Devices (Hard drives, tapes, ...) 1 05-02-2004 12:25 PM


All times are GMT. The time now is 01:20 PM.



Powered by vBulletin Version 3.0.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.

2013 DriverGuide is an iCentric Corporation Company.     All rights reserved.