PC Hoarder Patrol wrote on 2022-03-29, 08:14:

vic_e21 wrote on 2022-03-28, 20:02:

Unfortunaly, same error with this image bios, i think the promblem is in the bios what actualy on the mobo. Because on last week […]
Show full quote

Repo Man11 wrote on 2022-03-28, 04:54:

I found a live link; though there's no guarantee that this isn't the same as you already have, it's worth a try.

Unfortunaly, same error with this image bios, i think the promblem is in the bios what actualy on the mobo. Because on last week i update bios on my everyday rig motherboard, and have simillar issue - Gigabyte on B550 chipset, and mobo been have a custom bios, and motherboard don't wanna been upgrade on the new official bios, until i don't use a custom flasher . Maybe a same problem here.

Anyway the images of the motherboard, and jumpers (careful, general photo of the motherboard is a big - around 18 megs)

The latest pics seem to confirm that it's not an OEM board after all, but an Intel retail version and from the later production runs based on the AA678039-104 / 4L3TT0X0.86A.0007.P03 basic ID info, so the Gateway BIOS file (7502875.exe) linked above isn't really appropriate for this board.

One point of confusion is that in your original post you have a pic showing the flash utility as release 2.6, but as far as I can see the latest versions (certainly the ltbio10.exe linked above by @Repo Man11 are using release 3.1) - where does your release version come from?

New day, new question.

😀

Do you flash from HDD or from FDD? Did you try flash from floppy in recovery mode with recovery jumper enable?

Babasha wrote on 2022-03-29, 19:53:

Do you flash from HDD or from FDD? Did you try flash from floppy in recovery mode with recovery jumper enable?

This time i try flash from HDD, do you think to need flash from Floppy? I try. About recovery mode - if i put jumper in this mode, PC loading but without any image on the display, just a black screen, but keyboard leds are react, i mean capslock, numlock. Maybe this is a some issue in S3 videocard in this case?

vic_e21 wrote on 2022-03-29, 20:05:

Babasha wrote on 2022-03-29, 19:53:

Do you flash from HDD or from FDD? Did you try flash from floppy in recovery mode with recovery jumper enable?

This time i try flash from HDD, do you think to need flash from Floppy? I try. About recovery mode - if i put jumper in this mode, PC loading but without any image on the display, just a black screen, but keyboard leds are react, i mean capslock, numlock. Maybe this is a some issue in S3 videocard in this case?

FDD is the best way!
In recovery mode there no image on screen only sounds of floppy and pc-speaker beeps (it may take up to 5-7 minutes to complete recovery, dont worry just wait).
Do not forget to reset ESCD by jumper after BIOS update. And install this and other jumpers to default position!

https://web.archive.org/web/20040216010452/ht … TX/lt_confg.htm

vic_e21 wrote on 2022-03-29, 19:43:

New day, new question. […]
Show full quote

PC Hoarder Patrol wrote on 2022-03-29, 08:14:

vic_e21 wrote on 2022-03-28, 20:02:

Unfortunaly, same error with this image bios, i think the promblem is in the bios what actualy on the mobo. Because on last week […]
Show full quote

Unfortunaly, same error with this image bios, i think the promblem is in the bios what actualy on the mobo. Because on last week i update bios on my everyday rig motherboard, and have simillar issue - Gigabyte on B550 chipset, and mobo been have a custom bios, and motherboard don't wanna been upgrade on the new official bios, until i don't use a custom flasher . Maybe a same problem here.

Anyway the images of the motherboard, and jumpers (careful, general photo of the motherboard is a big - around 18 megs)

The latest pics seem to confirm that it's not an OEM board after all, but an Intel retail version and from the later production runs based on the AA678039-104 / 4L3TT0X0.86A.0007.P03 basic ID info, so the Gateway BIOS file (7502875.exe) linked above isn't really appropriate for this board.

One point of confusion is that in your original post you have a pic showing the flash utility as release 2.6, but as far as I can see the latest versions (certainly the ltbio10.exe linked above by @Repo Man11 are using release 3.1) - where does your release version come from?

New day, new question.

😀

Isn't that an error you get when trying a standard cross-flash between an Intel retail BIOS (ID string 4L3TT0X0.86A) and an Intel OEM BIOS (ID String 4L3TT0X0.15A for Gateway say!) - is that what you were trying?

PC Hoarder Patrol wrote on 2022-03-30, 06:17:

vic_e21 wrote on 2022-03-29, 19:43:

New day, new question. […]
Show full quote

