REDONDOS

Already tried that. Also, I tried a couple of the new uxtheme.dll files around the forums, but none of them seemed to work, can you please point me to the right post? Thanks.

This doesn't work for me! On XP Pro SP2 I used latest Replacer version to change termsrv.dll for the old, concurrent sessions-enabled, file. Then applied the registry changes and rebooted. Enabled remote desktop and tried to log in with the same user that I was logged in with from mstsc, but this made the Welcome Screen appear. Then logged back on, remote desktop connection closed automagically, and tried to log on with some other account through remote desktop... same problem. Does this really enable me to be logged in and actually using the computer from 2 different locations at the same time? Because it isn't working... Thanks.

Great! Thanks a lot guys. It surprised me that I couldn't find any posts about this issue, since I don't think it's _that_ obvious what the files inside the [root] folder are for. (Actually, I didn't even see them )

Just slipstreamed SP2 into my SP1 Unattended XP CD (had to delete Winnt.sif first, otherwise SP2's Update.exe wouldn't update the installation files; but then recreated it with the new options incorporated in it). Then I created the bootable image and went on to try it on VMware. I get this message from Windows setup right after it starts, on the typical blue background (F3=Exit). Then I slipstreamed SP2 into my original XP SP1 CD, created the image, and booted. It all went Ok so I guess it has to do with my unattended configuration. What could it be? I can just copy over the files again, and I guess that will work, but I am really curious about what is causing this.

I got it, thanks man. Anyway, what I understand is that if the computer name is "blah" and you create a username "blah" and try to add him to the administrators group with this command: net localgroup Administrators blah /add then Windows thinks the username is missing, since "blah" is the computer's name, so it expects what you just said "COMPUTERNAME\USERNAME". I don't know if it's like what I understood, but now I have a clearer view on this. Thank you.

Oh, man. This was driving me crazy! Thank you for your post (and many others regarding this issue). Anyway, do you know why in hell adding a user to the Administrators group using the "net" tool when the username is identical to the computer name doesn't work?

wamatt: Sorry for not replying earlier. The trick is that if you need to pass any switches to msiexec, you have to "escape" them. That means use backslashes. For example, for the line you needed: start /wait AdbeRdr60_enu_basic.exe -p"-s /v\"/qn INSTALLDIR=\"c:\Progs\Media\Adobe\Acrobat 6.0\"\"" See that I escaped every set of double quotes except the first and the last ones? And if you need that inside your RunOnceEx.cmd file: REG ADD %KEY%\001 /VE /D "Adobe Acrobat Reader 6" /f REG ADD %KEY%\001 /V 1 /D "start /wait AdbeRdr60_enu_basic.exe -p\"-s /v\"/qn INSTALLDIR=\"c:\Progs\Media\Adobe\Acrobat 6.0\"\"\"" That is, of course, escape another set of double quotes since you need to enclose the line you need to install the program between "s. Another example would be what I actually use and works for Diskeeper 8: REG ADD %KEY%\002 /VE /D "Diskeeper 8" /f REG ADD %KEY%\002 /V 1 /D "%SYSTEMDRIVE%\Applications\diskeeper\setup.exe /s /v\"/qn INSTALLDIR=\\\"%PROGRAMFILES%\System\Hard Drive Tools\Diskeeper\\\"\"" /f pastl (or anyone willing to help, actually): Your tips were very useful, thanks a lot for them. The only problem I am having is that none of the installation programs made with Wise installer seem to like the /X switch. For example, Opera 7.51 just won't install if I use /X. Instead, the installer extracts the installation files to the directory of my choice but never actually installs the software. In fact, after reading Wise KB Article #564 I found out the following: /X pathname -- extracts files into pathname So I guess that Wise just doesn't have a switch for installing to an alternative directory, and that's why I just repacked the applications that use it and well, it seems that they work. Anyway, if anybody of you does know how to make Wise Installer install an application to a directory other than the default, please post your comments.

Thanks a lot, Joe User 99 & pastl.

Well, that's the question. I'd like to install -for example- Nero Burning Rom into: "C:\Program Files\CD Burning\Ahead\Nero" or ACDSee into: "C:\Program Files\Multimedia\ACD Systems" How can I accomplish this task? I've searched through the forum but found nothing but switches for the automation process, there is no information regarding changing the default path for the installation. I guess that creating a .iss file for InstallShield installations would respect the folder I chose at the time of the .iss creation, but what about Windows Installer, NSIS, WISE and Inno? Thanks in advance.