Kelsenellenelvian

WE DON"T DISCUSS THAT HERE!

/VERYSILENT

Just not a tiny one.

Its is one of the best tools around but it also needs to be updated.

Thats why there is the reg file that WPI.cmd runs before the installation process. The reg file takes care of both errors and the regtweak is reset after WPI is done running. You must have ran WPI.hta to begin your install or deleted the reg section from WPI.cmd.

WPI needs a web button for use in signatures and on websites. Please let me see what you can come up with. Ideas = A planet and the words "WPI" & "Revolutionizing Installations" (Note "WPI" is a must! The rest are just ideas)

Do you have a cold? LOL j/k Anyways yes a regular DVD player will read and play dual-layer disks.

It's actually pretty easy just wait for a week and the new pack should be out. Actually it is rather difficult to do but you may want to ask this question over at Ryan's forum.

WPI in no way modifies your iso or windows setup files.

Thanls for the heads up!!!

OK link added to the first post make sure to read the readme in the archive.

After some of the help I have gotten from a couple of the members here I have finally started to figure out how to make custom bootmenus! Still got some work to do on figuring out a couple of things with EasyBoot and how to add in more boot options. Here is a pic of what I have so far! I am willing to share the files with anyone. I really must thank C01eMaN and iainstott for their wonderfull help and ideas I got from them. Download here ----> www.wpiw.net/downloads/2bootmenu.rar Size - 406 kb MD5Hash = C5F7FEAFD5829CB979267F6C80228EAE

XPero has stated before he will wait untill IE7 goes final.

OK Here goes. #1, You can have WPI just start the programs and manually add in all of the info needed switches are not necessary. #2. EXE or MSI WPI will run them the same just as if you manually started the program your self. #3. There is no real benifit to having all of the applications in seperate folders in the install folder. I have all of my installer packages in the install folder and only one subfolder for registry tweaks. #4. Your cdroot should look something like this: I386 WPI ---->install ---->graphics ---->common ---->wpiscripts ---->wpi.hta win51 wpi.ico #5. Yes #6. no you do not really need to keep the nLite last session on the disk. Either run XPize to patch your I386 folder or run it after windows is installed through WPI either way works fine. Personally I patch the setup files. I have no clue about the drivers packs I keep them on a seperate CD just for troublesome systems that I have a hard time finding drivers for.

I don't have the time right now but in a couple of hours I will answer all of your questions.

XPize does not work with 64 bit windows.

I msut have missed this post at some time yet I am very willing to help in any way I can (Testing and ini file writing) whatever you need.

Hey thanks I will look into it.

It is forbidden I would remove it very quickly if I was you.

Are you aware you just posted info about cracking WGA or are you being facetious?

I smell a banning coming on!! Links/Requests to warez and/or any illegal material (porn, cracks, serials, etc..) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will also not be tolerated.

Sorry to ask and please don't flame me too much but I am asking to see if any one has a pre built boot image\loader for a dual XP pro disk? I want to setup a dual XP pro one for unattended installs and one for regular installs. I know all of the stuff like optimization and folder layout and such I just cant quite get the hang of doing the boot menu. Can someone help me and maybe share theirs if the have one written?

It is actually a lot easier than that just copy over your config.js file into the newer version.

WPI 5.0 is going through major changes. We are in the near final testing stages now. Might be a week or 2 though we still have a couple of major issues to work out. Development is going at a crazy pace. You guys should love all of the changes.

Did you patch your uxtheme.dll?