Ok, so I have been able to install themes for CursorXP, IconPackager, and WindowBlinds (had to use a Reg Key for WindowBlinds to make it totally work), but am not sure how to do the same with BootSkin (1.05). Here are the codes I've been using in RunOnceEx (please note, that each of the *.exe Installs were created with AutoIt 3 scripts).

REG ADD %KEY%\075 /VE /D "CursorXP 1.3" /f
REG ADD %KEY%\075 /V 1 /D "%systemdrive%\Install\Applications\CursorXP\CursorXP_1.3.exe" /f

REG ADD %KEY%\076 /VE /D "CursorXP Skin" /f
REG ADD %KEY%\076 /V 1 /D "%systemdrive%\Install\Applications\CursorXP\Abracadabra.CurXPTheme" /f

REG ADD %KEY%\077 /VE /D "IconPackager 2.5" /f
REG ADD %KEY%\077 /V 1 /D "%systemdrive%\Install\Applications\IconPackager\IconPackager_2.50.exe" /f

REG ADD %KEY%\078 /VE /D "IconPackager Skin" /f
REG ADD %KEY%\078 /V 1 /D "%systemdrive%\Install\Applications\IconPackager\Abracadabra.ip" /f

REG ADD %KEY%\079 /VE /D "WindowBlinds 4.4" /f
REG ADD %KEY%\079 /V 1 /D "%systemdrive%\Install\Applications\WindowBlinds\WindowBlinds_4.40.exe" /f

REG ADD %KEY%\080 /VE /D "WindowBlinds Skin" /f
REG ADD %KEY%\080 /V 1 /D "%systemdrive%\Install\Applications\WindowBlinds\Abracadabra.wba" /f

REG ADD %KEY%\079 /VE /D "BootSkin 1.05" /f
REG ADD %KEY%\079 /V 1 /D "%systemdrive%\Install\Applications\BootSkin\BootSkin105.exe" /f


It appears the BootSkins have 3 separate files (note one like all the other applications).

Anyone have any advice or tips on getting this to work?

What reg key did you need to add for windowblinds...maybe I can add that into the script (automated).

I'll look into bootskin later today...hell I didn't even know about the app till I was surfing thier web site the other day.

Any ways post what you come up with and I'll look into it as soon as I stop feeling like death warmed over....got a nasty cold right now.

Oh did those latest edits to IconPackager work out fine or are you still having issues with it?

Wow, ok, 1 at a time....hehehe...

1. Here is the reg key I use to install a theme with WindowBlinds v4.4 (this in addition to the RunOnceEX entry above)...

;----- WindowBlinds Silent Theme install
[HKEY_CURRENT_USER\Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX]
"Skinset"="C:\\Program Files\\GUI\\WindowBlinds\\Abracadabra\\Abracadabra.UIS"
"Skinset2"="Abracadabra"

The reason why I do the reg key, is because WindowBlinds needs you to click a popup tray bubble to apply the skin. Well you can't do this during RunOnceEx, so by adding the reg change, the skin is applied.

2. I found a couple of reg entries for BootSkin, but the problem is, Bootskin wants you to Apply them when the skin is selected. So my current work around is to run the Skin from RunOnceEx...

REG ADD %KEY%\082 /VE /D "BootSkin Skin" /f
REG ADD %KEY%\082 /V 1 /D "%systemdrive%\Install\Applications\BootSkin\WinBlue.bootskin" /f
REG ADD %KEY%\082 /V 2 /D "taskkill.exe /F /IM BootSkin.exe" /f


Then add this to the registry...

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"


This enables the Skin I want. Was hoping there was an easier way though.

3. Actually still having problems with IconPackager and CursorXP. Both popup windows after they are installed. CursorXP brings up the Mouse Properties Screen (from Control Panel). While IconPackager brings up the same window. The workaround is actually easy, after cleanup.cmd is run and the system reboots the folders go away.

blah lost my orginal responce...to foggy in the head and clicked the wrong button...blah

Well I'll look into fixing the scripts again...I don't know why it works for me and not you since we are both USA....very odd.

Any ways I'll do a write up and post some beta scripts for you to try out.

Okay since its been my experince that UIS file names always match the skin name and folder name I've added only one new user var "$SK_1" which should ideally match as I said before. So setting that value will add the values needed for the reg entry.

I've also added in that should the script fine a self extracting WinRar file (sfx) called Skins.exe it will extract it to the installation folder.

The base idea is that since all wba files are just zip files with the file extension renamed...on just extracts them into a folder then use's winrar to rar them then change the rar file into a plain jane sfx file...with no fancy stuff added. then drop the sfx file in with the compiled script and install file and one is good to go.

