yes its acer 2.1 and yes you can rename it to whatever you want to name it. do you need the command to install it too?
@Brainsuck Hi, it wasn't there when i started to type, <smiles> prolly was editing as you posted it ... great work & fast! looked up waaay too late
@7-eleven.hell-hole_rider Yes, i have the GA-EP45-UD3P (rev. 1.1) f9 BIOS. I have not installed the f10f DATED 2009/08/25 BETA BIOS yet.. If i install the f10f Beta Bios will it change my SLIC? @Brainsuck Muchos Gracias man! i will try your bios mod...hope to have that SLIC 2.1 and install W7 at last !!!
alright open command prompt as administrator type slmgr.vbs -ilc %CERTPATH% replace %CERTPATH% with the full path of the xrm-ms cert on my machine i always copy the cert to the root of the drive for windows like slmgr.vbs -ilc C:\ACER2.1.xmr-ms
@Brainsuck The BIOS mod you mentioned is for BIOS f4, i would like the f10f bios mode if it is possible... Thanks anyway!
Gigabyte BIOS mod Tips Greetings everyone, I recently upgraded my motherboard, due to a Asus BIOS update failure, to a new Gigabyte GA-EP45-UD3LR motherboard that did not have a SLIC table in the BIOS. I found a BIOS mod for the motherboard that had SLIC 2.1 and updated the BIOS using QFlash. The update installed fine and now I have a BIOS with SLIC 2.1. Here are some tips I have learnt alone the way, since performing my first BIOS update a few years ago with Windows Vista. 1. The SLIC 2.1 BIOS mod I used included a Dell SLIC 2.1 table. While this does not have any effects on the performance of the PC, and the Award BIOS application functions as normal, I had to use a Dell SLP Certificate to activate Windows 7. If you mod your BIOS with a SLIC 2.1 table from a different manufacturer than your motherboard, just make sure you install the matching SLP Certificate in Windows 7. So if your motherboard is Gigabyte and you mod it with a Dell SLIC 2.1 table use a Dell MS Cert, if you have a Asus motherboard with a HP SLIC 2.1 table, use a HP MS Cert, and so forth. 2. Don't ever use Windows based BIOS update utilities, as stay resident programs, such as Antivirus software, can play havoc with the validation process. If the validation process fails, your motherboard wont boot and you will need to take steps to fix the corrupted BIOS file. This can be a real pain! Also, make sure any BIOS mod you use matches your motherboard exactly, as using the wrong BIOS file can also harm your motherboard! 3. Microsoft have yet to release their Windows 7 Validation tool online, but a good way to check if your copy of Windows 7 is genuine is to install a Microsoft product the checks validation during install. An example of one such application is Microsoft Security Essentials, which is a free download and a good replacement for Windows Defender with built real-time antivirus protection. 4. Product keys and SLP Certificates are interchangeable between 32 and 64 bit editions of Windows 7. This means that the same product key and SLP certificate can be used for either system you install. I have found it useful to enter the product key during installation. Just make sure you untick the 'Automatically activate Windows online' tickbox, as you will be performing an offline activation. This way all you need to do is install the certificate to activate Windows. 5. This method of activation is the best way of activating Windows 7. It is highly unlikely that Microsoft will deactivate a copy of Windows that has been activated with a genuine SLP certificate, as this would result in thousands of genuine machines becoming non-genuine. This is not the case, however, with Loaders, as these types of tools usually modify portions of code that can be traced. As loaders are not provided by Microsoft to OEM manufacturers as are SLP Certificates, and are usually produced by independent enthusiasts, you run the risk that the loader will be detected and this will deactivate your copy of Windows. Good luck and enjoy Windows 7.
And even not case sensitive. Actually i didn't have to do anything with BIOS of my Gigabyte MB to activate XP with proper oembios files cause it alredy had "Gigabyte Technology Co., Ltd." in DMI in Base Board Information section.
My motherboard already have a SLP 1.0 string as default by gigabyte them self. I didnt add any. Check it out with SLIC Dump Toolkit (latest version).