Csimbi

I do not let nLite integrate WMP11. I use Windows Media Player 11 Slipstreamer by Boooggy and n7Epsilon to do it - works like a charm.

Here's my script. I install SPTD, then reboot, then DT, then remove the crap. REM Daemon Tools Phase 1 START /WAIT %1\!INSTALL\DAEMON\SPTDinst-v160-x86.exe add /q <insert reboot cycle here> REM Daemon Tools Phase 2 START /WAIT %1\!INSTALL\DAEMON\daemon4304-lite(158).exe /S /D=%ProgramFiles%\DTLS_LT\ REM Daemon Tools Phase 3 - uninstall the toolbar for /f "tokens=3*" %%i IN ('reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\DAEMON Tools Toolbar" /v "UninstallString" ^| findstr "REG_SZ"') do "%%i %%j" /S REM Daemon Tools Phase 4 - remove leftover DIR_LOC.CMD "%ProgramFiles%" "RD /S /Q " "_DTLite.xml" You can find DIR_LOC.CMD here.

Tried again. This time it worked. I wonder why didn't it work earlier. Thank you!

I tested again with nLite 1.4.9.1 - it stores new settings (e.g. Path) in the .ini and keeps the ISO-Setting. Really? I added this to the end of the nLite.ini file (same place as nLite.exe) : [ISO] ISO_label = TEST and nLite wiped out the whole file and created a new, blank file containing only this: [General] Path1 = CPriority = 2 Am I doing something wrong?

g-force, thank you, that's exactly what I was looking for. Unfortunately, it does not work with nLite 1.4.9.1; nLite will create a blank INI file.

Bummer. Someone hacking nLite's executable is out of the question I guess?

Ok, I had enough of looking at that rubbish left behind. To remedy this issue, I made a generic script that will locate a directory with the specified files (max 6 can be specified) under it. I attached this script. You should put it to a directory specified in %PATH%. Start the script without parameters (or, insufficient parameters), and you will get the help. Start the script with the right parameters, and you get what you wanted. It gives no other output than the help, so you can call it silent. Now, back to the .NET framework rubbish. Invoke said script like this: @DIR_LOC.CMD "%SystemDrive%" "RD /S /Q " "amd64\filterpipelineprintproc.dll" "i386\filterpipelineprintproc.dll" And the rubbish will be gone. Have a nice day. PS. I wonder if it should be a separate topic; could be quite useful for other matters, too. DIR_LOC.CMD

Right, I know that, but that's not what I am I looking for. I guess I was not clear about that, let me try again. Entering the same volume label every time you create an ISO is becoming a pain (just build two images per hour, and you will see what I mean). Hence, I am looking for a way to tell nLite to use a specific volume label for the image. The easiest would be if it could be added to the INI file, but it seems that it's not saved there automatically, so I guess it's not possible (or, not documented)...

Hi there, nLite always set the volume label to "WinLite". I have to enter it manually every time because, it seems that it is not saved into the Last_Session.ini. Is there any way to tell nLite to use a specific volume label instead of "WinLite"? Thank you. Edit: Updated the topic title to reflect that it's solved; see post #7 from g-force below.

I usually do that kind of things with ccleaner, and have it scheduled to execute regularly. Right. What I mean is: immediately, after the installation of .NET and its updates. We know it's going to be there, but we don't know its name.

Checked the INI file. The "ComputerName = " is empty. I could not find any user accounts apart from the built-in ones. Create a real Admin account and make sure it's not the same as ComputerName in Last_Session_u.ini: [Users] Administrator|||True|Administrators|password|False|True|True Guest|||False|Guests||True|False|False MeMySelfAndI|||True|Administrators|mepassword|False|True|True Then, set auto-login to MeMySelfAndI in Last_Session.ini: [Unattended] ComputerType = Automatic AutoLogon = MeMySelfAndI ...

