Nologic

You sure they are in @ProgramsCommonDir and not @ProgramsDir or heck they could be in both....so while you may move the allusers folder...you may not be moving the active user folder....or in some case's trying to move some thing thats some where else ie alluser vs user

Well its good it worked because I was really out of idea's of what to do next to try and fix things. Yeah it blows that I have to fix the scripts...but not nearly as badly as it would should several thousands of people be using my scripts...as is very few are. Plus the amount of scripts to fix now is far less than what it would be a few weeks down the road...so better now than later.

hmm this will really suck if this is correct but give it a shot. Do a find and replace all of "@WorkingDir" with "@ScriptDir".....if that does do the trick then I got a s*** load of scripts to correct. Tho its better to have them working than broken.

Heh yup...here is a few examples...cut up and edit how ever you like. Run ( "setup.exe" ) Do Sleep ( 250 ) Until ProcessExists ( "setup.exe" ) = 0 Run ( "some.bat" ) Exit Or RunWait ( "setup.exe" ) Run ( "some.bat" ) Exit Ether should do the trick

[link]

hmm you could see about editing that script of mine in the Winamp Autoit thread. Should really just be a matter of removing the stuff for the registration is all.

chrno2004 - Heh sure you may ask but that doesn't mean you'll get an answer. J\K What it does is execute all the entrys you just made in the RunOnce reg key. So in the above example you would see a dialog list called "Installing CD & DVD Tools" that would look some thing like so: After that one completes it would disappear and a new dialog list would be displayed....lets say Tools - Shell is next...you would then see So on and so forth....just one dialog at a time...and only one displayed...no clutter and nothing running off the screen...and all happening prior to first logon. Hope that explains it...

There is nothing that I know of that does it in that manner...best bet would be to try out Xplode and see what you can do there....

In your WinNT.sif file under [GuiRunOnce] add lines to future files like so: [GuiRunOnce] "%systemdrive%\Install\Tools\Tools - Archive.cmd" "%systemdrive%\Install\Tools\Tools - CD-DVD.cmd" "%systemdrive%\Install\Tools\Tools - Java.cmd" "%systemdrive%\Install\Tools\Tools - Macro.cmd" "%systemdrive%\Install\Tools\Tools - Media.cmd" "%systemdrive%\Install\Tools\Tools - Network.cmd" "%systemdrive%\Install\Tools\Tools - Office.cmd" "%systemdrive%\Install\Tools\Tools - Shell.cmd" "%systemdrive%\Install\Tools\Tools - Spyware.cmd" "%systemdrive%\Install\Tools\Tools - System.cmd" "%systemdrive%\Install\Tools\Tools - Text.cmd" "%systemdrive%\Install\Tools\Tools - Viewers.cmd" "%systemdrive%\Install\Tools\Tools - Web.cmd" Each file is then coded up like so: cmdow @ /HID @echo off for %%i in (C: D: E: F: G: H: I: J: K: L: M: N: O: P: Q: R: S: T: U: V: W: X: Y: Z:) do if exist %%i\WIN51 set CDROM=%%i SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing CD & DVD Tools" /f REG ADD %KEY%\005 /VE /D "Installing ASPI Layer" /f REG ADD %KEY%\005 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\ASPI\ASPI.cmd" /f REG ADD %KEY%\010 /VE /D "Installing Alcohol 120%" /f REG ADD %KEY%\010 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\Alcohol\Alcohol_120%_1.9.2_au3.exe" /f REG ADD %KEY%\015 /VE /D "Installing AutoPlay Media Studio" /f REG ADD %KEY%\015 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\AutoPlay Media Studio\AutoPlay_Media_Studio_5.0.0.1_au3.exe" /f REG ADD %KEY%\020 /VE /D "Installing BlindWrite" /f REG ADD %KEY%\020 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\BlindWrite\BlindWrite_5.2.5_au3.exe" /f REG ADD %KEY%\025 /VE /D "Installing CD-Eject" /f REG ADD %KEY%\025 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\CD-Eject\CD-Eject_2.62_au3.exe" /f REG ADD %KEY%\030 /VE /D "Installing CDR Diagnostic" /f REG ADD %KEY%\030 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\CDR Diagnostic\CDR_Diagnostic_1.7.2_au3.exe" /f REG ADD %KEY%\035 /VE /D "Installing DVDInfo" /f REG ADD %KEY%\035 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\DVDInfo\DVDInfo_Pro_3.29_au3.exe" /f REG ADD %KEY%\040 /VE /D "Installing EasyBoot" /f REG ADD %KEY%\040 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\EasyBoot\EasyBoot_5.0.3.426_au3.exe" /f REG ADD %KEY%\045 /VE /D "Installing ISOBuster" /f REG ADD %KEY%\045 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\IsoBuster\IsoBuster_1.6_au3.exe" /f REG ADD %KEY%\050 /VE /D "Installing NERO" /f REG ADD %KEY%\050 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\Nero\nero6316.exe /SN=****-****-****-****-****-**** /WRITE_SN /SILENT /NOREBOOT" /f REG ADD %KEY%\055 /VE /D "Installing UltraISO" /f REG ADD %KEY%\055 /V 1 /D "%CDROM%\SOFTWARE\Tools - CD-DVD\UltraISO\UltraISO_ME_7.2.2.872_au3.exe" /f start /wait rundll32.exe iernonce.dll,RunOnceExProcess EXIT Each file will be executed one after the other...enjoy

Updated LogonStudio hunts for a logon in "Logon" folder, then will add in additional logon's with a sfx rar called "Logons.exe" that should be placed next to the script\executable.

Same deal as above

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

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.

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.

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 @WorkingDir & "\Skin\*.bootskin"

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

blast....I thought I had uploaded the uncommented version...sorry. Run ($DL_1 & "\BootSkin.exe") 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?

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" Opt ("TrayIconDebug", 1);0=no info, 1=debug line info 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.

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.

hmm Firefox, Extensions, themes, bookmarks, passwords, plug-in's and more all in this script. For Extensions and themes only look 4+ posts up in this thread.

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.

God don't you just hate it when you have to eat s***. Well I finally got crahak's method of installing extensions to work...no clue how I f'ed it up but I managed to...same build as tested against prior...so...I got a mouth full. That said create two folders...one called cache_theme & the other cache_xpi save your themes in the theme one and as I'm sure you guessed drop your extensions iont the xpi one. Then place the attached executable out side of both folders, when called from batch or runonce or what ever it will install the contents of both folders...for this to work firefox has to be installed prior...and in its default location.

comment out line 112 ;ProcessWaitClose( "Skins.exe" ) and let me know if that makes a diff

button 18 works for me while testing with it installed.

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.