Hi Andy When performing an SSV3 mod and shrinking the 1B module; if the module is shrunk back to original size then it is inserted SSV2 style What exactly is difference between SSV3 and SSV2? if 1B module size equals original, then uses SSV2, what does this mean realistically? SSV3 has a pointer to SLIC, so SSV2 does...?
SSV2 = SLIC is not in any module, but replaces FF bytes in the BIOS file. SSV3 = SLIC is in system (1B) module Putting the SLIC in 1B increases the size of the module. When there is a size difference it is readded using MMTool (or in the past AMIMMWIN). With SSV2 the 1B module can be kept the same size and replaced manually (without MMTool). In both mods there is a pointer in RSDT & XSDT referencing the address the SLIC will be found in RAM.
SSV3 mod - the SLIC table is included in the 1B module. The pointers are updated to reflect this. The 1B module's size does not matter. It is reintegrated with amimmwin/mmtool. SSV2 mod - the SLIC table is in the main BIOS image. The pointers in module 1B are updated and the compressed size of module 1b is made the same by altering some strings so that it can be copied back directly without using amimmwin/mmtool. The hybrid SSV3 method (only works for a SSV3 mod when always shrink 1b and use extra space are selected from the options) aggressively shrinks the 1B module to its original compressed size - not always possible - and if this is achieved it is copied back into the BIOS without using amimmwin/mmtool (aka SSV2). I think I have only every come accross one BIOS where this was even vaguely necessary. It should NOT be used routinely - it can cause problems when tools like EZ-Flash are used to flash subsequent BIOSes. It is included for completion and research! Cheers Andy
Hi Andy Let me firstly say that your tool is the best, most thorough tool out there for slic modification of bios. I pretty much understand now that the SSV2 approach would make sure the offsets of each module are maintained, and while this is not necessary in general, some fussy bioses may need the SSV2 method. SSV3 is fine for the most part when 1B size is not critical and mmtool or amimmwin would reintegrate the module appropriately. A couple of questions: how do you extract or copy back the 1b module when it is the same size without using tools? and when EZ-flash would have issues with future bioses when using SSV2 why would that be, could it be related to checksums or something else? Cheers JohnnyC
1) 1B is copied back with simple binary file manipulation. File is read into an array of bytes. The 1B module is read likewise. A simple for/next loop copies the bytes from one array into another. Manually you can do this in WinHex or Hex Workshop and copy/paste. 2) The issue is not with SSV2. The issue is with the extreme shrinkage of the 1B module in the SSV3 hybrid method. There are some strings (after the AMIBIOS 0800 string) - that EZFlash seems to use to identify the BIOS. When these are absent it won't flash. DOS flasing is still fine. Note - these are NOT altered by default for any method. They are ONLY altered when 'use extra space is ticked' and ONLY altered when the normal (safer) areas do not allow enough shrinkage - and this should ONLY ever happen when trying to shrink an SSV3 1B - and this is RARELY ever needed. Andy
Where exactly does it fail? (Assuming SSV3) ie. 1) does it launch mmtool OK 2) Does it change to the replace tab OK 3) Does it insert the path/filename of the 1B_SLIC.BIN in the correct textbox 4) Does it insert 1B,0000,0000 in the other textboxes 5) Does it correctly go to the replace button 6) Does it then go to the save button, bring up an 'are you sure' dialog, and exit? Cheers, Andy
things just keep getting beter, thanks again for the new version, so far i can't fault it on english vista ultimate.
@ Andy your bios tool just gets better all the time i was just noticed that if you change the manufacturer the option's settings change for different ones, i take it these are the safest settings found so far for modding? Just tried latest version 1. loaded unmodded bios file 2. selected other as manufacturer because it was an ASRock bios 3. selected dell.bin 4. selected DELL.XRM-MS 5. Slic and certificate Match 6. select go SLIC performed successfully ============================== 1. loaded the modded bios file 2. comes up with, This bios allready has SLIC table added with SSV2 method 3. selected DELL.XRM-MS the one i selected before 4. comes up with, SLIC and certificate do not match Question is should the Slic and certificate have matched or is that part for checking an original unmodded bios with slic against certificate ? Thanks
1) The options change - they should (!) be the safest. The main thing is that the 32bit checksum is never changed for MSI/XFX boards, and is always corrected for ASUS boards 2) They should match in both cases. The certificate checking is completely independant to the SLICing process. The SLIC should (obviously!) be the same one. Could you post a link to the BIOS? Thanks Andy
Could you tell me where exactly it fails in the automated process. (Assuming SSV3) 1) does it launch mmtool OK 2) Does it change to the replace tab OK 3) Does it insert the path/filename of the 1B_SLIC.BIN in the correct textbox 4) Does it insert 1B,0000,0000 in the other textboxes 5) Does it correctly go to the replace button 6) Does it then go to the save button, bring up an 'are you sure' dialog, and exit? Could you also try an SSV mod and tell me if that works / how far it goes? Andy
Win XP RUS : item 4 don't work. Win Vista RUS : item 6 don't work On SSV mod also don't work. Win XP RUS : item 3 don't work. Win Vista RUS : item 6 don't work