wixfigura

Since WPI 5,1 I always have this errormessage: WPI loads the first time correctly, the second time I have this error. WPI is on HDD e:/ and has ho entry in config.js. Does WPI need to start from cdrom?

An EXiT Button for installer would be great!!! The close Window button doesnt shut the mshta.

Hello sorry I have no Micr&%$§ Excel. Only Open Office, and your file doesent work with it. Can you explain the different injection methods, or load up a config.js? This would be great! Bye

@ Dje looks great! What about uploading your config.js? It interesting how its done.

WISH: an exit button in the installer, or functionable window-header. to interrupt the installation. now its only possible if I manually close the mshta process.

Heres mine: replace the boxes.js + useroption.js in your wpiscripts directory DOWNLOAD: Grace5

Hi I have a problem with the new installer / execute before-after function. If I use the func I get following error: The WPI Folder is still on HDD. Ive tried some paths, like these: - %WPIPath%\Install\test.exe - %CDRom%\Install\test.exe - C:\Dokumente und Einstellungen\Administrator\Desktop\WPI\Install\test.exe ( real path ) but doesnt work. Always the same error if I activate the execute before-after function. In WPI5RC2 it works, in final it does not. what to do?

Hi - the Downloadable $OEM$ folder ,for autostart WPI after Unattended installation, doesnt work right. The runonceex.cmd hasnt the CD search routine included. So it will install from drive c: (or where ever your system is). Also with this method there could be problems, if you have an other drive(s), which is empty. Windows will stop the process and generate a splashscreen, what to do ( ignore etc...). Not very unattended anymore. Here is a better solution. This small autoitscript doesnt search for the CDrom anymore, it starts wpi.hta exactly from the drive where the script runs from. Also shows no black dos-screen. Just replace runonceex.cmd in $OEM$ folder by my WPI.exe and replace the entry "runonceex.cmd" in the cmdlines.txt through "WPI.exe" One thing: WPI folder must be in the root of the CD (as usual). DOWNLOAD: WPI.exe this is the Autoit- code - very simple, isnt it? FileChangeDir("..\") RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\999","1","REG_SZ",@WorkingDir& '\WPI\WPI.hta')

Hi good work - looks nice!!! One thing, spacing between the lines in mainwindow is higher than in wpi4.3. result is, getting less items in one window ( now there is with same config.js a scrollbar/ nextbutton ). how to change this? which of the WPIscripts to change? Thanx

Ive modified Ktool a little - added an exit button Download

Can you upload it with AI?

Hello thera are 3 possibilities to call wpi during install. I prefer after reboot, cause some programs need the reboot first. So do it this way: -place wpi.cmd in this folder on your windows CD - if you do not have it, create it: $OEM$\$$\system32 -add to your winnt.sif following line: [GuiRunOnce] command5="%systemroot%\system32\wpi.cmd" -and check that you have also this entry: [unattended] OemPreinstall = "Yes" This works! The background of this uncommon way is, that CD drives can have various drive letters and have no systemvariables. So wpi.cmd searches for a file that is ONLY on your cd. In your case it is WPI.hta in the line "for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\WPI.hta set CDROM=%%i:" If you want to integrate WPI into a Windows-CD ( not standalone ) replace WPI.hta by WIN51 , cause it is only in the root of windows CDs. Also your WPI- Path is incorrect if it is included into a Windows CD, it should be %CDROM%\WPI Best you replace items 1, 2 and 5 in your script through this ones: REM Example, how to look for CDROM-drive. Must have WIN51 at the root of the CD. for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\WIN51 set CDROM=%%i: REM Determine the WPI startup path. REM if wpi should run off the cd the replace %~dp0 with %cdrom%. set wpipath=%CDROM%\WPI REM Make WPI directory the current directory. for /f "delims=: tokens=1" %%i in ("%wpipath%") do %%i: cd "%wpipath%" Or take this one: Download WPI.cmd - it calls wpi.hta with reg. changes and has no cmd. blackscreens Good luck !!

OK - I fixed it. Now it should work.

Its not the right place in that forum for things like that - but what does it matter!!! Nice that you like my theme. I created it completly by myself - from Hellacopters Album Cover "By the grace of god". So I called it graceXP. Overall it looks like this: If you want that the theme appears before first logon you need to run the regfiles at T12 And you need a hacked uxtheme.dll in your XP So here you can download it: GraceXP Theme + regTweaks Bye

