blinkdt

Discussion Removed.

Every once in awhile I run across a topic here at MSFN that merits bookmarking and printing for further study. This is one of them. A sincere "thank you" for making the effort and taking the time to document your procedure.

Not sure what you mean, as there where some problems with the Windows Update site itself today. The "big boy method" described by hsu22 works fine from here.

I say do what YOU think needs to be done, you are the expert. I suppose that if it doesn't behave the way people expect then you will receive feedback, and that's OK. All part of the process. But I'm sure it will be fine.

Discussion Removed.

Looks nice, background color and border can be changed, keeps time with the music. Nice work.

Real good. Maybe some margin or spacing to distance the version info from the right edge of the screen and slightly smaller text? Just thinking out loud, like I say I think it looks real good.

Oh, you could have saved me the pain. I'm no scripter, you dah man! Keep up the great work, this is polishing up nicely.

Looks good. So just replace the "if" section beginning on line 129 and leave in place the "else" section that follows. An now we have: //insert checkbox and label // -- checkbox -- if (debugOn) txt += ('<font class="txt">' + i + '</font>\n'); txt += ('<input type="checkbox" id="chkbox' + i + '" '); if (uid[i]==null || uid[i]==""){ txt += ('name="chkbox' + i + '" '); txt += ('onclick="checkCategory(this, \'' + cat[i] + '\');" '); } else { txt += ('name="' + uid[i] + '" '); txt += ('onclick="checkDeps(' + i + ');" '); } txt += ('onMouseOver="qdh(prog[' + i + '],desc[' + i + '],Style[0]);" '); txt += ('onMouseOut="htm();"'); txt += ('/>\n'); // -- label -- Correct? Seems to be working fine here.

No need for an apology, perfect releases do not exist. Yes, the Help button seems somewhat redundant given the mouseover tips for each button. Maybe the version number could be added as a comment to the .hta file, included on the User Manual homepage, or both?

@athomsen Oh, excellent, just what the doctor ordered. Thank you! This is worth waiting for, thank you again.

The category selection feature "is what it is" at the moment. If we have any Javascripters out there willing to take a look at the function and perform a rewrite, by all means tackle it. Use it, ignore it, or tweak your categories. Those are the only options available at the moment, sorry for that.

You are probably using cmdlines.txt to import Windows-specific reg tweaks. I like to take advantage of WPI's awesome features to import program-specific reg tweaks. You can import reg tweaks before (regb) or after (rega) the commands, for example: pn=15 prog[pn]=['XP PowerToys'] desc[pn]=['<center><img src="./icons/power.png" width="128" height="128"><br>Useful collection of non-intrusive power user tools.</center>'] cmd1[pn]=['%cdrom%\\Programs\\PowerToysXP\\TweakUI.msi /qb'] cmd2[pn]=['%cdrom%\\Programs\\PowerToysXP\\PowerCalcPowertoySetup.exe /s /v/qn'] cmd3[pn]=['%cdrom%\\Programs\\PowerToysXP\\CmdHerePowertoySetup.exe /s /v/qn'] cmd4[pn]=['%cdrom%\\Programs\\PowerToysXP\\TaskswitchPowertoySetup.exe /s /v/qn'] rega[pn]=['%cdrom%\\Programs\\PowerToysXP\\PowerToysXP.reg'] dflt[pn]=['yes'] forc[pn]=['false'] cat[pn]=['Geek Tools'] ordr[pn]=[150] uid[pn]=[''] deps[pn]=[''] pn++ ...or as part of a command line itself: pn=25 prog[pn]=['WinZip 9'] desc[pn]=['<center><img src="./icons/Winzip.png" width="128" height="128"><br>An essential tool for creating<br>and opening .ZIP format files.</center>'] cmd1[pn]=['%cdrom%\\Programs\\WinZip.exe'] cmd2[pn]=['REGEDIT /S %windir%\\Temp\\WinZip.reg'] cmd3[pn]=['%windir%\\Temp\\WinZipSFX.exe'] cmd4[pn]=['\"%programfiles%\\winzip\\winzip32.exe\" /noqp /notip /autoinstall /cleaninstall'] cmd5[pn]=['REGEDIT /S %windir%\\Temp\\WinZip2.reg'] dflt[pn]=['yes'] forc[pn]=['false'] cat[pn]=['Utilities'] ordr[pn]=[250] uid[pn]=[''] deps[pn]=[''] pn++ If you have one large reg file, maybe consider adding it to the last item being installed. Hope the examples help.

Cool, here is my Tooltip Graphics package. Enjoy!

Rock on, TommyP! Please ignore my comment re the two hotfixes, everything is fine. Would be hard to retrace my steps at this point, but everything installs flawlessly save for the DX9c issue, which I now install from RunOnceEx, but it sounds like you are all over it. Tried repacking with IExpress together with the /Q:A /R:N switches as per your instructions, no luck as you appear to be aware. I'm on pins and needles. Will these features be available in your next release? Oh, and a simple and sincere "thank you" for all of your hard work. Edit: almost finished tweaking my disc, did intend to post back here and let folks know that the "2 hotfixes didn't install" issue was a non-issue.

