Fujitsu Stylistic ST6012

[Maxinator500]

I have some news. Just an update on progress regarding BIOS unlocking.
It looks like this is going to take a little longer.


The ROMEXEC presence error was easily fixed. But, as it turned out, this BIOS is not so simple. Instead of one error, there's another, more serious one appeared. It sounds something like: error in module OLD1.RLS. I don't remember how it spells exactly, but it doesn't matter.


Now there are two possible scenarios... This is in case if we want an almost completely unlocked BIOS. And I WANT IT.
First, we can manually recreate the look of the BIOS UI with all its menus, including the hidden ones, by illustrating it in a notepad. For example, how I did it for some Samsung notebook. But I do not want to resort to this, because then was just a hopeless situation, and the Fujitsu BIOS also has too many more settings to tinker with.

Second, it is more likely to fix the problem in a certain part of STRINGS module. I already localized it. One of the values corresponding to a name string identifier is not correct, and for both EN and JP languages.
And yes, I've tried removing one of the language packs, hoping to fix this issue quickly. But no luck. Maybe a compilation error?

Enforcing PBE to continue loading even if STRINGS is corrupted, I found out that this problem does not occur artificially due to PBE, missing ROMEXEC or else. PBE still can read menu tables from the TEMPLATES module correctly. The only thing is that there is no names for anything, except entries types.

Will see what I can get.

[Remdale]

Thanks for the update.
Many options there? I'm very impatient to know what those are.

PBE is old and needs to be updated, I wish we had its source code for this purpose.
Wouldn't you mind making a guide about how to fix the whole thing to make it readable in the PBE? I guess someone might need it if they get in the same trouble. We will also have to be able to compile the BIOS back if possible. Otherwise, how do we save the edits?

By the way, do you have enough skills at IDA disassembler?

[Maxinator500]

Thanks for the update.
Many options there? I'm very impatient to know what those are.

I think I can make it real.

I confirmed the bug location. Chose name string, which in my opinion is correct. Next, assigned its numeric identifier for all others in the STRINGS module.
The error is gone. Now I need to filter out incorrect value(s) in the same way.
Will do when I have time.

Wouldn't you mind making a guide about how to fix the whole thing to make it readable in the PBE?

Maybe.

We will also have to be able to compile the BIOS back if possible.

No worries. We'll be able.

By the way, do you have enough skills at IDA disassembler?

I do have some skills. So I was able to move forward. I used IDA to skip the ROMEXEC warning and else...

[Remdale]

That's awesome! So is the BIOS file problematic itself or it's the PBE which is too old to be able to open the new format?

I do have some skills. So I was able to move forward. I used IDA to skip the ROMEXEC warning and else...

Great, I will PM you

[Maxinator500]

That's awesome! So is the BIOS file problematic itself or it's the PBE which is too old to be able to open the new format?

I would say the culript is the BIOS.

Check this out.

The error is gone. Now I need to filter out incorrect value(s) in the same way.
Will do when I have time.

Can you indicate for me which menus are not available so I could start unlocking?

[Remdale]

I have removed the BGA CPU from the motherboard, so I can't check out which options are available unless I solder it back on the board. But I have a manual with all the tabs and menus. I don't remember if all of these are actually visible, but I hope they are. Have a look

[Maxinator500]

I have a manual with all the tabs and menus.

Thanks.
The only thing I see not available is the Advanced Chipset Control menu. Not quite sure how to make it visible. I didn't ask Sml6397 about this.

So I did the following. I moved all the settings from this menu to an Intel menu in the hope that it is not affected by the hide flag, and moved this menu to an accessible location.
BIOS MOD: Fujitsu Stylistic ST6012.zip
Confirm if the modification went smooth when you get the motherboard to work.


And here's something for you to play with: Remdale.zip

[Remdale]

Ok, thanks. Will flash as soon as I get the device back to the working state.

In the notes in the 2nd archive it says "First, load dummy, then load a target Phoenix BIOS file." Does it always have to be done after each start of the program? How does this change anything?

In the notes in the 1st archive there addresses next to each setting. What are those addresses about? What is the whole file for? And what does "space 4320" mean?

[Remdale]

Oh, I forgot to ask. How do you think why are these without proper names?

[Maxinator500]

In the notes in the 2nd archive it says "First, load dummy, then load a target Phoenix BIOS file." Does it always have to be done after each start of the program?

After each PC reboot or PBE overflow error. To open the problematic BIOS for some reason it requires to load valid data of some normal BIOS to RAM.

In the notes in the 1st archive there addresses next to each setting. What are those addresses about? What is the whole file for? And what does "space 4320" mean?

See this.

How do you think why are these without proper names?

The manufacturer's mistakes, I guess.