WPI 7.8.0 Feature requests.
#2
Posted 29 July 2009 - 03:23 PM
Also, are you sure you don't need a WPI launcher that runs it as administrator and selects the correct MSHTA 32/64bit version? That could be quite useful.
This post has been edited by Francesco: 29 July 2009 - 03:37 PM
#3
Posted 29 July 2009 - 03:39 PM
#4
Posted 29 July 2009 - 08:47 PM
start "" /wait "%windir%\system32\mshta.exe" "%wpipath%\WPI\WPI.hta"
#5
Posted 31 July 2009 - 04:15 PM
mritter, on Jul 30 2009, 04:47 AM, said:
start "" /wait "%windir%\system32\mshta.exe" "%wpipath%\WPI\WPI.hta"
Yes, I know, but having to use batch files to launch the correct version is ugly, having a launcher would be much better. Anyway, I made it. It's 2kb without the icon, 8kb with the 6kb WPI icon. I attached the version with the icon to this message.
If you need some changes tell me. This launcher could be also used to pass to WPI informations that it's unable to read, for example rather than having WPI check for explorer with findexplorer, this launcher could tell WPI if explorer is loaded with a reserved command line parameter.
This post has been edited by Francesco: 01 August 2009 - 02:56 PM
#6
Posted 31 July 2009 - 08:08 PM
Got the mshta white screen...
Waited for a long time (5min)...
Nothing.
#7
Posted 31 July 2009 - 09:12 PM
I ran it on folder outside of the wpi.hta and not beside the wpi.hta.
#9
Posted 03 August 2009 - 11:55 AM
Is it possible to set the environment before a command is executed?
Thanks
Al
#11
Posted 03 August 2009 - 01:22 PM
Actually, yes, it could very easily be done. Consider it done.
Just to ask: should it be an option or just do them all? (%root%, %wpipath%, etc.). Or just certain ones?
hdd, cddrv, root, wpipath, oslang, oslocale, would be the whole list.
Delete them when WPI exits?
#12
Posted 03 August 2009 - 06:29 PM
{JSCRIPT}=removeEnvVar(Variable)
They are removed when WPI exits.
#13
Posted 11 August 2009 - 12:52 PM
would also be very nice.
GlobalFlag = true: set variable in system-env
GlobalFlag = false: set variable only for current process (sub-processes should also can use them).
e.g.:
{JSCRIPT}=setEnvVar("LOGFILE", "%SystemDrive%\install.log", false)
%ROOT%\apps\myapp\install.cmd
Now install.cmd can use %LOGFILE%.
Because this variable is only used during install-process it should not be set in system-env - but it should be accessible for the next app without to redeclare it.
Al
#14
Posted 12 August 2009 - 04:56 AM
Also if WPI is incompatible with some applications like Nero or need some certain windows files I can detect those and warn the user so they won't come complaining here when WPI doesn't load.
#15
Posted 12 August 2009 - 07:00 AM
Keep the launcher simple.
#16
Posted 12 August 2009 - 11:48 AM
mritter, on Aug 12 2009, 03:00 PM, said:
The launcher could set the environment variable, or pass a command line parameter, or the setWPIPath function inside core.js could be changed to remove the last directory entry so it wouldn't be such a big problem.
mritter, on Aug 12 2009, 03:00 PM, said:
Most people will go directly to the EXE now that they'll see there's one. Newbies will use it because they don't know that .HTA files can be run, pros will run it because they'll think it is now necessary to use it (and it is, if they want to avoid all the error messageboxes on vista because of UAC). Having only the executable and TXT files in the main dir could help make things less confusing.
mritter, on Aug 12 2009, 03:00 PM, said:
Adding some file/registry key checks to detect missing files or conflicting applications could hardly make the launcher bloated or slow because it c++ code is very fast and small.
#17
Posted 16 August 2009 - 12:04 PM
Placed above the Begin Install Button, when pressed it would display the contents of a readme.txt file.
In the file, you can place instructions, and explanations about the programs on the list.
For instance, I have a program that always ahs a problem during the install (no matter what I do).
I could warn the user, that program may need operator intervention.
If the file doesn't exist, then there would be no need to display the button.
Thanks
#18
Posted 17 August 2009 - 12:00 PM
Once again I wish for a WPI commandline switch to disable all Cancel or Exit Buttons and Keyboard shortcuts so that people are forced to continue with an installation.
Bye,
Alex
#19
Posted 17 August 2009 - 12:02 PM
#20
Posted 17 August 2009 - 11:37 PM
Quote



Help

Back to top










