Djé

Same thing: network is there (ping ok) but I've got the same message: now user's password is null... (username is an existing one on the server). I'll give a try with a real password. EDIT: using a password, it works !!!! I got the same message as above BUT net use now works while it did not without password.

Ok, I'll give it a try. I just need to find a floppy drive! edit:That one is a zip. How could I've missed it last night. Thank's for puting me back on my feet.

@theUtmost: Thanks for this good summary. While trying to help clivebuckwheat (hi man, how is it going on?) I wanted to make my own dos boot cd with network support, but so far it doesn't work. I'm using bartPE on a regular basis for re-installing windows (both through network and from a partition) but I am interested in solving clivebuckwheat's problemS and in giving network dos install a try. Anyway, so far my 'best' result (with bart's dos network boot disk) is being able to ping the 'server' ! But I still cannot connect to the share. I've tried other dos network boot disks, including clivebuckwheat's (ghost boot disk?) but couldn't have the network working properly with any of those. All systems are using NETBEUI. And I also tried using TCP. Now the thing is: my setup might be too specific. I connect directly both PCs (server -running xp home- and client) using a crossed cable and give them fixed IPs (10.0.0.254 and 10.0.0.1 respectively). Also workgroup is the same for both PCs. So no proper network, no dhcp, no real server (and of course no domain), just one link. This setup works very fine using BartPE (so windows) but not at all using dos. And now the questions (@theUtmost or anyone else, of course): do you know what I am missing? Did you run into such problems during your testings and/or do you have any opinion about my problem? Does someone have a good documentation source for protman? @Admins & mods, please add me to the supporters of a subforum for Network-based installs.

