Kelsenellenelvian

in your language file: Line 243 = txtCollapseAll[lang] = ['Collapse All']; "Collapse All" means "Fold all" or "Minimize all" Line 644 = Don't worry about this one the chances of it being shown are very small. 1016 - 1066 Not sure how to explain these Yeah so there is only 1 line that you really need to update.

I am sorry but I am having issues getting a chm to launch from within wpi's interface. I just don't have the time to dedicate to this right now.

Any news on this?

Updated manual

This is what I get:

Your key is in the file winnt.sif inside the i386 folder. Open it with notepad. Grab your old disk (the original) and a sp3.exe and make a whole new disk.

WOW I actually get a blank chm file when I open that.

I will look into it. Please send me a sample chm file.

Open api.js and change: (line 19) strFile=wpipath+"\\ReadMe.txt"; to strFile=wpipath+"\\ReadMe.chm"; and line 376 from: strFile=wpipath+"\\ReadMe.txt"; to strFile=wpipath+"\\ReadMe.chm"; then in information.js line 340 strFile=wpipath+"\\ReadMe.txt"; to str File=wpipath+"\\ReadMe.chm"; then in customthemecode.js change line 124 from: strFile=wpipath+"\\ReadMe.txt"; to strFile=wpipath+"\\ReadMe.chm"; PLEASE ALSO REMEMBER!! WPI is NOT free for business or corporate uses...

Thank you for the translation... Extra Buttons??? WTH would you use them for? Adding buttons is pretty code intensive and there is NO way to make easy ad-able buttons (plus when all the buttons that there are total are active the left side is pretty full)

Hmmmm lemme ask: WHY not use the %wpipath% variable as is and always has been shown in the exaples???

I really dont understand what your issues are. I have imported several regfiles files for all 4 branches since the inception of WPI and never had an issue.

Hey guys? WHY are we not usig the proper WPI commands to pass a reg file? {REGEDIT} "%wpipath%\Install\RegFiles\Smalliconsinstartmenu.reg"

You are not listening: I gave you a perfectly fine answer with your existing setup... Just change the **** comandline it works fine that way. Otherwise you have to change ALL of your folder structures and commandlines... You are completly wrong when you say the installation files are not on the c:\drive. the way you have set it up the windows installation process copies them during windows setup...

Lemme ask you 1 thing: WHY go trough all of the extra steps when you already have ALL of the files being copied to the local system and only need to delete some info from your cmdline?

YOUR ISSUE IS WITH THIS!!! It COPIES THE Office files to the c:\Install dir!!! Office install WILL NOT look for your "network drive" without extra steps

ECHO. ECHO Installing Office 2003 Professional ECHO Please wait... start /wait "c:\install\Applications\Office2003\setup.exe" TRANSFORMS=Unattended.MST /qb-

I like long walks on the beach and playing D&D... BUT this is NOT a dating site.

WTF??? I dunno what game you are playing... HERE is the easiest and simplest way to do this: Autorun.inf: [AutoRun] OPEN=WPI.exe ICON=WPI.exe Disk contents:

... and as usual I am a day late and a dollor short with too much information in the wrong place. :S

Please send me via email or pm. Your non-profit paper\proof and I will send you a lifetime WPI license for the orginization. That way there will never be a question!

Materials required: Windows 7 x32 install media Windows 7 x64 install media Hex editor with search-and-replace, and support for unicode strings. WAIK 2.0 Optional materials: Windows 7 Enterprise x32 & x64 install media (only required if you wish to have these editions available) Stage 1: arranging files Okay, in this guide we shall be working on the D: drive, but any drive letter you have available shall do. In this stage we set up a directory structure to be used for the rest of the stages. Firstly, create the folders: D:\AIO\DVD and D:\AIO\WIMs Next, extract contents of the x86 DVD into D:\AIO\DVD Delete all .clg files from D:\AIO\DVD\sources delete ei.cfg from D:\AIO\DVD\sources Then move install.wim from D:\AIO\DVD\sources to D:\AIO\WIMs, and rename it ULTx86.wim Then extract install. wim from the x64 DVD to WIMs, and rename it ULTx64.wim And optionally, extract the install.wim from the x86 and x64 Enterprise DVDs, renaming them ENTx86.wim and ENTx64.wim respectively. Finally, extract the content of the sources directory (except install.wim and ei.cfg) from the x64 DVD to D:\AIO\DVD\sourc64, and copy the setup.exe from the x64 DVD to D:\AIO\DVD as setup64.exe Stage 2: Building the WIM Now we must build the install.wim (that's the file that contains the different versions of windows, if you didn't know), by exporting images from the .WIMS we have. Assuming you've done exactly as I've said, open the deployment tools command prompt (from WAIK), and enter these commands: You can skip the Enterprise ones if you chose not to include Enterprise. Well, you could skip any of them, but I reccommend including all you can, as it does not take up much additional room (I assume WIM automatically reuses files), and you never know when you might need to do a clean install for someone! Sage 3: Modifying the BCD Here we modify the DVD's BCD, so as to add an x64 recovery option. The recovery option is just that: it cannot install. To improve user transparency, the boot timeout shall be set to 3 sec, so as to be almost unnoticeable if not needed. Ok, open an administative command prompt. Navigate to D:\AIO\DVD Now make a copy of the default loader by executing: This command shall tell you the GUID of the copy made, make a note of it. Next set the new loader to load the 64 bit PE by executing: Replace {GUID} with the GUID you noted down) Finally, alter the boot timeout by executing: Stage 4: getting upgrade to work Now, the one problem left is upgrade installs on 64 bit. This involves hex editing files, and so breaks the digital signature, causing the ugly yellow UAC prompt. This is, I am almost ashamed to say, the first of two such cosmetic glitches. Now first open D:\AIO\DVD\setup64.exe in your hex editor. Search and replace all instances of the unicode string "sources\" with "sourc64\". Although this breaks the signature, it does not break the program, because both strings are the same length. Now, open D:\AIO\DVD\sourc64\autorun.dll, and replace all instances of the unicode string "sources\setup.exe" with "sourc64\lunch.cmd" (in case you were wondering, it was going to be launch.cmd, but I had to drop one letter...) Now, create a file in D:\AIO\DVD\sourc64 called lunch.cmd containing exactly this: NOTE: If you are using a SP1 slipstreamed image, lunch.cmd should instead contain exactly this: This is the cause of the second cosmetic glitch. A command prompt is briefly visible before setup is launched. Now, the autorun.inf must be modified so that it runs setup64 on x64 systems. Modify it so it contains: Now, finally, we're ready to master a DVD. Open up the deployment tools command prompt, and enter:

I do believe he is asking this though: "How do I ad a silent .exe application package that was made by winrar into nLite?" Answer: You cannot add it like that. nLite does not take silent installers plain as they are! Ryanvm integrator however does...

I want to thank you to those coupla members that have helped so for.

I hate to do this but please hear me out. I have had some recent extreme finacial setbacks and am in dire straights right now. I am hoping and asking for any kind of donations any of you can help me with. Please send whatever you can via paypal directly as a gift to kelsenellenelvian@gmail.com (As a gift so neither of us incur charges) Also I am cutting buisness\corp WPI licenses to $100 usd for a limited time. I appreciate any help I can get.