Djé

Ok for that point. Now, if you don't have any other solution you may have to check if AHK can be run at all from cmdline.txt. Do you get the AHK window poping up by doing this?: ".\AHK\AHK.exe"

Sorry to ask that but since your text file WIHU.txt is in the same directory as the script, wouldn't you write simply: ".\AHK\AHK.exe WIHU.txt"??? I don't know AHK, but usually progs are opening files relatively to their location. Also, the tutorial uses / instead of \, but I don't know if it's a typo or a cmdlines.txt's feature!

Hi Benners, I liked your idea so I've been researching for it the whole day yesterday but to no avail. It looks like it's a feature to avoid any security breach. Now, there is still the AutoIt solution. Mozilla uses is own type of controls with no text visible from outside and that you cannot access directly using 'controlclick' but this kind of solution is working: ;title of the extension installation window (something like "program installation") Const $xpiInstallWindowTitle="Installation de logiciel" BlockInput(1) ;Improve this from the user's choice _xpiProfileInstall(".\extensions\fireftp-0.90.1.1-fx.xpi") _xpiProfileInstall(".\extensions\adblock_plus-0.6.1.2-fx+fl+mz+ns.xpi") _xpiProfileInstall(".\extensions\adblock_filterset.g_updater-0.3.0.2-fx+fl+mz+ns.xpi") _xpiProfileInstall(".\extensions\colorful_tabs-1.1-fx+mz.xpi") _xpiProfileInstall(".\extensions\bookmark_duplicate_detector-0.2.2-fx.xpi") ;... ProcessClose("firefox.exe");Shut the door when leaving... BlockInput(0) ;...and hand back the keys ;Da workin' man func _xpiProfileInstall($extensionfile) Run('"' & @ProgramFilesDir & '\Mozilla Firefox\firefox.exe" "' & $extensionfile & '"') WinWait($xpiInstallWindowTitle,"", 10) If WinExists($xpiInstallWindowTitle) Then sleep(5000) Send("{ENTER}") sleep(3000) EndIf EndFunc I tested it at run time and it went smoothly. Test is still need at install time. I hope this can help, and I also would be interested in your installer, as well as the one for thunderbird, if you don't mind sharing them here.

I don't think so.Try to add another 'DelFiles' section for your inf: [DefaultInstall] DelFiles=cleanup,cleandown [cleandown] myself.inf [DestinationDirs] cleanup=16409 cleandown=YourInfFolder May I ask why do you want to use .inf instead of batch for this?

Ousted at the .inf door, let's come back through the .cmd window! Same features: - copy the dlls in a folder inside 'Program Files' - register the dlls - install custom settings for the toggle extensions - add ability to register/unregister any dll (right-click) - add a full uninstaller for the above features in the add/delete progs control panel. - Easy customization (language, install location, unattended or not, installed features, etc.) @SpiritPyre: this is meant to replace your Install.cmd, but only if you think it is worth replacing . Usage: -Edit it to your needs -put it (with the dlls you want to use) in a folder on your cd (or anywhere) and simply run it. -no need for any other .reg file. this time, I've been a little more serious testing it on my computers FullInstall.cmd

Oups Sorry, I though MIMO was just a brand name. I'm googling about it right now... and getting your point.

I only tried from RunOnceEx. But I would bet it works from cmdlines.txt: 'minutes' are going very fast after this point (T12) and Start Menu shortcuts (including the one to the Wireless Wizard) are created much before. I'd love to read the results if you/someone experiment with this. [selfquoting]look in the .inf and get the files mentionned in the [sourceDisksFiles] section ... plus the .inf and any .cat hanging arround. [/selfquoting]Sorry if it was buried in a too long post, moreover inside a double IF statement that you may have evaluated to false . Would you test this? That would be interesting to know. I inderstand that both NICS are on the same computer. Why that if I may? Please move the thread to the drivers section if you feel you should do so.

