Kelsenellenelvian

Well heck I DO HAVE the last version! Please instead of running WPI.hta place this in the WPI folder and use it. Then tell me the result.

WOW thats a hell of a project OK it looks like CDROM is not getting defined. (you are right) look at the variables section of your 2 logs. I will ask mritter to send you the .exe run file that we are instituting on monday when he gets home. For now though: How are you starting WPI?

Can you include a pic of your folder layout?

It has been said many many times that with win7 and vlite you cannot use the ua settings page. I am willing to bet that is your issue...

Windows SteadyState is free for genuine 32-bit (x86) Windows XP and Vista user and can be downloaded from Microsoft Download Center. WGA validation has to be passed before downloading, 64-bit operating system is not supported though.

'{EXTRACT} %CDROM%\\DVD-Apps\\FlexRena80.rar "%ProgramFiles%\\Flexible Renamer"' Try this

You removed "Manual Install and Upgrade" Thats were they went.

PM sent, topic closed...

You HAVE to use Vista-SP1 WAIK with vLite as it was NEVER (vLite that is) optimized or made for win7 wingapi.dll is part of WAIK and although WAIK is a free download you cannot distrubute only parts of it.

nLite IS NOT for buisness or corporate usage!!!

Your disk is bad... I just checked and those file do not even exist on a normal XP SP3 CD. Where did you get your source from?

NO derfinatly not one company... The iso just refers to the main format they use...

Might work... The SATA drive will be your biggest issue. HOWEVER, most drivers for XP work fine under 2000.

Glad you like WPI so much Now do me a favor= Before WPI runs add this into a .reg file and execute it Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main] "Disable Script Debugger"="no" "DisableScriptDebuggerIE"="no" Then run WPI with Office 2007

Sorry I though my WHOLE post went through... This is a common error due to application error reporting in Internet Explorer. How old is your run_wpi file? We instituted fixes for this awhile ago. However, it seems to me that your setup is not getting the fix... Couple more questions: Which version of IE do you have on your disk? If IE6 -- Is it an unmodified disk?

No it doesn't.

"molex to sata floppy power" <-- I had to add the last part to find a better list. Sorry here is the google result: http://www.google.com/search?q=molex+to+sa...amp;startPage=1

Its a "Molex to SATA" adapter. Goolge it, there everywhere. http://www.tigerdirect.com/applications/Se...8&CatId=790

http://esupport.sony.com/US/perl/swu-list....&SelectOS=7 Here are the drivers for XP. Sony says it is fully comatable. Windows 7 is however AWESOME!!!

OMG.... I see now why you say 5&6 are similiar. My bad... (Slams face on keyboard over and over again) Damnit How in the hell could I do that?

OK you ask some tough questions. I am working on the manual tonight, so your opinions will be taken into consideration. NOW for the meat of your post: WPI has gone into MAJOR development lately. there is scads of things in there that have barley been touched on. While the changelog is informative and the manual does show all of them the options are endless. There are dozens of conditions to check for nearly anything in a os and the hardware. Please check chapter 5 & 6. Plus mritter is adding ALOT more each version. Checking for a vm install is pretty easy if you check on a reg key or even a VM specific piece of hardware. To run WPI fully silently you just put timer=1 or even 0 after configurating using the cmdline switch or through the options wizard. Now for the feature request you can use the new JSCRIPT addshortcut feature mritter JUST added and add a short to the desktop to run WPI after the initial run with different switches so the user has time to choose the apps. There is several ways to do this. mritter might have a better idea on this too. As for the slow time. I bet you have a CD\DVD in your main drive right? WPI checks for that. Also the "Allow check for a internet connetion" may slow down the start process abit. Please take some time to read the changelog and rest of the manual, you will see that there are close to, if not over a hundred newer features in WPI that EVERYone is still getting used to. v8 (Comming soon) Will have a HUGE new Network Wizard tab and Even the ablity to set user profiles up. mritter is a wizard at this! Untill last year WPI barely had NO manual to speak of. (I hate the bookwork and so does mritter) I have been concentrating on the manual. I see now that we need to get more technical with it, I had based it on just the base functions and a new user. I will make the next version much more informative. I already added 2 new chapters to it so I have plenty of room. I was recently donated a demo video software maker so I will strive to put out a mid level configuring WPI video soon. Not untill Tue at the earliest as the weekend is really busy for me.

Yes it does. Kinda hard to figure out to get it to work though.

YES!!! THANX OK my disk is built with easyboot as the base, but instead of 2 XP folders I only have 1 and one is setup to recognize and use "autoi.sif" (Renamed Winnt.sif file) and the OEMpreinstall=yes in that for custom files, themes and such. Then 2 is a standard-non-extras setup for when I need to reinstall on a pc that isn't my main one. I am attaching a pic of my simple boot menu. Right now I am working on adding ubcd4win (The legal thing, not the pirated boot disk) to it so I will have an extra option. Thanks for the comments!!!

for /f "delims=: tokens=1" %%i in ("%~dp0") do set drive=%%i: set wpipath=%drive%\wpi SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\WPI /V 1 /D "%wpipath%\WPI.hta" /f JUST Checked the internal code and it reads as above. It will see WPI and run it just fine even if you bury it several folders deep.

I am not sure if this step is right. As I understand it and see it the OS install looks for the OEM folder at the root. My dual OS disk does (But mine is rather different) Easy to test after setup run a vm test and see if the OS recognizes it or not. If not then Copy it and place it at the proper install dir of each OS folder. The RunWPI Files are built to where they "Should" see the WPI folder at the root and run it no matter where theyu are physically located at. Now they might need abit of tweaking but I am willing todo that for you. You'll just have the fun of testing