xehqter

OEMScan - Automated Multi Manufacture Pre-Activation Utility

354 posts in this topic

I can make the keychange.exe if needed.

Sounds good. Here is something weird though. In my HP MCE install i was following the manual steps to change a vlk key from that link i posted and i changed a oobetimer value in the registry to de-activate windows.

Next step was to run "%systemroot%\system32\oobe\msoobe.exe /a" so you can choose to update the key. Well, the registry value change didnt de-activate Windows and still showed as activated when i ran msoobe /a command.

The magicjellybean key changer wouldnt change it ither. Is this feature only for a vlk install?

Edit: Also tried M$'s new keyupdatetool.exe and it gave a "Must be ran on a supported version" error.

Edited by Randy Rhoads
0

Share this post


Link to post
Share on other sites

ToDo list:

1. Suggest using A16F9D62 instead of E4143622 in oemscan.ini - DONE

2. Variable to pass Bios Match

Workaround: run a different copy of a script for each OEM instance via CMD in oembios.ini) - DONE

3. Change CDKey

Workaround: run a script to change the CD Key via OEMSCAN.INI

4. Dry-Run (doesn't copy files) command line argument

Scan a Specific Range

5. Add option to specify exact range to scan - DONE

6. Fix Bug: Original OEMBIOS.CAT backup file isn't deleted from %Systemdrive% - DONE

7. Delete dllcache\OEMBIOS.CAT - DONE

8. Fix Validation Bug - DONE

1, 2, and 4 should be easy.. I’ll definitely include them in next weeks release.

Edited by xehqter
0

Share this post


Link to post
Share on other sites

Jellybean uses the Microsoft script, check the help. The scripts only support VLK->VLK changes. KeyUpdateTool is the only known tool that can change anything better and so far it's QOS record is poor. KeyUpdateTool doesn't support MCE at all, which means that there are no changes to MCE that KeyUpdateTool is authorized to make. I think it's mainly a VLK -> Retail key changer.

>Well, the registry value change didnt de-activate Windows and still showed as activated when i ran msoobe /a command.

Activation is calcuated only during WinLogon. The status is maintained until another WinLogon.

0

Share this post


Link to post
Share on other sites

@severach

::confused::

I was planning to implement it with WMI in C++ (same method as SP1 VBS script). I’ve used jellybean numerous times in OEM <-> OEM, OEM->ROYALTY, ROYALTY<-OEM situations. It would be somewhat redundant to use my application on a VLK CD.

I'm not going to worry about MCE at the moment.

Edited by xehqter
0

Share this post


Link to post
Share on other sites

This method works to change the key here, verified with magicjellybean, but one would have to have a reg for each key unless someone knows how to convert the key to the digital id without changing all the kieys manually which i was gonna try but not getting anywhere. I also ran the magicjellybean on a Toshiba OEM Pro i have on Virtual PC with the same error message i got from MCE.

I'm using the latest version 1.51.

HP MCE Reg:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents]"OOBETimer"=hex:ff,d5,71,d6,8b,6a,8d,6f,d5,33,93,fd

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]

"CurrentBuild"="1.511.1 () (Obsolete data - do not use)"

"InstallDate"=dword:44e4d5c0

"ProductId"="76487-OEM-0011903-00803"

"DigitalProductId"=hex:a4,00,00,00,03,00,00,00,37,36,34,38,37,2d,4f,45,4d,2d,\

30,30,31,31,39,30,33,2d,30,30,38,30,33,00,2d,00,00,00,41,32,32,2d,30,30,30,\

30,31,00,00,00,00,00,00,00,c6,9d,2f,0e,00,58,a1,02,03,41,ff,5b,44,75,01,00,\

00,00,00,00,e0,9d,e4,44,60,bb,00,00,02,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,35,36,38,32,31,00,00,00,00,00,00,00,a0,16,\

00,00,3d,9f,1a,00,00,02,00,00,e9,17,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,db,27,be,d6

0

Share this post


Link to post
Share on other sites
Actually Randy I was going to play around with the same thing. I think maybe xehqter could allow a special string to be specified in the cmd= key that way if his tool sees that string then it knows to send the bios string that is found to the cmd. For instance:

CMD=".\keychange.exe" @Bios

Could return:

