Let us know what you might like to see added into WPI!

Francesco: You probably have seen the previous posts about this. Checking is the desktop is already loaded via JavaScript is next to impossible. And this option was never meant to be used the way you are using/wanting it. It's meant to be used from DVD after Windows finishes installing and WPI is started, items picked, hit Install, desktop loads, then WPI installs apps. It is not meant to be used from the desktop.

Correct, getDesktopLoaded() is not working. I can't find a 100% "flag" to check.


If you can provide and app that can do an accurate desktop loaded check, then yes, please send it over.


Let me do some thinking on your other ideas. I do like the Reboot before install starts.

The main reason to load the desktop first is for registry tweaks. The user's account/desktop must be up for most to take affect.

I can write a small command-line tool for that. I know how to check if the taskbar is present and how to wait until the taskbar is started (explorer sends a message to all applications when the taskbar is created) would that be OK?



That's exactly how I'm using it. I run WPI from RunOnce but with that option enabled WPI just shuts down and the desktop loads and, in order to have WPI install, I have to run it again from the DVD again and tell it to start installing. I also have the problem that it closes when I launch WPI from the desktop (and I understand that's by design but I still think it could be improved so I don't have to keep 2 versions of WPI, one for first boot install and one for desktop install) but the most annoying issue is when WPI closes after being launched by the runonce entry.



If the taskbar check is enough I can easily do that. It's just a dozen lines of code.



We can add that option anyway to simulate the old behavior. It also can be useful for IE/patches install when desktop isn't loaded, that would save a few reboots.

mmmm you do know WPI supports command switches right?

With switches you can have unlimited WPI configs and call it ANY way you want.

Francesco: Yes, please email the program. Then we can talk in email so this topic doesn't drag on here on the forum. We will tweak it via email.

Why do you not use objects for configuration instead of multiple arrays?

Maybe it could speed up WPI if you switch from

to something like this:


With this you hold one array of all applications an can quickly access the properties of the current application.
--> I hope this could be faster - but I'm not sure.

Al

I have thought about converting to XML, dropped that, now still thinking about JSON. But, it will be a major update to either.

What about a message box (and an option to enable it) that asks for confirms before reboots? Like when "reboot before install" is on or when you select an entry that has reboot commands in it. It could have three options: "OK", "Reboot Later" and "Cancel", where Reboot Later sets WPI to start at the next reboot. It could be useful.

How about check boxes next to entries in the Config menu, allowing you to delete more than one entry at a time?

I'm having a few annoyances with 64bit applications and also with applications upgrades.
I premise that I use the conditions properties to hide applications that are already installed (and where the version is equal or higher than the one present in WPI), so that the same applications aren't installed twice and I don't have the screen flooded by applications already installed.

Usually for 64bit applications there are two kind of installers: a separated installer for the 32bit and 64bit versions, or an unified installer that installs the right version for your system. The first kind of installer would usually require a batch file that launches the correct setup or need two entries for the 32bit and 64bit version inside WPI, but this can be avoided by using the %PROCESSOR_ARCHITECTURE% environment variable, that I suggest should be added in the Commands/Paths menu. With both the installers however there's another problem that lies in the install conditions: since MSHTA runs at 32bit by default, the %programfiles% envvar will always point to the 32bit path, while the real 64bit programs files path is stored inside %ProgramW6432% (that on 32bit systems doesn't exist), so when you want to have a single entry for the 32bit/64bit application this can become quite a problem, because you have to use javascript expressions in the condition to select the right path, so I suggest to have WPI replace the environment variables when 64bit processing is enabled, offering the %programfiles% and %programfiles(x86)% variables on both 32bit and 64bit system and setting them to the correct paths so that they work correctly in the conditions, or another alternative could be to use a launcher for WPI that launches the HTA with the correct version of MSHTA (in case it's needed I can write that, I can also make it terminate other MSHTA instances so there won't be any more mshta.exe hanging in background preventing WPI from open).

The other problem is with applications that have to be uninstalled before the new version can be installed. This can be quite challenging because the way of uninstalling each version could be different for each version and usually requires pretty long .bat files, so I suggest improving WPI by adding an Uninstallation tab that allows detecting older versions (with a condition) and uninstalling all of these before the new version installs. This could be also used to have WPI work like an uninstaller, that when it sees that an application is already installed offers you a "remove checkbox" to uninstall it.

I think that WPI could greatly benefit from a move to a more application-centric approach where you have only one entry for each application and WPI, natively, does all the version checking, uninstalls of previous versions, and installs the correct version for each architecture.

Thats friggin insane. Someone would have to build a giant database of apps and keep it up to date. IF and only IF we got paid enough (Or really any at all) then we might consider all of the extra work.

You see though this isn't glamorous at all. We gat paid almost nothing! mritter has gotten like 15 dollars in donations in the past couple of years he has been at this.

Then we get trouble makers that are not ever satisfied and think they could do better, emails from people who ask for help becuase the warez makers use WPI in most of their releases. (Stopid emails too Like "I lost my [insert warez release name here] serial what is it?) and people who just want to complain...

Francesco,

Look at this thread, 64bit has been covered already.

Also, if you specify the complete path to mshta in your cmd scripts when starting WPI, it will run the appropriate 32 or 64bit mshta.





As far as an uninstaller, I see your point in wanting it, but could be really hard to work out. Like, what if the uninstaller wants to reboot before new version could be installed? You would have to know that ahead of time. Lots of little things need to be accounted for. Will take some serious thought and planning.

Hi, I really wish for an AND function with Conditions.

ex. I have Nvidia files in my WPI where i would like conditons like:
Cond. GetOSVer=Win7, Vista AND Getbits=32

If i do this:
cond[pn]=['getOSver()=="Win7","Vista"','getbits()==32'];

it shows the app. in XP-32bit and 2003-32bit.

is there anyway you could make a rule like if first answer is NO and second answer is YES, the condition is "not show" - only if first answer is YES it will check for next answer/cond. in line.?
or maybe like this:
cond1[pn]=
cond2[pn]=

Thx for good programming, i've been using WPI for several years now. :-)

There is an AND function. All the operators are in the manual.

getOSver()=="Win7" && getbits()==32

(getOSver()=="Win7" || getOSver()=="Vista") && getbits()==64

You will want the second example.

Thx Mritter, sorry for not seeing that in the manual.

I ended up with:
cond[pn]=['getOSver()=="Win7","Vista" && getBits()==64'];

now it works fine, THANKS :-)

EDIT:
Actually it didnt quite work. but this did:

cond[pn]=['getBits()==64 && getOSver()=="Win7"||getOSver()=="Vista"'];

Thx again.

Sorry if I didn't post a reply before but I had quite a few problems with my PC, my motherboard broke and I'll have to wait an entire month until I get a replacement because the shop where I bought it is closed.

I didn't mean anything near the complexity of an applications database. What I meant was to add a tab to the config wizard to do version detection, where you specify the current version and how to detect it (registry key, file version, INI value); a tab where you specify uninstall commands to remove the older versions (and all the commands you put there are added in front of the install commands so there's nothing else to rewrite and WPI will also handle reboots) and a column to the commands page's list control where you specify if the command has to be ran only on some architectures. I can add that stuff to WPI and post the changes if that's a problem.

Actually, it is a problem........right now.

I am already working on a major update to the Config wizard that will take me a little time. Don't "waste" your time doing anything yet; the code will be changed quite a bit.

I'm not against your ideas, but we need to coordinate what is done. Give me a few weeks and we will talk about this in emails. I am looking to make a HUGE release for next version, so it COULD be part of it.