I haven't done it yet so I don't know if it will work entirely, but my first try will be brute force: xcopy from the backup to the profile. I may also try the poshier Robocopy. But I must gain education about usage first. I completely agree with Lazy8 about the tradeoff. It's just a sucking manichean tradeoff! And I must also agree about the Files and Settings Wizard.

I don't want to abuse my power so I would just suggest: - /? on any command for comprehensive explanations about its usage - Petrol Hahn for your hair! Btw, when you'll have your script finished and working, why not contributing it here so everybody can benefit from it? Cheers

xcopy "%ALLUSERSPROFILE%\Menu D‚marrer\Programmes\7-Zip" "%ALLUSERSPROFILE%\Menu D‚marrer\Programmes\Compression" /H /I /Y works very fine here, although not tested during setup nor RunOnceEx. Would it help you keep your hair on?

What exactly doesn't work? copying? deleting? both? Why not posting your code (both versions) so we can criticize it and laugh look what's wrong with it? Sorry for the bad joke .

If your answer is yes, AND if you can't find this simple setting elsewhere, here is what I did for retaining full control on my D-Link dwl-g650+ wifi pcmcia card: -Get the latest drivers set. -Only extract from it the driver files (look in the .inf and get the files mentionned in the [sourceDisksFiles] section ... plus the .inf and any .cat hanging arround). -Only install that driver (right-click/Install on the .inf, or New Hardware Wizard) at the exclusion of the full proprietary management utility. Unattendedly, you would put those files in a folder under $OEM$\$1 refered to by OemPnPDriversPath in the [unattended] section of winnt.sif, or Bashrâtify it. Doing so, only the necessary driver files for the card will be installed. The accompanying software (usually extremely useless) won't be installed and full control of the card will remain to windows. You can then use windows, even unattendedly , to configure your WLan. And LATER, optionnally install the full driver set if there is a functionnality you need in it. Hopefully the settings may be transmited from windows to the proprietary management utility. But this last part I'm not doing, so I wouldn't bet my D-Link card on it, even my Intel/pro 2100 3B .

Yes. And that sucks. Actually, I don't see any better solution than the one in the 1st post if you just want to have your new installation re-using SOME docs&settings from the previous one without messing the usernames.

If you need only simple script support (western european basically) you may not need the WHOLE folder. At least, during my testings i used to remove it completely ... before updatepacks create it back to put some stuff in it, which I did not remove. Here's the stuff (1.51Mb !!!): cplexe.ex_ imekr61.im_ imjp81.im_ imjp81k.dl_ imjpcd.di_ imjpcic.dl_ imjpcus.dl_ imjpdct.dl_ imjpdsvr.ex_ imjpinst.ex_ imjpmig.ex_ imjprw.ex_ imjputy.ex_ imjputyc.dl_ voicepad.dl_ voicesub.dl_ I'm pretty sure it's not necessary but I'll wait for you to test that hypothesis!

Yes, sorry, it looks like the other problem is different if the files are even not inside drivers.cab. But for yours, I was just thinking that it may be lsass.exe or another file it uses when login to the system account which is not copied correctly during the text setup (or which is already corrupted on your CD), and then causes problems later. We basically have the same opinion on the problem: Except that I think you may not be responsible for it...Also what about those setup log files you're talking about in your first post? What do they say?

