Djé

The way ExtractArgs(cmd) tries to extract the arguments part is not optimal as well: using "-" or "/" at the start of an argument is absolutely NOT mandatory. Actually I have a lot of commands with the arguments part not starting with any of these. And this will also make the FielExists(cmd) test fail...

Hi, And first of all, congratulations for the amazing work. There may be a small glitch in installer.js: In function InstallPrograms(), I found somewhat unfair the handling of the commands: Only those passing the FileExists(cmdLine) test proceed to the shell. Others are tagged as failed even before getting a chance to defend themselves. This way of doing leaves behing a whole lot of valid commands which are located in the PATH and that people usually call without any path (making the FileExists test failing). The most common example is 'REGEDIT' but RUNDLL32, NET, MSIEXEC, all the CMD commands, and many other would fail the test as well, while still being valid commands. As a practical case, with the new 'feature' I can't have anymore an Item grouping a whole lot of reg files like this: regb = 1stfile.reg cmd1 = regedit /s 2ndfile.reg cmd2 = regedit /s 3rdfile.reg [etc. [rega = 8thfile.reg]]My WPI_Log shows: cmd1 Fail: 'regedit' '/s 2ndfile.reg'because it could not find 'regedit' (while it just used it for itself one command before ) Of course I could go by using %windir%\regedit.exe, but that would be far from elegant. The thing is, I am also denied to install .inf files using RUNDLL32, to connect to shares using NET, etc. So I am really not sure that FileExists(cmdLine) is a good test, at least 'as is'. Specially if it's the only one. If I may suggest a couple of ideas for solving the problem: - At least an option might be necessary to disable it. (As for myself, I would prefer an option to enable it, for those who really need to check that). - The purpose of this test is to find out problematic commands by writing a log file of the results, isn't it? I don't know enough javascript, but doesn't the shell.run function return an error code if it fails? Wouldn't this be more recommended for debuging a list of applications? And at least the command would be marked as failed AFTER having been run Anyway, I am really impressed by the quality of the application and if I can be of anymore help to solve this, I'd be more than glad to give a hand. Thanks again, Djé

As a result of fruitful discussions with Sangi, Babylon6 silent installer is now on the air.

At the [url="http://www.msfn.org/board/index.php?s=&showtopic=34494&view=findpost&p=508816"]general request[/url] of Sangi, here is the follow-up of [url="http://www.msfn.org/board/index.php?s=&showtopic=20197&view=findpost&p=479407"]this[/url]: [size=4][color="#3333FF"]Babylon Pro v6.0[/color][/size] Script version: BabylonV6.0.au3 v0.0.1 [url="http://www.babylon.com"]Babylon Pro[/url] is an offline/online dictionnary. It runs in the system tray. You just call it using a (selectable) hotkey or mouse-key combination on the word you want to look out. It offers a very wide range of dictionaries that you can download to you computer for a free trial (30 days). ...but curiously no French-Portuguese dictionary This script not only installs Babylon6 (whichever main installer you choose), it also has the following features: [indent]- Completely Language Independant. -> No need to feed it with windows' title & text. It doesn't need it. - Uses a fully customizable .ini file to read the options from. - Completely silent. - All Setup Wizard's answers can be freely adapted: Language, License, Mouse Button, Destination Directory, Icons, Start now and spam. - Any number of additional glossaries can be silently installed during the same process, in a chosen order. - Reg tweaks (Dictionary Updates, Hide Translation window, Start with Windows) can be selected. - Microsoft Speech engine can be installed. - License files can be installed silently as well. [/indent] * No need to edit the script. * Just edit the options in the .ini file. All options are fully documented. * Then just run the script, compiled or not. Optional usages are also documented. The zip attached contains the AutoIt script (.au3) and my babylon.ini file as a template for yours.