I could not find any post about unattended/silent installation of the Codegear RAD Studio. I did some research and I got it working, so I thought I would post my findings so others could benefit from it, too. I use Codegear RAD Studio v2009, but I am pretty sure that these parameters are valid for v2007 as well, since it uses the same installer. 1. RAD Studio install SETUP.EXE /s KEY1=<KEY1> KEY2=<KEY2> KEY3=<KEY3> KEY4=<KEY4> LANGUAGE=<LANGUAGE> TARGETDIR="<TARGETDIR>" DEMOSDIR="<DEMOSDIR>" COMMONFILES="<COMMONFILES>" USERNAME="<USERNAME>" USERCOMPANY="<USERCOMPANY>" Required parameters: /s - silent install switch <KEY1>: The first group of your serial number. <KEY2>: The second group of your serial number. <KEY3>: The third group of your serial number. <KEY4>: The fourth group of your serial number. Optional parameters: <LANGUAGE>: The language setting. It is either English, French, German or Japanese. <TARGETDIR>: The directory where you want to install Rad Studio. <DEMOSDIR>: The directory where you want to install the demos. <COMMONFILES>: The directory where you want to install the common files. <USERNAME>: Name of the registered owner. <USERCOMPANY>: Company of the registered owner. Optional toggles (=TRUE or =FALSE): AUTOCHECKFORUPDATES - Obvious. INSTALL_AJAX - I did not find an Ajax installer on my v2009 disk; maybe a leftover from v2007? INSTALL_BOOST - Obvious. INSTALL_DBPACK - Obvious. INSTALL_DEMEANOR - Obvious. INSTALL_HELP - Sounds obvious, but has no effect on v2009 at least. INSTALL_RAVE_REPORTS - Obvious. There are a lot more parameters, but I did not really need them because the serial number will determine what components will be installed. If you are interested, just check the install scripts embedded in SETUP.EXE and you will find these. If you figure out how to use those properly, please post your instructions here. 2. Microsoft document explorer install For some reason, the help system cannot install Microsoft document explorer silently. On top of this, the help system will refuse installation unless Microsoft document explorer is already installed. So, you will need to install Microsoft document explorer prior to installing the help system. You can obtain the Microsoft document explorer installer from several places. There is one on the Rad Studio DVD, too; my script is using that one, so I refer to that when I say: grab a 7-Zip unpacker, extract the archive from the DVD, then run the following command: mFileBagIDE.dll\bag\install.exe /q 3. Help system install Help_Setup.exe /s TARGETDIR=<TARGETDIR> Required parameters: /s - silent install switch <TARGETDIR>: The directory where you want to install the help system. NOTE: The "\HELP" will be appended to TARGETDIR automatically. 4. Importing your license I did not bother with that since this is something you normally do on the first start and not the installation - it is just two clicks. I guess it is possible to copy the license file to the appropriate place and update the appropriate registry keys. 5. Automating the whole process I attached a script that will install both Rad Studio, Microsoft document explorer and the help system in one go. The script is best used on a clean install, where the .NET framework is already installed. See this post for .NET installation. The script is not completely silent; it will ECHO three lines to the screen during the installation, telling you when the installation of a certain component has began. I did this because the process it quite long even on a fast machine, so you don't wonder what's going on. If you don't like it, you can safely comment out these ECHO commands in the script. My script requires only three things to work flawlessly (assuming you have the appropriate permissions on the system): - The RAD Studio DVD in your drive. - 7ZA.EXE in a directory included your PATH variable. 7ZA.EXE is the 7-Zip command line version. Get it here. Without this, Microsoft document explorer won't install, and as a result, the help system won't install neither (unless of course you have Microsoft document explorer already installed). - Edit my script and replace the dummy serial number placeholders with your own serial number in the TARGETPARMS environment variable. While you are editing my script, you may want to update the TARGET* environments variables to your liking as well (if you are not happy with mine). I know the script could be improved, but since it works, I did not bother. If you have suggestions, post them along with the updated script here. RADSTD_U.CMD

http://www.msfn.org/board/microsoft-net-fr...ce-t136991.html

Post your INI files. (remove private data!)

That's a common mistake. Glad you could resolve it.

As far as I know, this is not a bug. You need to create another account with Admin privileges even if you did not change the name of the Administrator account.

I have a gut feeling that it is not a good idea to disable the Admin account during setup; you can disable it later from RunOnceEx, using the NET command. Anyway, it's just a gut feeling, checking if that might be causing the problem. I did not have any bug with renaming the accounts - works like a charm here.

The first False means that the account will not be active. Did you try switching that to True? Also, I assume you are disabling the Administrator account for security reasons. Well, you should not. You should rename the built-in accounts instead: Also, since you did not specify any passwords, you should change the highlighted flags to False. Or, if you want to keep those True, specify the passwords at the highlighted locations.

The [users] section looks good, it should work. I had problems with user creation when I used a non-clean source, see: http://www.msfn.org/board/index.php?showtopic=136951 Try using a clean source.

I am unable to download the TaskSwitchXP addon; it seems to be deleted. Could someone put it on Rapidshare or some other hosting service that does not require signing up? Thank you. Edit: Got a new link from rado354.

I had to dig deep in the closet to find my original disk. Applied the INI files to it and it works like a charm. Apparently, something got screwed up along the way...

