how to not brick my newest toy fujitsu system

[Lost_N_BIOS]

But it's not in manufacturing mode now correct? Is there a full screen logo show setting in the BIOS?
If it's still stuck in Manufacturing mode, maybe I can find this tool to get it out of that OEMIDENT?
http://www.sp-it.net/index.php/2016-01-2...-bios-r120

Did the other guy get it correct, or do we need to link him to BIOS file to use? I'll check, I like to help and hate seeing people stuck with BIOS issues when I know I can help. He probably noticed us talking about it in this thread If you are a member there, post and tell them if only two memory slots work to update the CPU microcodes, or post the file I updated if you want.

[kokodin]

i am not a member there, he used Phenom X3 720 BE anyway so he might be ok

As for is the board in manufacturing mode now... I have no way to test for it, it retain settings as normal so it might just be that bios look blue due to the lack of graphics do display?

Yesterday i was trying to install windows on my old 500gb hitachi hdd only to discover that this drive was in my box not without a reason. even low format didn't make it usable
So i sat sad on my regular pc and made a cute chicken graphics just in case
i have no idea what format should an image be, so i made it small enough to fit lenovo bios image patcher (i think) 16 colors bmp 34kb with custom color palete

[Lost_N_BIOS]

Yes, I suppose if he has memory issues he would have posted there to ask or complain about it already

I think manufacturing mode would show if it's still that way, otherwise it seems like it's just a one time boot thing.
BIOS may look blue because that's how it's designed, not sure, you'd have to try and find a BIOS image from that specific system and see if it's blue or not too. That can be modified to any color, but I'd have to hunt down how to do that since it's been so long. What is the text color?

I haven't had time to look for the logo/splash yet, but I'll grab your chicken when I do and test it

[kokodin]

I was thinkering around those bios flashes again to check some things.
Basically i dumped my patched working bios made out of that flash you provided with microcode updated (2904mv2.bin).
Then i used oryginal flashing software from fujitsu provided for d2904 board.
Flashing software detected that this motherboard is in fact now compatybile for flashing, but version of the bios is the same, so it kindly asked for confirmation if i want to flash it.
I did flash it aaaaand nothing has changed, nothing, absolutely nothing, even ram support is still there, no logo, blue boot screen, most of my bios settings, simply works as before so i restored defaults and other than floppy controller no option has changed and again no logo, on both cpu's mind you.
So i expect that oryginal flashing program have a data provided what areas of the bios it suposed to flash and which to leave alone, otherwise it should remove cpu microcodes and ram support (or i just put the processor wrong into the socket at first time) or add graphics back.
So i dumped that flashed oryginal bios too. (2904ogf.bin)
if you could tell me if microcode patch is still there i would sleep better, because i expect it still be there , if not i have no idea what happened.

other thing i did was reading my bmp file in hex editor to see the bmp pattern, adjusting for the line length of 272 as expected bring in image clearly visable in hex editor (as expected), so i expected it could look similar for the bios embeded graphic and i spended around 2 hours adjusting hex editor line size to see any patern, and failed to see anything, there were some funky repetitions but nothing that would look similar to graphic pattern of a bmp file
 of course i was working with the oryginal d2724 bios dumped from the board in the first place
most of the difference is still in the header, but i am afraid to copy over that just to see some graphics :] not untill i actually buy that programmer (because i dropped the idea when flash worked the first time)

edit************************
oh by the way, bios is running in 800x600 resolution if that makes any thing easier

[Lost_N_BIOS]

BIOS updates usually only write to certain regions, and does not always erase then write, unless programmed to do that which is not always the case. Sometimes only update if new/different data within a region by the byte. So, sometimes any microcodes that are there for example, that aren't in the BIOS you are flashing will remain, unless it erases then writes. Sometimes BIOS updates are set to only flash certain regions too, so microcode may be one that is passed over by the stock flasher, especially if they over several updates never added any then it may be a block they don't include in the normal flash command switches. It really all depends on the flashing program and how it flashes, and the commands /flags used during the update too.

For your peace of mind, I can show you BIOS micrcodes/dates/versions included before and after I updated those, if I didn't already include that image in the BIOS package when I uploaded it for you (I usually do). The microcode was always there, it just wasn't up to date to the latest possible version, that's why I updated it.

Here's an image showing the microcodes included in the two files you attached


And here's the one comparing stock mod BIOS vs the one with updated microcodes I sent you before, looks like same comparison


On the BIOS image, it could be any number of formats, does not necessarily have to be a BMP.
PNG, JPG/Exif, BMP, EPA, GIF, PCX, TGA, TIFF, ICO, WMF, J2K, JXR, WebP, JP2 (JPEG 2000 Image Format (*.JP2, *.JPA, *.JPM, *.JPX))

More common image formats used back then for logo's/splash images would be BMP (but actually AWBM not real BMP), EPA, TIFF, TGA, or PCX

You'd have to lookup hex headers or markers for each to maybe easily find them.
When looking for images in BIOS, here's the some headers / signatures for some image formats

42 4d (4D42) is BMP \x42\x4D

Others are more complicated, but you can look them up for an easier summary. Just look for each type of file in google and it's hex header or signature hex
Here's some I pulled from a UEFIImage extractor's python file.

BMP
(\x42\x4D.{4}\x00{4}.{4}\x28\x00\x00\x00')

PNG
(\x89\x50\x4E\x47\x0D\x0A\x1A\x0A')
(\x49\x45\x4E\x44\xAE\x42\x60\x82')

JPG (Starts with FF D8 FF. Ends with FF D9
(\xFF\xD8\xFF\xE0.{2}\x4A\x46\x49\x46\x00) # JFIF marker
(\xFF\xD8\xFF') # Any marker
(\xFF\xD9')

GIF - GIF8 (GIF8) (hex: 47 49 46 38), followed the version 9a (hex: 39 61)
(\x47\x49\x46\x38(\x37\x61|\x39\x61)')

PCX
(\x0A((((\x00|\x02)|\x03)|\x04)|\x05)\x01(((\x01|\x02)|\x04)|\x08).{60}\x00(((\x01|\x02)|\x03)|\x04).{2}((\x00|\x01)|\x02)\x00.{4}\x00{54})

TGA
(\x00|\x01)(((((\x01|\x02)|\x03)|\x09)|\x0A)|\x0B).{4}((((\x0F|\x10)|\x18)|\x20)|\x00).{8}(((((\x00|\x01)|\x08)|\x10)|\x18)|\x20))

TGA2
(\x54\x52\x55\x45\x56\x49\x53\x49\x4F\x4E\x2D\x58\x46\x49\x4C\x45\x2E\x00.')

TIFF
(\x4D\x4D\x00\x2A|\x49\x49\x2A\x00)')

Purchase a programmer and SOIC8 cable, they may not be needed for this system, but you'll be happy you have them some day in the future
Plus they're so cheap everyone should have a set. What kind of BIOS chip is in this system anyway, you may not even be able to use common cheap programmers that are around today, you might need special $16-20 one if it's PLLC32 BIOS

[kokodin]

well i quickly run ripper5 and x-ripper over a oryginal backup bios file and it didn't find anything to extract, so there might not be any normal graphical headers at all
if they were there it would find them and extract graphics

[Lost_N_BIOS]

You'd have to do it over the extracted non-compressed files, here is those files from both. Rom.SCR is just file list/info text so you can skip that one
http://s000.tinyupload.com/index.php?fil...1375834878