Oh, and BTW: * This should work for themes as well. * Custom list of extensions are easily maintainable with a couple of clicks using the 'InfoLister' (in both Fx & Tb) and the 'DownThemAll!' (in Fx) extensions: - Use the attached custom template in InfoLister in both applications. - In Thunderbird, have InfoLister save the output automatically on startup to an html file of your choice. In Firefox: 1- Open 'about:info' (bookmark it to avoid retyping this long url ). This will display a list of your Firefox extensions .xpi links. - Or open your saved html file from Thunderbird (bookmark it?). This will display a list of your Thunderbird extensions .xpi links. 2- DownThemAll! to wherever you want (let's say a 'myExtensions' subfolder next to the script). Then use: MozillaProfile.exe Fx myExtensions or (for Thunderbird) MozillaProfile.exe Tb myExtensions InfoListerTemplateXPIdownThemAll.htm

The original idea is from benners: We both found that it is better to allow each user to use the extensions (s)he wants and ONLY them, because extensions are made for improving the USER's usage of the software. So we found ways to install extensions to the user's Profile folder (in %appdata%) and not in the Program's folder. The solution eventually found by benners is better than my 1st suggestion because it does not need to wait for the delay imposed on extension installation. Here is my version of his script. It also works for both Firefox & Thunderbird. But it does not deal with the application installation at all (I just use the -ms switch on the installer). Instead, it has other features: - It can restore a previously backed-up profile, or create a new one, or prompt the user to choose a profile to restore. Profiles are created/restored to the user's 'application data' directory.- It can install extensions to the user's profile. - Just feed it with their file names, or with a text file list or with a folder name (install everything in it). - Please note that the application must be installed AND a profile must exist prior to the use of this feature. - An option is still provided to install the extensions to the application directory, for those which the administrator feel are mandatory.- It automatically recognize and install Thunderbird dictionaries to the proper location (Thunderbird program dir\components\myspell). For this last trick to work, you will need to make sure that you don't use this stupid reg tweak about .zip files which deletes the CompressedFolder classe: Only keep the LAST line if you absolutely wish to Speed up Copying/Moving of .ZIP Files How to make the best use of it: *Multi-user environment*: - Have a post installer (like WIHU, XPLODE or WPI) run when a new user logs in for the 1st time (use a RunOnce key in the Default User's NTUSER.DAT hive for example). - This post installer could display a list of Profile options (create a new profile or restore a backup, etc.) as well as a list of available extensions or group of extensions that the user could choose from. - Each choice make run this script with the appropriate options to perfore the corresponding task. *Individual users*: -Just have one command in your unattended setup using this script to restore your profile, and one command using it to reinstall all your extensions at once. USAGE: Just run the script without argument to display the help message. It will tell you about what arguments does what. ...Or just read it in the script! ***Recent Beta AutoIt version required to run/compile it**** [Edit]minor changes to the help message. MozillaProfile.au3

Here it is, yet another version of the forked version This new version is compatible with the previous one. It has just *more* possibilities... Which will be used in the next version of the excel Progs Lists Manager. Stay tuned! kToolv1.1aY.1.au3

What about 'OEMSkipWelcome' (case sensitivity ) ?

Guys, did you search the forum or what??? For having the $oem$ folder copied over using winnt32.exe, you need both oempreinstall=yes AND either the $oem$ folder INSIDE I386 OR OEMFilesPath=..\$OEM$ in winnt.sif

Description: Substring search function that can search starting from the left or from the right. Programming Language: Visual Basic (for Applications, but I guess it works also with VB & VBS). VB functions for searching a substring in another string (like Instr()) all start from the left and search in the right direction, with an optional start parameter to start searching only from this position. No easy way to find the last occurance of the substring (like when you want to discriminate a file name from a file path searching for "\"). The attached function can accept a negative 'start' argument to start the search left wise from the end of the string, with a 'start' offset (also from the end). Both the offset and the returned position still apply to the leftmost character of the substring. Example usage code provided in the attachement. The 'maths' involved to avoid an unlegant 'If start<0...' were interesting... There is also another way arround using StrReverse(), but it is in fact not much simpler. stringFindFirstLR.vb.txt

Yes. Using a Reboot = 1 command will reboot right then (modulo a $RebootTimer period), after having scheduled itself to restart from where it stopped at next login (HKCU\...\RunOnce).

You may want to give a try to this method of finding the Drivers.cmd from DetachedProgram in winnt.sif. Just replace 'Detached.cmd' by something like '..\Drivers\Drivers.cmd' That way you could use any path. Check the value of 'dospath' in the '\SYSTEM32\$WINNT$.INF' when you install from your multiboot DVD, and adapt from that. Also, you may want to share the $OEM$ at the root as well by using something like: OEMFilesPath=..\..\$OEM$ in the [unattended] section of the different winnt.sif files.

I'm gonna try it as well. The .cvs thing was just what was missing in jcarle's. A question, though: what are those dll for?

Très très bonne idée, T D I haven't enough time right now to install OpenOffice* and look at how we can fix it, but if we could manage to make this work in a free, Open Source software, I would be delighted. Next Excel version of this is also queuing after my current project. I'll let you know, but if someone needs something, better ask it now *BTW, how would I do it unattendly?

Your list of switches is for firefox SETUP, but -setdefaultbrowser is a switch for the application itself. You would have first to install Fx, and then to run it using this switch. But this is not silent at the moment and you would have to close (manually or AutoIt) Fx window. In the next version (1.5.0.4) they will normally add a -silent switch to do it unattended: firefox.exe -silent -setdefaultbrowser

Kels, this is not a problem of SID or whatever. HKCU works fine. The problem, as usual, is to find the right time(s) to import it. Which can change from one tweak to another. This one tweak is really picky and needs the desktop (or explorer for that matter) to be allready loaded in order to work (that's why it works manually). But you can't import it at T12 nor with direct RunOnceEx. You'll need to make use of the 'programs\startup' folder to import it after the desktop is loaded. I've made a little batch that take care of this thing together with a couple of others needing the startup folder, if you want to give it a glimps...

The main technical problem is that you have to be able to read the content of your recovery CD. Usually those CDs are locked so they can only be read on the same machine, or at least on a machine from the same manufacturer. Can you find any I386 folder on the CD? How many files are there in it? If you insert the CD in the other machine and boot on it, what does it says?

Man, why not trying them all in real situation, and choose later the one you like best? Look at this thread.

Be careful: I think you have to have a 'space' and 'enter' (or vice-versa) after the word (which as to be spelled correctly, case sentive maybe). If you slipstream sp2 after the extraction of I386, you may not even need to write them, as they may be generated automatically by the slipstreaming process. On the other hand, if your CD has allready sp2 included and you don't slipstreaming anything, you'll have to write a 3rd file (win51ip.sp2 ?). The Setup.exe at the root is just the launcher thing showing-up when you insert the CD under windows, asking you what you want to do.

you only need the win51 file and its siblings. Others are useless. Search the forum for posts with win51 in the title and you'll have the recipe to make them.

That was a bit of work: I took the 'Drivers & utilities' CD and copied it to my HD. Then I went to Toshiba's website and upgraded the above tools and drivers with the last versions when available. For each of them, I then looked if there were an .inf file to install the drivers. - If found, I made a folder under $OEM$\drivers\ with all the necessary files for that driver (including the .inf & the .cat) and added the folder path to the 'OemPnPDriversPath' directive in the [unattended] section of 'winnt.sif'. See the guide for more details. - For the remaining ones, comming only with an .exe, I made a custom kTool file (you can use a batch, WPI, or whatever) to install them unattendedly at T12 (after having made silent installs using the -R switch & the setup.iss file). Unfortunately some of them still complain when installed this way and message boxes appears with errors. After trying different solutions (T12, RunOnceEx) for each of these problematic progs, I found out that despite these messages, they do get installed properly: the messages are in fact related to the 'running' of the progs which is automatically launched after the install (no way to prevent this) but don't work before the desktop is fully loaded or collide with the 'Run' reg key setup by these progs. So I just install them @T12 and don't look at the message boxes ! I prefer to have the ugly things occur at this early stage and have my RunOnceEx clean, without any error message. [Edit] Also, for some of the 'drivers & utilities', I simply did not install anything! Just because they are useless bull$hit...

I agree with maxXPsoft. 1. You only need the 4 files & the key. If the system on the computer is still the original one, you can use this method (provided the Royalty thing). 2. getkey.vbs works fine. Don't know about the other. But hey, it's not bad to have a confirmation: try both!

You've got 2 different things here: -the making of the 'local source' when using dos, which happen at the very beginning of the install. -the using of winnt.sif's answers such as the computer name, which does not happen before well in the GUI mode setup. I'm not sure what exactly you want to achieve in DOS (but tell us more about if you succeed) but AFAIK, the computer name inside winnt.sif has nothing to do with it so early in the process. And there are many other ways to deal with it later (but still unattendedly). For example the one adviced by Bezalel.

* What's in your 'autologon.reg' so that you have to import it for each user? REGEDIT /S autologon.reg * NET ACCOUNTS affects all users (type net help accounts for more infos) so for sure, this one doesn't need the repetition of the command: net accounts /maxpwage:unlimited * The /user: in NET USE is a user on the server, not on the workstation you're setting up accounts on. So again, no need to repeat the commands. Just have one line for each drive, using a user VALID ON THE SERVER. And don't forget the colon ( : ) after the drive letter. OK, more complicated now: you want to map to different shares for different users. So just use the environment variable %USERNAME%: NET USE H: \\computername\applications /user:workgroup\%USERNAME% 123456 NET USE J: \\computername\%USERNAME% /user:workgroup\%USERNAME% 123456 - The above syntax is only valid if you have shares named 'applications', 'user1', etc. on the server. If what you have on 'computername' is just one share 'sharename' and folders in it, the syntax you used ('\\computername\sharename\applications') may not work. AFAIK, NET USE just map a drive letter to a shared resource, not to content in it. In that case you may want to map one drive letter to the share and then use the 'SUBST' command to map other drive letters to specific folders: NET USE Z: \\computername\sharename /user:%USERNAME% 123456 /persistent:yes SUBST H: Z:\applications ::remove any previous mapping to the J: drive letter SUBST J: /d SUBST J: Z:\%USERNAME% -Also the /user:domain\username syntax is valid for a domain but nothing in the help about a workgroup. If you have no domain, just use /user:username (I'm using it that way) -As for the passwords, which I suppose are different from 123456, I don't know of a simple solution. But keep in mind that it is a password (of an account) on the server. You may just want to have a special account on the server having only access to sharename, and use it instead of the individual users. I'm not a specialist of this and use only XP home, so no room for customizing too much here. Now if you want to succeed quickly, I would advice to experiment with your Mapdrive.cmd before using it in your CD. Try the different things, see how they work and adapt it to your need. Finally, tell us about so other users can benefit from it.

None of these, but right after the other line they're talkin' about. I'f you don't want to search for it, I've just posted an addon to fix it.