I'm trying to do the mod but i'm getting the following errors: C:\bios\CBROM_1.82\CBROM 1.82>cbrom 1007e.awd /Slpkey bbpubkey.bin cbrom V1.82 [04/11/07] (C)Phoenix Technologies 2001-2007 Adding bbpubkey.bin 100.0% 1007e.awd have not enough space for adding ROM. (Over 3BE1BFh bytes) C:\bios\CBROM_1.82\CBROM 1.82>cbrom 1007e.awd /Slpmarker bbmarker.bin cbrom V1.82 [04/11/07] (C)Phoenix Technologies 2001-2007 Adding bbmarker.bin 100.0% 1007e.awd have not enough space for adding ROM. (Over 3BE1BFh bytes) C:\bios\CBROM_1.82\CBROM 1.82>cbrom 1007e.awd /ISA Iasus.bin cbrom V1.82 [04/11/07] (C)Phoenix Technologies 2001-2007 Adding Iasus.bin 76.6% 1007e.awd have not enough space for adding ROM. (Over 3BE1BFh bytes) Any solutions available? Thnks
It is noy an error, it is just a bug in the cbrom's interfece. The module is actulay added 100%, but displayed as x%.
Ok so 1007e.awd have not enough space for adding ROM. (Over 3BE1BFh bytes) Is not a problem and my bios file is now ready to flash ? (offcousre I will do the mod again but then only: C:\bios\CBROM_1.82\CBROM 1.82>cbrom 1007e.awd /Slpkey bbpubkey.bin cbrom V1.82 [04/11/07] (C)Phoenix Technologies 2001-2007 Adding bbpubkey.bin 100.0% 1007e.awd have not enough space for adding ROM. (Over 3BE1BFh bytes) C:\bios\CBROM_1.82\CBROM 1.82>cbrom 1007e.awd /Slpmarker bbmarker.bin cbrom V1.82 [04/11/07] (C)Phoenix Technologies 2001-2007 Adding bbmarker.bin 100.0% 1007e.awd have not enough space for adding ROM. (Over 3BE1BFh bytes) As described in the openings post
IT IS AN ERROR!!! THIS means what it says: You bios has not enough space left!! You have to get some free space. A possible solution is to release EPA logo and add a black one. Please post a link to your original bios. I'll have a look and we can see what we can do....
@Jur, soory for giving you wrong answer in my previous post. I didnt read it well, I havent noticed that it was saying not enought free.. It is good that Yen noticed it before you got in to trouble.
Jur; Are you able to get a clean readout of all the modules in thr bios? i.e. cbrom yourbios.awd /d Reason I ask is I have a feeling your bios is not compatible with any cbrom because its an Asus mobo. I could be wrong. If I am right, find acbrom, this tool is made specifically for Asus. Oh and when cbrom says adding xxxxx.xxx 74%, or anything less then 100%, I think its not an error at all but tells you that it compressed the new added module to that ratio. When it says 100% then it did not compress it and the file was added as is plus header. Edit: Yup you have a special bios that cbrom 113, 115, 182, 208, 219 can NOT open, so do not flash bios if you used cbrom on it. Even abcrom can't open it. I got a read out using bit.exe, and looking at bios in hex editor you have plenty off free space. Code: ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД No. Item-Name Original-Size Compressed-Size Original-File-Name ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД 0 System BIOS 20000h (128K) 103F5h (64.99K) original.tmp 1 IA-32 Microcode 485Eh (18.09K) 37DDh (13.97K) cpucode.exe 2 Other(6000:0000) 7550h (29.33K) 3E0Eh (15.51K) AWARDEXT.ROM 3 EPA pattern 642h (1.56K) 2A1h (0.66K) awardepa.epa 4 ACPI table 3A07h (14.51K) 1495h (5.15K) ACPITBL.BIN 5 VRS ROM 1F65h (7.85K) 12BBh (4.68K) cav_shdw.bin 6 OEM2 CODE 40DEh (16.22K) D07h (3.26K) acpiboot.bin 7 Other(A800:0000) 6481h (25.13K) 3FD6h (15.96K) file1.rom ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
Mmm indeed when I use cbrom /D the program hung (with the command prompt in vista). No solutions for me then (softmods also don't work)
You will need to manually mod your bios with hexeditor. Are you able to recover from a bad flash either hotflashing or using eeprom programmer? EDIT: Yen making SSV3... I will try make ssv3 it myself then will compare to yours Yen as learning experience
WAIT PLEASE! I'll do a SSV3!! It'll work for sure!!! Marker and key won't work! Just give me another 10 minutes for re-check the mod!!!
Offset is easy to calc. Systembios offset 1E000 is always mapped to FE000 physical memory. I've put SLIC at offset 1D000 (free space) which means it'll be mapped always to FD000 physical memory. So the pointer is always 00 D0 0F 00. This fixed method is called SuperStaticV3 (SSV3) and usually used at AMI bios. BTW: Which tool have you used to edit the bios? (You've missed to edit the OEM to _ASUS_Notebook at RSDT ) Edit: It's fine now!!
It seems that all my cbrom versions are not able to edit the bios. Which one have you used??? Edit: Just saw you used bit.exe
Oh kewl! 1. I used bit.exe to extract bios so I can get my hands on the acpitbl.bin, next I used acbrom.exe on my own bios that it works with. I then released acpitbl, added /other 4045:0 slic.bin (4045=nocompress). These Asus bioses has 3rd checksum 8bit at the end of every module so acbrom is very nice to help 2. Using Winhex, on Jur's bios I found the compressed acpitbl.bin and copied modules following it overwriting acpitbl.bin module. Filled in some FFs at the end. This is manual way to /release hehe. 3. At end of that I hex copy/pasted the slic.bin from my bios to his. 4. Calculated offset in his bios and edited his acpitbl.bin. 5. Added his acpitbl.bin to my bios, again thx acbrom for checksums 6. Now hex copy/pasted the acpitbl.bin from my bios to end of his, right after the slic. 7. Forgot the oemid, so redid the process lol I think mine should work too. Unless there is some other overall checksum at end of bios that will be wrong I dont know. edit: there is no overall bios checksum.
Nice info! I've copied / pasted the modules into a new file. End with *.lha easy to decompress with winrar. Calculated checksums with ctrl + F2 at winhex and added as last byte of the module after the zero byte manually. To compress the systembios again I used the cbrom dummybios /other 5000:0 original.tmp command and used the created bios.rom file to re-insert again. Same with acpi command. The created bios.rom file is always the compressed one as result, no matter if it was added or not. I moved the modules backwards to get free space for the larger modules.
Yen & flagmax youre both magicians !!!! It took me an hour to find a working floppy device Flashed the bios and windows is activated Thanks alot (I also requested this one in the request topic shall I make the notification? but I don't wanna take the credits)
Up to you! Yes, no problem. Glad that we could find a solution. Which mod have you tried? Because we did a different method.