Djé

write protected? Sure of that? How come? why that? I suspect something else. Or, if really write protected, even something else (and bad) protecting it in your back (how coward it is). Here, none of my quicklaunch shortcuts are protected. I would not tolerate it. Let's start by the beginning: can you confirm that the above command does work? I don't know Shortcut.exe but what does it says when you run that line without Start /B ? Are the paths corrects (you have all your programs in %SYSTEMDRIVE%\Programme ?) Why are they translated? Anwendungsdaten? Programme? My French XP has 'Application Data' and 'Program Files' in english, why not your?

Yes, after posting, I just remembered one of your posts showing the >nul for stdout, although it was for each individual command. What is that 2>&1 doing for stderr ?? And maybe hougtimo doesn't want that level of nudity (that is really bare bone) and would appreciate a few veils of echo to tell what's going on? but that's just a conjecture. Hey, jdoe, you seems to know a lot about that advanced inf syntax. Do you have some link to good documentation about it? Last time I could not manage to register/unregister dlls using that advpack.dll,LaunchINFSection stuff.

I think that your \Control Panel\Desktop keys (at least, i did not parse your file thoroughly) will be overwritten by the Theme manager upon your first logon. Your best bet may be to - tune your settings, - export a Theme with all that, - and load it when installing. Make a try and then tell us about the remaining stuff.

That's very true!Specially when displayed as a dense blue text like in the code/quote boxes of this forum. That's a pitty there is no color coding for the main languages used here. Something like [code type=vbs] tags. Anyway, I loved (and understood!) your simple 2 lines example. I may try VBS one day... ...When I will have forgotten a bit how frustrating its sibling VBA is. Anyway, spazmire11 has the right answer to the original question, I guess.

Yep, that's the way to go. BartPE, Net use command and winnt32.exe command. Search for the right winnt32 command line on the forums. You will be making a local source that way. After reboot, the normal stuff will go on... without CD! No more CD burning, just Bart. Don't forget to put the $OEM$ inside I386.

There are 2 parts for RunOnceEx: 1- the .cmd file store actions in the registry when it's executed (T12 in your case) 2- The actions themselves are executed just after the next login (first login in your case) For the first part: I would first remove cmdow @ /HID and @echo off for having a clear view while debuging (it's like searching for something in a darkroom with sunglasses!). Then, replace exit by pause at the end of the file. And see if the installation stops for your script at T12. Also you can try to put "RunOnceEx.cmd" as the first line in cmdline.txt and see if that change something (be careful to remove exit at its end) Now if the 1st part is executed normally but the 2nd is not (you should have a list of progs installing before the desktop loads), and if the keys are in the registry at the correct location, I'd say something may be broken. also sometimes, the RunOnceEx takes some time to show up (specially if one of the progs is returning an error!) and some other times it has no time to show (small list on fast computer!) but progs are executed indeed. Winnt.sif shoud be in the I386 folder.

Have a look in dosnet.inf and txtsetup.sif in your I386 folder. Although the list is not exclusive and none of this is simple to deal with. You may also want to read thoroughly some posts on RyanVM's forum do understand what these files do... Anyway, good luck and thanks for all the fish.

Thanks, and here you are: Manufacturer: TOSHIBA Model: Satellite M30 544F5348 494241 Manufacturer: COMPAQ Model: PRESARIO 1721LA 470027-254 434F4D50 4151 Manufacturer: Packard Bell NEC Model: 00000000000000000000000 5061636B 61726420 42656C6C 204E4543 Reverse chronological order so the 3rd one is there for archeological purpose (not that the others are brand new...). Model is a EasyNote Sc 3703. Anyway manufacturer still exist! Also I don't have pre-activation on this one: it was shipped with WinMe!

Thank you very much, benners Give me a few days to look at that. I'll keep you informed and tell you about how i'll use/modify it. And maybe I'll have some questions...

