trackfan

I followed your suggestion and copied setupp.ini from current install . Is that what you suggested or should I have modified the file? I got through an unattended setup until dreaded volumne lisence key popped up, It rejected code I used in nlite /winnt.sif questionaire. The setupp.ini file is [PID] Extra Data= 28 or so digits PID=8 digits where as the OEM copy puts "OEM" in the insignia. Do you have any suggestions where I may have mucked this up?

At the risk of sounding a bit dense......volume lisence then won't work with systembuilder OEM or is it restricted to retail or boxed version only? "Doesn't work" meaning OS won't boot ? Any tips how to best keep an OEM lisence fresh? My problem is that the current corporate or volume lisence I am using has been heavily modified and for some reason I can't seem to get past Sata driver installs. I followed Beginners tutorial and use n-Lite but gotten frustrated enough to just go out and buy the darn OEM copy for a buck fourty.....

Hey Lord B......not intending to hi-jack your thread, hope you don't mind if I ask a related question.... Based on experience posted in this thread, is the following scenario possible? Purchased OEM System Builder XP Pro SP2 and just cracked seal to make ISO image and use that image to get a copy ontro my HD. I have a valid volume liscence key that I currently use in my OS. Can I use OEM version .....tweak it.... and then use volume lisence to activate? I am building a new system but don't like the idea of marrying an activation key to my set-up Any response is appreaciated.