Q about PC Bios flashing
Posted: 14 Nov 2011 12:48
Hello, can anyone put me back on track,I am new to Promming.
My PC Bios is shot and with an S4 I need to reload the flash data file. The Dataman library for the Bios chip: V29C5100T has been loaded and from a PC the Bios image file: A7V8xx3.awd , an award bios update size: 256K (262,144bytes) has been uploaded at 00000,3FFFF.
When I burn the eeprom, a failure message occures indicating the address and that the ROM/RAM contents are not consistent. Originally I thought I was using the incorrect file format so I changed from ASCII to Binary, I then tried with remaining formats.
When I used a hex editor and checked the file contents on the PC and then compared sections in the RAM i.e DU 01000,f0 I noticed that some addresses had other values than what was shown in the Hex editor, these were the values that changed when in the Hex editor I toggled between ANSI <-> OEM (Windows <-> Dos char. set).
One question I have since I've gone through the file format collection (Intel,Tex, Motarola, Ascii & bin) and not been able to burn the eeprom are there other file formats which are not supported by the S4? since I do not image this to be the case, this brings me to the orriginal call, can anybody tell me what mistake I am making?
My PC Bios is shot and with an S4 I need to reload the flash data file. The Dataman library for the Bios chip: V29C5100T has been loaded and from a PC the Bios image file: A7V8xx3.awd , an award bios update size: 256K (262,144bytes) has been uploaded at 00000,3FFFF.
When I burn the eeprom, a failure message occures indicating the address and that the ROM/RAM contents are not consistent. Originally I thought I was using the incorrect file format so I changed from ASCII to Binary, I then tried with remaining formats.
When I used a hex editor and checked the file contents on the PC and then compared sections in the RAM i.e DU 01000,f0 I noticed that some addresses had other values than what was shown in the Hex editor, these were the values that changed when in the Hex editor I toggled between ANSI <-> OEM (Windows <-> Dos char. set).
One question I have since I've gone through the file format collection (Intel,Tex, Motarola, Ascii & bin) and not been able to burn the eeprom are there other file formats which are not supported by the S4? since I do not image this to be the case, this brings me to the orriginal call, can anybody tell me what mistake I am making?