Kelsenellenelvian

Sorry, I missed your last reply. Please attach your config.js. (In the wpiscripts folder) Coupla questions: Did you delete the tools folder? When and how are you starting WPI? Also please note - The reboot.js error has been fixed for those people that have been getting the reboot.js error. I can send you a script or new setupcomplete.cmd to start WPI with that should fix that error if that is the one you are getting.

Actually when using conditions and exclusion the proper term is like so: ConnectedToInternet()=="False" The above will make the entry disappear if you are connected to the internet. YES I know it's not in the manual, the manual is in the process of being re-written and should cover everything this time. (I just hate the bookwork ) Nearly everything can be found in the changelog though... With this I would add the reg as a totally separate entry with the needed condition added in, be it looking for a file, a program is installed name or anything like that. then just add it as a dep to the parent program.

You're very welcome. ;-)

%root%

No your path does not HAVE to be WPI\install. You can use direct paths, %root%, %Cdrom% and really andywhere you wish. It's just easier to troubleshoot and explain if it is at wpi\install.

The thread was also posted last 2 years ago... The original post is way over 3 years old.

This is your main error. You need to be on a x64 system to make a x64 disk.

Ok just for giggles (I used to get that before in the earlier days). Please do the following: Move the txtsetup.oem file into the x64 folder like in the pic I added. Then after running nLite but BEFORE making iso put the sys file in the I386 folder. (Just so that setup can see it for sure) Hopefully if you found the right drivers everything will be fine...

OK dav pm me with a messenger addy if you have one. It is time to really get this sh*t fixed for you.

http://www.wpiw.net/downloads/winntbbued_3.1.exe

You are obviously not using the right drivers as you HAVE to have the txtsetup.oem file that goes with them. Try using the massstorage drivers pack from http://driverpacks.net/

I really think you need to stop "Finding" and "Aquiring" versions of Windows XP it is illegal. Once you have BOUGHT a copy of XP then you MUST have the proper drivers with an .inf, .sys and a txtsetup.oem file (Note the OEM file is the key file you have to have.)

Yes you do. Hence why ryan's pack is called "Post-sp3"

English Please.

Can you post your vLite preset? I have gotten both errors before but not at the same time.

http://www.wpiw.net/downloads/ncab-211.exe This will make a "lite" nero 6 for you.

simply use /S (Note the CAPITOL "S")

Thats the rub though. Thats a "generic" OEM key that only matches the proper oem's disk and will only activate with thier disk.

OOOoOoooO I test!!!! Me me me me! Please I would like to test. One of my sons PC's is a win2k box.

Massstorage drivers.

WPIPATH is supported in execute before\after just it doesn't auto truncate.

LOL I would say Win2000 or XP!!! J/K Seriously though you need to update the core stuff first: DRIVERS IE6 DX9 WMP then SP's and extras. Then maybe Drivers again (Sometimes they get fubared with all of the updates)

No you don't need the autorun files if you are using it in an XP\WPI combo disk.

OK copy JUST the Run_WPI.exe into the $oem$ folder and open the existing cmdlines.txt with notepad then enter (really anywhere except the first line) "Run_WPI.exe"

NO FLASHING DOS WINDOWS...!!! God I hate those also.