Hi everyone,

I own an original copy of an OEM XP SP1 Home CD (french version).

I slipstreamed the SP3, hotfixes and some drivers (SATA, Chipset, LAN and Audio), and everything went fine for the first part of the install.

Unfortunately, it says that the product code is incorrect, although I entered it in the last steps of nLite.

What's worse is that I cannot bypass this step, when leaving the fields blank and asked if I wish to enter it later (it normally says that the input of the CD Key is highly recommended, but not derogatory at this time of the install), it simply won't do anything and I basically have no other choice than typing in the CD Key.

I enabled the "OEM install" and used "Provided defaults"... perhaps the issue comes from that ?

I msut say that I used nLite on my laptop, which is using the Windows 7 RC. (for now, i don't have access to any other computer witb XP)

I've attached my last session.ini file, if you ever need it.

Thanks for your help.

Last_Session.ini

I msut say that I used nLite on my laptop, which is using the Windows 7 RC. (for now, i don't have access to any other computer witb XP)

There's your problem. You need to run nLite on a Windows XP or a Windows Server 2003 machine. There's are issues (like the one you're having) when running it under Windows Vista and Windows 7. Your best bet without a Windows XP machine would be to temporarily install Windows XP in a virtual machine and run nLite from there (you can use your OEM copy - it won't activate, but that's fine).

Thanks for your reply. My OS is the problem then.

I didn't say it in the first post, but I set nLite for Windows XP compatibility in the properties. Isn't that supposed to fix the Vista/7 instability ?

sublow, sometime Compatibility mode will help but in your case you are slipstreaming an SP and that will not work. It is possible that you can run nLite under Vista (or W7) as long as you don't slip the SP. I would suggest you continue running Compatibility Mode. Also, please make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

It`s a well-known bug: http://support.microsoft.com/kb/950722

At my "German-WinLite.de" a user came up with a solution:

http://www.german-winlite.de/wbb/index.php...p;threadID=1969

It says you got to replace (after nLite) the "pidgen.dll" with the one from

the original XPCD (maybe SP2). It didn`t proof that, bur give it a try.

Thanks.

I'm currently trying g-force's experimental method, we'll see where it leads me but i'll keep you informed.

I was thinking: Win 7 comes with a Windows XP virtualization thingy, can I use it for a nLite-running platform ?

Thanks.

I'm currently trying g-force's experimental method, we'll see where it leads me but i'll keep you informed.

I was thinking: Win 7 comes with a Windows XP virtualization thingy, can I use it for a nLite-running platform ?

Heh... I forgot about that. I don't think anyone's tried it yet, but I don't see why it wouldn't work. I'd say try g-force's method first and if that doesn't work, use the Windows XP virtualization layer (or whatever it's called) in Windows 7.

sublow, don't know. Please give it a try and let us know. Enjoy, John.

Win 7 comes with a Windows XP virtualization thingy, can I use it for a nLite-running platform ?

I never tried to. If you do so, please report so others can benefit.

Ok, g-force's method didn't work, at least in my case (French WinXP Home OEM SP1)

I'll try the Win 7 virtualized windows XP...

Edited July 17, 200917 yr by sublow

Try integrating SP2 then SP3. I know it doesn't sound "normal" but some people reported it worked.

sublow, I am curious what version of PIDGEN.DLL you used. I extracted an ENU version of SP3 (using 7-Zip) and found two copies, version 5.1.2600.5512. The really strange thing is that they are the same size but the hashes are different. In a while I will try extracting SP3 with its own process and see what I can find. Perhaps one of these SP3 PIDGEN.DLL's will work on g-force's fix. Enjoy, John.

EDIT:I got the same two PIDGEN.DLL files when I extracted using the built in extractor.

Edited July 17, 200917 yr by johnhc

It`s a well-known bug: http://support.microsoft.com/kb/950722

At my "German-WinLite.de" a user came up with a solution:

http://www.german-winlite.de/wbb/index.php...p;threadID=1969

It says you got to replace (after nLite) the "pidgen.dll" with the one from

the original XPCD (maybe SP2). It didn`t proof that, bur give it a try.

Well,it has been posted here also:

http://www.msfn.org/board/index.php?showtopic=105980

http://www.msfn.org/board/slipstream-SP3-i...p2-t112325.html

though reports are controversial...

There is (maybe was) a report which I can only find through Google cache:

http://209.85.135.132/search?q=cache:DNIt2...pidgen.dll+msfn

where some other files are mentioned.

Maybe DPCDLL.DL_ ?

http://www.msfn.org/board/index.php?showtopic=128930

jaclaz

Some news

I tried g-force's method again (pidgen.dll file replace) as I noticed that I didn't made a brand new install when rebooting after being asked my CD Key (I just started again where it hung with the modified burnt XP cd).

So I must say it actually worked...until the first true boot, after the install's complete.

I get a message, vaguely saying that my CD Key cannot be precisely read (error message 0x80004005)

So I searched for it in the windows knowledge base: http://support.microsoft.com/kb/306081

Fine, lets reboot from the XP cd then...problem, I don't have any access to the repair console (R key) !!! What do I do now ?

I'm getting really really annoyed now. I first used nLite because it was the only way for me to include SATA drivers, having no floppy drive anymore, but it's been worse and worse, i've got plenty unfinished or unusable XP installs polluting my drive and I still don't have any clue what is going to REALLY SOLVE that mess. (and I can't install the virtual XP module either).

How do I get the Repair Console on my XP CD ?

Thanks.

Edited July 17, 200917 yr by sublow

More news:

Read how to access the Repair console, sorry about that but I'm currently boiling inside.

Still, the MS fix didn't work in my case and I still have that error message saying that myKey can't be read.

I'm never gonna have a functionnal XP install now !