Nologic

Miranda is a nice app...haven't used it much in the past but its good and worth looking at. GAIM is great...tho I have no idea if they fixed file transfers with it...only thing really holding it back in my mind. I own Trillian and use it normally...and its really slick...but that being said...right now I'm having a hell of a time staying connected to MSN...normally not a prob, but right now its a headache. My version is 3.1...and from what I hear on its forums most long term user's say its currently best to stay with the 2.x release's. Any ways my pick is Trillian...but MSN support is hosed currently.

Well edit it some more. change the finish window code to have a time out applied WinWaitActive ( "title", "text", 60 ) ; 1 min till time out If WinExist ( "title" ) then WinActivate ( "title" ) ; This gives focus...if focus was the problem double check commands...but it should be changed to some thing like that. I know this isn't posted in the thread any more...but all my scripts are only tested by me in windows...I have never tested unattended. Tho few have ever reported problems...hehe but problems have came up all the same. If that fixes the issue let me know I'll edit the script to reflect the changes.

Well last I checked the autoit thread wasn't locked. Just list what the file is for and attach it in any file format (txt au3 zip rar) or if need be copy the code in...tho its best if the file is attached so the thread doesn't get to unmanageable over time. Any ways its good to have another scripter around. cya

First off why is this not in the AutoIt thread...best if you stuff a copy in there for easy searching. Below is who I'd write the script based off what you have...you may or may not find this helpful. Dim $PID ; On Error Function Func _error($text) MsgBox (0, "Windows Messenger", $text, 3) ProcessClose ( $PID ) Exit EndFunc $messenger = @ProgramFilesDir & "\Messenger\msmsgs.exe" ; If Exists If NOT FileExists( $messenger ) Then _error("Messenger program not found, Exiting") Else $PID = Run( $messenger ) EndIf ; Logon Window #1 WinWaitActive ( "Windows Messenger", "LogonWindow", 2 ) If NOT WinExists ( "Windows Messenger", "LogonWindow" ) Then _error("waited for Messenger -- TIMEOUT") EndIf Send ("+{F10}!TO") ; Personal WinWaitActive ( "Options", "Personal", 2) If NOT WinExists ( "Options", "Personal" ) Then _error("waited for Options -- TIMEOUT") EndIf ControlClick( "Options", "", "SysTabControl321") Send ("{RIGHT 2}") ; Preferences WinWaitActive ( "Options", "Preferences", 2) If NOT WinExists ( "Options", "Preferences" ) Then _error("waited for Preferences -- TIMEOUT") EndIf ControlCommand( "Options", "", "Button1", "UnCheck", "" ) ControlCommand( "Options", "", "Button2", "UnCheck", "" ) ControlClick ( "Options", "", "Button10") ; Logon Window #2 WinWaitActive ( "Windows Messenger", "LogonWindow", 2 ) If NOT WinExists ( "Windows Messenger", "LogonWindow" ) Then _error("waited for Messenger final pass -- TIMEOUT") EndIf Send ("+{F10}!FC") Really the only thing I honestly have to suggest is that you make your code a little more readable...other wise your doing a great job, keep up the good work. Note: I may have the Send keys hosed.

Check AutoIt thread...not silent...but automated.

Check the autoit thread, I have a script in there...not tested for correctly hooking up to a drive server on the network...but other wise should be fine.

rcc1968 - Well the installer for WindowBlinds blows goats. One has to do a LOT of hunting around with the AutoIt Window Spy....since the name of the buttons are all over the place and not where they should be....and some I don't even think show at all....hence why I don't have it completely configurable....just way to much work for little to nothing in return...heh might be different if there was money involved...but when its for free...p*** on it. Any ways I've attached a more recent build....that should solve some issues for others. Namely if they wish to install one of the default skins rather than a 3rd party one....3rd party skins are still supported as before....just look through the user var's and set things correctly. Basically if you choose to apply one of the default skins....it will prevent you from applying a 3rd party....this doesn't mean that you can not add 3rd party skins via the skins sfx file....you can still do that. Any ways take a peak and see if things are better for you or not...if your looking to tweak every thing possible....your compltely on your own...since I have no disire to do that much hunting.

Well link to a post that use to be here at one time. [link] Any ways looking through the script you can see where I've copied stuff into the default install...so that it would be later added to any new user accounts made. Any ways you could modify that script to move things around or install themes and extensions...so that they are available for every one. Sorry this isn't directly on subject....tied up with other things so just kind of spamming threads while I can do so.

