[twig123]

Siginet, on Sep 20 2006, 12:36 PM, said:

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?

[severach]

>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.

This post has been edited by severach: 21 September 2006 - 12:07 AM

[Randy Rhoads]

Quote

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.

This post has been edited by Randy Rhoads: 21 September 2006 - 11:28 AM

[TheUni]

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""

This post has been edited by TheUni: 21 September 2006 - 06:40 PM

[xehqter]

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

[TheUni]

that almost makes TOO MUCH sense. Hah!

Brilliant. Thanks.

[Bezalel]

xehqter, on Sep 21 2006, 08:48 PM, said:

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"

[xehqter]

@Bezalel even better didn't think of that.

[twig123]

TheUni, on Sep 21 2006, 06:30 PM, said:

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

[TheUni]

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.

[FreeStyler]

TheUni, on Sep 22 2006, 08:36 PM, said:

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.

I dont see a problem why this couldn't... tweak the changekey.vbs or alike so it checks what kind of install it is home, pro or mce and specify which key to use...
doesn't sound to hard to acomplish

This post has been edited by FreeStyler: 22 September 2006 - 01:13 PM

[twig123]

TheUni, on Sep 22 2006, 02:36 PM, said:

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.

I am very aware of this, the reason for my asking is that I use the same update packs, drivers, and addin software for both my Home & Pro distro's... and it would be nice to not have to modify the keys and software every time I want to compile a different vesion. So, basicly if I would type in all the keys for Home and All the keys for Pro... and it would detect that is one or the other, and use the appropriate key.

[TheUni]

i see where you're going, i guess

i have 2 .vbs files.

1 for changing the key to a string found in a file. ie:
changekey.vbs "..\dell\serial.txt"

2 is for prompting for a new key. This is the case for a NON-Royaltiy oem sticker:
promptkey.vbs

for changekey, i guess i could have the script try more than 1 key for each file. That would be alot easier than checking for home/pro, then using that key. it would be easier to try them both. if one fails (if you try to use a home key for pro it WILL fail) then use the other

so your dell\serial.txt would just look like this:

123ab-123ab-123ab-123ab-123ab 'DELL XP Home Key
123bc-123bc-123bc-123bc-123bc 'DELL XP Pro Key

it wouldnt have to prompt you at all. just quietly use whichever one works
good enough?

This post has been edited by TheUni: 22 September 2006 - 02:56 PM

[twig123]

TheUni, on Sep 22 2006, 03:55 PM, said:

it wouldnt have to prompt you at all. just quietly use whichever one works
good enough?

Yeah, as long as it works... but I have seen some key-changers that allow you to type anything (after windows is installed) and it will change it to an invalid key, but windows complains after the fact. that is the only thing that I am concirned about.

But if it works, it works. Sounds good to me
Maybe after the scripts are complete, could you be so kind as to share the wealth?

Thanks

[TheUni]

sure

The script wont let you change to an invalid key. i've tried.
i haven't tested it during an install, but it works fine otherwise. i assume it'll work fine.

they're on my pc at home, i'll post when i get back.

[twig123]

TheUni, on Sep 22 2006, 08:44 PM, said:

they're on my pc at home, i'll post when i get back.

I'm patiently waiting, it sounds exciting

[severach]

>So, basicly if I would type in all the keys for Home and All the keys for Pro... and it would detect that is one or the other, and use the appropriate key

To install home & pro from the same disk, wouldn't you just use CDShell like everyone else? With two separate folders, there's nothing to detect. The Pro keys would live in the pro folder and the home keys would live in the home folder.

Seems to me the optimal way to produce the disk is to have CDShell test the BIOS and tell the user that the system isn't supported, instant confirmation, or continue installing the user's selected Windows. Half way through, a custom QFE, the same for all Windows, tests the BIOS again and updates the OEMBIOS set and another QFE, different for each Windows, changes the key. The key needs to be updated before the first logon before it is written to HKEY_LOCAL_MACHINE\SYSTEM\WPA\KEY-* where it is hard to delete.

[twig123]

severach, on Sep 23 2006, 12:15 PM, said:

>So, basicly if I would type in all the keys for Home and All the keys for Pro... and it would detect that is one or the other, and use the appropriate key

To install home & pro from the same disk, wouldn't you just use CDShell like everyone else? With two separate folders, there's nothing to detect. The Pro keys would live in the pro folder and the home keys would live in the home folder.

Seems like some ppl are missing my point...
I dont want 2 seperate scripts for when I compile my CD's. All the rest of the files that I use are universal... aka RyanVM Updates, BTS Driverpacks and can be used with Home AND Pro... why not the key script? I would rather have 1 big code to do so, rather than a seperate code for each version of windows... make sense to me, and would make it easier IMO

This post has been edited by discountpc: 23 September 2006 - 11:14 PM

[Siginet]

Hey xehqter...
Do you mind if I post some Integrator addons on my forum using your oemscan tool? It will make it much easier for people to use your tool. I think oemscan has pretty much made my tool, ("The OEM ACT") obsolete. Honestly I think oemscan is pretty much perfect the way it is now.

@discountpc I think the script TheUni is making will be exactly what you want. At least that is what it sounds like to me.

This post has been edited by Siginet: 23 September 2006 - 11:56 PM

[twig123]

Siginet, on Sep 24 2006, 12:52 AM, said:

@discountpc I think the script TheUni is making will be exactly what you want. At least that is what it sounds like to me.

I think so too, I just wanted to clarify for the people that didn't understand what I was requesting.

Thanks