Not unless he changed the string. The tool inserts "Dell Computer". Change the test to "Dell System" and it has a chance. I do not know where the tool inserts SLP strings. This is a core7 bios and is much different than core8 that is done easily here. These are very difficult. With the added code, the bios crashes the mmtool necessary to view it. At least mine crashes..
ok ive installed ACPIscope, but when starting it says the driver failed to start (win7 retail) so i installed RW Everything, which starts ok. i click on ACPI Tables tab, and im suppsed to click on SLIC tab next, but dont see it anywhere??
Im going to use Asus SLIC 2.0, but i´ll use it after the new instalation of Vista 64 bit, because im not really sure, if those tools VOATKToolsv.2.5 will determine something what was used for activation on my old XP. Because when i´ve first installed these XPs, it didnt want any activation from me, it runs great as it was from first instalation, so i dont know if it had some pre-installed activation, which can´t be determined or something like that... so i´ll rather go with fresh instalation and then use Asus SLIC 2.0.
ISA = This is code written by Tommiy that allows a slic to be introduced into memory as the bios initializes. The bios code is not modified, per se, a module is introduced that contains the slic code and other code to put it in memory. 0+2=0+2 method involves changing the bios code proper. A non-compressed module is introduced to the bios and the address is noted. This address is used to figure the slic placement in memory after the bios is decompressed; this is the slic pointer used later. The acpitbl.bin module is removed and the OEMID/TABLEID are changed to the slic manufacturer at the RSDT table, and the XSDT table as necessary. The tables are increased in size and pointer addressees are put in place to call the slic code. The Main module (module 0) is then resized to allow for the main module (0) and the acpitbl module (module 2) to remain their previous offsets. If the module 2 is increased in size by 16h then the module 0 is decreased by 16h.. These modules are all removed and replaced without altering the offsets of the other modules in the bios. Sometimes there are up to 13 modules.. If you are good, you can accomplish this task in around 15min. The tool does all the manual calculations, movements, and insertions in a few seconds..Cool huh? Not as much fun though. As you can see, the ISA is much safer. No code is modified from the bios, just a module introduced that runs its own insertion routine.The others are much more dangerous (or were), but we have gotten them down very well, and the tool is consistent. OEM mods are similar to the 0+2, but does not necessitate the removal of the mainbios module.Code is replaced, moved, altered, etc in all but the ISA. in order of intrusion, I would say this..for award; least to most: Pubkey/marker ISA SSv1 OEM7 w/no manipulation of epa OEM7 w/black epa and acpitble in same location 0+2=0+2 SSv3 All this is dependent on other factors..It is not always easy just to replace the existing SLIC as the sizes need to be kept relative and lately the ofsets need to be kept same. checksums are another lovely discussion. My suggestion is read the mod you own bios sticky and absorb the information. There is a lot of info spread about..
this was very informative, going to check the stickies out since i got some free time off work today. thx zort for the edumacation!
i don't know then, only thing i can assume is that you don't have a slic table if it's not listed but don't take my word i'm still learning myself. i'm sure one of these other fellas will point you in the right direction as they have helped me more than enough already.
I'm not referring to Legitimate ways of activating windows but I am talking about Loaders, patches, cracks, frankenbuild, and other ways of tricking windows into thinking it is genuine and legitimate when in fact it is not.
hmm, thats strange, it will be my luck i have the only motherboard in the world that cant be touched lol.... is there anybody who could tell me where im going wrong?