Check your WINNT.SIF file found in the I386 directory of your installation source. You should find the problem entry at or near the line specified in the error message. You may want to remove the line or modify it. Can you post your WINNT.SIF, just the relevant section, in tags for all to see?

@redfive19: nice work on the autoupdate feature, I'll definitely be putting that into all of my installs, worked like a charm.

I don't think that's doable. I'm sure you have read THIS THREAD, which dicusses the no-ifs-ands-or-buts necessity of editing the dxsetup.exe file for a Win2K install. This has been an issue for DX9a, DX9b, and DX9c. My RunOnceEx.cmd for Windows 2000 Advanced Server: @Echo Off SET PP=%systemdrive%\Install SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%\060 /VE /D "DirectX9c" /f REG ADD %KEY%\060 /V 1 /D "%PP%\DX9c\dxsetup.exe /install /silent" /f You can grab the 42.05k dxsetup_new.zip file at the end of page three of the thread mentioned above. I'm just thankful that nxskingdom made it available. I'm using TommyP's integration method for most of the install work (try it, it is truly fantastic), but using the "/Q:A /R:N" switches as Tommy suggested together with nxskingdom's IExpress guide to pack a switchless silent DirectX9.0c installer did not work for me. Tommy didn't indicate that I needed to use the hex edited dxsetup.exe, and so maybe I shouldn't have. Or maybe I really did need to use the "/install /silent" switches despite Tommy's admonishments. Dunno. Anyway, it's done: I use the hexed dxsetup.exe file together with the /install /silent switches from cmdlines.txt as indicated above and all is well. And since it is installing from cmdlines.txt, I can always remove it easily to cut bloat.

I have a Windows 2000 machine ready and waiting. Edit: worked flawlessly on my Win2K machine, almulder, very nice. I take back what I said in an earlier post, I believe I WILL be using the player.

TommyP's method is peerless, truly a joy watching his work in progress. IE6 slipstreamed, hotfixes slipstreamed, switchless installers installed. I used his method on Windows 2000 Advanced Server SP4 and it went off without a hitch, save for two problematic hotfixes. Eh, small potatoes.

That looks really nice and clean, will you be making that available for download as a theme that others could use, d0nut?

It has been mentioned before by Ghost82, and the more I think about it the more I want it: "Themed" selections. Let's use the example of a parochial school environment with an already overburdened network: 1. If I have to reinstall on five machines during the lunch hour, the school's lunch program software will choke (don't ask). Network installs are out of the question. Install from CD works. And with WPI on my side, I can get in done in the time allowed. 2. In my case, four Themes would be real handy: student, teacher, office, parish. Short and sweet. I could give a disc to one of my sixth graders, and he/she could do the install. "Andrew, take this to Miss Sue's room and scrub computer four, partition it 20/40 and choose the student theme, got that?" How cool would that be? And child labor laws do not apply. If you could pull that off, Almulder, I for one would be eternally grateful and consider my WPI complete. I can envision new variables added to programs in config.js. The rest is a hair-pulling mystery to me at this point. But where to put the check boxes? Below the main buttons and above the clock?

Looks very nice, LS, especially that clock.

@Lost Soul: I suspect there is a way to keep that popup in place. There's a great Javascript feature called overLIB you may be familiar with, and maybe that code can be adapted for WPI. I know the current WPI code behaves a lot like overLIB, for example, you can adjust the code to move the tip box further from the pointer. My pointer is large and invariably covers part of the tip box title, so I moved it about 25 pixels away from the application description (I think the default is 10 pixels, too close for my tastes). The overLIB code lets the box disappear on mouseout, or close with a click to a small "x" that appears in the right margin of the title. If the box can be made static, then your link feature would fly, Lost Soul. @Glent: Before Lost Soul does all the work , any interest?

Maybe the next version can ship with two themes, "Classic" and "Gloss"? In the early going the emphasis was on functionality maybe, 'cause the graphics were pretty basic and I never did hanker to them. I know whoever made the title worked long and hard on it, but.... Moving the title to the top area was smart, in my opinion, as that top area represents 10% of the viewable app. The move creates more room for all of your apps where it counts. And those buttons.... Of course, Kel- has included the buttons I made so my opinion is hardly neutral. The reason I busted my butt was to help improve the look and feel of the app. The transparent .gif effect simply does not work, so something needed to be done, IMHO. For example, the old buttons included a highlight effect, but is was hardly noticable, and had a choppy white outline. Again, if the original creator is reading this, my apologies up front but that's the way I feel. I also feel the emphasis on functionality remains at the top of the agenda, and that's a good thing. A lot has been done under the hood with this new version. For example, getting the audio player working, and working as well as it does, is nothing short of miraculous to me. Am I ever going to use it? Probably not. But it's there, and it's much easier to remove than to create. The category selection feature is nice, and several bugs have been ironed out from features beneficial to n00bs. Did I need or desire those features? Heck, I still edit the config.js file directly and probably always will 'cause I'm a stick-in-the-mud that way. No attacks intended or implied, this is a discussion worth having.