PC Hoarder Patrol wrote on 2022-03-29, 08:14:

The latest pics seem to confirm that it's not an OEM board after all, but an Intel retail version and from the later production runs based on the AA678039-104 / 4L3TT0X0.86A.0007.P03 basic ID info, so the Gateway BIOS file (7502875.exe) linked above isn't really appropriate for this board.

One point of confusion is that in your original post you have a pic showing the flash utility as release 2.6, but as far as I can see the latest versions (certainly the ltbio10.exe linked above by @Repo Man11 are using release 3.1) - where does your release version come from?

New day, new question.

😀

Isn't that an error you get when trying a standard cross-flash between an Intel retail BIOS (ID string 4L3TT0X0.86A) and an Intel OEM BIOS (ID String 4L3TT0X0.15A for Gateway say!) - is that what you were trying?

No, he try to flash original Intel BIOS. It looks like best way to create DOS boot disk and flash from floppy or recovery in blind mode using BIOS boot block.

Babasha wrote on 2022-03-30, 06:37:

PC Hoarder Patrol wrote on 2022-03-30, 06:17:

vic_e21 wrote on 2022-03-29, 19:43:

New day, new question. […]
Show full quote

New day, new question.

😀

Isn't that an error you get when trying a standard cross-flash between an Intel retail BIOS (ID string 4L3TT0X0.86A) and an Intel OEM BIOS (ID String 4L3TT0X0.15A for Gateway say!) - is that what you were trying?

No, he try to flash original Intel BIOS. It looks like best way to create DOS boot disk and flash from floppy or recovery in blind mode using BIOS boot block.

You mean i can write a bios image on floppy, and load with this floopy in recover mode? Or i misunderstanding?

vic_e21 wrote on 2022-03-30, 10:01:

Babasha wrote on 2022-03-30, 06:37:

PC Hoarder Patrol wrote on 2022-03-30, 06:17:

Isn't that an error you get when trying a standard cross-flash between an Intel retail BIOS (ID string 4L3TT0X0.86A) and an Intel OEM BIOS (ID String 4L3TT0X0.15A for Gateway say!) - is that what you were trying?

No, he try to flash original Intel BIOS. It looks like best way to create DOS boot disk and flash from floppy or recovery in blind mode using BIOS boot block.

You mean i can write a bios image on floppy, and load with this floopy in recover mode? Or i misunderstanding?

There should be instruction in txt file. As I remember:
1) Format floppy - format a:
2) Make it bootable - sys a:
3) Copy content of BIOS and utilities (all files) to root of the floppy
4) Boot from floppy in update (usual boot mode) or in recovery mode (set by jumper on motherboard “blind mode”).

Babasha wrote on 2022-03-30, 10:19:

There should be instruction in txt file. As I remember: 1) Format floppy - format a: 2) Make it bootable - sys a: 3) Copy conte […]
Show full quote

vic_e21 wrote on 2022-03-30, 10:01:

Babasha wrote on 2022-03-30, 06:37:

No, he try to flash original Intel BIOS. It looks like best way to create DOS boot disk and flash from floppy or recovery in blind mode using BIOS boot block.

You mean i can write a bios image on floppy, and load with this floopy in recover mode? Or i misunderstanding?

There should be instruction in txt file. As I remember:
1) Format floppy - format a:
2) Make it bootable - sys a:
3) Copy content of BIOS and utilities (all files) to root of the floppy
4) Boot from floppy in update (usual boot mode) or in recovery mode (set by jumper on motherboard “blind mode”).

Try both of methods, usal mode, recovery mode, nothgin is change . Same errors вepending on BIOS version. I wait a 15 minutes in recovery mode, but nothing is hapend. Probably is quest to hard)
Or need try to find another bios images

I create floppy image with minimal MSDOS 6.2 installation and BIOS P04 for your board.
It looks one-to-one as flash floppy for my TC430HX board an SHOULD work.
At last in recovery mode it SHOULD give some sound from floppy (sound of floppy boot).

Just unzip and write floppy using some image write/copy tools.

SET ALL JUMPERS IN DEFAULT POSITION AND LOAD BIOS SETUP DEFAULTS!
Then boot from floppy in usual mode or set BIOS RECOVERY jumper and boot in blind-mode

Babasha wrote on 2022-03-31, 07:57:

SET ALL JUMPERS IN DEFAULT POSITION AND LOAD BIOS SETUP DEFAULTS!
Then boot from floppy in usual mode or set BIOS RECOVERY jumper and boot in blind-mode

