Nologic

hmm not sure if there is suppose to be quotes around the 8 when using id's...well use ?mouseclick? to move the mouse where it needs to be to click the button.

Well you could use Javascript, VBscript, or AutoIt to help improve over the batch script. I'd personally suggest AutoIt, since you could build simple gui's if you like for end users or your self...also its easy to setup so that only certain updates or upgrades are available to certain mac address's or domains\workgroups. AutoIt could automate login as admin, performing the required updates then logging out to enduser...so every thing is done after hours out of sight and mind of the staff there.

Well I've been away from the scene for a bit...but its my understanding that most recommend using the control id rather than the name of the control....if that still doesn't fly...maybe just send the mouse over to click the control. Also in newer builds of the installer different controler names may have been used. Keep in mind that windowblinds should be the last autoit item to be installed since its skinning of controls breaks autoits ablity to read and manipulate them.

Hehe there are other reasons to use autoit to install applications....like being anal and not wanting a cluttered up program files folder and start menu.

MOONLIGHT SONATA - Here you go...should be right...kind of rusty with batch scripts...autoit man my self...hehe hence I use AutoIt to do this exact same thing. CMDOW @ /HID @ECHO OFF SET TAGFILE=\WIN51 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:%TAGFILE%" set CDROM=%%i: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Group 1" /f REG ADD %KEY%\010 /VE /D "Application 1" /f REG ADD %KEY%\010 /V 1 /D "%CDROM%\install\Group1\App1.exe /silent" /f REG ADD %KEY%\015 /VE /D "Application 2" /f REG ADD %KEY%\015 /V 1 /D "%CDROM%\install\Group1\App2.exe /silent" /f REG ADD %KEY%\020 /VE /D "Application 3" /f REG ADD %KEY%\020 /V 1 /D "%CDROM%\install\Group1\App3.exe /silent" /f START /WAIT rundll32.exe iernonce.dll,RunOnceExProcess REG ADD %KEY% /V TITLE /D "Group 2" /f REG ADD %KEY%\010 /VE /D "Application 1" /f REG ADD %KEY%\010 /V 1 /D "%CDROM%\install\Group2\App1.exe /silent" /f REG ADD %KEY%\015 /VE /D "Application 2" /f REG ADD %KEY%\015 /V 1 /D "%CDROM%\install\Group2\App2.exe /silent" /f REG ADD %KEY%\020 /VE /D "Application 3" /f REG ADD %KEY%\020 /V 1 /D "%CDROM%\install\Group2\App3.exe /silent" /f START /WAIT rundll32.exe iernonce.dll,RunOnceExProcess REG ADD %KEY% /V TITLE /D "Group 3" /f REG ADD %KEY%\010 /VE /D "Application 1" /f REG ADD %KEY%\010 /V 1 /D "%CDROM%\install\Group3\App1.exe /silent" /f REG ADD %KEY%\015 /VE /D "Application 2" /f REG ADD %KEY%\015 /V 1 /D "%CDROM%\install\Group3\App2.exe /silent" /f REG ADD %KEY%\020 /VE /D "Application 3" /f REG ADD %KEY%\020 /V 1 /D "%CDROM%\install\Group3\App3.exe /silent" /f START /WAIT rundll32.exe iernonce.dll,RunOnceExProcess EXIT maxXPsoft - This is fine for those that don't want to get to deep with thier unattended CD\DVD while cleaning up RunOnce....yes your application is far more polished...but its probably much more involved than whats shown above as well. For the hobbiest & general power user...I'd have to recommend the above method...for the hardcore\admin\techs...I'd then recommend your app or WPI or Xplode or the like.

There is a different way to go about it...and thats to spawn runonce multiple times. In your batch file basically fill the runonce reg entry will all the programs you wish to do for a section, then call "rundll32.exe iernonce.dll,RunOnceExProcess" to execute that section. Then simply repopulate the runonce entry again, followed again with the above call...rinse and repeat, as needed. The end result is seeing runonce execute with say a list of CD\DVD apps...and installing them...then runonce will disappear and a new runonce will appear but this time say with Data Recovery software, so on and so forth. It doesn't give you sub menu's...but it does greatly clean up the look of things.