CMD=".\keychange.exe" Compaq

Then keychange.exe could be a tool that will change your key according to the manufacturer code sent to it. ;) If a manufacturer code is not found then it can open a box asking for a valid key on first boot.

I can make the keychange.exe if needed. ;)

Sounds great to me! :)

Is there a way to add detection for what version of XP is being used? maybe another switch on that that would insert a different key that is provided depending on if it is HOME or PRO or MCE... for those of us who like to be legit? ;)

0

Share this post


Link to post
Share on other sites

>I’ve used jellybean numerous times in OEM <-> OEM, OEM->ROYALTY, ROYALTY<-OEM situations

I'm told an old version of Jellybean will change a lot more than the new one. I never tried to figure it out.

@Randy Rhoads

Have you checked your DigitalProductID tests with MGADIAG to ensure that there is no diagnostic?

>for those of us who like to be legit

??? It's not a matter of being legit. You must have a key that matches the version you're installing. For those of us who want to be super legit, we want the correct Royalty key to match the hardware. Deploying one key set to all hardware is the right way for a smacked bottom, just as the keygen'd VLK keys have turned out to be.

Edited by severach
0

Share this post


Link to post
Share on other sites
I'm not going to worry about MCE at the moment.

Should'nt have to. MCE uses the same files, just have to use a specific setuup.ini pid value, the MCE cab files directory in the source root, and a MCE slp key.

Ive tried every keychanger i can find; MagicJelly, keyupdatetool, rockxp, keyviewer, and some others and nothing will change this key. I even edited oobetimer with all values of "FF" rebooted and it was still activated. The only thing that will change my key is that reg file.

Edited by Randy Rhoads
0

Share this post


Link to post
Share on other sites

I asked siginet about this, and his board pointed me this way. Seems like this implementation might make this a little easier...

would it be possible to add support for royalty AND non-royalty oem licenses? So if it failes to identify a SLP, it defaults to the last entry. Here, you could copy the oembios files from the real XP OEM disk, and run a script that prompts for the serial on the sticker. For example:

[iBM CORPORATION]

PATH="\IBM\"

CMD=""

[TOSHIBA]

PATH=".\TOSHIBA\"

CMD=""

ELSE

PATH=".\OEM"

CMD=".\PromptForChange.exe"

on another note...

I've already created a .vbs script that changes the key that takes a file (containing a key) as an argument. it works successfully in sp2 to change my key. For example:

cscript changekey.vbs "..\dell\serial.txt"

would this work for this project?

then we could have this entry:

[DELL]

PATH=".\DELL\"

CMD="cscript changekey.vbs "..\dell\serial.txt""

Edited by TheUni
0

Share this post


Link to post
Share on other sites

Sounds nice, right now I’m busy disassembling Microsoft’s Genuine Advantage code to better understand how OEMBIOS files work, I don’t have much time to add it.

If you want a quick hacked solution.

[AMI]

CMD=".\PromptForChange.exe"

[AWARD]

CMD=".\PromptForChange.exe"

[PHOENIX]

CMD=".\PromptForChange.exe"

put at the end of the oemscan.ini file will have the same effect as ELSE :)

0

Share this post


Link to post
Share on other sites
Sounds nice, right now I’m busy disassembling Microsoft’s Genuine Advantage code to better understand how OEMBIOS files work, I don’t have much time to add it.

If you want a quick hacked solution.

[AMI]

CMD=".\PromptForChange.exe"

[AWARD]

CMD=".\PromptForChange.exe"

[PHOENIX]

CMD=".\PromptForChange.exe"

put at the end of the oemscan.ini file will have the same effect as ELSE :)

Or you could search for a string that appears in every BIOS.

[SM]
CMD=".\PromptForChange.exe"

0

Share this post


Link to post
Share on other sites
on another note...

I've already created a .vbs script that changes the key that takes a file (containing a key) as an argument. it works successfully in sp2 to change my key. For example:

cscript changekey.vbs "..\dell\serial.txt"

Does this detect the difference between Home & Pro? so it can be made universal
0

Share this post


Link to post
Share on other sites

the key isnt what changes the distro btw home and pro. They're different disks.

afiak you'd still have to use a home cd to install home and a pro to install pro. if you're wanting to do both, you should look into Powerpacker made by siginet.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.