Thanks for your offer; I have posted a message in your mailbox, with a link to a jpg in mediafire of what I have.
@MyDigitalName: Server R2 Standard will come real soon. Support for Enterprise is on hold right now because there are no OEM Slp keys for Server R2 Enterprise. AmjadAli: Windows 7 itself is not modified at all. All this little tool does is run a script when you install win7 to activate it via loader or bios mod method. noeth2: I got your message and I would have to say lol man
Thanks for your work, it works brilliantly. I combine it with a runoncex.cmd to also install the latest updates from MS & some reg tweaks. Is there a way of telling whether it's using a loader or bios to activate? I assume if it's the bios grldr won't exist in the root drive.
That is one way to tell, most likely though that if you have a bios mod that is from a company that is supported through certs that you do not have the loader but you will if you either have a unsupported bios mod or no bios mod at all. It is programmed to do the bios method first though.
HP 550 and ASUS EeePC Then, HP 550 and ASUS Eeepc is completely activated with version 2.3: The error was in my script that run some system updates before activation; shifting the execution of activation before the updates, all ok. Thanks a lot Hazar & Company
I have tried your kit but it does not work for me in either vmware or on a real laptop. I am useing an AIO (windows 7 and Windows server 2008 R2). Could that be the problem??? will it work on an only AIO Windows 7? Please let me know. Thanks
Well it works fine with all versions of windows 7 besides enterprise obviously.. But if you have a AIO with 2k8 and Win7 shoudnt matter if your installin win7, no error message appearing ? Im uncertain if this kit will activate Server 2k8, but theyre pretty much the same i guess..
I have tried this on several machines and it did not work, instead it installed the loader rather than installing certificate, I have however managed to fix the scripts. Below is the places I fixed in the install.bat, also all the certificates will need to have the space after there name removed, which it turns out is only some of them (the ones Hazar put in, the new ones put in by Sam do not have spaces in, which they theoretically should have done if it was working anyway). i.e. ASUS .XRM-MS BECOMES ASUS.XRM-MS (notice the space in the first one). Also SETUPCOMPLETE.cmd should also be updated correspondingly with certs that have no space and also have extra lines put in for the new certificates so they are removed after install. See bottom for this. Install.bat (not all of it, just the bit that needs changing) SETUPCOMPLETE.cmd Hope this will help peeps, it has certainly allowed me to make an awesome all in one now. ^_^
lol yep didn't tell you about that one sorry The problem arose with the SET VAR=ASUS & GOTO thingy It put a space at the end of ASUS and I didn't think about putting the whole filename in there lol
give me one reason 2 make this work ? isn't slic & cert file should be same ? as i see isn't same at all, u use modded loader 4 30 cert file, how u got this idea ? what about 'copy /b' 2 all 3 part's ?
Yeah, I was not sure myself why you had not used the complete filename, thought it might of been cause it caused issues, but when i tried it it all started working. I have loads of different machines at work all with different SLIC's and different corresponding certs and I am regularly making new images for new machines that come in and it was just not working with them but I new it should work, but did not have a good chance to fiddle with the script until this weekend. But glad to be of help
Code: %query% | FINDSTR /I HPQ IF NOT ERRORLEVEL 1 SET VAR=HP & GOTO MSG %query% | FINDSTR /I LENOVO IF NOT ERRORLEVEL 1 SET VAR=LENOVO & MSG %query% | FINDSTR /I MEDION IF NOT ERRORLEVEL 1 SET VAR=MEDION & MSG %query% | FINDSTR /I MSI IF NOT ERRORLEVEL 1 SET VAR=MSI & GOTO MSG the middle 2
More bad news The whole RSDT detection process doesn't work: The query environment variable gets set to: REG QUERY HKLM\HARDWARE\ACPI\RSDT rather than the outpot of the Reg command. I found this when testing your release on a Laptop that just had a BIOS update to SLIC 2.1 - the result of using your release showed it looked to be an ASUS Notebook rather than a Toshiba Laptop. That sent me looking at the routine itself. I find this command produces the desired result: for /F %%V in ('REG QUERY HKLM\HARDWARE\ACPI\RSDT') do set query=%%V just trying to help, coding is a bitch.