Dynaletik

Hmm, only thing I changed is the WPI.cmd and the config file. Nothing more. My WPI.cmd looks like this: cmdow.exe @ /HID @ECHO OFF 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: set WPIPATH=%CDROM%\Install\WPI\ for /F "delims=: tokens=1" %%i in ("%WPIPATH%") DO %%i: cd "%WPIPATH%" start WPI.hta If you want Windows to wait until WPI has finished, just use start wait instead of only start in the last line.

Try this Addon. It also has got no extras in it and will disable the autostart entry, even if an Java App has been running. IEXPLORER and MOZILLA are set to 1.

@ Solid as a rock: I already have got my Install folder out of WPI. I use it since I use WPI and in the beginning, the Install folder wasn't in WPI folder, so @ root I got "Install\Programs", "Install\Drivers" and "Install\WPI". So WPI is in the last, and programs and drivers in the other folders. The install cmd and reg lines look like this: cmd1[pn]=['%cdrom%\\Install\\Drivers\\ITouch\\setup.exe -s -f2"%temp%\\ITouch.log"'];

This is what we are here for. Everybody learns something. You inspired me to shrink down the Java Installer, and I tested and searched for a solution for the JavaUpdate AutoRun entry.

But when you integrate the posted .reg file into your registry after install has finished, this should not happen. I tested it some times now and got success. (Before installing I uninstalled and deleted registry entries and Sun Folder in %appdata%).

There are some switches that prevent the installation from restarting the pc, you are right. For InnoSetups this is "/NORESTART". For InstallShield Setups, the created .iss file defines if the PC is rebooted or not. For Windows Installer the reboot switch often is "REBOOT=Suppress" or "/norestart". You have to look what type of installer you have got and then choose the switches to take.

Ok, I think I got it now. But it is quite tricky, because there are RegKeys that have to be changed AFTER install! If you integrate them into the .msi file, they will get overwritten, don't know why, but Java does it. So what I first did was changing some values in the .msi files properties (in InstallShield it is "Property Manager"). AUTOUPDATECHECK was 1, changed to 0 IEXPLORER was 0, changed to 1 JAVAUPDATE was 1, changed to 0 JU was 1, changed to 0 MOZILLA was 0, changed to 1 SYSTRAY was 1, changed to 0 WEBSTARTICON was 1, changed to 0 I know, that you can set every property using an switch, just look what is in your switch and change the rest or add additional switches. Now the "problem" comes. There are still 2 settings in the registry that cause the AutoUpdate and must be changed. Here they are: [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy] "EnableJavaUpdate"=dword:00000001 "PromptAutoUpdateCheck"=1 So to disable the UpdateCheck that gets created in Autostart at first run of an Java app, I execute the following .reg file: Windows Registry Editor Version 5.00 ;Removes Java Update [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy] "EnableJavaUpdate"=dword:00000000 "PromptAutoUpdateCheck"=- Now on the first start of an Java app, there is no Java tray icon vibisible and no Java UpdateChecker in autostart. Only thing is, how to integrate it into the file you made. I would solve it by using an Java.bat that first calls Java Setup with its Switches and then executes the .reg file. I hope this helps you.

Your Java Installer looks really nice. Could you tell me, with which switch you start the install? And how did you remove extra.zip and other.zip? Did you edit the .msi file for that? EDIT: Hmm, strange, when I just install it, the automatic update in autostart is not activated (jusched.exe), but when I run the first webpage with Java elements, the autostart entry get created. Any solution? I think you are using JAVAUPDATE=0.

When does this error message come up? Just when you start WPI doubleclicking the WPI.hta file? Or when install starts?

Ok thanks zorphnog, this fixes our bug.

EDIT: WPI 5.4 out!

Ok, I can reproduce the bug with 300 seconds. Your useroptions.js is not the reason. It is definitely a bug in the timer, just tested with 60, 70 and 300 seconds, but with 300 seconds the error in timer.js line 54 function tTimer comes up when the timer runs out. EDIT: Solved by zorphnog.

Ok, already fixed that for the Royale theme for 5.3.

Hmm, I can't reproduce the error with the timer you get. I just tested from HDD and from DVD with 60 seconds and everything just goes fine. What delay do you use? How many seconds?

EDIT: Royale for WPI 5.4 is out!

Thanks for the new release! I hope it fixes our bugs. I just updated the german language file and attached it. I think there are a lot of unused strings in the translations now, because you worked on the optionswizard and a lot of explanations are not used now. Perhaps you can clean up the translations for 5.4. EDIT: Did a first test to look for bugs, but there are no bugs!!! Very good work! Everything installs fine. Attached translation moved to translations thread.

Hey, thanks for the update to 4.5 XPero. I just saw that you already posted the alternate mirror on my server. So I don't have to say you, that I just uploaded the new files and they are ready to download.

Did you remove Internet Explorer with nLite? You shouldn't do that.

Since version 5.0, WPI does not use the GuiRunOnce method, it has its own installer. And this new installer does not start again after reboot, I think.

Do you have the "sort by category" option enabled? Because this brakes your install numbers. I "solved" it by creating an config.js that has got the install order that I want so I don't need the sort option and can use the install orders.

Please read what mritter wrote in THIS Thread. Wait for WPI 5.3.

Just a wish: Please release WPI 5.3 as a Beta first, and if there are now bugs in it, call it final.

Hast Du schon WPI 5.2 probiert, inklusive der Fixes, die im gepinnten Bug Thread gepostet sind? Wenn Du das einmal testen könntest wäre das super. Ich denke, dass der Fehler in WPI 5.3 gefixt sein wird, Du kannst also auch ein paar Tage warten.

I never used "Show Source". So one more vote.

Yeah sadicq, that solved the problem. But I do not have to post this, because we did not expect anything else, or did we? So if the errors of Pilek are solved, what about releasing WPI 5.2.1, because with WPI 5.2 there is no way to make an install from Disc drive.