Well first you need to grab autoit its self [link] Then mostly its just looking at other peoples scripts, and reading the help file. Now the script above simply executes an *.exe installer, hopefully that of zonealarm. Next it simply waits for a given process to start...keep in mind that was a wild guess of mine of what Mailfrontier executable is named...so that may need to be altered...any ways once that process starts the script then continues...which is to kill that task and only that task. So idealy the rest of your zonealarm installation should go fine. So after you got AutoIt installed and the script edited to reflect the correct executables, you should be able to compile it into a exe its self...make sure the script is named different than the installer...other wise when the script is compiled it will replace the installer exe with its self...and to make matters worse...it would then repeatively reexecute its self...very very bad thing.

Heh just a few extra lines of code...never know might actually use that feature some day.

Maybe use a simple autoit script like below: ; Execute Installer If FileExists ( @ScriptDir & "\setup.exe" ) Then $PID =Run ( @ScriptDir & "\setup.exe /s /noreboot" ) Else Exit EndIf ; Process Hunting ProcessWait ( "Mailfrontier.exe" ) ProcessClose ( "Mailfrontier.exe" Exit

Heh well good deal

In AutoIt it would be ProcessClose ( "NLT4OfficeXP.exe" )

Installing a new shell isn't a problem...how ever far as I'm aware...they all sit on top of explorer...so adding new shell features will only increase the amount of memory used by the system. As for figuring out how to do silent installs...none of it is hard...the problem is there are dozens of ways in which to go about it. I'd suggest going the batch route..not at all because I feel its the best method...but from the sheer fact that more people in these forums are more comfortable with them, so you are likely to get the answers that you need in short order...rather than having to way days or weeks for a responce from some one in the know, for lesser used methods. Hehe just talk to any one thats PMed me with a question about one of my AutoIt scripts...I can be slow or unresponcive at times.

[DVDIdle Pro v5.5] Hehe the autoit file was there...but the name in the post was incorrect...name fixed.

Well if its just to move a shortcut...why not just use "FileCreateShortcut" to create a shortcut. That said there are a number of ways to go about it. If you already know how to find the CD via batch scripts, then you can use a batch to execute an autoit script on the cd next to what files you are looking to copy, move, install,.... by simply using the macro @ScriptDir which is the pathing info based on where the script is. So if your CD is D:\ and your script is in a folder called foo then @ScriptDir would = D:\foo That said I use the following code which is a mesh of code written by my self and Mhz...mostly Mhz's work tho. Func _FindDrive($type, $name) Local $drvs While Not $Drive $drvs = DriveGetDrive($type) If Not @error Then For $i = 1 To $drvs[0] If DriveStatus($drvs[$i] & "\") = "READY" Then If FileExists($drvs[$i] & "\" & $name) Or DriveGetLabel($drvs[$i]) = $name Then $Drive = $drvs[$i] & "\" Return $Drive EndIf EndIf Next If Not $Drive Then If StringInStr("CDROM|REMOVABLE|NETWORK", $type) Then If StringInStr("CDROM|REMOVABLE", $type) Then If MsgBox(21, "Warning", "Please insert media into a drive now") = 2 Sleep(1000) If MsgBox(36, 'Important', 'Are you sure that you want to exit?') = 6 Then Exit ElseIf $type = "NETWORK" Then If MsgBox(21, "Warning", "Please connect to a network now") = 2 Then Sleep(1000) If MsgBox(36, 'Important', 'Are you sure that you want to exit?') = 6 Then Exit EndIf EndIf Else If MsgBox(36, 'Drive Not Found', 'Drive could not be found would you like to exit?') = 6 Then Exit EndIf Sleep(2000) EndIf EndIf WEnd EndFunc You'll have to look up DriveGetDrive to get all the options that can be used for the $type values that can be passed to it. $name is passed to the function so that has a one of a kind file to look for example "win51" thats normally on all unattended install cd's. Your not limited to only the file name...you can pass path information along with the file name...but a file name is expected. Any ways you can see it put to use in my autoit replacement for RunOnce that is attached. *Update* Mhz did some code clean up on the _FindDrive function as can be seen above. I made $Drive global, and fixed the #include issue. Should work fine now.

Well then I guess you'll have to write your own application...and I really don't see or understand your dislike of these app's...your hang up I guess.

hmm Metapad, Notepad2, PSPad, SciTE...I don't know I mostly look for feature rich applications...hehe not feature starved.

hehe good deal & your welcome

it basically just adds to some thing prior...in the above case it adds a macro to a text string, then adds another text string to that. Heh its the same as the start where you have: Run (@ProgramFilesDir & "\D-Tools\... which joins what ever the pathing info is contained in @ProgramFilesDir to "\D-Tools\..., so its just splicing in info...its the same thing you have been doing...just placed some where else is all. Okay more of an example "\D-Tools\" is the same as "\" & "D" & "-" & "T" & "o" & "o" & "l" & "s" & "\" More examples Okay we know that @ScriptDir macro contains the pathing information of where the active script is located, in your example "D:\Install\battlefield". Now lets say we need the 8.3 file name conversion...short name in other words. Well we also know that by using the fuction "FileGetShortName" that it will return the 8.3 naming information that we need, example: $a = FileGetShortName("C:\Program Files") ;$a is probably "C:\PROGRA~1" But in our case it would need to be: $a = FileGetShortName(@ScriptDir) ;$a is probably "D:\Install\battlefield" So if we needed 8.3 file naming in it, then the line would look some thing like so: Run (@ProgramFilesDir & "\D-Tools\daemon.exe -mount 0," & FileGetShortName(@ScriptDir) & "\BFV_1.iso")

Run (@ProgramFilesDir & "\D-Tools\daemon.exe -mount 0," & @ScriptDir & "\BFV_1.iso")

Well here is a custom Avatar pack, size ranges from 48x48 to 100x100 in GIF, JPG, and PNG formats. They are archived in 7zip format, and there is a little over 2,200 of them, needless to say there is a wide selection to choose from. [link] Also if one would like to keep IM native emoticons. [link] Or if one wants some really fancy ones. [link]

Please no double posting. 1) Normally next to the application installation file. I use the following code to test if the file is there and if so install other wise exit. ; Execute Installer If FileExists ( @ScriptDir & "\GetRight_6.0.exe" ) Then Run ( @ScriptDir & "\GetRight_6.0.exe" ) Else Exit EndIf Now as for where on disk, every thing goes...well since I don't see the need to copy stuff to disk I just run from the CD, so the application would be located at some thing like "Software\Internet\GetRight" from the root of the CD. I use a custom AutoIt script to replace the RunOnce batch script...but there are dozens of threads on how to launch applications from the UA CD. 2) No 3) No, but refer to 1) 4) it may...not sure since I always use the @ScriptDir macro to set pathing information...that is if your talking AutoIt...if your talking about the RunOnce batch...then yes it does require full pathing info.

Well this is what I'm using from Deviant Art [X-05]

hmm resize the windows..and change the toolbar icon settings...probably a few other things tha could be done. Hehe of course one could throw money at the problem and get a bigger monitor and run a higher rez.

hmm why so hostil? I did NOT say every 3 days it crashed, I said about every 3 days...some times 2 days...some times two weeks. I also said what i'm running is modified, so that also should be taken into account when factoring in stablity. Most the skins I recall from 2.x blew, the ones I've seen thus far for 3.x look nice...plus if one really needed a 2.x skin to work with 3.x it would take all of what 3 hours in photoshop and a text editor to do the port. Plug-in's so far all the ones that I've had any interest in at all work fine with 3.x...tho your interest is bound to differ from mine. 2.x is nice...but it wasn't till 3.x rolled out that I decided to crack open my wallet.

WotC - Yeah every thing was updated to most current, but the problem has been solved...needed to add a check next to ssl or some thing like that for the MSN dll. So alls good again. Ghostrider - I disagree with you about stablity...trillian 3.1 crash's maybe every 3 days...so its fairly stable, and has yet to nuke any data. Also I have yet to run trillian plan jane so the crash's could be caused by a misbehaving plug-in...also I think the skinning format has changed from 2.x to 3.x so not running your prior builds skin should not be some thing to hold against it. Any ways if one likes lots of toys, trillian is the one to go with 2.x or 3.x...if you just need some thing to do multi IM then GAIM fits the bill nicely. tho those are the only multi IM app's I've ever spent any time with.