mritter

kTool is no longer supported at this time. I have never used XPlode so don't expect that any time soon. I will check it some time down the road.

No, there is no need/use for it since whatever you, or whomever, makes will be obsolete in a few weeks. Yes I do like the idea of it for v5.0 when I/Kels release it. Then make an editor. I'm not stopping you by any means, just saying hold off for a bit.

A theme editor/creator would be nice. But before any one goes jumping on it, v5.0 themes WILL NOT BE BACKWARDS COMPATIBLE with v4.4 or lower. Before you all moan and groan, it is all for the better. It will actually be a little bit easier to modify the Glossy theme to your design since I cleaned up the code for easier reading/following. I took out some unnecessary code. I added some code. I moved some code. Yada yada yada. I will actually keep an editor in mind for down the road.

You are one of only a handful of people that have fully caught that problem. I just fixed it the other day. It has been wrong probably since day one. For some reason there was some VBScript code in there checking for the computer name.....who cares? We want to match what config I requested be used. Took that VBScript code out and fixed the problem. v5.0 will be out soon........

Select all "problem" was never noticed by me. BUT I did make some code changes in the upcoming v5.0 I have been working on that eliminates that not possibly working correctly. I also fixed a bug in there no one ever mentioned: the check on load didn't set the proper config, it totally ignored it. Anyway, be on the look out in the next 2-3 weeks for v5.0.

I have been seeing several posts about JavaScript error messages recently. It is hard to answer them all simpy because of the way WPI tries to track the errors. I have added a new tracker and plan on updating it even more in the next few days. On the another note, I have gone through the code extensively and have tracked down all the errors I could. Some were simply missing the end of line semi-colon, other were duplicate code fragments, etc. I hope to have more of my updated done this week, but will probably take me two weeks. I will then hand out some copies for beta testing. If you can hold tight until then, you will have much better luck and satisfaction with the new release.

Added to my To Do list. Will base it on sortorder[], install same order as displayed in the selection window.

Use the topbar.jpg for btmbar.jpg, not the orange one.

OOOOooohhhhh......gotcha now. So want that as an option in one of the configs: Disable category 'Select All' check box? * Yes * No

OK, yes, with 120 apps it will take longer to render the config window. That is something I have been thinking about in the back of my mind. I have a general idea on how to "fix it". What WPI is doing is doing a for(...) loop and creating a <form> for each entry, which is 205 lines long. So 120x205=24600 lines of code. I only have like 30 apps, so mine does render fairly quick.

In talking with Kels, he brought up the idea of disabling entire categories. We have seen that requested before. What I am unsure of is, why? Are you not wanting them installed on a particular computer, but is OK for another? Then you should be using SelectMultiDefault option and not set those items as defaults for that particular computer. Are you giving the CD/DVD to someone and you don't want them to be able to chose your "special" programs? Then, how do you want to enable/disable them? My first thought was to add lines to config.js at the top like: cat['Drivers']=true; // enabled cat['IllegalStuff']=false; // disabled ...... then the items........ Then how do you want to change them? Manually in config.js or in the Options screen? I am just looking for input so I go about it the right way the first time. Tell me all your thoughts.

Am I missing something that you guys aren't? When I watch mshta in the Task Manager while working with WPI, it rarely goes above 15%, usually hangs at 5%, sometimes goes to 23% to 85% when doing a large change, like going to Options. It does use 36MB of RAM, no more than running Explorer for a web site. There is no delay like WotC is having (I also have AMD64). It just reloads the page like hitting refresh in Explorer. I don't see any difference in using WPI to install everything compared to kTool or RunOnceExe. It is not the program slowing the computer, it is the program being installed. Once the install process is started, the GUI of WPI is idle, 5% CPU. I somewhat like the idea of mshta closing so the desktop could come up and you could do some work. But your computer is still slow due to the programs being installed. I could just be used to having a fast AMD64 and don't really notice the time for installs. And I do walk away and go about my business on other computers, so I don't really need to do background work.

You should be able to start wpi directly: wpi.hta Don't use start mshta at all.

What version are you using so I can check the generate.js error? cmdow.exe is in Tools, not Common

I have seen people asking how to disable the tool tips. The best answer so far has been to delete code from main.js. That to me is bad/wrong. I have added a new feature to Options to enable/disable the tool tips, which will be saved in useroptions.js. No more modifying the code. To go along with that, I have updated the tool tips to a newer version. It has 50 transitions, more color options, more image options, etc. The only draw back is that the Style[] is now different. Longer actually. But no big deal. I will put a description in the code for the new flags. I will get with Kels down the road about when we'll update it for a release. Stay tuned........

I would say you messed up the code for the player in the wpi.htm theme page. Check this <embed> line <embed width=300 height=44 align="middle" name="MediaPlayer" showstatusbar=0 volume=68 ></embed> and the <script> code below that <script> document.all.MediaPlayer.src='./Audio/WPI.m3u' document.all.MediaPlayer.loop="true" if (showmpWPIBtn == 0) { document.all.MediaPlayer.src=''; } </script>

Depending on what version you are using, I suggested to Kels, and we have moved it, the audio.exe program is now in the Audio folder, where it always should have been. Change line 236 to ".\\Audio\\Audio.exe"; <---- add the semi-color And verify audio.exe is in the Audio folder.

There is no definite answer since the fonts are proportional. It all depends on the letters in the words. As in, the letter i is skinnier than w. All you can really do is name something with all W's and try and count them before the install process completes, then base it on that.

Inside WPI.cmd there is a line to run a clean up script. Just remove the REM and rename it to your file. And use cmdow @ /HID @ECHO OFF as the first 2 lines.

Before you switch back, I have done some code updates and when I get with Kels about a new addition I am a making, the next version should have several little bugs like yours taken care of. Stay tuned....!

Yes, post your original code. It may come in handy for me at work.

I can't get my Multiset installations to launch, either. It has to do with kTool because if I put back the original RunOnceEx code they will work. I like the idea of kTool but it sounds like more problems are arising weekly. Ugh.....

The error in main.js on line 406 has to do with the loading of a theme. Check that for errors.

cmd1[pn]=['setup_a.exe'] cmd2[pn]=['sleep.exe 30'] cmd3[pn]=['setup_b.exe'] Has to be in a command #

One thing I came across that affected some of my testing and code modificatons was that some of the functions {} don't have the line position=generate.js; or whatever file they are in. I added them in in all the files and it fixed my error. I don't know if that would fix your problem, but I have talked to Kels about me updating/cleaning all the code. All I can really say is: watch for a newer version soon.