It has more security features and other added bonuses, I wont go into detail here but it would be very nice to have.
PIDGEN for ENT SLP OEM Dear, pls, upload DPCDLL.DLL & PIDGEN.DLL compatible with 2003 ENT SP2 SLP OEM key for making OEM CD Thanks in advance
Indeed, it is. A test installation in VMware confirms this -- see attached image. [Edit] You need to check the PID, though. The key is verified by BINK 0x59, thus the seven digit part should read 4411902, not 4211904. (42XXXXX seems to indicate non-R2 setups while 44XXXXX is probably used for R2 keys.)
Thanks for the time to test it. Yeah, the PID I used was gave using a 2003 key tester and wasnt from a real install output. I noticed R2 keys have a upper range on the last 4 digits as well. Examples:
That's interesting. I'm not sure, however, whether this implies a technical limitation or ist just the result of an internal numbering scheme at MS. Something else: Embedded into pidgen.dll, there's a list of valid PID ranges for each ECC key. That's why MS can use the same ECC key for Standard as well as Enterprise editions -- they just define different serial ranges. This is the list for R2 Enterprise: Code: Empty KeyID (DD) Low bound High bound Flags 0x0000 0x54 (42) 071-000000 082-999999 0x00000022 0x0000 0x54 (42) 084-000000 084-999999 0x00000022 0x0000 0x54 (42) 357-000000 361-999999 0x00000022 0x0000 0x54 (42) 367-000000 369-999999 0x00000022 0x0000 0x54 (42) 771-000000 774-999999 0x00000022 0x0000 0x54 (42) 779-000000 780-999999 0x00000022 0x0000 0x54 (42) 786-000000 787-999999 0x00000022 0x0000 0x54 (42) 789-000000 789-999999 0x00000022 0x0000 0x55 (42) 119-004000 119-004999 0x00000022 0x0000 0x55 (42) 119-006000 119-006999 0x00000022 0x0000 0x55 (42) 132-000000 161-999999 0x00000022 0x0000 0x55 (42) 163-000000 163-999999 0x00000022 0x0000 0x58 (44) 071-000000 082-999999 0x00000122 0x0000 0x58 (44) 091-000000 092-999999 0x04010122 0x0000 0x58 (44) 101-000000 102-999999 0x04010122 0x0000 0x58 (44) 286-000000 290-999999 0x00000122 0x0000 0x58 (44) 786-000000 787-999999 0x00000122 0x0000 0x58 (44) 793-000000 793-999999 0x04010122 0x0000 0x59 (44) 119-004000 119-004999 0x00000122 0x0000 0x59 (44) 119-010000 119-010999 0x04010122 0x0000 0x59 (44) 132-000000 161-999999 0x00000122 0x0000 0x59 (44) 176-000000 177-999999 0x04010122 I'm not sure whether these constraints are exhaustive, as I did not check the whole PidGen code. Also, the meaning of the "flag" bytes is unclear. The third byte might imply the R2 status, but other than that ...
Are any other files required for the conversion from retail/VKL media to OEM? (apart from the obvious oembios*) Thanks sebus
VLK 2003 to OEM is the same process and file swaps as VLK XP to OEM. The files will be: DPCDLL.DLL, EULA.TXT, OEMBIOS.BIN, OEMBIOS.SIG, OEMBIOS.CAT, OEMBIOS.DAT, PIDGEN.DLL, SETUPREG.HIV, NT5INF.CAT ======================================================= Retail 2003 to OEM should be the same as XP, but I havnt tried it as I converted from VLK. For Retail, you just copy over the 4 OEMBIOS files, change the PID value in the SETUPP.INI to OEM, and use a SLP key. Now, you must have a real retail copy, not the evaluation copy, as it requires extra files to be swapped, but can be done.
Thanks, I have VKL media (downloaded straight from MS Licensing site) Of course I could use VKL key (but that is no fun) Which DPCDLL.DLL, PIDGEN.DLL, SETUPREG.HIV, NT5INF.CAT are to be used? Are they Server media specific? or they can be the XP versions? In the first post there are only 4 OEMBIOS files (which as it seems are good for the retail) Thanks sebus
You used the wrong SETUPREG.HIV file, the one you grabbed is for Enterprise Edition. Throw that 2003 disk you just burned in the trash, add the Standard Edition SETUPREG.HIV file to your ISO image, save changes, and reburn the cd over. Do a format and re-install of 2003 with new disk. This should fix the R2 issue as well. Attached the correct file for you.
And thank you very much for this Suicide Solution, appreciated (and also explanation why it happened) What a change a little file can do..... sebus PS Is it all controlled just by (Default) in setupdd key? EDIT Using Retail discs/isos like direct downloads from MS site ie. en_win_srv_2003_r2_enterprise_with_sp2_cd1_X13-05460.iso works like expected with only oembios*, setupp.ini & winnt.sif files needing replacement to be fully activated on Dell PC
Does the same hold true for SBS 2003? I have HP OEM install disks, what is needed to change to DELL. Thanks
To change from "HP SBS2003 OEM" to "Dell SBS2003 OEM" wouldn't you just need to change the OEMBIOS fileset ?