Dumpy Dooby

Alert when non-hexadecimal color is put in there? Alerts are so 1999!

Oh, that's what I figured you were going to say. I said, "I, personally" because I don't use WPI to edit my config. I used it once, and from then on, I've just used notepad to do it. I knew it overwrites the file, though. Although your point still stands; it was irresponsible of me to recommend putting it into config.js without noting the problem with doing that. I just assumed nobody changes their config.js ... like me, which of course, was probably a silly assumption.

You guys tried implementing my mod to not show the checkboxes when "category selection" is disabled, but something went wrong. I'll look it tomorrow. Just figured I'd let you know in case you wanna look at it.

Just out of curiosity, why is this? Is config.js parsed by line number or something? I just assumed you used regex to parse code from it. And it's also the most constant file (I've had the same config.js file for the past 8 months ... with only adding the new pcmd as of recently). Anyway, just wondering why it can't be put in there. PS- Gonna PM that code you wanted right now (so check your PM if you haven't already).

To answer that very last question: Create a new .js file. You're simply talking about a javascript function. You can then call the javascript function from anywhere else, just as long as the dependencies are met. I, personally, would put it in config.js, and then the gcond could include certain service packs, OSes, and whatnot (instead of just "if file exists"), plus you don't have to worry about having to change the file when you upgrade (since config.js doesn't seem to change much).

There is no need to do any renaming. That won't make command.com behave in a different manner. That's a silly notion.

I exclusively use Softpedia.com's summaries and screenshots (the little thumbnail one) in WPI. I'll only develop my own screenshots and summaries when the software in question isn't on softpedia.

there is no resion it shouldnt work with IE7. however, useing firefox just about makes this pointless, as most (probly 99.9%+) of the sites wont infect firefox. 67% of all statistics are made up on the spot.

Have you tried cmd /c (from RunOnceEx, that is)?

Thanks. I actually didn't know either of those.

Not sure if this will fix it, but I know with .NET Framework 2.0 one needed to change the registry entry that said Windows Setup was in progress. Here's the batch file I wrote for that. @echo off SETLOCAL ENABLEEXTENSIONS FOR /F "tokens=2* delims= " %%A IN ('reg query "HKLM\SYSTEM\Setup" /v SystemSetupInProgress') DO SET SSIP=%%B IF /I '%SSIP%'=='0x0' SET SSIP=0 IF /I '%SSIP%'=='0x1' ( SET SSIP=1 ) ELSE ( SET SSIP=1 ) IF /I '%SSIP%'=='1' ( reg delete HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW /f reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 0 /f ) ResChanger parametershere reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d %SSIP% /f I guess you can give that a shot. *shrug* note the line that says ResChanger parametershere. Change that accordingly. edit: btw, I'm thinking this might work because there may be a limitation on Windows to not change the resolution when setup is in progress.

From the thread: You can open generate.js and find "function FindCDRom()" There should be a bunch of "if (FileExists[...])" commands. Rearrange them, or list your own file accordingly. Be sure to follow the same pattern that you see in the file.

Could we get a different code tag? The one here displays the code awkwardly. It has a wordwrap which just doesn't look right with code (who codes with wordwrap on?). I think it should be in a div with overflow: auto or something similar. I'd be more than willing to write it, while taking multiple browsers into consideration.

Oh snap. I had forgotten to check to see if the user had enabled the timer before displaying the stop sign. The way it was before, it would display the stop sign onclick on the body regardless of whether or not the timer was enabled. Oopsies. It should be fine now. If anyone happened to use my old script, check my post again and use the fixed one.

The Win98 version of command.com is very limited. It doesn't support nearly as many options as the WinXP flavor. I'm not sure what your wpi.cmd file looks like, but there is a chance that you will have problems if the code is too complex. There's far too many differences to be able to go over all of them.

haha. Sorry bud, HTML is my specialty. I rely on this community for all help regarding unattended installs.

Thanks. Let me know if you guys need any help with further development.

Okay, this will be a little more complex. If you're a newbie, you can give this a shot, but just make sure you know how to undo anything you mess up (back up any files before editing if you're unsure). This will only look right if you used my PNG tweak above (due to 8-bit alpha indexing in stop.png). Again, we're going to edit WPI.HTM. Find (this is from the post above; if you already did that one, then you can skip this step): <img id="stoppedimage" src="./themes/Glossy/stop.png" alt="Timer stopped" height="0" width="0" style="position: absolute; visibility: hidden;" /> <div id="stopped" height="0" width="0" style="position: absolute; visibility: hidden;"> <table class="text" width="100%" border="0" cellpadding="0" cellspacing="1"> <tr> <td valign="middle" align="center"><b><!-- <script type="text/javascript">document.write(getText(TimerStopped)); </script> -->Stopped</b></td></tr></table></div> (Note the commented javascript. That's in case this gets implemented into WPI permanently. But for now, just ignore it and keep it commented.) (Also, note stop.png. I will be providing that image in just a second. Make sure you put it in ./themes/Glossy/) Now we will edit timers.js... Find: function stopInterval() { position="timers.js"; whatfunc="stopInterval()"; window.clearInterval(interval); interval=""; } Replace with: { position="timers.js"; whatfunc="stopInterval()"; if (Timer) { timertr = document.getElementById("countdown"); stoppedimg = document.getElementById("stoppedimage"); stoppeddiv = document.getElementById("stopped"); /********************************************************************************** * These are just estimations that tend to look okay with the various resolutions. * I'm sure they could definitely go for some improvement. **********************************************************************************/ spacel = document.body.clientWidth / 60; spaceb = document.body.clientHeight / 10; timertr.style.visibility="hidden"; stoppeddiv.style.visibility="visible"; stoppeddiv.style.width = "120px"; stoppeddiv.style.height = "120px"; stoppeddiv.style.left = spacel; stoppeddiv.style.bottom = spaceb - 35; stoppeddiv.style.valign = "middle"; stoppeddiv.style.align = "center"; stoppedimg.style.visibility="visible"; stoppedimg.style.width = "120px"; stoppedimg.style.height = "120px" stoppedimg.style.left = spacel; stoppedimg.style.bottom = spaceb; } window.clearInterval(interval); interval=""; } Here is stop.png (right-click, save, and rename accordingly): And finally, here's a screenshot that shows off my modifications (for those that care). Click the image for the full size version.