Thanks a lot again Babasha, but it still not work, i write your image on the floppy, all jumpers in default positions, all bios options in default.
Try blind mode - just 10 seconds of floppy sound and nothing. Just black screen, try the usual flashing method - nope, image bios error.

:\

Sad, no ideas(((

Babasha wrote on 2022-03-31, 20:36:

Sad, no ideas(((

Last what i about think is use a specifiec flasher for Pheonix bios

I look jumpers manual where J9c1-B group where 1-2 (flash normal), 2-3 (flash protect) and user manual where J9c1-B group where 1-2 (bios setup enable), 2-3 (bios setup disable). This is strange.
And factory configured J9c1-B 4-6 (do not alter)… maybe its interesting jumpers for override? 😉

Babasha wrote on 2022-03-31, 21:02:

I look jumpers manual where J9c1-B group where 1-2 (flash normal), 2-3 (flash protect) and user manual where J9c1-B group where 1-2 (bios setup enable), 2-3 (bios setup disable). This is strange.
And factory configured J9c1-B 4-6 (do not alter)… maybe its interesting jumpers for override? 😉

Still not. Probably we don't fix that with the means we haveю.

And by the way, on the Iflash screen, there is a top line, the part number is written on it, I think this is the motherboard number. And it doesn't match the sticker on the motherboard.

vic_e21 wrote on 2022-04-02, 08:14:

Babasha wrote on 2022-03-31, 21:02:

I look jumpers manual where J9c1-B group where 1-2 (flash normal), 2-3 (flash protect) and user manual where J9c1-B group where 1-2 (bios setup enable), 2-3 (bios setup disable). This is strange.
And factory configured J9c1-B 4-6 (do not alter)… maybe its interesting jumpers for override? 😉

Still not. Probably we don't fix that with the means we haveю.

And by the way, on the Iflash screen, there is a top line, the part number is written on it, I think this is the motherboard number. And it doesn't match the sticker on the motherboard.

The number you're seeing on the top line is the iflash part / release number, so 643643-031 is iflash release 3.1 - the last 3 digits should reflect the various release numbers if you check. As I mentioned before, your board is definitely an Intel retail version - the serial number (IKLT74706414) on the label / POST screen match as does the Intel AA (Altered Assembly) number 678039-104 with known production runs of this board.

I've been looking again at the various BIOS versions available using some of the iflash command line options, but sadly they all appear to be fine so I'm at a loss to explain your issue - maybe the flash memory chip is failing somehow and has corrupted part of the current BIOS.

I read sometime ago topic on rom.by about how to combine Intel BIOS flash parts in one file, maybe its real and flash it using mr.bios from Gateway 2000 (Intel 430VX). But its to unusual and deep theoretical.

PC Hoarder Patrol wrote on 2022-04-02, 08:57:

vic_e21 wrote on 2022-04-02, 08:14:

Babasha wrote on 2022-03-31, 21:02:

I look jumpers manual where J9c1-B group where 1-2 (flash normal), 2-3 (flash protect) and user manual where J9c1-B group where 1-2 (bios setup enable), 2-3 (bios setup disable). This is strange.
And factory configured J9c1-B 4-6 (do not alter)… maybe its interesting jumpers for override? 😉

Still not. Probably we don't fix that with the means we haveю.

And by the way, on the Iflash screen, there is a top line, the part number is written on it, I think this is the motherboard number. And it doesn't match the sticker on the motherboard.

The number you're seeing on the top line is the iflash part / release number, so 643643-031 is iflash release 3.1 - the last 3 digits should reflect the various release numbers if you check. As I mentioned before, your board is definitely an Intel retail version - the serial number (IKLT74706414) on the label / POST screen match as does the Intel AA (Altered Assembly) number 678039-104 with known production runs of this board.

I've been looking again at the various BIOS versions available using some of the iflash command line options, but sadly they all appear to be fine so I'm at a loss to explain your issue - maybe the flash memory chip is failing somehow and has corrupted part of the current BIOS.

Thanks, don't know about this digits. btw i try use later version of IFlash - 6.*, But this isn't help. Yes, i agree with you, probably actually flash memory have a some issue, only way is find a modded iflash version (if they exist), which was ignored this error. Or update bios trough hardware programmer

Babasha wrote on 2022-04-02, 10:34:

I read sometime ago topic on rom.by about how to combine Intel BIOS flash parts in one file, maybe its real and flash it using mr.bios from Gateway 2000 (Intel 430VX). But its to unusual and deep theoretical.

Thanks, try to find some information in this way