Nologic

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?

crahak - My option. hmm I didn't feel that I did attack you or make any thing personal. I took issue with your wording of your feelings towards AutoIt. I stated my findings, nothing more nothing less...for me your method is broken unless a time buffer is put in place and short paths are used in the syntax. I also stated that I know it works for some, but doesn't for others. All of them using proper syntax. If it was only my self exprincing this I wouldn't be stating its broken, I would have figured that I was simply doing things wrong some how...but I checked repeatively, and spoke to others about it, hence my comments. As for a AutoIt script hanging...normally if not allways its just a matter of getting the script to a point where it can pick up the ball and move on...and as for the orginal issue with the hang...well that deals directly with the lack of experince of the coder of the script and would be reflected just as well else where in thier unattended install, AutoIt or not. As for quiting...hehe well lets just leave it at the fact I've had my fair share of flame wars over opposing opinions...and I'm tired of it....I stated my facts as I know them...you then made it personal...so for me bowing out is just simply avoiding what I know is coming...I simply have to much on my plate right now to go round and round about stuff on some forum. In the end its my call, and well I elect not to contrib to the forum any more. SiMoNsAyS - hmm its also ones personal pref to contrib or not. This is not about being shown up...matter fact...I still don't see that as the case...I stand by my findings. It works for some...and doesnt' for others. Diabolical82 - Well I guess low end would now be: Athlon XP 2800+ 512mb PC2700 700gigs+ ATA 7200rpm ATI 9500 Pro (all other spec's not required) Frankly I find that over kill for running a batch file. Actually an old 486 33mhz would do fine.

Well mine my not be the top system here, but I won't call it "slower low-end rig". I tested from the command prompt ever which way...all syntax correct...I've heard this from many others when doing that way...it works for some and doesn't for others, system specs have nothing to do with it. That said I'll remove my self from the forum.

Well I'm a AutoIt fan boy. I'm moving away from silent installs...prefer more control over my setup now that I"m starting to toy with DVD builds...thus I don't have a Start Menu from hell or a Progam Files folder from hell ether. Tho if you like silent installs than I would suggest this helpful tool for finding what they are for a given app: Universal Silent Switch Finder

az

az

az

First off was it my scripts you where using and if so...what dialog box didn't show up...heh would like to get the scripts to work correctly for every one's use.

I would hanker to guess that if its my scripts the issue could be that I didn't place: Exit At the end of the script...please add that snippit of code and see if every thing works dandy. Other wise your guess is as good as mine.

No clue what you got looks right to me....this is what I have: REG ADD %KEY%\035 /V 7 /D "%CDROM%\SOFTWARE\System-Tools\Diskeeper\DiskeeperPro_8.0.478.exe /s /v /qn" /f

First off grab and start using this app right here. As it will inform you if a installer has any silent switch's. Oh and the switch is /s by the way.

az

Vann - hmm I don't know about ugly hack...matter of taste I guess. Actually I prefer the control that AutoIt give me over just a plain jane silent install...only a few installers out there allow you to set the destination directory and start menu directory...in general most just toss crap every where so when you finally login you are faced with a ungodly mess. Sure you can add in batch files to clean stuff up....but thats adding to the unattend CD\DVD and making more of a mess. Also I don't see the diff between keeping track of your setup.exe vs an autoit.exe.... I also find it reasuring to see app's actually installing rather than sitting there wonderiing if the system is hung or not. For each thier own...but I wouldn't be so quick to diss on AutoIt just for s***z and grinz.

Well I've started to do some thing of the sort with my AutoIt scripts....tho I'm just setting its install path if allowed by the installing app....some don't give you this option...so maybe in some corner cases I'll see about applying your idea. Any ways good post

Well you can use CMDOW.exe to hide the console rather quickly...or at least I see it for a brief second. Put the executable in your system32 folder under $OEM$ so that it gets copied over to your path. Then in your batch files put the following code at the top of it - cmdow @ /HID Tho I personally am getting around to using AutoIt more for things than batch files. As for themes....well I use the following entry in my WinNT.sif....don't know about editing the winnt.ini CustomDefaultThemeFile="%Systemroot%\Resources\Themes\ChaNinja Default.theme"

Heh not sure how to take that comment but any ways the script is currenly the last in this THREAD. Enjoy

There isn't one...thats what we tried to tell you. Maybe I'll write up a AutoIt script for it...might be nice for the unattend I guess.

Heh hopefully god will forbid it. I much rather see some one do up a autoit script and share it with the masses...then to have hunderds or thousands of people do the same manual work some one else has already taken care of. I mean look at how awesome it is to have XPCreate...awesome showing of scripting to save the masses work and effort and endless amounts of time.

To find out the installer and generally the switch's used for it please refer to the following link: Linky **UpDate** Just looked at the file its a SFX rar file, that then seems to extract its self and run a setup file that more or less moves the files where they need to be and makes the shortcuts and reg entrys as needed. The actuall setup executable doesn't seem to have any known silent switches. So to that end...I'd have to say make an AutoIt script to install it. You can find a number of sample scripts and links at the following links: Linky #1 Linky #2

This has also been addressed - -Here And -Here heh lots of people playing around with the idea.

I have it in "C:\XPCD\$OEM$" GreenMachine - Heh true enough

Well its been a long time since I've ever really done any programming but I know and understand most of the current conecpts. Really there shouldn't be any values needing to be pulled from the runonceEX key. IE or what ever will likely name its sub key out side of the naming convention used by us....thus IE might have a sub key called "ie_vxd_replace" or the like that wouldn't be over writen by some thing called "045". Also when apps add those sub keys they are assuming that you are fully logged in...not in the pre-login state that you are currently...which is what they are needing to preform what ever actions they need done. So really them being forced to run while in this state shouldn't be harmful at all. As for breaking things up I gave an example on page 2 of running multiple files doing this. Well here it is again just to save time hunting. WinNT.sif [GuiRunOnce] "%systemdrive%\Software\CD-DVD_Tools.cmd" "%systemdrive%\Software\Media_Tools.cmd" "%systemdrive%\Software\System_Tools.cmd" "%systemdrive%\Software\Shell_Tools.cmd" Thus like you said its easier to hunt through and code...plus to debug. I have no doubts that your method works as you have written, but I do think this way applys more cleanly...well codes more cleanly.

Your welcome

File #3 Complete set. If any one else has some good clean book marks please share.

File #2