alfa1 Posted February 9, 2008 Share Posted February 9, 2008 Hi there.Ive notice that after slipstreaming SP3(latest build) into Windows XP SP2 volume licenses, it will no longer accept my current cd key. ive tried to replace the pidgen.dll with the one from the sp2, then it did not ask for a key but at the last part of the installation i get endless error while setup is doing the saving part, complain that an error accur while trying toverify licence.i also tried this mathodhttp://www.msfn.org/board/xp-sp3-cd-key-t1...481#entry732481and used a random key found in i386\pid.inf, the result where that i end up having a 30 days trial version.I tested it on a fresh install and did not remove anything only Unattended it.the only way i could install SP3 is by adding it via svcpack.inf. this work perfect and windows is genuine activated again .This method sucks. is there a fix for that or am i doing anything wrong?Please advise.P.S= i notice that the Unattended process will still show the computer name screen with the pri configured name in it and will have to click next.this is only happen when using hide pages. fully Unattended has no proplem. Link to comment Share on other sites More sharing options...
Etz Posted February 12, 2008 Share Posted February 12, 2008 Hi there.Ive notice that after slipstreaming SP3(latest build) into Windows XP SP2 volume licenses, it will no longer accept my current cd key. ive tried to replace the pidgen.dll with the one from the sp2, then it did not ask for a key but at the last part of the installation i get endless error while setup is doing the saving part, complain that an error accur while trying toverify licence.i also tried this mathodhttp://www.msfn.org/board/xp-sp3-cd-key-t1...481#entry732481and used a random key found in i386\pid.inf, the result where that i end up having a 30 days trial version.I tested it on a fresh install and did not remove anything only Unattended it.the only way i could install SP3 is by adding it via svcpack.inf. this work perfect and windows is genuine activated again .This method sucks. is there a fix for that or am i doing anything wrong?Please advise.P.S= i notice that the Unattended process will still show the computer name screen with the pri configured name in it and will have to click next.this is only happen when using hide pages. fully Unattended has no proplem.Try "read-only" mode... Link to comment Share on other sites More sharing options...
Innocent Devil Posted February 13, 2008 Share Posted February 13, 2008 just replace pidgen.dll of SP3 cd with that of SP2. it simply works Link to comment Share on other sites More sharing options...
k3wf3w Posted February 13, 2008 Share Posted February 13, 2008 Hi there.Ive notice that after slipstreaming SP3(latest build) into Windows XP SP2 volume licenses, it will no longer accept my current cd key. ive tried to replace the pidgen.dll with the one from the sp2, then it did not ask for a key but at the last part of the installation i get endless error while setup is doing the saving part, complain that an error accur while trying toverify licence.i also tried this mathodhttp://www.msfn.org/board/xp-sp3-cd-key-t1...481#entry732481and used a random key found in i386\pid.inf, the result where that i end up having a 30 days trial version.I tested it on a fresh install and did not remove anything only Unattended it.the only way i could install SP3 is by adding it via svcpack.inf. this work perfect and windows is genuine activated again .This method sucks. is there a fix for that or am i doing anything wrong?Please advise.P.S= i notice that the Unattended process will still show the computer name screen with the pri configured name in it and will have to click next.this is only happen when using hide pages. fully Unattended has no proplem.Try "read-only" mode...What do you mean exactly?Do you need to make pidgen.dll read only after replacing it? Link to comment Share on other sites More sharing options...
Innocent Devil Posted February 14, 2008 Share Posted February 14, 2008 it doent matter just replace the new pidgen.dll with old one from sp2now it will accept u r keys Link to comment Share on other sites More sharing options...
alfa1 Posted February 14, 2008 Author Share Posted February 14, 2008 (edited) just replace pidgen.dll of SP3 cd with that of SP2. it simply works As i wrote before, This method is NOT working with Corporate version. its only give u a way to pass the cd key input requirement , once the install finish and the system try to confirm the ur serial no. u will see this endless error. this happen when the system first try to save setting before reboot.Now i tried all other method with no luck.1.replace pidgen.dll of SP3 cd with that of SP2 = fail .2.replace pidgen.dll of SP3 cd with that of SP2 and set read only = fail3.set unattandend to read only= fail.upgrading SP2(nliting or not) to SP3 after install has no problem what so ever.I think that....1. as of SP3 windows is no longer supporting the Corporate version CD keys method found in SP2.2. could be that nlite is not 100% compatiable with SP3 as some users report.3. as i wrote on my first post, not all options found in nlite is actually working with SP34. Could be because of VMWare.So for those that managed to get it to work, could u please give more information. read only is not enough info.P.S= the above tests made using the latest SP3 build, slipstreaming Windows XP Pro SP2 Corporate version without modifing anything. and running on the latest version of VMWare.this images shows the error(on VMWare) u get when i replaced pidgen.dll with the one from SP2 Edited February 14, 2008 by alfa1 Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted February 14, 2008 Share Posted February 14, 2008 I dunno what your problem is but my VOL is working super... Link to comment Share on other sites More sharing options...
alfa1 Posted February 14, 2008 Author Share Posted February 14, 2008 I dunno what your problem is but my VOL is working super...could u please give more details as of ur installation. 1.did you slipstream it using nlite?2. did you replaced pidgen.dll or deleted it and just added the one from SP2?3. Did you set permission on the above file?4. have u made any modification to the source files?5. in SP3/I386 folder there is a pidgen.inf, did u remove it?I just confirm it and its NOT a VMWare issue. ive burned the iso and tried it on 2 machines, as well as tried it with 2 versions, English and Japanese both Corporate versions. Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted February 14, 2008 Share Posted February 14, 2008 lets see here1 = yes2 = no3 = no4 = lots but none that are different form my sp2 builds or would affect the whole key\installation proccess5 = yes there is and no i didn'tYour key might be one of the newly blacklisted ones. They add more with each service pack... Link to comment Share on other sites More sharing options...
Etz Posted February 14, 2008 Share Posted February 14, 2008 I dunno what your problem is but my VOL is working super...Also my VLK disc, without any pidgen.dll replacement... Link to comment Share on other sites More sharing options...
alfa1 Posted February 14, 2008 Author Share Posted February 14, 2008 (edited) Your key might be one of the newly blacklisted ones. They add more with each service pack...My key works fine.upgrading SP2 is not a problem at all. as well as all other windows related appalication. Could u confirm and post your build no? Edited February 14, 2008 by alfa1 Link to comment Share on other sites More sharing options...
jkey Posted February 14, 2008 Share Posted February 14, 2008 Works perfectly for me please attach Your last session.ini Link to comment Share on other sites More sharing options...
Innocent Devil Posted February 15, 2008 Share Posted February 15, 2008 (edited) isnt that erro due to improper version (VLK,OEM,RTL)/key combinationcheck ur setupp.ini for Pid=XXXXX270did u activate it by "oobe/msoobe /a"EDIT: checked with v3300 and found working even without swaping pidgen.dll Edited February 16, 2008 by Innocent Devil Link to comment Share on other sites More sharing options...
alfa1 Posted February 17, 2008 Author Share Posted February 17, 2008 isnt that erro due to improper version (VLK,OEM,RTL)/key combinationcheck ur setupp.ini for Pid=XXXXX270did u activate it by "oobe/msoobe /a"EDIT: checked with v3300 and found working even without swaping pidgen.dllIm not sure of what you mean.i can upgrade my running SP2 with out any error. system properties show Service Pack 3, v3.264i did not use any activation, only used my cd key. Link to comment Share on other sites More sharing options...
severach Posted March 12, 2008 Share Posted March 12, 2008 (edited) ... Edited March 12, 2008 by severach Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now