Hi I have been trying for hours to get CBROM to open my phoenix - awardbios v6.00pg bios. I have the CBROM program in the root directory with the bios file 631F1P61.bin also there.. The bios file is 512kb in size. I am entering c:\cbrom198 631F1P61,bin /d and i get cbrom version blah blah 631F1P61.bin file not found. I have tried about 8 different versions of CBROM and two different bios's but always the same?? Everything I have read tells me I am doing it correctly!! Been hours and hours.. Please show me the light.. many thanks.
Hi Tito, Thanks for responding. I have uploaded the bios to bit share. The link is (sorry not allowed to post the link according to site rules.. not enough posts..) I will see if I can send you a pm with it. Don't know what you mean by manual modding?? Please explain. EDIT: unable to pm you either, not enough posts... Feeling really welcome now! The board that the bios belongs to is a foxconn G9657MA-8EKRS2H. If you wouldn't mind googling it and going to the Foxconn site, the bios is listed under the tech support tab. Hope thats ok. Thanks.
I had this problem too. You must be directly in the folder with cmd. You can't use c:\cbrom198 631F1P61.bin /d But first you must cd to C:/ and then run cbrom198 -d 631F1P61.bin
@benik3 Hi thanks so much.. funny thing is I tried that originally but C: at the command prompt would always default back to c:\Users\Keep Fighting> which isn't the root, hence cbrom wouldn't run.. Any idea why C: would not get me to C:\> ?? Would have saved me a helll of a lot of effort... Anyway, I have set up a new A directory and put all the files in there, A: at the command prompt gets me to the root, A:\> where all the versions of CBROM work.. superb, mate thank you. @tito Thank you for all the efforts. It wasn't so much as which CBROM to use but more the syntax to get it to recognise the bios file!! What is the Lenovo 2.2 slic you have added please? What is this for? I am interested in updating the CPU micro code to support the wolfdale Core 2 Duo processor.. I am aware that the G965 chipset has been updated successfully to achieve this on some HP - MSI board machines.. I am new to this, but I have put a bit of effort in reasearching/reading modding bios's, and wasted a hell of a lot time banging my head on the desk trying to open the bios file... where I was not quite in the root directory... Hoping to get my head round it now I can get out of the starting gate.. By the way, what did you mean by "Manual Modding??" in your original post? Is there some thing I should be aware of? Many thanks for your help.
SLIC 2.1 is used for activating windows 7 by OEM certificate+key With manual modding he probably mean without using any special tools BTW I tried the C: problem and you must use cd C://
cd c:\\ works.. ..straight to c:\> would have saved me four/five hours of finding and researching cbrom instructions... cheers. I don't need the SLIC mod as windows is already avtivated, maybe some one else can use it. It's the cpu micro code support I want to update.. I can extract, delete and replace some modules now... The ncpucode module doesn't seem to extract a copy to the root directory? not sure why yet? tried extracting it using cbrom fox.bin /cpucode extract processes, but no output.. keep on reading... any tips would be welcomed.. looking at two prospective Gigabyte donor bioses (My board is Foxconn but looked for any 775 socket G965 board that supports E7500 wolfdale, not sure if that ok) can't see any cpucode rom displayed, maybe it's in the system bios rom Keep reading..
If you will make clean installation of windows, I recommend SLIC activation. It's better as it is "official". The activators change important system files...
Thanks but I will stick with activation via microsoft. Any Light on the cpu micro code update at all.. Thats is what I am interested in, not really any activation mods to be honest.. I have sourced intels cpu microcodes list and extracted it with microdecoder.exe As I understand it I need to find out which codes apply to the E7500 ((1st issue)which at the moment I can't... supposed to be able to do it with info from cpu-z but I cannot see any info relating to cpuid, platform, version and date - which is the format of the microcode updates??) and delete the ones I don't need, maki9ng sure I keep the latest version of any duplicates. I then need to create a new NCPUCODE.BIN file by running copy /b *.bin ncpucode Delete the existing ncpucode.. make the new NCPUCODE.BIN read only via properties.. And insert it back in to the bios.. 2nd issue is I don't get any official output when running the following.. cbrom fox.bin /nc_cpucode release I havn't tried re-inserting ncpucode using the following yet, but I am about to.. cbrom fox.bin /nc_cpucode NCPUCODE.BIN See what happens.. I have also read that the NCPUCODE is actually written into the system bios rom, and that you need to copy from a donor bios with the updated microcodes in already, and paste that block of hex into your bios, using hex editor, making sure the size of the block is not smaller, if so over write any of the residual bits at the end with a hex value (can't remember what it was now.. some thing like FF - i can check again though) wondering how you identify the hex which represents the NCPUCODE within hex editor? Wanted to look at the system bios in hex editor out of interest, but again I am not sure what command will extract this using cbrom.. cbrom fox.bin / system bios extract cbrom fox.bin / bios extract cbrom fox.bin / original.temp extract don't work.. Would be very grateful for answers to these questions or guidance what is the best way forward.. Please bear in mind that as well as an end result, part of my goal is to learn the correct way to do this myself. Thanks for your help.
The command C: will take you to whatever the current directory on unit C: happens to be. On a Windows system that will by default be the current user's home folder. To get to a specific directory you have to enter the 'change directory' command followed by the path to where you want to go. Like to the root directory of C: cd C:\ or cd: C:\\ When at the C:\ prompt, enter 'help' and all will be revealed.
thank you for that. Still hoping for some useful guidance to the other questions relating to updating microcode process.. Cheers
anyone help please.. In terms of people adding microcode to create support for a newer CPU i.e what I was attempting, is this possible? From what I read it may be with the processes I have used.. i.e. cbrom release, insert or Directly using an Hex editor.. The guys in the HP thread I linked to in my previous post were able to update the microcode support on a Q965 chip set. contrary to Intels official support guidelines.. It's been six days of hard work, which has been worth it for the learning aspect but it would be a shame to walk away if there was something I was missing or an alternative solution. Here's what I did.. I carefully went through the original bios and wrote down every offset where the individual cpu microcode began and made a complete list which tally with the CBROM cpuid listings. I calculated the total size of each CPU microcode update and the total tally with the *ALIN16* ncpucode size indication. I then constructed a new ncpucode.bin file incorporating the E7500 (1067a) microcodes and soem others where the size of the block I would be replacing was exactly the same as the size block of NCPUCODE hex I was removing.. This way I did not have to change the size of the *alin16* ncpucode indicator.. I didn't do this the first time, I chopped the overall size of the NCPUCODE block and reduced the *ALIN16* NCPUCODE size indicator to match.. This didn't work as the bios came out at 510kb instead of 512kb and displayed with some corruption in cbrom - I understand it is possible to add an extra byte to balance the size but it seemed simpler to make sure the new block of hex with the new microcodes, exactly matched the block that was removed, leaving the original size registered by *ALLIN16* xxx the same and correct. This method appeared to work well, all the updated was present in the modded bios and cbrom created a new checksum and displayed the updated cpuid list. The modded bios flashed normally and the result, as I said earlier was.. Pentium D still posted (even though the 0F64 (pent d) code was removed?) E6400 (06f6) posted normally E7500 (1067a) fans spin up and post error card shows a halt at C1. This link is the modded bios using Hex editor.. (sorry no link allowed, please pm me) This link is the original manufacturer bios.. (sorry no link allowed, please pm me..) Could anyone shed any light please. I did start this thread in the hope I would get some guidance in the process of updating the NCPUCODE and whatever else necessary to modify the bios to support the E7500 (1067a) processor.. Here's patiently hoping?