To make the timer go away when you stop it (presumably by clicking anywhere on the page), you can do the following... Find the following in wpi.htm: <!-- Timer and StopWatch --> <tr> Replace with: <!-- Timer and StopWatch --> <tr id="countdown"> Now in timers.js, find the following: position="timers.js"; whatfunc="stopInterval()"; And add the following after it: timertr = document.getElementById("countdown"); timertr.style.visibility="hidden"; So the stopInterval() function should look something like this: function stopInterval() { position="timers.js"; whatfunc="stopInterval()"; timertr = document.getElementById("countdown"); timertr.style.visibility="hidden"; window.clearInterval(interval); interval=""; } I'm going to work on replacing the timer section with a stop sign or something. I intend to use stop2.png from the PNG Collection pack that Kels posted a while back.

Use \n to denote new lines (in case you didn't know that). So if you want, you could do something like... function opsave() { var agree=confirm("Are you sure you wish to save\n\n OK = yes\n Cancel = no?"); if (agree) { "My Code" } } I dunno. I've seen that before, but I think most people understand how to answer the question. Perhaps VBS will allow you to use yes/no/cancel prompts. I dunno...

Javascript can't do that, as far as I know. You can use a DIV layer with the appropriate buttons a la Gmail's "report phishing" option. Also, sorry for not responding on YIM. I wasn't home. Just got home. Long day. Gonna hit the hay.

replace alert with confirm. function opsave() { var agree=confirm("Are you sure you wish to save?"); if (agree) { "My Code" } }

It looks good, but I would prefer the buttons to not be images. It's just more space on the disc that is ultimately not even going to be used all that often, thus making them almost innocuous. Ever notice how the "admin" sections of sites are pretty basic? We're trying to appeal to the End-User. Everyone on the administrative side is already impressed with WPI. No need to fancy it up on that end. I say you just do a div, with a color as the background (could be specified in the css), and apply a filter that will make the div have 70% opacity. This would solve that problem with people's inabilities to read the text, plus it wouldn't increase the size of the disc at all (which is a major concern with guys like me that have to count each MB). Again, this is just my personal preference. If you don't agree, that's fine and dandy. I'm not even sure if I would ever even make use of this script. :shrug:

I actually don't know if the XPize shortcut is put in the Startup folder in the Start Menu or if it's a registry entry. But if it's a shortcut, you can simply go to the properties and select "minimized" from the "Run:" menu.

I was actually going to create an editor for tooltips. I didn't think it was necessary though. Meh. If people want it, I can make it. *shrug*