(05-08-2022, 03:09 PM)zxvdblm Wrote: the model reads as "SLIC-CPC"
I have a question for you. How did you install my mod? Using SPI programmer?
It turned out that MMTool clears the padding areas. That empty space between BIOS modules. And there those serial numbers are stored. As soon as I examine your original bios backup, I found all the data in it! Anyways, the AFUWIN program should have flashed new BIOS with preservation of serials. So confusing. Now I want to find out what sequence of events led to the current situation in order not to make things worse.
I apologize for my amateurish statement from the 4th post that everything will be all right. Actually, that's I screwed up with MMTool.
when i made the first backup with the ch341a i inherently thought i screwed something up and decided to flash the fresh untouched backup back onto the bios chip, when i was then greeted with the diagnostics screen that i keep seeing, then i uploaded the backup onto here hoping that someone could properly edit the backup, at that point it wouldn't matter what i'd use to flash your mod with because i've already messed something up to begin with, but i did use AFUWIN included in the zip file.
I also looked into my original backup that i've uploaded here with something called AMIBCP and i can't really see much of the data, if you're saying you found the data then it could be maybe be recovered?
Posts: 1,037
Threads: 5
Joined: Jan 2020
Reputation:
9
(05-10-2022, 09:47 AM)zxvdblm Wrote: it could be maybe be recovered?
Maybe. But first, let's take a closer look at what happened.
I would like to know what the BIOS chip contains at the moment. This page says that you need to use flag "/O" for this. Thus, please execute "AFUWIN.exe /O" in the command line window.
Posts: 10
Threads: 1
Joined: Mar 2022
Reputation:
0
(05-10-2022, 09:47 AM)zxvdblm Wrote: it could be maybe be recovered?
Maybe. But first, let's take a closer look at what happened.
I would like to know what the BIOS chip contains at the moment. This page says that you need to use flag "/O" for this. Thus, please execute "AFUWIN.exe /O" in the command line window.
AFUWIN v4.42 displays "Error: Loading Driver" , and the one included in your mod displays "Error: Problem opening file to write"
Posts: 1,037
Threads: 5
Joined: Jan 2020
Reputation:
9
(05-10-2022, 10:52 AM)zxvdblm Wrote: "Error: Problem opening file to write"
Perhaps it requires a filename to be specified?! Example: "AFUWIN ROMFILE.ROM /O" If no go, I will give a link to the archive with an additional batch file for backing up BIOS image.
Posts: 10
Threads: 1
Joined: Mar 2022
Reputation:
0
05-10-2022, 12:02 PM (This post was last modified: 05-10-2022, 12:03 PM by zxvdblm.)
(05-10-2022, 11:05 AM)Maxinator500 Wrote:
(05-10-2022, 10:52 AM)zxvdblm Wrote: "Error: Problem opening file to write"
Perhaps it requires a filename to be specified?! Example: "AFUWIN ROMFILE.ROM /O" If no go, I will give a link to the archive with an additional batch file for backing up BIOS image.
That worked, attached the file here, I'd like to also point out that i've looked at multiple other BIOS dumps just now, even ones that aren't publically available and noticed they all have the same thing. The serial number isn't in the backup after you make a dump, which makes me lose some hope
Posts: 1,037
Threads: 5
Joined: Jan 2020
Reputation:
9
This is like a programmer writing error. Lines break in random places. And because of this, model number had acquired a standart name after the first startup.
I believe that the simpliest thing that can help you is flashing the very first bios backup using the ch341a.