@Ryan, just run AutoWEP again with your second set of parameters (SSID and key). Do it for as much networks you want to log to. (You don't need any ini file anymore with the last version): AutoWEP.exe mySSID1 myKEY1 [WPA] AutoWEP.exe mySSID2 myKEY2 [WPA] I wonder if we can make it simpler. Maybe automatic recognition of the key type to get rid of the optional last parameter... If you don't want to have your keys in plain text in your RunOnceEx.cmd or wherever, THEN use ini files BUT let those ini files on a [removable] drive (floppy, usb, partition, share, whatever) from where they can be deleted after the install is finnished. Just provide the full path of the ini files to AutoWEP: AutoWEP.exe F:\whateverpath\myNetwork1.ini AutoWEP.exe F:\whateverpath\myNetwork2.ini Or even better, have only a batch with the above command lines (AutoWEP.exe mySSID1 myKEY1 ...) on the removable drive.

Maybe not comprehensive but jdoe just pointed us to a nice list albeigt a german list in this post. Read also my following post for less hassle if you don't speak german.

Do you use a vanilla xp sp2 or do you integrate hotfixes or UpdatePack? In case you're using the last version of RyanVM UpdatePack, I would recommand posting in the thread I linked to in his forum, because the guys there might help you better than here. In case you integrate hotfixes manually, I would recommand using the addon linked to in this post of the thread. Actually I'm using it succesfully but I did not bother integrate that addon with the RVM integrator. I just open it and manually copied the modifications to the appropriate file(s). And it solved that specific problem of icfgnt.dll (I'm also installing through a network share, but using BartPE and winnt32). If you tried this using the integrator or nLite, did you double check that the entries were added to the appropriate files(s). In any case does it work with a vanilla xp sp2 source ? In Japan they use to say: Gambatte! It's a cheering interjection meaning 'good luck' and 'keep on fighting' all together. That's all I wish you.

Bezalel, I must agree with you for the drivers for which you can install everything with the inf file. But many laptops for example, come with a set of 'Drivers and Utilities', some of them not totally useless and some of them requirering to be set up using an exe installer (no inf provided or not every feature installed by the inf). The trouble comes when the formers and the laters are the same. Then, since each set has to be installed on its computer, you would benefit from knowing which computer you're installing on. Actually, I was waiting for your Oembios files thing to tweak it in that direction. Beside, on laptop, you don't upgrade so much the hardware, and making the 'database' is relatively straight forward. Now, all my computers are from different manufacturers. Do you know if WMI is functional *enough* at T12 to be queried by something like the above script, so I can at least find out that piece of info, which in turn will be enough to decide on what files to copy/CD-key to use/Apps to install? edits: bad english to somewhat better english

Wow ! That's an impressive amount of work all together. And I know where I'll go when I'll want a big bunch of consistent scripts to start learning vbs from . Thanks man!

MHz, I think you did not get it exactly. I'll try to explain it better below, and also why it still works the way you do. AFAIK, at T12, HKCU (meaning the loaded user hive, or profile as you call it) does not map to the hive in the Default User Profile, which does not exist yet. Rather, it maps to HKU/.DEFAULT, which is NOT the same. HKU/.DEFAULT is the registry hive for No User (before someone logs in). It is stored in '%SystemRoot%\System32\config' along with all the system hives. Its file name is simply 'default'. In there you can also find a folder called 'systemprofile' which stores the 'No User Profile' files. I don't know yet when, but after T12, the Default User Profile is made out of (copied from) this 'No user Profile', and the 'default' hive is copied to the NTUSER.DAT (user's hive) of that Default User Profile (meaning in '%ALLUSERSPROFILE%\..\Default User' ). That is why you don't have to load the Default User hive and it still works (you already know that, later, when a new user logs in for the first time, his profile is made from that Default User Profile). Why I'm saying it's not clean and why Yzöwl made this hive loading batch is that using HKCU at T12 leaves some stuff in HKU/.DEFAULT which has no reason to be there, since No User does not need any shell folder. Now, I must agree, it's not that a big issue. But if you do that for all your reg tweaks, well... yes it works, but I maintain: it is not very clean. We can do better. And loading a hive, tweaking it no more than necessary and then unloading it IS clean. It may be some more work, but it does not leave any mark behind. @Yzöwl: no I don't have any little script coming on. And I would not, except if you ask me to do it. I was just commenting (that's always easier ).

1- Yep. That's the clean way to do it. HKCU at T12 is not very clean. So I guess the sequence would be: a- schedule redirect.vbs in HKLM RunOnceEx (from T12, T13 or whatever for the first login). b- schedule the above batch (including a moving of redirect.vbs to the proper location) to be run also by HKLM RunOnceEx so it will set-up the things for subsequent users. Now, if redirect.vbs has to remain on the computer for any potential user (re-!) showing up. Maybe it would be ideally located in %SystemRoot% 2- I have no vbscripting techniques, so my suggestion remains theoretical.

Localgroup Names are language dependant: In French, we have to use: net localgroup Administrateurs EndUser /addOtherwise EndUser stays a user (Utilisateurs) by default. Appart from this and the above suggestion about space, I can't see anything else.

2 questions and 2 possible (related) suggestions: 1- When you say ' logon script', do you mean runOnceEx or are talking about something else that I will want to know about. If it is runOnceEx, you may have it run for every user by using the runOnceEx key not in the HKLM hive, but in the HKCU one at T12. This way, the running command will be copied to the Default User hive and then to every users hives to be executed when they first login. It you're not talkin about RunOnceEx, what is it then? 2- Are the keys changed before or after the creation of the standard Shell Folders by windows? If it's after, wouldn't it be interesting to also delete those standard Shell Folders with a few more lines in the script, since they aren't needed anymore?

Yes I'm really impressed. I loved that "%ALLUSERSPROFILE%\.." and your first line as much as your "PUSHD %OEM%||PUSHD %SYSTEMDRIVE%" in another thread. Batch scripting can be a bit harsh, but you know how to put oil in it.

HeHeHe too busy since then so you forgot about the $OEM$ stuff in my post and tridgely's addition. BTW, how did you solved your problems? You'll have to make a full tutorial for others when done.

@Yzöwl, depending on your posts I see you using either: FOR %%? IN ('MOUNTVOL^|FIND ":\"') DO ...Or FOR %%? IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO ...And now adding this nice CALL :SUB "%%?:" &&GOTO START trick to the later. Are you researching for the best way to do it or is there specific reasons for picking up this or that method?

No way ! Regexp in my batches?!? I'm learning every day. Have to find out about those escaping ^, tho. Why and where do I need them? My friend?

You can already do it simply by running firefox with the ' -setDefaultBrowser' switch. Starting from v 1.6 (still beta), you will be able to do it unattended: the ' -silent' switch of firefox will work again, so something like the line below will do the trick the right way: "%ProgramFiles%\Mozilla Firefox\firefox.exe" -silent -setDefaultBrowser You'll have to have a valid profile already defined or add the ' -CreateProfile default' switch, tho. Otherwise, you'll be asked to import IE settings.

Updated the RunOnceEx explanation (even more breaking down to details!) in the above tutorial.

Hard to grab that switch thing hé? Actually the ' /S /v/qn' switch is for the 'installer command', not for the REG ADD command as you put it: * The whole 'installer command', including the silent switch, has to fit inside the quotes. - It is NOT YET a command stricto-sensu. - Rather, in this context, it is just a text added to the registry by the REG ADD command. -> As such it needs to be surrounded by quotes and to follow the /D (data) switch of REG ADD. * The REG ADD command needs a ' /F' switch to force the addition/overwriting of the value in the key. * You don't need to repeat the REG ADD %KEY% /V TITLE /D "Test Programs Installation" /F line for each program. - This line is only setting the title of the RunOnceEx list window (the one showing up just after login, saying it is installing your programs). - It writes the data (/D) 'Test Programs Installation' to the value (/V) TITLE of the key %KEY%. - If you repeat it, it repeats the exact same action, and only that. No need to do so, one time is enough. *Open a command prompt and type 'REG ADD /?' to learn about the syntax of this comment. And as I said before, switches are specific to each installer. So the one for Adobe ( /S /v/qn) may not work for Spybot. Appart from this, it looks good. Keep on learning! Your correct RunOnceEx.cmd should be: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Test Programs Installation" /F 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 REG ADD %KEY%\002 /VE /D "Test with Spybot" /F REG ADD %KEY%\002 /V 1 /D "C:\install_test\spybotsd14.exe /SpecificSilentSwitchForSpybot" /F Just replace ' /SpecificSilentSwitchForSpybot' by the correct switch for this program.

Change the switch from ' /silent' to ' /S /v/qn'. That is, I beleive and tested, the actually working one for silently installing that version (7.0.7) of Acrobat reader. There may be some different way to go for installing your apps (from HD, from CD, etc.) but usually there is only ONE possibility for the switch for one particular prog to get install silently. You have to use the correct ones for each app (search for them in the guide or on the dedicated forum).

just a few other (bad) ideas: - Technet also says you don't need to use lh for smartdrv, it is automatic. - You use the /V option. what does the output says? - When smartdrv is run , drive U does not exist yet. Does this has any importance? - My best advice would be to first try an autoexec with only 1 line: a:\smartdrv.exeand see what it says. - Or specifically disabling disk caching for a: : a:\smartdrv.exe A- Good luck

Why do you use the ' /NOEMS' switch? According to M$ Technet, it "prevents access to expanded memory".

Maybe you need to specifically set temp to somewhere smartdrv can write? I'd try SET TEMP=C:\ My 2 cents.

What Yzöwl was saying was not to add a % sign at the end of your path, but to double any % sign there may be in it. that's because % sign are used for variables (like %AllUsersProfile%).

That's Ok, I'm not offended. But writing such tutorial requires quite some time, so I'd better now before if other users don't give a s*** about it. Or have improvements to suggest. Criticism is *always* welcome. It's just because that step is difficult to grasp and that the official guide may not be enough that I wrote it. I also had hard time there. I understand your situation. Now just have a glimpse at mine. Anyway, your question are still welcome. But try to keep the whole thing in 1 single thread in order for the other users here having a hard time grasping this same stuff to benefit from it without having to look for all the bits dispersed in different threads.