Nologic

hmm why not just use LogonStudio....it works well and even has a AutoIt script to install it and apply a default logon. By the way its a free app offered by Stardock...the guys that make WindowBlinds, they also have one for boot screens.

battleangel3222 - CachemanXP request completed....that bloody thing is a monster. Hehe I expect to see some scripts out of you now over that one. The other one I'll look into at some point...but CachemanXP I did have a interest in...thus why its done up now.

Well if you use the AutoIt script that I created you should be just fine check the sticky.

Well you don't normally rar the au3 file, you ether compile it into a exe, which requires you to install AutoIt then just right click on the script and select compile script or you can have the AutoIt main executable copied over to the System32 folder then you can pass the script to the executable AutoIt.exe C:\Install\ObjectBar\ObjectBar_165_au3.au3 I maybe wrong about how its passed tho...I normally compile the script after what ever edits I need to make of course. So for me I would have some thing that looks like this: ObjectBar_1.65.exe <--StarDock ObjectBar Setup File ObjectBar_1.65_au3.exe <--Compiled AutoIt Script Now you could if you wanted to....rar those two files and in the comments section of the rar add some thing like: Setup=ObjectBar_1.65_au3.exe Tho thats guess work...you would actually need to look at the readme file for WinRar or search the forums...I know its all posted here some where.

hmm treading dangerous ground...warez and such are not to be discussed here and probably not even hinted at. This site gets a lot of traffic thus its watched...to give you an idea how much...I was at a Small System Builders thing here in the Seattle area held by Microsoft, and while shooting the s*** with a guy I happened to mention this site as a wealth of information and idea's. Low and behold the guy actually knew about the site. Oh any one from MS reading this. Thanks for the server packages and the new media edition. wOOt Scorage Really if MS has any thing going in your area at any given time...go to it..it was fun and very informative...tho could have been two hours shorter. Plus walking away with a hand full of goodies was worth ones time if any thing else.

You did use: Run ( "Outpost.exe" ) Or in some case's: RunWait ( "Outpost.exe" ) Now if the executable in not in the same place as the script you may need to do some thing like so: RunWait ( @ScriptDir & "\Outpost\Outpost.exe" ) Which basically means that on the same level as the AutoIt script there is a folder called "Outpost" and with in that folder is a executable called "Outpost.exe"

theres alsays AutoIt [link]

hmmm couldn't one also do it like so- RunWait(@ComSpec & " /c start %systemdrive%\ABC\abc.exe", "", @SW_HIDE)

Actually C:\ = @HomeDrive C:\Windows = @WindowsDir C:\Windows\System or C:\Windows\System32 = @SystemDir There is a huge list of them in the help file...look under "Macro Reference" Any ways your sample code would look like so: Run( @HomeDrive & "\ABC\abc.exe" )

okay I'll take a look at it later today.

While not silent...it will install it automated. [link]

Well some thing that could be done is to edit my pro build I just released to work with the PE version. [link] Just post it to that thread once done...and don't forget to tag your nick in as author

Well you could try your hand at AutoIt to install it. I'll probably start on IM's in about a week maybe sooner...hard to say starting on doing stuff dealing with security right now...antivirus, firewall,... If you do write one up be sure to share it.

Looks good I'll see about giving it a spin here before to long.

Maybe just AutoIt [link]

From what I'm aware of BootSkin actually doesn't edit any kernals....it simply creates and runs a service that masks the orginal kernals boot screen with that of the applications. That said I'd suggest using that BootSkin script I got written up and if you follow the directions fully, it will setup the bootscreen you want for your second boot. Now if you dont want to install the application, I think Alanoll has a topic pinned at the top of this forum that discusses how to manually edit the kernal.

Well if you save it off as *.logonxp and then use the AutoIt script I wrote up you should be able to do this no problem, just follow the directions for the script and you should be good to go.

[link]

Generally you can't...there is one type of installer that allows you to do this via a switch but for the life of me I don't recall. Now if you use AutoIt to automate the install rather than going silent...most apps you can change the default install directory...but there are a few that you still can't...well you could but its a pain in the rear end.

humm untested but some thing like this should work...and be fairly expandable to include other future hotfix types. Func _HotFix( $dir , $switch ) $search = FileFindFirstFile ( @ScriptDir & $dir & "*.exe" ) If $search <> -1 Then While 1 $fix = FileFindNextFile ( $search ) If @error Then ExitLoop RunWait ( @ScriptDir & $dir & $fix & $switch , "" , @SW_HIDE ) Wend FileClose ( $search ) EndIf EndFunc ; HotFix Type 1 _HotFix ( "\Type1\" , " /z /n /o /q" ) ; HotFix Type 2 _HotFix ( "\Type2\" , " /Q:A /R:N" )

Well you could compile a AutoIt script to do that fuction...some thing like the below code should do all of it if not the bulk. ; Install Type 1 Hot Fixes $search = FileFindFirstFile ( @ScriptDir & "\Type1\*.exe" ) If $search <> -1 Then While 1 $exe = FileFindNextFile ( $search ) If @error Then ExitLoop RunWait ( @ScriptDir & "\Type1\" & $exe & " /z /n /o /q" , "" , @SW_HIDE ) Wend FileClose ( $search ) EndIf ; Install Type 2 Hot Fixes $search = FileFindFirstFile ( @ScriptDir & "\Type2\*.exe" ) If $search <> -1 Then While 1 $exe = FileFindNextFile ( $search ) If @error Then ExitLoop RunWait ( @ScriptDir & "\Type2\" & $exe & " /Q:A /R:N" , "" , @SW_HIDE ) Wend FileClose ( $search ) EndIf Exit

Yeah you could try my incomplete AutoIt script...it gets it installed and thats about it...I don't own the app so...CloneDVD

mahi - Looks like they forgot to mention all the entrys in the WinNT.sif under [GUIRunOnce] for each file to be executed.

Well maybe its a url....ie MSN.url or maybe some other file extension....I'm sure you can remove it...its just a matter of finding out what type of link it is.

Well if you have the option of not installing it, when your manually installing the application...then it would be possible through the use of AutoIt.