Cebaoth

I got all the answers I was looking for. I will put them together here as a help for other people: 1. Renaming the Administrator account: I used renuser.exe: a.) put the renuser.exe in the $OEM$\$$\system32\folder b.) put this line in the cmdlines.txt: "renuser Administrator MontyBurns" By the time the cmdlines.txt is executed no user was logged on, so you get the renaming very clean and smooth. the renuser.exe is attached. 2. Own settings for the Eventlog this reg tweaks sets the eventlog to a size of 4 Megs and lets it override itself when full: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application] "MaxSize"=dword:00400000 "Retention"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security] "MaxSize"=dword:00400000 "Retention"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\System] "MaxSize"=dword:00400000 "Retention"=dword:00000000 3. Default use of the classic theme In the winnt.sif add the following lines: [Shell] CustomDefaultThemeFile = "%SYSTEMROOT%\Resources\Themes\Windows Classic.theme" DefaultStartPanelOff=Yes renuser.zip

I put setenv.exe into the $oem$\$$\system32 folder to make sure it is reachable. Then I started a set_var.cmd file containing some changes on variables: md %systemdrive%\temp setenv -d tmp "%systemdrive%\temp" setenv -d temp "%systemdrive%\temp" setenv -m tmp "%systemdrive%\temp" setenv -m temp "%systemdrive%\temp" This batch is called by cmdlines.txt during setup. As I understood, the system variables you see within the system properties are not equal to the variables you get in command line with "SET". E.G. if you add a user variable "test" in the system properties\environment variables dialogue you won't see it at the command line. Maybe somebody knows how the two variable types belong together?

Thanks for your answers. Yes, I meant the old style theme (didn't come over the right word Does this count as default for all new users? The WIHU Utility looks great!! I think I'll take a further look on the tool. That leaves one question: how do I change the size of the eventlog unattended?

Hi folks, my unattended installation runs smooth so far, but I'm still dealing with three problems: 1) Is it possible to rename the "administrator" account unattended, i.e. as a vb-script run before the first login (it-security reasons in our firm; until now we done this at the security policies) 2) How can I increase the size of the eventlog and systemlog? (should be 4 megs) 3) How do I get the old style pattern as default for all users?

Thx for your help guys, you were right. I did only copy the \i386 dir from the cd. I built the cd again, this time with the files in the root - et voila it runs smooth.

Well, VM-Ware indeed IS better, but as I'm researching at work, my boss won't allow me to by a VMW-licence for testing purposes, so I have to stick to the VPC-Test version from MS. Well, never mind Doesn't find the setup-files... Sounds reasonable. I dropped a winnt.sif in the \i386 folder, theres one point beneath [data]: MsDosInitiated="0" if set to "1" it would ask for disks, but as it is set to "0" I can't think of this as the problem... I'm triing another imagemounter (Daemon-Tools) Maybe that helps with the problem... Will let you know

Hi folks, I slipstreamed a XP-CD with SP1. I used the ms_cdimage found at unattend.msfn.org and also created an iso with nero. To install, I mount the ISO using Nero ImageCD and booting up a PC with "Virtual PC", with the ImageCD-Drive connected. It first comes into the Setup but after loading the IDE-controller it refuses to go on. It always wants to continue from drive a: When I'm mounting a regular XP-CD setups continues as intended. Does anybody have experience with installing a virtual pc using a mounted image?