Same thing more or less applys to BootSkin as well.

I'll post a file with like changes to it as well.

Okay same deal as above...test it and let me know if it does in fact need to be ran through the executable.

Ok, I have been testing the BootSkin one, and have found a few problems (and stuff I needed to change for my install).

I guess you are installing a version that comes with LogonStudio (I have the freeware version from StarDock's website), as I dont have any of that Logon Studio stuff.

The script works good (and even the Wincustomize Window closes down now), but the Skin part doesn't work correct. Here is what I've done to correct it so far...

1. I fixed the name problem, should be this..
$SK_1 = "WinBlue.bootskin"

2. When the skin is extracted from Skins.exe, it is placed in the BootSkin folder (I changed the location in my install to GUI\BootSkin, and this is where the Skin is placed. However, this is incorrect, BootSkin reads all it's skins from the BootSkin\skins folder.

Ultimatly, what needs to happen is, the file is extracted from Skins.exe, and then executited. This will create the WinBlue folder under \skins, then BootSkin comes up, and you need to just click the Apply button. Then Click Ok when the new window pops up. Then Close the BootSkin Window.

Okay updated the script a bit. Use the same link above.

Okay the skin folder was some thing I goofed on.

How ever I don't think we are on the same track about the *.bootskin files....hehe and my head is still floating so...any ways the *.bootskin files are in and of them selves zip files....what I'm purposing you do is take them and extract them into a folder...which should in and of them selves create folders inside that one...which should match the name of the skin.

So if you have a file called WinBlue.bootskin and extract it into a folder called foo, there should now be a folder inside foo named WinBlue-

foo\WinBlue\

Now inside of WinBlue you should have *.bmp and bootskin.ini and maybe another file most likely another *.bmp

That aside...the idea behind the skin.exe is to archive a number of boot skins...that have already been decompressed, and place them where they need to be...I'm fairly certain that BootSkin is just reading the registry for the file to load...and if so then just the reg edit is needed.

Now $SK_1 should just be:

$SK_1 = "WinBlue"

Since its used for the reg edit only...example



basically amounts to



The edit you just posted...would not apply correctly in this case. If is does then I'm dumbfounded as to how.

Well if I got things screwed up...I'll have to look over things in a day or so after I'm done with this cold...my head is total s*** right now

Any ways best of luck

Ok, the new BootSkin script is working very well. Only problem now is getting the correct Skin to load. Apparently, the two Reg keys listed don't seem to work (it keeps starting with the TimeWarp skin (and I have been unable to find where this setting is in the Registry.

These are the paths I've found so far...

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"

I'll look tomarrow, if there is a hidden switch I don't know about....

Okay let me know whats up, and we'll get things all tweaked up.

Well, I've tried both BootSkin and WindowBlinds, and am unable to get either to load the skin correctly. I have checked all the registry entries, but it appears there is something I'm missing and can't find.

The Strange thing is, if you actually click on either of the Skins (WinBlue for BootSkin, and Abracadabra - in my case - for WindowBlinds), and then apply the registry tweaks, they work fine. Must be missing some setting in the RAR.sfx files. Not really sure.

Is there a way to have AutoIt run the skin files, and perform the steps necessary to install them as part of the overall script?

So for example, after the WindowBlinds software is installed, the skin you want (*.wba file) is doubleclicked, and run (which requires the bubble in the system tray to be clicked to apply it). Or for BootSkin, when you double click the file, BootSkin comes up, and you need to click Apply, then Ok, to have the Skin installed.

Well I got some idea's of how to go about that...I'll see what I can get coded up.


*Update*

Got some thing for you to play with that should do the trick for WindowBlinds.

Just set $SK_1 to the name of the skin you want to use as it would appear in the skin browser...since thats how its going to find it.

I gave it a 4sec sleep "Sleep ( 4000 )" after selecting the skin...to hopefully give it time to load, before closing the browser window.

Just WinRar the decompressed skins like mentioned prior, and SFX it to a executable "Skins.exe" and place it next to the script and you should be good to go.

'Cross's fingers'

I'll look into bootskin later.

Ok, found some new problems with the new WindowBlinds script...

1. #cs before Run causes the script to hang. Removing this causes the script to continue.

2. I get this error, when the Script is just about finished.

Line 0 (File "C:\Install\Applications\WindowBlinds\WindowBlinds_440.exe"):
$wba = FileFindNextFile($search)
Error: File Handle invalid. Make sure that the FileOpen command succeeded.

Oh my god......this cold is going to be the end of me I swear.

Okay for one the right file is now linked above.


Yeah #cs to #ce is stuff commented out, with out needing to put semicolons on every line.

Well try the new script...it "should" work now that its the right one.

Script doesn't even seem to start, get this message...

Error: "If" statement has no matching "EndIf" statement.

Also noticed there are no more Registry entries at the bottom. So not sure how your making the correct skin load.

Would just like to say thanks for working with me on these scripts, and I hope you get well soon. My only advice, take ColdEeze.....reduces the duration and severity of colds big time.

I have a question on the CursorXP script you did as well on a previous post, but lets finish the WindowBlinds, and BootSkin problems first...

Okay links in this thread have been updated with the "If...Then...EndIf" issue resolved.

Man not doing for s*** on these scripts.

Ok, script gets hung at the "WindowBlinds Advanced Configuration" screen. It appears to be getting stuck at the Finding Skin screen (not sure if it is even looking, but I see where your going, and this looks promising).

Well is it hung or sleeping....it has a 4 second sleep after hopefully finding the skin.

Basically whats suppose to happen when you get to that screen...is that it opens the "find" dialog....enters the name of the skin, hits {ENTER} performs the search....which 'should' come up good if the name is entered correctly....then it applys the skin and goes into a 4 second sleep in hope of being enough time for the skin to fully apply before closing the window...and moving on to doing other things.

So if its sitting for more than 4 seconds...its hung...if its only for 4 seconds then thats working as it should....now if the skin doesn't apply correctly then the sleep time will need to be increased.


doh! reread what you posted...frigging cold.....okay I'll look into the code there...it shouldn't be hanging on that dialog at all.

Okay try the attached code

Hehehehe, no problem, your on the right track. It does Hang (well after 4 seconds).

I guess the steps appear to be the following...

1. Click Find another Skin.
2. Enter Skin name.
3. Click Enter.
4. Click Apply this skin now.
5. Wait 4 seconds for skin to load.

It's hanging at the Find another Skin part.


I'm testing your new script now....

[Update]
Nope, new script above still hangs at the Find another Skin section. If I click find another skin, it will continue on with the script (all they way through to step 5), but the Skin doesn't load. Its as if, the Apply this skin now button wasn't clicked.

Okay...well I see my code is some what flawed any ways...well for testing any ways....since I'm seeing the times shift on the window...which of course depend on the font and font size used.

So have to try and make it more fool proof....blah

Okay....I think I got it....

Ok, now your really close, it still hangs at the Find Skin Screen. However, if I click the Find Another Skin button, the script continues to run, and the skin is installed without a problem. So just need to figure out why it hangs at the Find Skin Screen...

Does it enter the name of the skin before it hangs...or does it happen prior to the name being sent.

It happens before the name is being sent. So basically, the WindowBlinds Advanced Configuration comes up, and just sits there. If I click on Find another skin, it will fill in the skin name, and continue on with the script.

Okay try this

Nope, same thing happens as my above post.

I hope this does the trick because I'm starting to run out of idea's.

blah if you grabbed this with in the first 30sec's of it being posted please redownload...had a line commented out for testing.

Still stuck as listed above. Not sure why it wont select the "Find another skin" button. Especially when the whole rest of the script works fine. Maybe you need a pause in there somewhere.


Are you sure it's button 18, maybe that is the problem?

button 18 works for me while testing with it installed.

Hmmm, this is so strange. It looks like it should work, yet it never selects the Find another skin link (and the script is paused). If I manually click the Find another skin link, the script will continue, and everything works.

comment out line 112



and let me know if that makes a diff

Go figure, I go to tell you the good news, and my cable service goes out. Well, that last fix did the trick. I had to make one change, that was to increase the Sleep time to 2 seconds before clicking button18...

EndIf
;ProcessWaitClose( "Skins.exe" )
ControlClick ( "Installation Complete", "&Finish >", "Button3" )

; Configuration
ProcessWait ( "wbconfig.exe" )
;WinWait ( "WindowBlinds Advanced Configuration" )
Sleep ( 2000 )
If $SK_1 <> "" Then
ControlFocus ( "WindowBlinds Advanced Configuration", "", "Button18" )
ControlClick ( "WindowBlinds Advanced Configuration", "", "Button18" )

This gave it time to pick the correct skin, and then apply it (with a setting of 500, it would just select the default skin selected because it was so quick).

Thanks for all the help with that problem, now for the BootSkin issue....

hmm well we are closer to being done with it....not fully tho.

ProcessWaitClose( "Skins.exe" )

Was ment to make sure all skins had been installed prior to selecting one....as is its fine if only a small handful of skins are installed...tho if its a larger collection....depending on where the disired skin is in the archive...could reflect on if its installed in time or not.

So kind of need to find out why that hangs the script...or some thing to replace it....but we are dang close thats for sure.

Well, instead of using ProcessWait (skins.exe), why not just put a sleep value there. Not really sure you need it though, as the point of the script is to install a skin (just 1).

Any update on the BootSkin problems Nologic?

Just as an update, the Registry settings don't seem to work. The correct Skin has to be "Activated" within BootSkin for it to take affect.

Ok, after doing lots of research on the matter, I found a file that needs to be copied as well as the reg tweaks to make BootSkin work from RunOnceEx.

Basically, you need to run BootSkin, install the skin you want to use. Then copy the file vidstub.sys (from c:\windows\system32\drivers).

For Example, I'm using a skin called ab_bs. So after installing the skin, I copies vidstub.sys. I put this file in my $$\System32\drivers folder.

Then I copied these registry entries into my softwaretweaks.reg file (that installs after RunOnceEX)...

;----- BootSkin Silent Theme install
;[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BootScreen\Parameters]
;"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\ab_bs\\BootSkin.ini"
;[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\BootScreen\Parameters]
;"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\ab_bs\\BootSkin.ini"
;[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BootScreen\Parameters]
;"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\ab_bs\\BootSkin.ini"

That's it. When Windows starts up, the correct Bootskin is running.

Okay this should do the trick....should require no hunting through the file system or reg entrys.

Just create a folder next to the script called "Skin" place the normal *.bootskin in it...it should ideally just be one skin...and the one you want as the default...if more than one is placed in there then it will be the last *.bootskin file imported that will be used....this is not recomended to install a bunch of skins this way since it would be very time consuming...thus the Skins.exe is still in place to handle any others to be added to the cache.

Tho I'm also thinking it might be nice to add to the script the ablity to delete default skins that are not disired by the end user as well.

Any thoughts on that?

Well let me know how it goes...should work just fine...then again I've said that prior with mixed results.

Script seems to hault at the WinCustomize Window. Doesn't search for the Skin at all...

Also, the part where...


; WinCustomize Window
Sleep ( 500 )
If WinExists ( "WinCustomize" ) Then WinClose ( "WinCustomize" )

Doesn't seem to work (doesn't work in IconPackager either). The folder WinCustomize comes up, but WinClose doesn't seem to do anything. Not sure if maybe the Window isn't active, or maybe WinClose isn't recognized (after all the script haults at this point). I'm thinking maybe you need to do a Control+W to close the window (or ALT, F, C).

thats really odd since it shouldn't hault there at all...I mean its a "if" statement with a really simple task.

It checks to see if a window called "WinCustomize" exists in some form or fashion...if not then the line is ignored.....should it actually find a window like that it will close it.

The way its setup doesn't matter if the window is active or not...just that its there...drawn or not.

Now it does close the window on my system...for both app's...that why it bug's me that it fails for you some how.

Well be sure to have this line under "Script Defaults"


to see where it is hanging...while the script may not be closing that window...it still should not hang.

Actually here is a newer version with a few tweaks to it...also one of the reason I'm slow to toss in Win+W or Alt+F+C is because of the possibility of some one running a app in the background....it might grab focus and thus get killed....and thats the same reason why I try to stay away from the "Send" command in general...if I have to I have to...but other wise...its a no no in my book.

Now if thats what you have to do to get it running correctly on your system then by all means edit it in that fashion.

Ok, strange stuff. If #cs is listed before run, I get the following error...

Line 0 (File "D:\the location of the file on my hard drive\BootSkin\BootSkin_1[1].05.au3.exe):

Run ($DL_1 & "\BootSkin.exe")

Errir: Unable to execute the external program.

The system cannot find the file specified.


The actual file name is BootSkin_1.05.exe, so not sure where it's getting BootSkin.exe from (I also removed the #ce just in case it might have caused problems too).

So if I remove that line, the script runs again. Now, here is the second weird thing. The program comes up, but nothing happens. I have to click Next at the Welcome screen. Then I have to click Browse, enter the location of the program (C:\Program Files\Tools - Shell\BootSkin), click OK, then Next, and then the script starts running again. If I check the Tray, it just says "Line: WinWaitActive".

I'm wondering if your running this on a virtual system, and its super fast, so you wont see some of these problems?

blast....I thought I had uploaded the uncommented version...sorry.



is used to run the application after its installed....but since I had the commented version up...the comments prevented the install of the app...thus the app's executable wasn't there.

As for the welcome window....I've been having some off tests with it...some times it works with "WinWaitActive" and some times not...thus resorting to "WinWait"...so other than getting the script to kick start it worked fine I take it?

Yep, works good. Funny thing about these scripts...I might have problems having to click buttons on occasion, but when you do it from RunOnceEx, they always work without a problem. Kinda strange, but that's why I'm not a programmer...hehehe

After seeing the work you've done to BootSkin to get it to load a Skin, I can't wait to see you fix IconPackager. I've been trying it, and its a b***h. Lots of screens you need to click just to install and load the Package.

Oh, and one more thing about the...

If WinExists ( "Object Desktop" ) Then WinClose ( "Object Desktop" )

The problem apears to be the time set to wait in the script. For IconPackager, I set the Sleep time to 5000, and now the Window will close. I think there wasn't enough time between when the Finish section was done, and when the above command was run.

Time for an update...

So I ran my Unattended CD with the changes to CursorXP, WindowBlinds, and BootSkin, and found these problems...

1. CursorXP: The Mouse properties comes up, when I click OK to close the window, the script seems to finish, but the correct skin is not installed (it's not even listed).

2. WindowBlinds: Wrong Skin is installed (its acutally the default skin that is listed that is installed). Again, the skin I want loaded isn't listed in the application. I'm guessing that the Skin.exe portion of the script isn't running correctly.

3. BootSkin: Waits for the first Input (up until after the Browse section), then it will pickup and run the rest of the script. However, the correct skin isn't installed (and again it's not even listed in the application).


I believe there might need to be some delays put in between the launching of the various parts of each script (as this seems the most likely cause, as each script seems to run fine, once I'm in Windows). I'm going to play around a bit with each script, and I'll post back what I find.

1. Thats odd

2. I think I changed the manner in which the default skin is applied...I think it now looks for a wba file in a folder called "skin"....double check the script and what I have posted...maybe we got somemix and match going on...or some thing.

3. hmm odd again....that should be working fine...I think we've been using the same method to select the default for bit now...so it should work.


Well I changed up how IconPackager selects the default theme....which should wait till the app's executable is in fact in the right spot at the right time....tho it may break else where...lot of windows as you have stated before to get s*** to fly....let me know.


This looks for ether of these (*.ip, *.iptheme, *.theme) in a folder called Theme for the default theme to apply

Okay changed around this as well....should pause till the app's executable is where its suppose to be.


And it is looking for a *.bootskin file in a folder called Skin....for the default file

Okay I got a little over zealous and deleted all the prior scripts to try and limit people from grabbing old scripts..well managed to delete the latest windowblinds one as well which some how I managed to also not save off locally.

Any ways this is a attempted to get things back where they where publically plus hopefully solve the issue with skins and themes not getting applied....this app also now checks to make sure every thing is in place before trying to launching any executable.

It also hunts for a wba file in a Skin folder in the same folder as the script to use as the default.

The code here hasn't been tested at all...but ideally it should work fine....key word is "should"

Really explorer and the registry are at the time of RunOnce loaded up well enough to handle this stuff....but I'm running out of idea's on how to fix stuff up. Well try them out and let me know how things go...and we'll go from there.

****, lots of testing...

Ok, here is what I found. Changing WinWaitDelay to 1000 (instead of 250) makes a big impact on how the scripts run. Currently, sometimes the scripts run to fast, and if you dont have a fast PC, it wont be able to keep up.

1. IconPackager: I believe you have a different version than I do. I am using 250h, so when you try to install the skin, it's looking for something different. So unless I can get your version, or I send you mine, wont be able to work on this. I believe the 250h is the newest version out.

2. BootSkin: Looks good, am going to test it Unattended and will let you know.

Update:
Just did another unattended and BootSkin again stalls at the first "Next" screen. Once you click Next the script continues. Then, the part about installing the Skin, never comes (Skin isn't copied over, and the default Skin is used).

3. WindowBlinds: Here is the old version that works...

Okay retweaked WindowBlinds script...default skin is a *.wba file in the skin folder next to the script. The archive is the last thing done in the script so any skins in it will not be able to be used by the script.

I think I may have an answer for BootSkin issue with the first window....give me a bit to code it up.


IconPackager....well its searching for the three main formats the packages are in...and I think the only diff between the versions we are running is that you see the lic screen where I don't for some odd reason...other wise they should be the same and look for the same formats.

latest build for Bootskin

*Update* Controlset or what ever doesn't seem to work when selecting the skin...thus the change to "send".