Nologic

Okay try this

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

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

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

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

Okay links in this thread have been updated with the "If...Then...EndIf" issue resolved. Man not doing for s*** on these scripts.

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.

Not as of yet...haven't even looked into that....this is the first time I ever monkeyed around with these apps.

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.

Fixed...blah the same frigging typo

ProtoWall managed to get a typo in it...now fixed As for it not working at all....all I can think of is that your not toying with the Beta which is what the script was done for....I'll look into doing the release version later today if possible.

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

Your welcome...hope it didn't cost you a disk.

hmm run it as just a script and see if you can get a line number...I'll look into it...hands tied up right now. Heh okay never mind found the issue...bad copy paste deal....no idea how I managed it but I did...try the scripts now...they have been updated. Sorry about that.

There are no switch's but there are scripts.

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 "\" & $SK_1 & "\BootSkin.ini" basically amounts to \WinBlue\BootSkin.ini 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

Also the file for Protowall if you use that as well Updated.....victim of a bad copy paste....hehe had two "then" statements back to back. Updated....blah typo managed to slip by

Well where to start...hmm how about hunting through the attached script and getting a feel for it...then move on and try your own hand at this. I'm just learning my self...so I keep finding new ways of doing things for the better. Any ways install AutoIt, edit the scripts user var's to what you like, compile the script and place it next to the install file, then just call the compiled AutoIt script from RunOnce or your batch file...or how ever you do it and the script should run smooth as silk. Updated.....victim of a bad copy paste....hehe had two "then" statements back to back. Updated....typo error

Is it a freeware app? If so then maybe I can whip up a script for it...if its not insane to install. Okay found it...it is freeware...so I'll take a look at what I can do...tho in turn I'll hope that you will also take up writing scripts and sharing them with others. Makes life easier for every one.

Check this thread for a tool that will help you out.

Should just need: /S It must be upper case.

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

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.

If you place it in the default profile thats stored in the firefox app folder it should be copied to any and all profiles created.

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.