In SiMoNsAys FF thread I have some code that will install extensions and themes post FF install. I still haven't looked at the 1.01 update...maybe they have fixed the issue that I'm having of adding extensions and themes directly to the installer with out me needing to automate the repackaging of the extensions...maybe I'll get around to it....tho the rough in code for this is also listed in simons thread. So any one that wonts to get thier hands dirty go a head, but be sure to post your results when done.

Very minor update changed USSF to use latest build of PEiD v0.93. (simple find and replace in script) [PEiD] For those that do not know the Helper.bin is just the exe of PEiD renamed.

ZileXa - Whats the title of this thread? I don't think its AutoIt Q&A Also the FindCD fuction does work...I have a more advanced version of MHz code used in a RunOnce script of my own. Quickly looking over your code I'd suggest altering the last line to look like so: Run($installapps & "\autogk.exe") If that doesn't solve your problem...then don't post it here in this thread....PM Mhz or my self or some other autoit author or simply post in the normal app forum. Asking questions in this thread would quickly make it useless.

SiMoNsAyS - Thats not fully correct...that set of scripts I posted prior to add XPIs and JARs does work....the problem being the install.js files contained in most of those files fail...or so it seems. Out of the current 78 XPIs I use only 3 managed to install, jslib & launchy...and some other one that doesn't come to mind off hand. I don't recall if the theme JARs installed correctly or not...I was far more interested in the XPIs. Maybe tomorrow I'll look into automating repackaging the XPI files prior to adding to them to the installer. So we are close to a break through on repackaging the installer...if I just get off my a** and finish some stuff up and do some more testing....so maybe...just maybe.

LOL well I just changed a bit of the code you showed before....I actually didn't test it against Opera....I just said that....I used Notepad since I dont' have Opera installed....and what was originally in that post of mine...made a very ugly mess. Any ways just launch it from the registery to keep it hidden from the old man.

CyberSlug - Thanks for the update to the code & good to see you visiting.

Opt ('TrayIconHide', 1) While 1 Sleep ( 250 ) IF ProcessExists ( "IEXPLORE.exe" ) Then ProcessClose("IEXPLORE.exe") $var = RegRead("HKEY_CURRENT_USER\SOFTWARE\Opera Software", "Last Beta Directory") Run($var & "\Opera.exe") EndIf WEnd MsgBox ( 0, "title", "text1" & @LF & "text2" , 60 ) doh first code would spawn the hell out of Opera

You should be able to export them to html and import them back or into any other browser out there....but its native bookmarks...no clue.

Well I personally haven't messed with hiding windows or keeping things minimized tho there are commands available to do so....how well the script works while in that state is unknown to me. Personally I prefer to see the installation taking place even more so when it comes to AutoIt handled installations....some times a script will fail if written incorrectly...with the installation shown...if need be you can abort it...where hidden...it could be difficult to exit the application and recover. Heh how ever you do have the source code so by all means dig in and see what you can make happen with it.

heh got to pimp AutoIt...yeah off topic to some degree. FileMove ( "G:\My Documents\Firefox Downloads\installer.ico", "G:\My Documents\installer.ico" , 1 ) ProcessClose ( "iexplore.exe" ) WinClose ( "Yahoo!" )

muiz - Not to get down on you...just you phrased your statement wrongly...in which you kind of knock the project...and also expect things beyond what the project was meant for. Yes it would be nice by all means if it reported MSI files, and maybe I or some one else will alter the source code to reflect that...since it is public. Any ways refer to the Unattended Guide for the bulk of information about switchs. If you need at the drop of a hat information dealing with MSI's just open up the console '{WIN+R}cmd{ENTER}msiexec /?{ENTER}' and full details will be listed.

Here is the old AutoIt script....its one of many that I need to update and repost in the AutoIt thread. If it doesn't work for you...well your kind of on your own till I get the newer version posted. Well good luck. file removed

May I ask why you would need to know what the switch's are when you already know its a MSI file?

Just do the plain jane install...don't delete or loose your prior settings...just don't use them for the time being...and see if every thing works at that point. If every thing works....then add back in your settings...and test again...if a given xpi then fails try removing blocks of settings per xpi till you find whats causing it to fail....from a dup of your settings of course and not the original file. Once found check and see if the setting thats the problem is really correct or even still applies....if it is correct and still applies...then maybe hunt for a different xpi that does the same thing...but doesn't cause the conflict. If it doesn't work with a plain jane install try to find out what xpi if any are the cause of the conflict....and if one is found hunt for a replacement xpi or file a bug report...or better yet do both. I know for a fact I got to go through and alter mine....since a lot of stuff has changed since the last time I created my standard settings...it'll take time and effort....but at least I'll know I'm solid for ff 1.0