@Yurek3 Take a jpg in your desired resolution ( maybe if your Monitors res. while installation is 800x600 reformat your pic to 800x600 ), rename it to ktoolback.jpg and copy it to WPI\Tools folder - thats it !! ktool cannot stretch or resize a small pic to full window size Maybe in a later version of Autoit. If you do not want a background just remove ktoolback.jpg and make shure there isnt a copy of it in your %temp% folder. If you want to resize a little just edit line9 in ktool.au3: SplashImageOn("1", $destination, 1280, 1024, -1, -1, 3) you see - resolution is 1280x1024 - you can change it anyway you like it first -1 means x-position middle 2nd -1 y pos middle, 3 means always on top, without headerbar. If you modify it like this: SplashImageOn("Yurek3 WPI", $destination, 200, 150, 20, 400, 0) then you have a Pic with 200x150 dimension, 20pts x-pos from left and 400 pts y-pos away from top. Title is: "Yurek3 WPI". Compile it with Autoit - thats all ! You see - quite easy. If you want to know more, here you can get Autoit. It has a very good helpfile inside! AutoIt 3 Download Here you get other language Help Files Other Language Helpfiles Its pretty interesting to work with Autoit. You can do many things better or more than with .cmd files. And is not as heavy as it looks like ( I began 1 month before to work with it). Bye - good luck

Its just the Arial. search in ktool.au3 for arial and replace it by your desired font, then compile it with autoit.

Here is a little modified ktool. the rightsidebar is called ktoolside.jpg size 172x413 and background ktoolback.jpg 1280x1024. you can replace it by your own pics. place all in your tools folder. You can also exit the installation by pushing the esc button. To fit for your own language the autoit ktool.au3 source is included. just search for headline= "Installiere Programme" and Progress= "Fortschritt" and compile the ktool.au3 with autoit to get ktool.exe. Looks like this: Download it: Ktool modified

Hey - try this one: WPI2XPlode.rar Ive modified some things - runs from WPI folder - writes programs.xml file into system32 directory - doesnt need to write XPlode on HDD - an Autoit file now starts XPlode ( not the ugly cmd ) - its called neu.au3/exe ( I forgot to change the name!!!) Ive NOT tested to run from CD/DVD yet. From HDD XPlode as WPI-frontend works fine. Have fun

Hi good idea - but doesnt work yet. its some problem in writing the programs.xml file. some suggestions: cleanup generate.js from ktool stuff - and what about integrate xplode into wpi installation-folders?

Hey sounds interesting. can you upload this?

@ lawrenca hey - good work! but wouldnt it be better to leave wpi as it is, and let ktool check which kind of installation it is? Im not good in autoit, but it isnt very hard, I think.

I have no problems with 4,4. Ive made of all my msi files self-exetracting rar-temporary files with the option (maybe): start after extraction blabla.msi /qb /norestart or something like that. But it also works with the prefix (example): msiexec /i ACDSee7.msi /passive in WPI (i think so). this is the method how to open a msi in autoit. The other problems are solved now, i think. In my DVD it works perfect. The closing of mshta is connected with opening the ktools.exe before, so you cannot use WPI.exe in 3.8 or lower. It works like this: In WPI you can choose the files to install, after pushing install WPI tranfers to ktool and WPI doesnt need to run anymore. So WPI.exe closes mshta. In 3,8 or lower mshta is needed til WPI finishes. So you are right - the ktool method needs not as much system-resources than without. ktool is just a little autoit-script that reads the installation from a txt file.

Just look a few topics behind - its a testing version with new setupscreen, but works fine, the only thing is, that working with .msi files isnt worked out ( cause its based on Autoit and this needs a special way to call msi files. Some changes in Config.js and it also works ), heses the link WPI 4,4RC1 good luck - bye

Hey Boys n Girls!! Nobody realized that the new wpi.exe ( the autoit file ) in WPI4,4rc1 closes mshta after calling the ktools.exe???

I have made a XP-DVD with BTS 5.1 integrated, which works very fine. Now I want to update to the latest Version, but Im a little afraid of messin up the DVD Source files. So I got some questins before, hope somebody helps and could instruct me: How can I re-integrate BTS Pack into a DVD where BTS exists in an other version?. Are there some folders/files to delete ( OEM folder, $OEM$\$$\INF, ....) or can I leave it all and only start the process? What about changes made in files like TXTSETUP.SIF? I prefer integration way number2. Thanx for helpin.