Nice idea But i've got 3 of them (different manufs), I am lazier than you, I don't know vbscript enough AND the output is a msgbox from which i cannot copy/paste ! Can you improve this (clipboard is enough, I'll do the rest) please?

I think I understood you .What I was trying to say is that the values you are looking for (the path/name of the start menu and other folders in the local language is stored in the registry at the keys I gave you. Just run regedit and navigate to these keys and you will see what I'm talking about. You can follow Yzöwl and switch to vbs or inf syntax, where there are built-in constants for the names of these folders so it's easy to use. If you want to stick to batch syntax, here are a few tips: To have a %menustartprograms% variable AUTOMATICALLY containing the name of the start menu in the local language, you first need to have your batch look for that name in the registry and then AUTOMATICALLY attribute it to your variable. - The batch command to access the registry is REG. Type REG /? for more details. - For reading a value %VALUE% in the %KEY% key you would use: REG QUERY "%KEY%" /V %VALUE% - To create a variable and store data in it, you have to use the SET command. Type SET /? for more details. - For storing myvarvalue in the %MyVar% variable, you would use: SET MyVar=myvarvalue - To link the 2 previous commands so you can store the result of the query in your variable, you need the FOR command. Type FOR /? for more details. - Now your full command line to get your %menustartprograms% should be: FOR /F "skip=4 tokens=2*" %%I IN ('REG QUERY "%KEY%" /V %VALUE%') DO SET menustartprograms=%%J where %KEY% and %VALUE% are variables that you would have previously set to the registry key and value that you want to query (total to get your local-language-start-menu-name in a variable: 3 lines). You can also write directly the key and value of the REG QUERY command, instead of setting variables (total to get your local-language-start-menu-name in a variable: 1 line (quite complicated, I must admit). - If ever the value you are querying contains a variable (like %SystemRoot%) you'll have to replace DO SET by DO CALL SET to have it properly expanded. Ok, now I know all those commands look cryptic at first, but that's normal at the beginning and with the help of us here, of some good pages about batch scripting on the web and of your best friend /?, no doubt you will succeed.

Sorry for the delay. Yes, I'm interested in your script (does it copy back the profile as well?) I am also interested in the XPlode part. I've never used that one but now that you are talking about that plugin, it would be very interesting. Also I am currently working on an excel sheet (+ vb macros) to allow me to maintain only one list of programs while trying different method of install (RunOnceEx, kTool, WPI for now) and I'd love to have a working xplode example so I can add another method plugin. If you want to try that one, I'll post it as soon as it will work properly, and tell you about it.

You're right, the answer is really simple, as bledd gave it in the first answer: But you're wrong with the /f. Use /? on the REG command and you'll have the right meaning of that switch. Now gratz, if you have some problem with your runonceex maybe you should show us your script. Attach it if it is too long. And explain which program is not polite enough to line up.

You may build your own %menustartprograms% and more by having a look at: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders and the SM_ values at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

Now that everything is back to batch syntax, may I submit for testing a small modification to this method? Using it as specified in the 1st post, there may be a weak point in the way Drivers.cmd is looked for, namely the Arguments line in Winnt.sif: * All the lines of $WINNT$.INF are processed regardless of their relevance/risk.* %I$OEM$ works fine for installing from CDROM but for installing using a local source (from dos, network, etc.) we need to use %I\$OEM$ I would suggest the following 3 steps: 1- put Drivers.cmd in \$OEM$\$1 instead of \$OEM$ Doing so, it will be copied to %SystemDrive% at the end of the Textmode Setup2- Have a really simple Arguments line: Winnt.sifDetachedProgram = cmd.exe Arguments = "/Q /C START /MIN %SYSTEMDRIVE%\Drivers.cmd" 3- Modify Drivers.cmd to find the exact source folder at the beginning and to remove itself at the end: Drivers.cmd * The FOR can now use quotes so it can properly target the folder referenced by the dospath line, at the exclusion of any other potential folder referenced by the other lines of $WINNT$.INF. Although the risk of having another $OEM$ elsewhere is low, this may avoid unexpected things to happen, * The next line allow for use in any situation: install from CDROM and install using a local source, * Then a control is performed, * Eventually the current directory is set to $OEM$ and the rest of the operations can follow. [edit]: added the 'START' command in the arguments directive, otherwise .cmd files are not processed.

No definitive answer but it looks like you are using a deprecated version of that Drivers Installation Method. Maybe you should uprgade to the new one? From what I read in the corresponding thread, it looks like some users had troubles keeping setup from running (away ) while installing drivers using the old version. But I am not a user so I cannot tell for sure. Also about the brutal argument for Detached Program, I will submit a much more targetted (and so secured) one on the relevant thread for testing.

Before what? Maybe you have change something (even a tiny thing) for this to popup now, haven't you?Right now, I am a bit puzzled by the Detached Program argument. I understand that it tries to look for the location of the $OEM$ folder (can you confirm that Autoit3.exe and (or at least) Drivers.au3 are in $OEM$?). But it does it in a really brutal way (well, maybe there are no other possibility) and some strange thing may happen because of this. Is the whole thing related to Bashrât's method? In that case I think he may be of much better help than me, because I don't use it and know little about it. Also what is this SetupCopyOEMInf.exe like (inside)? But then, your error message show an exception while trying to use $WINNT$.INF. Is you computer faster/slower now than before ? Did you add/remove some drivers? Maybe $WINNT$.INF is still locked by Detached Program and the normal setup cannot access it for its own use???

As far as i can see, your [RegionalSettings] looks correct but now I see you have a DetachedProgram line which is running from T39 and which plays with $WINNT$.INF. So it most probably comes from that part: Now we need your Drivers.au3 file!

Indeed.ウザーガイドを読みませんでしたか? Also, 'Owner' is the default user (administrator) if you don't create any user (and skip OOBE). So why bothering recreating it ?

Well, intl.cpl is the language & regional setting control panel applet and $winnt$.inf is basically your winnt.sif with a little modifications. So I guess the problem is in the processing of your language and/or regional settings in winnt.sif

what???????it only installs extentions that you tell it to What? What ???????Of course, but 'all users' means in the 'program files' extensions folder, not in the 'profile' extensions folder. If different person are using the same computer they may not want to have their browser poluted by unwanted extensions. For exemple, my grand-mother may not use the same extensions as me (such as the web developper toolbar, for which I have no use). And my grand-daughter neither (sorry no grand-daughter yet, so no exemple). So we need to have separated extension set (even with possible doubles) in our own profile folders. Beside, it's a good practice to not assume what people want or need. And so install things to relevant users profiles and not ALL users when they are meant to be used by only one user. Mozilla knows that and installs extensions to your profile when done manually. You know me better than I, heh!?

Edit config.ini to skip their installation. (xpcom is already skipped by default) In that file, you can also set install mode to silent, so you won't any switch.

@stickzilla I LOVE your diplomacy!

And here's a much lighter batch version: FOR /F "skip=4 tokens=2*" %%G IN ('REG QUERY "HKCU\Control Panel\Desktop" /v UserPreferencesMask') DO set upm=%%H REG add "HKCU\Control Panel\Desktop" /v UserPreferencesMask /t REG_BINARY /d %upm:~0,4%07%upm:~6% /f

Here is an AutoIt spell invoking that magic (see link in the first post) to heal the wounds: RegWrite("HKCU\Control Panel\Desktop", "UserPreferencesMask", "REG_BINARY", StringReplace(RegRead("HKCU\Control Panel\Desktop", "UserPreferencesMask"),5,"07")) It works fine at run time but I am conjecturing that for unattended installation, it won't work until SECOND reboot: from what I understood, the breaking occurs after the theme manager loads the custom theme. And this theme manager, AFAIK, is run for the first time only AFTER RunOnceEx is finished. Recommended usage: Compile and ... have it called by the second RunOnceEx from the first! Or test it directly in the first one.