traumphase

hi there, i have read alot of threads in here and out there in the other world. still got no answer to the following: i use windows xp sp1 german integrating sp3 and future updates. then i create the following oem directories... $OEM$ ├── $$ │ └──Temp └── $1 └──Temp both TEMP directories have some files in it. as far as i know windows copies those $$ and $1 files and directories to harddisk while txtsetup. what if windows does not? how to test what went wrong? could vmware easy-install produce this error? do i have to add entries to any other files besides winnt.sif? excerpt from winnt.sif [Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes UnattendSwitch="yes" TargetPath=\WINDOWS would be nice to have some help DEBUGGING this... traum

hi jootfish, i experienced something near it with nlite and/or creating xp on a vista system. nlite (1.4.9.1) seems to imply files from vista system instead of using the given files and directories. use a running windows xp system to create the disc and maybe you go the steps up to sp3 + updates manually instead using software for it. at least you should know if its nlite which makes the mess! check your pidgen.dll. the new ones reject my oem key (my key is original and never used twice, not blackliste and works with the sp1!) cheerz traum