mritter

From your message and above, maybe I don't get what problem you are having. I took a random entry, picked 3 programs it is dependant on. The entry is disabled until all the other 3 are checked. That is how it should be. Now, if you put a condition in one of the dependants, it may get hidden with a FileExists() check, for example. That was where I was getting the error message. Now with the update I sent you, a dependant can be hidden (WPI acts like it wasn't even there) so only the other 2 have to be checked. If you want me to require that if one is hidden then the entry can't be checked at all. It may aftect how other people have done checks, so it will take some thinking over.

I put the new code in and it seems to work. I didn't get the pop up window. Will send it out to beta testers.

I haven't tried the new code yet, still getting back in to the swing of things after vacation. And it's my birthday so not doing any work. ;-)

Just tried a quick test.......I see what you are getting at. I think I have a fix for it.................

This was reported earlier, but I can't replicate it. It works fine for me. I will add it to my list.

Someone posted that they have this issue with a network share with write priveledge denied. Yours too? I would say no since your file did write. Did it write to the correct path? Put a JSCRIPT=alert("Pause") in an early command, then check where the file is. If wrong or correct place, let me know. Vague, but trying simple ideas first...............

I have had a few reports of this. I don't know if it is new or no one ever reported it in older versions. I have not touched this code in a LONG time so it can't be anything new. All I can say is: I will look in to it.

I don't know why only that drop-down box would cause an error. THey are all the same. I do have some some new code coming soon so that may fix your problem. Or it could be your language. Try it with English just as a test. Post results here.

I may have a solution from the person who posted about using WMI for the cd/dvd check. I will post if works or not later. I thought this was just a Vista problem, but may be an XP x64 issue also. Dunno for sure.

When I first came on board with WPI a few years ago I liked the idea of it being open-source in javascript/html. It meant anyone could update the code, take ideas from it, learn from it. Then, like you, I thought it kind of sucked that it wasn't in a compiled language. But then I got over it when I needed some help and the forum users posted the answers. Yes, they still could have had the C code............ I would love to get away from mshta and just IE, too. And now with x64, twice the headaches, as you know. A compiled WPI wouldn't have as many issues since it wouldn't rely on the program that launched it. The code would grow and get complicated with IE/FF/Opera checks since not every command/option is in all browsers. Each browser renders a little different. A lot of small technicallities. WPI could, I think/guess, be used without mshta but it would have to be opened in a full browser window like a web page. All the navigation buttons/bars would be visible. It could be used like any web-based program (firewall, vpn, etc.) but would not look "normal" when launched from a DVD. Wouldn't be borderless (IE can do kiosk mode). Given enough time I can figure almost anything out. I will keep this on the back burner.

Yes, which theme does this happen with? More than one or just a certain one?

That file is placed there for simplicity and an always known path. I will have to do some checking, but the file should only be created if a REBOOT is found. There is no need for it otherwise.] To see the file, put a JSCRIPT=alert("Pause") in one of the first items, then look at your C: drive. I don't do any virtual testing since I have 5 computers, 1 dedicated to just testing software, so I can't really test it yet. I will keep it in mind.

Sweet! I like it! I was wondering about firewall stuff myself. Will definetly work those in!

I am still on Jamaica "time", so sitting in a bar drinking with my laptop. Is that super geeky or what?!?!? Yes, I have seen that button problem before, but only on older slower computers. That may not be your case. Is it just with the Corporate theme, or others also? I still want to get a new button code worked in; not 100% happy with current buttons.

There are a few known problems with this release that I didn't have time to fix before my vacation to Jamaica: The Check For Update works fine for most people, but some of my beta testers reported failures. It seems to work fine for people in USA, but not Europe. It could it be related to latency times, or Imay have tweaked something I shouldn't have. The new grids in the Information window (Alt+G) are not showing colors correctly. I have sent bug reports to the authors, just have not gotten a working copy back yet. The grid works fine otherwise. The 64bit installer code has been tested thoroughly, but still in it's infancy. It's seems to be working fine, but, just making mention of it. It does only pertain to scripts and batch files with extensions of .cmd and .bat. Also for RegEdit tweaks. The css colors in all the themes has been changed from default text color of white to black. All the themes on th site have been updated, either download a new copy or change it yourself. Right at the top, the first color: reference, change from #000000 to #fffff. Two people have reported an JavaScript error at startup, Identifier expected. I tried WPI on 5 different computers, works fine for me. Kels has no problem. Just making mention of it. That's it. Report anything else in the bug tracker.

Fixed. Thanks for the report.

If you want to disable it now, go into WPIScripts/api.js Right up top is CheckForInternet(); Just comment it out //CheckForInternet();

1: Seems to only happen on Vista machines. BUt maybe others. Not sure why. 2: It is the internet check. It is an option you can turn off in 7.1.0 due out Sept. 1.

I downloaded your config to see if I would get an error.............none. So it's not your command lines, must some program causing a conflict of some sort. What, I have no idea.

I don't know if any one out there has realized that the new button skins I incorporated in 7.0 is not perfect. When a button is disabled, since it is not a real button, it is still clickable. Bad. Does anyone know of a system that will allow skinning of buttons but truly disabled them? I did some Google searching, but none with true disabling. I would like to just skin a <button type="button">Cancel</button> with a class="buttonSkin". If you know of any sites or have some code, please post them here so I can get them working properly. Thanks

There used to be a small doc about the tips in the Tools folder. The current tips is slated for a total revamp. Maybe even a total replacement. The code is outdated, not compatible with all themes, etc. If I still have it I will have Kels post it on the main release post.

Thanks, TwoJ. I will try to write some examples for the manual on conditions. Very few people read it, but......... FileExists() - Does file exist? yes/no !FileExists() - Does the file NOT exist? getOSlang()=="ENU" && getOSVer() != "Vista - lang is english and OS not Vista getOSlang()=="ENU" || getOSVer() != "Vista - lang is english or OS not Vista (getOSlang()=="ENU" && getOSVer() != "Vista) || getFreeRAM()>512 - lang is english and OS not Vista, or more than 512MB free RAM That will get you started. Find more online search.

Thanks rogergh and Dyna. I will have some more for this weekend.

Don't count on just changing what reg key it uses to work. It took me 4 hours to build in all the code needed to properly handle reboots, history, etc. Contact me and I will send you a beta copy of 7.1.0.

As Kels mentioned: I added "Load desktop before installation starts" into 7.1.0 which will be released September 1. WPI will launch line normal (RunOnceEx), do your thing, hit Install or timer run out, desktop loads, then WPI starts to install.