mritter

All but two of these has been added. @WosWasl: I may have an idea for the hardware checker. Made a note..... Started new topic at the top.

Post your ideas/requests here for future versions after 8.1.0.

The other thing is: when are you setting the cursor reg key? You would have to do it before WPI starts. That way the key is set, WPI runs, checks the key, does grayed accordingly. If you start WPI, begin install, set cursor, then no, the entry will never be grayed.

You are missing part of the key: RegKeyValue("HKEY_CURRENT_USER\Control Panel\Cursors\Arrow")=="F:\1SYSTEM\1cons\Cursors\Red.cur" Try it with the \Arrow added.

It works fine. You have to remember: the original intent of conditions was the OPPOSITE of what they are now. Big mistake on his part. Put an exclamation point in front of it. Think the reverse of it.

The CurrentInstall value on that line is set in a reg key under Current_User. If after the reboot, are you coming back as the same user? As in: I started the install process as Admin, created a user, installed some stuff, reboot, logged in as the new user.

I am using several <div>s with text-overflow:ellipsis;. I have it all working fine, but the ellipsis (...) is always black. How do I change the color to match the actual text color? In my style sheet I have tried: ellipsis {color:white;} Does not work.

No. That would be done better in a batch file.

Ummmm.......thanks. But there are only just a few strings translated. Could you do them all?

Your mission, if you decide to accept it, is to track down the tooltips flashing issue. In the Windows theme only the tooltips make the side panel buttons (Begin Install, Options, Config, etc) flash. It is very annoying. And the tooltip position is wrong. It gets moved above the mouse when it should be below it. That happens in all the themes. I would appreciate some help tracking this issue down. It is probably something simple that I am overlooking, but it is eluding me.

That is fixed for 8.1.0, as mentioned in another thread. 8.1.0 will be out soon........

I am not endorsing the use of it, but to whatever program you use it with it will look like a command line arg. If the program is finicky it may fail and not run because of a wrong arg value.

The cd check is slow. Nothing can be done for that since it is waiting for the drive to respond.

Sweet. I will get to work on the reboot request.........if I can get my computer to boot. I think it crashed last night.

Cool. "Number of failed installations:" should be an easy fix. Just wanted to make sure it was working as a whole. Will fix that tomorrow.

@kurzedmetal: Did you try out the beta copy I sent you via PM?

@icnocop: Did you try out the beta copy I sent you via PM?

I'd like to see people who I send betas to to get online and download them in under a week's time.

Each style has css and images. You need to create a new one from ground up if you want to change colors. Send me your samples if you have an idea for a new color.

I sent icnocop a beta copy with 2/3 of his requests done for beta testing.................

I updated the issue to handle the error codes properly. You are right, I had the results wrong. If no code is returned, WPI puts in 999. 0 is success. 1 usually means a file doesn't exist in a cmd call. cmd /c copy /y a b Used to return success, now returns 1. If file doesn't exist: d:\wpi\install\myprog.exe 999 will be returned since nothing was done.

That's why you don't extract the new version over top the old version. You end up with old unused files. Always extract to a new folder and then copy in your options files.

I did some updating of the WriteRegKey() to use the internal WMI version. This cut several seconds off the startup time.

I use a window resolution one size smaller than my screen so I can see the task bar, some desktop icons, etc. I only use full screen when burn a finished dvd. I will send you a "test" copy this weekend with some check points. Send me an email to remind me.

You probably need complete path names: start /wait c:\wpi\install\dotnetfx.exe /q /c:"install.exe /q" The /c:"install.exe /q" looks alittle weird, too.