Pourquoi tu n'intègres pas le pack avec nLite dans ce cas? Les packs de Vier marchaient avec nLite qd j'ai essayé (j'ai pas essayé la dernière version). Dans ce cas, pas besoin de nLite, fais tout à la mano:-Intègre avec RyanVM1.1 (n'oublie pas l'option avancée unicode->ansi) -Fais ton winnt.sif avec setupmgr.exe (dans les outils de déployement de \tools sur ton CD de XP, ou directement chez microsoft, regarde le tuto de msfn) en t'aidant de ref.chm et du tuto. -Met-y une référence vers tes drivers et ces derniers dans $OEM$ (regarde le tuto...) -Utilise cmdlines.txt pour importer tes regtweaks et installer tes progs. Again, lis le tuto. -Pour l'iso, cdimageGui (Tuto !) marche très bien, et pour burner, y'a plein de soluces, la plus simple étant ImgBurn. Où ? quand ? comment ?y'a tellement de possibilités pour que ça plante...

Well, I gave a try to this method (who knows?) and guess what? It failed on MY computers. So, well, I made an AutoIt script to Install version 5.0. There it is, in the AutoIT Script Collection. You may need to follow the links to Microsoft speech engine provided in the first post of this thread.

[size=4][color="#3333FF"]Babylon Pro v5.0[/color][/size] Script version: BabylonV5.0.au3 v0.0.1 [url="http://www.babylon.com"]Babylon Pro[/url] is an online/offline dictionnary running in the system tray and that you can conveniently call using a (selectable) Hotkey or mouse-key combination. This script allows to install silently: [indent]+ the main program: [indent]-including or not glossaries -with a licence code or a trial licence -in a choosen language -from any path, including UNC[/indent]+Some additional offline glossaries (to download first).[/indent] Usage: -Go down the scripts and edit the editable sections (3 first ones) to suit your needs. Comprehensive instructions provided. -Have the script run directly if autoIt is already installed OR compile it and have it run standalone from any point in your install. Attached zip contains the .au3 script plus an icon ResHacked from a Babylon Package to (optionally) compile the script with.

I don't know if your values are correct or not (I'd say yes !) but anyway, they come too late to change anything to how setup parses winnt.sif, because they are inside it. I wouldn't be surprised if, as you said, setup only knows how to parse ANSI winnt.sif. You said previously that unicode versions of it broke the setup process (did you try UTF-8?). Is there any info about that in ref.chm? A way to work this issue arround would be to set your name directly in the registry at a later point in the installation: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] RegisteredOwner="ąčęėįšųūž"

You should have something like OEMpreinstall=yesinyour winnt.sif Check exact syntax in ref.chm

Salut, J'utilise l'updatepack de CréateurXP (Vier) en version actuelle 1.1.4a intégré avec RyanVM Integrator 1.1 et tout marche nickel. Je n'utilise aucun addons: -ça fout souvent la merde -c'est pas forcement bien traduit -je preferre choisir ce que j'installe au premier boot (RunOnceEx, WPI, etc) -MAIS ça prend plus de place sur un CD. M'en fout, j'ai 1 CD pour windows (image disque restaurée avec BartPE) et 1 CD (ou partition ou usb drive) pour les applications après. Comme ça je peux utiliser l'un sans l'autre. Les seuls trucs que j'intègre directos (même pas un addon, je les cab et les mets dans I386) c'est notepad2 (renommé en notepad) et calcplus (renommé en calc). Pour les cpl supplémentaires, une solution simple est juste de les mettre dans $$/System32. @Ulysse Je suis quand même bien interessé par ton futur Microsoft Web Update Pack FR que je rebidouillerai pour le passer en fin d'installation avec mes autres applis! et je vais regarder les autres.

according to this thread the registry key connected to that part of the start menu is: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StartPage] You may want to dig in the "Favorites" value, but with no guarranty.

Sorry, i don't have an answer right now, but some other people are experiencing other troubles during install which may be related. Would you mind posting in that thread with a link to here so we can keep a record of all those problems and maybe find the cause?

Hey, nice reaction indeed . Obviously, you did not search very much before your first post, but that was just a normal beginner's reaction. You learned very quickly how to use the forum. Congrat! Yes, WPI can be a good solution for your need. There are a few other app arround with the same goal, but this one is a serious candidate. I like this forum too because it has a high signal/noise ratio ... except that I am currently increasing the noise !

Those files (yours, not mines) are inside the 'drivers.cab' archive on your CD.