[Licensing question OEM vs. Retail]

There are only four varieties of disk - a 32-bit Vista installation disk and a 64-bit Vista installation disk for RTM (meaning non-SP1) and a 32-bit Vista with SP1 integrated and 64-bit Vista with SP1 integrated.

What about Vista Enterprise? The four Vista x86/x64 RTM/SP1 comes with Home, Home Premium, Ultimate and Business, but not Enterprise.

Enterprise Version takes another DVD, i have the Enterprise SP1 ISO from MSDN... about 2 GB, because only have Enterprise version...

[Windows XP Pro Corp VLK]

Bigger companies are target now, like the Coca Cola company in Querétaro, they had all but no legal Windows copies installed .

Not only Coca Cola, same as Querétaro government... they had used pirated MS Office, which has been replaced with OpenOffice :)

[Vista replaced by windows 7.... why?]

Because Windows Vista is Windows Millenium Edition Reloaded :)

[ISOs on MSDN vs slipstream, any differences ?]

Someone with a VL version wouldn't need to bypass the product key screen, as they'd have a volume key they could use without activation.

Its obvious and it was not the point, i'm only answering to

I suspect that's the answer you're looking for. The SP3 version on MSDN probably includes the option to bypass the product key during install where an RTM -> SP3 manual slipstream won't have that option.

that is not the difference between my two images.

the original question was about the differences between a retail copy of XP and an MSDN iso - VL was not a part of the question. I answered the question completely, but didn't touch on OEM or VL because that wasn't the question.

The difference that i have pointed was on a VL disk (RTM+SP3 slipstreamed vs MSDN SP3 iso both VL versions), sorry if i was unclear.

So you didn't answered and my question remain: why they differ ?

Why not compare uncompressed files?

For example, driver.cab is smaller in MSDN than RTM SP3 because of MS deleted old files... the newer are in SP3.cab only. Integrating SP3 on RTM only copies SP3.cab in I386, doesn't modify driver.cab to delete redundant files...

And other files compressed differ... but some uncompressed not

[Changing XP from/To OEM,Retail,Volume License]

Be carreful about manupilate xp cd. Be sure you have right disc and right license ....

I confirm the volume/corporate version has differents oembios files (7 files exactly) from retail, not just setupp.ini ...

Exactly.

I'm talking about 4 OEMBIOS, PIDGEN.DLL, DPCDLL.DLL and Setup.ini... I write in my last post that i replaced In XP Pro SP3 Corporate Disk that files from XP SP2 OEM Compaq, and turn it a Corporate Version into a Royalty OEM Version... I installed Pro SP3 with generic key HP/Compaq and system is genuine, never tell me activate... WGA show my system is totally legal... because use of HP/Compaq OEM key...

My laptop is Compaq V2617LA and because is HP/Compaq i don't know if this CD works with my generic HP/Compaq key in others HP/Compaqs machines...

Edit: I downloaded HP/Compaq pack from matrixbk with purpose of compare my files with them... They're different... i don't know if that files work in my PC...

[Changing XP from/To OEM,Retail,Volume License]

Have you got an OEM version of XP but want a Retail or a Coporate Version of Window XP?

Well here is a way to do it, see below.

Please note you must own a legal copy with a legit CD Key.......

WinXP's setupp.ini controls how the cd acts. IE, is it OEM version or retail?

First, find your setupp.ini file in the i386 directory on your WinXP cd. Open it up, it'll look somthing like this:

ExtraData=707A667567736F696F697911AE7E05

Pid=55034000

The Pid value is what we're interested in. What's there now looks like standard default. There are special numbers that determine if it's a retail, oem or volume license edition. First, we break down that number into two parts. The first five digits determines how the CD will behave, ie is it a retail cd that lets you clean install or upgrade, or an oem cd that only lets you perform a cleam install?

The last three digits determine what CD key it will accept. You are able to mix and match these values. For example, you could make a WinXP cd that acted like a retail cd, yet accepted OEM keys.

Now, for the actual values. Remember the first and last values are interchangable, but usually you'd keep them as a pair:

Retail = 51882 335

Volume license = 51883 270

OEM = 82503 OEM

So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read:

Pid=51882335

And if you wanted a retail CD that took OEM keys, you'd use

Pid=51882OEM

Note that this does NOT get rid of WinXP's activation. Changing the Pid to a Volume License will not bypass activation. You must have a volume license (corporate) key to do so.

Hope this helps

Worf

And if you replace around 6 to 11 files in I386 folder of XP CD you can hack that CD to act activation process like a OEM, Retail, Volume etc...

For example, i have a Compaq V2617LA Laptop with Windows XP Home SP2 Spanish... I have created a Windows XP Pro SP3 CD with original OEM activation from Compaq with 6 files from my system over a Windows XP Pro SP3 Volume License...

The result is original Windows XP Pro SP3 OEM, and accepts other OEM Keys and ask to activate over the phone. Because I use the key in the registry (preactivated by Compaq) XP never tell me activate... I think is possible to make a Windows XP Home Volume License with these hacks but i don't achieve this for now...

[Multiple RDP sessions in SP3]

Hello everyone.

I have installed Windows XP Pro, with SP3.

I have replaced patched termsrv.dll in system32 folder

file size=

I have also created these entries in regedit:

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core]

"EnableConcurrentSessions"=dword:00000001

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

"EnableConcurrentSessions"=dword:00000001

Maybe I have wrong termsrv.dll file? could someone share it with me ?

thanks!

My trmvsrv.dll file is 5.1.2600.2055 English version.... It runs even on SP3 Spanish Version.... Do you have the correct version?

I don't know about breaking post rules if i'm if upload that file, i send you in PM if i can...

Edit: To remember everyone, you must replace termsrv.dll FIRST in C:\WINDOWS\SYSTEM32\DLLCACHE and until then in C:\WINDOWS\SYSTEM. If you don't replace the file in DLLCACHE, SFC will restore in SYSTEM32 the SP3 version...

[Multiple RDP sessions in SP3]

Yay! I got it working!

Yeah there's some registry settings. I'll see if I can find the .reg file somewhere...

I use two registry hacks with termsrv.dll SP2 Beta 2...

These are:

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Licensing Core]

"EnableConcurrentSessions"=dword:00000001

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

"EnableConcurrentSessions"=dword:00000001

With SP2 i have to edit some settings in gpedit.smc... But with SP3 i only patched those registry keys... And work it

What about XP Unlimited and Winconnect XP?, i had read about it. The patched XP Remote Desktop (termsrv.dll SP2 Beta 2) only allow 2 sessions, while the other programs allow 21 sessions, and of course, they're using Remote Desktop Protocol...

[Multiple RDP sessions in SP3]

Really? Hmm... I'll have to try that again, since so far it doesn't seem to have worked.

Multiple remote desktop sessions really works with XP SP3 with termsrv.dll from SP2 Beta 2....

I have running now and is the same as SP2 ... thought i'm using termsrv.dll SP2 Beta English version over Windows XP SP3 Spanish...

Don't worry about replacing the SP3 file with older SP2 beta...