Djé

@minusbfold WTF I'm writing a full tutorial for you to install that very app that very same way, but you prefer to start yet another thread just like if you did not read the answer to your first one??? I mean, I don't mind you not acknowledging, but then if everything is good why do you start another thread? On the other hand, if you think my post doesn't answer you question or is badly shaped, why can't you just tell it to me so I can improve it for other readers? This is very true if you find it too verbose, or unreadable, or whatever... I won't bite you, you know. 1- To complete gunsmokingman, if you install from hard drive use instead: SET PP=C:\Install\, or better SET PP=%systemdrive%\Install\ 2- This ' /silent' switch does not work for a silent install here. The one I gave you does.

For beginners, I wouldn't recommand mixing highly sofisticated automatic tools such as nLite with using basic 'manual' ones such as setupmgr.exe & cd_image. Either use nLite from A to Z. It works very fine but it is not the best to understand what is going on. Or DIY. You then will have to learn and do one step after the other, but it is the most interesting!

Solved there ! Sorry for you searching on this forum ... it's on another one !

Ok, I'm not sure what you guys exactly want so I'll try it another way. Following is the full comprehensively detailed procedure to make it work with a simple example. Try to follow it all along (even if some parts may be too basic for you) and things may get clearer. First, you need to have the program installers on your disk (harddrive or CD, or anywhere windows can look at) when RunOnceEx is processed. Now let's forget RunOnceEx for a moment and concentrate on commands to run programs: For example if you want to install Adobe Reader: 1- If you don't have it, download Acrobat Reader installer to your hard disk. It is a file named 'AdbeRdr707_en_US.exe' that should have been saved to your desktop (or another location depending on your browser settings and/or choice when downloading it. Anyway you NEED it and you need to know where it is. 2- In your 'c:' drive make a new directory and call it 'install_test' Move 'AdbeRdr707_en_US.exe' inside this directory from the above location. Now, the full PATH to the Adobe installer is 3a- So if you type (or better: paste) this full path in the Run box (Start Menu / Run) this will start the Adobe installer. You can try this and then abort the install (click cancel). 3b- Now open Notepad and paste the above full path in a new file. Save that file with a .cmd extension (beware to set file type to 'all files (*.*)'), for exemple test.cmd. Save it to any location, let's say your desktop. Now, double-click that test.cmd file. Since it is a command file, it is executed (line by line). Since its first line (our full path) is also a valid command, it is executed and Adobe Installer starts again. You can also abort this install (we are only trying). 4- In order to have your program installed unattendedly you may need to modify the command with some switches, something I won't explain here. - Suffice to know that switches are specific to each program. So the one for Adobe may not work for another program. - For this version of Adobe Reader it should be ' /S /v/qn' so our installer command would now be: C:\install_test\AdbeRdr707_en_US.exe /S /v/qn If you input that full line in the run box, it will install Adobe without you doing anything. If you put that line in the test.cmd instead of the previous one, it also install Adobe unattendedly. 5- Now let's try the RunOnceEx thing: * Open another Notepad and first, paste this in it: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Test Programs Installation" /F- The first line put the location of the RunOnceEx registry key into the %KEY% variable, so we don't have to type (or just read) that whole long thing again at each line. - The second line sets the title of the RunOnceEx list window (the one showing up just after login, saying it is installing your programs). -> It writes (REG ADD) the data (/D) 'Test Programs Installation' to the value (/V) TITLE of the key %KEY%. The ' /F' switch at the end forces the addition/overwriting of the value in the key. * Now, for installing our program, below the above lines, paste this: REG ADD %KEY%\001 /VE /D "Test with Adobe Reader" /F REG ADD %KEY%\001 /V 1 /D "C:\install_test\AdbeRdr707_en_US.exe /S /v/qn" /F- The first line adds a subkey named '001' to %KEY% and set its default value (/VE) data (/D) to the name we want to give to our program. This name will appear as an item in the RunOnceEx list window, and will be dispayed in bold when that specific item will be run. - The second line adds another value (/V) named '1' in the same subkey %KEY%\001 and having for data (/D) the command to be run for this item. Here it is our Adobe installer command from above. - It is important to grasp that here, the installer command is NOT YET a command stricto-sensu. - Rather, in this context, it is just text data added to the registry by the REG ADD command. -> As such it needs to be surrounded by the quotes and to follow the /D (data) switch of REG ADD.- If more than one command are needed for the SAME program, we can add more command values in the same subkey with increasing value name (2, 3, etc.): REG ADD %KEY%\001 /V 2 /D "C:\another\command\for\Adobe" /F. - Other programs to be installed will go into other subkeys: %KEY%\002, %KEY%\003, etc. creating new items in the RunOnceEx list window. * Save the whole thing as myRunOnceExTest.cmd in any location, let's say your desktop. And again double-click it. Now those commands don't tell the computer to run the installer but to write the installer command in RunOnceEx, so after the file is executed (black window) the installer does NOT start. Now log off and back on. You then see your installer starting automatically. Congratulations, this is your first successfull RunOnceEx. Cancel again to stop the install and proceed to your desktop. 6- Ok, now you may say: "all that is very fine, but I am formating my c: drive at the beginning of windows installation so after that, I won't have any 'C:\install_test\' directory anymore." Well, that is where the $OEM$ folder comes in: - It is a special folder that you create on you XP installation CD next to the I386 folder. (only the name is 'special' but don't forget to modify winnt.sif with OemPreinstall according to the guide for this to work). - In it you should create another special folder named $1. All what is in $1 will be copied to your system drive (most likely C:) at the end of the windows text mode installation (blue screen installation). This copying takes place before RunOnceEx, so everything will be in C:\ by the time the latter is processed. - So if you create an install_test folder inside $1, you then will have a install_test folder in C:\. - And if you place AdbeRdr707_en_US.exe in $OEM$\$1\install_test\ during your preparation, it will be copied to C:\install_test\. *-> That way, our command line : C:\install_test\AdbeRdr707_en_US.exe /S /v/qn will still be a valid one at the time it will be executed (RunOnceEx). * As a summary, during preparation, you should have Adobe Installer there: where XPCD is the location where you are preparing your unattended install (it contains your I386 folder).After burning your CD, it will be in where D: is your CD-ROM drive.During installation it will be copied to * myRunOnceExTest.cmd should be also in $OEM$, together with cmdlines.txt: with this last one having in it:[COMMANDS] "myRunOnceExTest.cmd" Those two files will go on your CD there: During install, they won't (and don't need to) be copied to C:\.Instead they will be executed directly from the CD: - if exists, cmdlines.txt is automatically parsed by windows setup at T12 - it calls myRunOnceExTest.cmd as we want, - myRunOnceExTest.cmd writes our commands to RunOnceEx in the registry. * Later, at first logon, RunOnceEx is parsed and our command being a valid one (Adobe installer file does exists in C:\install_test\, thanks to $OEM$\$1), it is executed and Adobe is installed: C:\install_test\AdbeRdr707_en_US.exe /S /v/qn - Et voilà! Now, sorry if this does not answer your questions. Please then be more specific. The above procedure might be a good ground to base your questions on. Anyway, i hope it can help someone.

Hi Laura and thanks for the comments. I think you may have misunderstood how the the script works so here are further explanations about them: Theme.cmd works by writing a MagicUPMask.cmd file to your startup folder (the path to this file is stored in the %UPM_CMD% variable). 1a. There is only ONE exit: Every thing on a line after '>>%UPM_CMD% ECHO ' is actually only TEXT to be written to the %UPM_CMD% file, not commands executed inside THIS script. So the first one in your quote is not an exit for this script, but only some text.1b. Why the last one wouldn't be executed anyway? 2. When the text DEL /Q /F %%0 is written to the %UPM_CMD% file (using the command '>>%UPM_CMD% ECHO '), %%0 is transformed to %0. So the %UPM_CMD% script can indeed delete itself after doing its job. Theme.cmd actually doesn't need to delete itself (or do you need all your installers to delete themselves?) The %doubling here has the same reason as all the %doublings, like in a for loop: prevent its expansion as a normal variable. Now, if this Theme.cmd doesn't work for you, there may still be a problem with the code page thing (if my memory is right, you use a non 'western european' OS). I have a workaround (not implemented in Theme.cmd yet) so let me know if it is the case. In order to test if Theme.cmd is actually working or not, without making any change to your system: - empty the theme & wallpaper file names in its config section, and set the repairs to 1. - Then run it. - If you now have a 'MagicUPMask.cmd' file in your Startup folder (Start Menu/Programs/Startup), Theme.cmd DOES work. - Just delete this MagicUPMask.cmd (actually this is the '%UPM_CMD%' file) if you don't want it to do the repairs at the next startup. - But before, look at it: you should see the DEL /Q /F %0 and EXIT lines at the end. Indeed, I'd like to know if your command prompt is different than mine: does yours can cope with unicode?

Ok, now let's proceed to next step: creating your own simple RunOnceEx.cmd file. Go back to TFM and read it again. Have a break an re-read it, slower. Once more. There is a simple exemple on it. Use it: copy it to a notepad and save it with a RunOnceEx.cmd name (type: all files). Now remove the lines corresponding to programs you don't want. An create new lines for the ones you want to install, following the patterns and explanations of the guide. Give it a try, even if you don't grab it in full. Then post your file here for comment and point out what you don't understand. Maybe what is missing in the guide is a general explanation of how runonceex works. So let me try: * RunOnceEx is a location in windows registry (internal settings) where you can write some commands. The commands at this location will be executed only ONE time (runONCEex) just after the next user logs in, and then be deleted. We use that feature by putting in RunOnceEx some software installation command.* The purpose of the RunOnceEx.CMD file is not to run these commands, it is to PLACE the commands in that RunOnceEx location. * So basically there are 2 times: 1- RunOnceEx.cmd is executed, and as a result, writes some installation commands in RunOnceEx (registry). 2- Windows process the commands in RunOnceEx (registry), and as a result, installation are performed.* The 1st time can be done at any moment before the 2nd one We usually choose T-12, meaning that we call RunOnceEx.cmd for execution from cmdlines.txt. * What is important to grasp is that the stuff inside RunOnceEx.cmd is not exactly the installation commands but commands (REG ADD) putting the installation commands into the RunOnceEx location in the registry. * For each program we want to install we put at least 2 informations in the registry (hence the 2-more lines for each prog in RunOnceEx.cmd): The installation command itself (2nd line and following)) as well as a name (1st line) that will be highlighted in the RunOnceEx list window during the execution of the command. Good luck

Yes, definitely, my WEP key is a cryptic Hex string 26 char long!

I'm back from field investigation! Here are the result: 1- windows (ANSI) code page (my 1252 above) is stored there: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage] "ACP"="1252" If ever you want to experiment and change it, do NOT do it directly in the registry. Use instead: Control Panel / Regional & Language Settings / Advanced Tab /Language for Non Unicode Programs dropdown. Once clicking OK, answer yes to bul***** dialog and yes to reboot. Back to 1252 the same way.Anyway to complete Delprat's patch, we should now write: FOR /F "tokens=2 delims=:" %%c IN ('CHCP') DO SET CodeP=%%c FOR /F "skip=4 tokens=3 delims= " %%? IN ('REG QUERY "HKLM\SYSTEM\CurrentControlSet\Control\Nls\CodePage" /V "ACP"') DO (CHCP %%?) FOR /F "skip=4 tokens=3 delims= " %%? IN (' REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" /V "Common Startup" ') DO (CHCP%CodeP%&& SET Startup=%%?) 2- To doublecheck that querying the registry was working for every language, I inserted a value with japanese data in the registry and changed my code pages to japanese as shown above. Note that japanese code page, 932, is the same for ANSI (windows) and OEM (cmd.exe) so no need for the CHCP trick described above. I then reg queried my value, which displayed fine. Then I did the FOR trick to keep only the data in a variable. And there, BADABOUM ! The value was truncated:日本語が分か instead of the full 日本語が分かるんですか。 So I tried different technics to grab the value correctly, all but one to no avail. Same was true about French accent (if not using the CHCP trick above). Below is the output (french version, japanese attached) from a test batch (see attachement) implementing the different techniques one after the other: -> As you can see, as soon as manipulated in any way, REG QUERY result got corrupted. I don't know if REG and CMD are different in Japan. -> I don't know exactly why, but I could not read the REG EXPORT file directly in the FOR loop. Probably because it is in unicode. -> I had to TYPE it and do the FOR on that. And only then, the result was correct. It means that who ever absolutely needs to use and internationalized registry value in a batch should use the following syntax: SETLOCAL ENABLEDELAYEDEXPANSION REG EXPORT "%KEY%" "%FILE%" >nul FOR /F "skip=2 tokens=1* delims==" %%I IN ('TYPE "%FILE%"') DO ( SET TEST=%%I ::We don't want to pick values in subkeys IF "!TEST:~0,1!"=="[" (IF "!TEST:%KEY%=!" NEQ "[]" GOTO ENDFOR) IF "!TEST:~1,-1!"=="%VALUE%" (SET DATA=%%J) ) :ENDFOR SET DATA=!DATA:~1,-1!& SET DATA=!DATA:\\=\! This seems to be robust because: -REG EXPORT calls regedit32 to do the job, which is done in Unicode. -TYPE can read Unicode (if it has the good code page) much better than ANSI, as it seems. 3- Ok, now it would be interesting to know if that technique is really working for our actual purpose and could be used specifically for placing last-minute tweaks in the startup folder, whatever language is set on the computer. The last attached file is a test batch that, if successful, would place another batch in the startup folder (Start menu / Programs / Startup). If you are interested to know if such a trick can work in your language, download & run it, and then look in your startup folder if you see it. Please, report about it here so others can benefit from your experience. result_jp_unicode.txt full_test.cmd startup_test.cmd

See, that's the problem with enthusiasm, it makes you stay awake far too long and make some last minute cosmetic changes which bugs what was running smooth before. Hopefully this one is not that much of an issue. I really though I had double checked specifically all the instances of this 'yes', but indeed, it should be a 1 now. Thanks Delprat, and I also updated the CHCP thing to take care of the non-850 cmd code pages (shouldn't be an issue in most cases), as you adviced. I will investigate further for the 1252 one (shouldn't be an issue either). Download updated in the first post.

Did you run a command like: Z:\I386\WINNT.EXE /unattend:Z:\I386\winnt.sif /syspart:C: /tempdrive:C:where Z: is your mapped drive and C: the local drive to which you're installing. Look at the doc but I think some of the arguments are mandatory for a network install...

If you don't have any serious clue about what can be the cause, I would advice to start diagnose from the beginning: make a much simpler installation and see if it works again. The algorithm is simple: 1- TEST a- If then it doesn't work, simplify it even more, get closer to an original XP install. b- If then it works, start adding back a few things. 2- Start over the test. That way you may solve your problem. By simplification, i mean removing apps, tweaks, custom stuff, drivers, addons, winn.sif stuff, etc. You may also go down to a bare xp install, and start over, little step by little step from there: first slipstream update pack or hotfixes. Try to install Attended. Then winnt.sif for unattended install. keep it simple first. Then drivers. One by one if necessary. Then tweaks, applications, customizations. Little by little. Good luck my friend.

Thank you ! Indeed, you may be right. But that was my first AutoIt Script, and still being a little boy, I was quite proud of it and wanted it to be perfect! Now I can only think of one more feature to add to it... Anyway, I learned a lot making it, including the last improvment. Thanks again!

No. But start the install with winnt.exe and tell us if any issue comes up

Thanks to BoarBabe who stung my curiosity, here is an even simpler version of autoWEP: It does not even requires you to set the 'wizard window title': it finds it on its own, like a big boy ! It should now be completely Language Independant, at least for western languages. Just feed it with your SSID and WEP/WPA (in a file or on the command line), et voilà! This version (AutoWEP0.3) doesn't requires anything else but a recent beta version of AutoIt to be compiled/run with. And more than ever, it works with Windows XP sp2 and above, but NO NEED for a wireless adapter! Addendum to The F*cking Manual: For specifying WPA encription within the .ini file, you must have a 'UseWPA = yes' or 'UseWPA = WPA' directive in the [Wlan] section of the .ini file (This was not well documented in TFM at the top of the .ini file, shame on me): autowep.ini [AutoWEP] version = 0.0.3b0 [Wlan] WlanSSID = OhFcukIForgotToInsertMyOwnValues Wlankey = WHATALAMERIAMICANTFIGURETHISOUT UseWPA = yes If you use a WEP key, just forget about this directive. AutoWEP0.3.zip

Did you attach something or not? I can't find any attachment in this thread although it is marked as having one... Anyway, you've just sting my curiosity by saying you could find the wireless dialog title automatically: that's just the only parameter (except for SSID & WEP/WPA, of course) that I couldn't automate in AutoWEP. So I spend a couple of hours on it and eventually found the solution I've posted a new and much simpler (not that it was very complicated) version of AutoWEP in its thread. Maybe you could share your little thingy here so users will have a choice?

why do you need a startup.cmd AND a cleanup.cmd? Can't you just have the cleanup.cmd in the startup folder? Deleting itself upon completion: DEL /Q /F %0

Answers: 1 You don't need to reboot. It works straight on. Reboot may only be required by other install. In that case only, try to give this thing enough time before reboot. Anyway, if it has not finished, it won't be deleted and start over at the next reboot and do the job. It is very stubborn indeed! I am just discovering that as I am writing I wrote a warning inside the file about giving it enough time, but in fact it is not even required ! This is true for the startup part. The RunOnceEx part has to complete. But there is no obvious reason why it should not. 2 svcpack ... addon ... this is all black magic to me. I'm trying to get rid of them ! No more deep integration ! Seriously, I don't know exactly when svcpack in processed, but if it is after start menu is built and HKLM is accessible, theme & tweaks should work fine. Wallpaper also if HKCU maps to HKU/.DEFAULT but that is dirty!

Thank you so much hazard_abio. It is absolutely gorgeous. My VBA window was barely a stool, it is now a full armchair, thanks to you. Merci beaucoup, Shukran, Teşekkürler Ederim, XieXie !

As the title says it all, this is a method to: - Load your Custom Theme together with - tweaks related to the theme, - all from a small single batch - run from anypoint in the Install. Prefered and only well tested point being RunOnceEx. * Theme (and wallpaper) choice: - this provide an alternative to the well known winnt.sif->[shell] method. - So far, I only found 2 old posts by Gosh (question & answer, link) related to this way of doing but more than 2 years old. Nothing new under the sun! - I did not find necessary one of the reg key he uses.But my own theme is a very small thing, so it may be used in other situations. Corresponding key is commented out in the batch.- IMHO, this method is more flexible than the deeply integrated [shell] one. It even can be used when creating new users, outside any unattended windows installation. -The new user can have its very own theme set automatically. -No need to share yours with your litle sister (or colleague) anymore! * Tweaks: - There again, I did not invent much. It's just annoying things that are still arround because their solutions is not standard and/or have pop-up recently: 1- The ungraceful white background behind menu items after applying a custom theme. BoardBabe recently found a solution about it.The cure can only be applied after the Theme manager has finished (after first RunOnceEx)2- SmallIcons reg key (windows Explorer toolbars): doesn't work when applied to HKCU before desktop is loaded (T12, RunOnceEx, etc.). Thanks to minalgar, the workaround was to use HKLM, meaning One-Size-Fits-All. This tweak is applied later to HKCU, allowing every user to load its own setting automatically, just like for the theme.3- Custom Theme is applied through an HKLM key before the Theme manager builds the actual theme keys from it. HKLM means -again- all-users-the-same. The 3rd tweak cleans that mess by removing the HKLM key afterward.- These 3 tweaks work by importing the reg keys AFTER the Theme Manager and desktop (?) are loaded. - A 2nd cmd file is written on-the-fly in the startup program group.- Progs in that group will be processed after RunOnceEx. - In fact, they will be processed even after Theme Manager. bingo ! - The 2nd batch file imports the keys and then deletes itself. - Et Voilà!-<edit cause=found>Credit for that startup thing goes goes to AndeK & blinkdt.-And of course, thanks to Zilexa puting me on the right track, this whole thing is language independant. * RunOnceEx is the prefered time, -especially if you set also your wallpaper this way: - its key is in HKCU so if it is applied before your first logon: --> it will go to the HKU/.DEFAULT hive (No User Hive), --> then to the Default User Hive --> and eventually to your profile. -The first one is just plain registry pollution, the second imposes your setting to other users while only the last one is necessary if you care about that.-The good time slot is thus quite short: - after user first login, - but before Theme Manager loads. -I'm affraid that this leaves only one possibility... - <POV>If, like me you love that green hill, with the mountains in the far, and those litle clo<Shut up!>, then you can call this batch from any point during install. But IMHO, puting it in RunOnceEx is more 'pro' since that makes a sharper discrimination between OS setup (in the first place), and customization (later). Now, that's just a POV. </POV> * USAGE: - The 5 actions performed by the batch are all optional. The batch itself is optional (but why are you still reading then?). --> Edit the 5 simple settings in it config section.- Attached is a zip containing: - the batch file together with - a folder to store you theme stuff (mine is provided as an example). -Its content will be copied to %SystemRoot%\Resources\Themes). -If you load a theme, keep it side by side with the batch and put them with your other apps to install. -Otherwise you don't need the folder. -Wallpaper, if used, goes parallel to the batch (not in the folder). Ijou desu suggestion, criticism and feedback wecome. ThemeRunOnceEx.zip

Bad news, ZileXa: That batch thing doesn't work (as for now) for ALL LANGUAGES, as you specified. Indeed, some cryptic local dialects such as french have accented letters in those path and cmd is horrible at dealing with them: - if you type the command directly, it will display the result correctly with nice accents - but if you want to use the output of the command, or a text file, then it messes up everything between ANSI & OEM. And my Menu Démarrer (Start Menu) becomes an ugly Menu DÚmarrer. Myself, I would become a DjÚ Can you imagine that? I don't know how to overcome that yet. Anyone has a suggestion? appart from learning another language? <Edit> Good news, ZileXa: I was about to start learning vbs (especially after I saw Yzöwl's new example above) when I heared a voice in my head "Google ... goooogle ... google...". So here is what DigitalMother provided for us in her goodness: CHCP 1252 FOR /F "skip=4 tokens=3 delims= " %%? IN (' REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" /V "Common Startup" ') DO ( CHCP 850 SET Startup=%%? )Where CHCP is the command for changing code page, 850 being the code page used by CMD and 1252 (my) windows' one, I guess. Please also note the change in the FOR syntax (I'm copying on the master) to cope for reg values containing space in their names: - tokens=3 only - delims= {TAB} ONLY - %%I and %%J replaced by %%? </Edit>

The advantage of using BartPE is those windows tools in it. Plus, when installing from a network share, you are AUTOMATICALLY making a local source. And I don't know about write access to a ntfs partition from dos to do this, if ever you don't have any fat partition arround. But maybe winnt.exe can deal with that. Don't know. For the $OEM$ thing: this is an additionnal folder that may be on your CD (next to I386) with some extra stuff to install (applications, drivers, etc.). If you don't have it then don't worry about it, you don't need it, otherwise nLite would have made it. Now, your turn: experiment and tell us about it. @tridgely: thanks for the OEMFilesPath trick. I'll make good use of it.

I'm getting crazy. This has to stop continuing to not work. Or to start quiting being disabled. Either way, anyone knows if it is possible, and how to enable (repair?) normal standard everday simple vanilla scrolling using the mouse wheel in the code window of Visual Basic for Application (M$Office macros language), 2003 flavor, actually used in excel. How do I go from the top to the bottom of a module without having to click on the scroll bar? I'd be interested in a solution that works also from the bottom to the top, just by a subtle change in the stroking of the little protrusion located between the two buttons of mice. And, to not drift too much off topic, it should idealy be something I can implement unattended. But i'm not asking for the impossible, just give what you have, I'll make do. Now, is it only me? That and the help files written by some smoking freaks, please do not recall me how much that piece of crapware costs.

Crock, the best way to import those settings is not the registry but a theme. Just set-up your computer with all those settings working, and then goto [i]Display[/i] Properties, [i]Theme[/i] Tab, [i]save as...[/i] Button. And reimport this theme at install. The reason registry does not work is that when you import the keys, it goes to your profile BEFORE theme manager is loaded. When it loads, it create your theme (custom or default) and overwrite all your stuff with its own keys it is creating from the theme definition (that you saved, or the default one). I was only interested in tweaking the CaptionHeight in [HKCU\Control Panel\Desktop\WindowMetrics], but I had to save a whole theme for making it work. I understood why later by reading gosh's stuff on the question. I am double-checking a few things and probably tomorrow, I'll post some 'updated' stuff about loading theme.

Here you are! I just grabbed jdoe on another thread and he posted back a zip full of documentation about advanced inf syntax. Invaluable. With a nice trick to register/unregisterr dlls. Incredible. With many new items available. Marvelous. Thanks god. OK. Now, that said, I don't have so much time to write again the inf, and the batch is working fine. B)

Waou jdoe, Thank you gozaimasu! Muchos Merci ! It looks like there is a lot to learn in this zip. Very valuable for learning advanced inf syntax. This should be back on the web. Half of the little I knew about inf, I already took it from you (I copied your installer for CABTool to make one for CBin ), but now you are taking a serious advance over gosh! cheers!