I am doing pretty much the same thing ;-) I did not rename the files though and I have arranged the files in different directories. BTW: it seems you missed one update for 1.1 SP1: NDP1.1sp1-KB886903-X86.exe Here's my GUIRunOnce: [GuiRunOnce] @ECHO OFF ECHO Applying Registry Tweaks... REGEDIT /S %Systemdrive%\HKLM.REG DEL %systemdrive%\HKLM.REG REGEDIT /S %Systemdrive%\HKUD.REG DEL %Systemdrive%\HKUD.REG REGEDIT /S %Systemdrive%\HKCR.REG DEL %Systemdrive%\HKCR.REG REGEDIT /S %Systemdrive%\TotalCommander.reg DEL %systemdrive%\TotalCommander.reg ECHO Installing .NET Framework 1.1 START /WAIT %Source%!INSTALL\DOTNET11\DOTNETFX.EXE /C:"install.exe /Q" /Q ECHO Installing .NET Framework 1.1 SP1 START /WAIT %Source%!INSTALL\DOTNET11\NDP1.1sp1-KB867460-X86.exe /Q /I ECHO Installing .NET Framework 1.1 SP1 Hotfixes START /WAIT %Source%!INSTALL\DOTNET11\NDP1.1sp1-KB886903-X86.exe /Q /I START /WAIT %Source%!INSTALL\DOTNET11\NDP1.1sp1-KB928366-X86.exe /Q /I ECHO Installing .NET Framework 2.0, 3.0 and 3.5 incl. SPs START /WAIT %Source%!INSTALL\DOTNET35\dotnetfx35sp1.exe /passive /norestart ECHO Installing .NET Framework 2.0, 3.0 and 3.5 incl. SPs hotfixes START /WAIT %Source%!INSTALL\DOTNET35\KB959209\NDP20SP2-KB958481-x86.exe /passive /norestart START /WAIT %Source%!INSTALL\DOTNET35\KB959209\NDP30SP2-KB958483-x86.exe /passive /norestart START /WAIT %Source%!INSTALL\DOTNET35\KB959209\NDP35SP1-KB958484-x86.exe /passive /norestart START /WAIT %Source%!INSTALL\DOTNET35\NDP35SP1-KB963707-x86.exe /passive /norestart ECHO All done. Initiating system restart. SHUTDOWN.EXE -r -f -t 60 -c "Your system will restart in 60 seconds..." SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\085 /VE /D "Cleaning Up and Rebooting" /f REG ADD %KEY%\085 /V 1 /D "%Systemdrive%\CLEANUP.CMD" /f Any clue how to get rid of the random temp dir left behind by the installer in the %Systemdrive% directory? Thanks.

Yes, I am aware of the situation with Nugi, thank you. The "|False|False|False" are for the three checkboxes in nLite under the User password section, in this order: - Blank password - Must have - Can change I tried giving a password and using different variations, did not work. The thing is that I should not have to change anything, because The release I am using has been slipstreamed using nLite (only the updates, no users and unattended install). But nLite does not complain about anything, so I assume that it can read back all the slipstreamed files. I found this in nLite.inf: [TO] ... HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_01",0x00000000,"nhelper net1 accounts /maxpwage:unlimited" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_02",0x00000000,"nhelper net1 user """"Csimbi"""" /add /passwordreq:no" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_03",0x00000000,"nhelper net1 localgroup """"Administrators"""" """"Csimbi"""" /add" ... So, I guess nLite does add it to the image, but for some reason the user is not created. Is there any way to find out why? I am not familiar with details, but I guess I could do some investigations using some pointers.

Hi all, I have created .INI files with nLite 1.9.4.1 in the past. See them attached. I have been using these successfully in the past. I set up a testbed under VMWare to test a new image yesterday. The installation goes fine, but there is no user account created. There should be one called 'Csimbi', as you can see from the INI files. When XP starts, only the Administrator account is available on the login screen and I need to create an account manually after I logged in as Administrator. I tried enabling/disabling auto-logon, but no luck with that. I wonder if anyone had the same problem and was there a solution for this. Or, was there any updates issued since April (that was the last time I made an image) that may be causing this problem? Thank you. Csimbi_1491.ini Csimbi_1491_u.ini

Right, thanks for the tip. But then I would have too many duplicates: one per XP disk, which is about 3G/disk at the moment - and I am managing 4 install disks, so that comes to about 12G wasted space. That's a lot. Also, it is a lot easier to copy INI file sections to the other XP installs than to sync directories every time.