Well SiMoNsAyS I'd suggest you first off do a plain jane install of firefox...that means no pref's, extensions, or themes installed or copied over....then try those two extensions to see if they work via the commandline. If they then work fine...then you'll have to check and see if its old pref's causing the problems....or more than likely one of your other extensions conflicting with one or both of those. I've in the past ran into extensions that simply do not get along with others.

SiMoNsAyS - Well don't know what to tell you other than it worked for me....and I'm using FF 1.0 with Moox unarchived over top of it (testing) and the extension applied correctly from the commandline...I dropped it into the ff directory and started up "Take Command" (commandline replacement) issued the standard augments to the exe followed by the xpi name...went in with out a hitch. Astalavista - Maybe try some of the builds listed on the site linked to above...some user's have repackaged a few...and maybe they have builds that will work for you. Worth a look.

Well this is a list of known working extensions via the commandline...as used through my script....which should by all means work fine with Crahank's batch file. Adblock_0.5.2+_Nigthly_39_pass3.xpi Add_Bookmark_Here_0.5.3.xpi Add_N_Edit_Cookies_0.2.0.4.xpi All-In-One_Gestures_0.13.2.xpi Allow_Right-Click_0.1.1.xpi Alt-Text_for_Links_0.1.1.xpi Anidisable_1.0.xpi Autofill_0.2.xpi Autohide_0.9.8.xpi Bandwidth_Tester_0.4.1.xpi BBCode_0.3.7.xpi Bookmark_Backup_0.3.1.xpi Bookmark_Duplicate_Detector_0.0.1_rep.xpi Bookmark_Link_Checker_0.6.8_rep.xpi Bookmarks_Synchronizer_1.0.1.xpi BugMeNot_0.6.1.xpi Canonical_URL_0.1.2.xpi Checkboxer_0.5.xpi ChromEdit_0.1.1.1.xpi ColorZilla_0.8.xpi Compact_Menu_1.7.1.2.xpi Context_Highlight_0.1.xpi Context_Search_0.2_pass1.xpi CookieCuller_1.1.0.xpi Copy_Plain_Text_0.2.1.xpi Copy_URL_Plus_1.3.xpi Cute_Menus_0.4_qute.xpi Dictionary_Search_0.7.xpi Diggler_0.9.xpi Disable_Targets_for_Downloads_0.9.xpi Download_Manager_Tweak_0.6.3.xpi Download_Scan_1.0.xpi Download_Sort_2.5.xpi Edit_CSS_0.3.0.xpi EMbuttons_1.0.2.xpi Enhanced_History_Manager_0.4.1.02.xpi Ext2Abc_0.2.1.xpi Ez_Sidebar_3.1.2005012901.xpi EZNav_1.0.1.xpi Favicon_Picker_0.2.5.xpi Findbar_Basics_1.0.xpi FlashGot_0.5.5.xpi ForecastFox_0.5.8.xpi Gcache_0.2.1.xpi Google_Pagerank_0.9.4.xpi GooglePreview_0.8.xpi Grippies_0.1_rep.xpi Habari_Xenu_0.9.4.xpi Hide_Searchbar_0.2.xpi Hotmail_Tabs_0.9.xpi jsLib_0.1.245.xpi JumpLink_1.3.1.xpi Launchy_3.8.0.xpi Link_Toolbar_0.9.xpi Linkification_0.9.19.xpi ListZilla_0.5.1.xpi Local_Install_1.2.5.xpi Open_Long_Url_0.1.2.xpi Paste_Happy_0.6.xpi Popup_Allow_0.2.2.xpi Print_It_0.2.1.xpi Related_1.0.xpi Sage_1.3.xpi Show_Failed_Url.xpi Sort_Bookmarks_0.6.xpi Statusbar_Clock_1.6.4_pass1.xpi Tabbrowser_Extensions_1.13.2005012901.xpi tabextensions_contextmenu_en.xpi tabextensions_ctrlnum_en.xpi tabextensions_focusprevselected_en.xpi tabextensions_smoothresize_en.xpi tabextensions_unread_en.xpi TargetAlert_0.7.3.xpi Toolbar_Enhancements_0.16.2.xpi Translate_0.6.0.6.xpi TripleSelect_1.5.xpi User_Agent_Switcher_0.6.1.xpi Windows_Update_1.0.xpi xMirror_0.1.1.xpi heh I'm sure there are many more...this is just a list of what I've used...and hence tested against. *Update* Added HTML listing of extensions...make it a little easier....but ever thing can be found at [link] Temp link to a rar of the collected extensions [link]