[BM]Crusher

I just tested my new USERACCOUNTS.CMD file in an unattended install, but I get an error with the following lines: net user "%username%" %password% /add net localgroup Administrators "%username%" /add the error is it is the second line (net localgroup) that causes the error? If I run this through windows it works fine...

if it generates a reg file, make sure it hasn't generated one with the "HKEY_USERS\S-1-5-21...." reg keys.... you can't import them if you reinstall windows i'd suggest trying to only change the LocalMachine reg settings see if that works

oh... you mean setting the process priority to "real" ? not "real mode"! hahahhaha... okay ignore my previous post i wouldn't recommend setting any priorities to REAL as your machine will pretty much be unusable and more than likely crash badly you won't get any more noticable performance by setting an application to REAL priority anyway... if anything, crank it up to "Normal" priority, but it doesn't make that much of a difference anyway

you probably need all the lines that contain 0x00000200 and 0x00000800 as they look like the new settings... don't worry about the cryptography seed I dont think you can import HKEY_USERS\S-1-5-21-73586283-746137067-1060284298-1003 settings during an unattend install... I'm not the best with registry editing I only just manage to get by

ok i already know you can create user accounts and set an auto-logon account through dos, as well as being able to change the computer name... but how do you change the "Registered Owner" through dos? is there a handy little utility to do this, or is it a simple matter of making a reg tweak to do it? i know how to make a reg tweak that does it... but it seems like there should be some easy to use little utility to do it for me? @echo off title Setting registered owner and creating auto logon account cls & echo. & echo. & echo. & echo. & echo. set /p username=Enter your desired user name : echo. set /p password=Enter your desired password : echo. & echo. set /p realname=Enter your full name : echo. set /p business=Enter your organisation name : echo. & echo. net user "%username%" %password% /add net localgroup Administrators "%username%" /add if exist %systemdrive%\install\autologon.reg del %systemdrive%\install\autologon.reg echo Windows Registry Editor Version 5.00 > %systemdrive%\install\autologon.reg echo. >> %systemdrive%\install\autologon.reg echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] >> %systemdrive%\install\autologon.reg echo "DefaultUserName"="%username%" >> %systemdrive%\install\autologon.reg echo "DefaultPassword"="%password%" >> %systemdrive%\install\autologon.reg echo "AutoAdminLogon"="1" >> %systemdrive%\install\autologon.reg REGEDIT /S %systemdrive%\install\autologon.reg echo Windows Registry Editor Version 5.00 > %systemdrive%\install\user.reg echo. >> %systemdrive%\install\user.reg echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] >> %systemdrive%\install\user.reg echo "RegisteredOwner"="%realname%" >> %systemdrive%\install\user.reg echo "RegisteredOrganization"="%business%" >> %systemdrive%\install\user.reg REGEDIT /S %systemdrive%\install\user.reg echo. & echo. & echo. & echo User Account created successfully . . . pause

if you set UnattendSwitch=yes and forget to make an auto-logon user account (or forget to set the account you made as as Administrative account) the runonce settings get processed and they all fail, and it won't clear the runonce list so every time you boot it fails the commands, until you set up an Admin account or log on as admin

get a registry monitoring program, like REGSHOT it takes snapshots and compares them... so you take a snapshot while it is set to 10MB, then do a snapshot after you change the setting to 2MB, it will show you what changed in the registry... then you can make your own registry tweaks

I didn't think you could "put" your processor in real mode... "real mode" is only needed for backwards compatability to 8088 processor architecture i thought? everything from about 386 onwards operates in real mode during BIOS etc but runs in protected mode as soon as you boot an OS? The 386 supported virtual real mode, where you could run several real mode sessions simultaneously... Real mode is a mode that enables Intel 286 and higher processor to take on the attributes of a lower 8086 or 8088 processor in order to run older software programs Protected mode is a mode found on Intel 80286 or newer processors that provides the access of addressing extended memory and allow multitasking

if that is the "Press F8 to Accept" dos mode white writing on blue background screen, the problem is in your winnt.sif when making a multiboot, you normally move the winnt.sif to a different location... double check you put your winnt.sif in the correct directory (re-read the multi-boot guide)

I don't do this and mine sets itself as Australia quite fine (with English (Australia) language)

i love your signature jrzycrim does jrzycrim stand for jersey criminal?

I'd suggest re-doing the silent installation... test it on an already installed windows first... (uninstall NAV2004, then silent install it, see if it works... if it doesnt uninstall, modify, silent install again)

bah! never mind stupid typo [sourceDiskFiles] should have been [sourceDisksFiles] damnit I quadruple checked the txtsetup.sif additions i had made... stupid! bah! some moderator please delete this topic i'm useless!

Previously, my disk has always worked good I added all the raid drivers I needed by hand (based on manufactureres txtsetup.oem files) and successfully had the Intel ICH5R SATA RAID DRiver, Silicon Image 3112 SATA RAID Driver, Via Integrated SATA RAID DRiver and the Promise 20376 SATA RAID DRiver... today, I decided I should add the Silicon Image 3114 SATA RAID DRiver to cope with a new server system building today that uses the ABIT KV8-MAX3 mainboard... I did the same as always, copied the driver folder to the $OEM$\$1\Drivers\3114 directory and added that path to the winnt.sif, added the correct settings to the txtsetup.sif and compressed the si3114r.sys to si3114r.sy_ and placed that in the I386 directory.. the same thing I have done for the other 4 drivers I have added.. also today, after I had added the 3114 driver, I compressed my drivers folder and set it up to extract as a DetachedProgram I burnt the disk, sure that it would work perfectly, only to get an error saying the si3114r.sys file is missing or corrupt.... i double checked all my files and modifications to the txtsetup.sif and everything is perfect... I remade the ISO image and decided to use Virtual PC 2004 to test it rather than make another coaster.. only to get an error about unable to load iastor.sys (it started to search the floppy drive).... I remade the ISO image and started again, this time it stopped at the si3114r.sys missing or corrupt message!?!? I am using virtual pc 2004 but never before have i had an error with the raid drivers

UnattendMode=FullUnattended won't show you any screens, unless information has been left out of the winnt.sif (it will give an error saying the administrator has not provided all the required information, then continue unattended after the info has been provided) based on his winnt.sif it should work... i'd assume the original compressed version still remains or that he isn't booting from CD (booting from floppy or running setup from windows)

what file has the error in line 43? add a download link to the file, or copy and paste lines 40-45 so we can actually see the file, so that we might actually be able to help you

set your internet explorer options through the winnt.sif file! that is the easiest and best way... read the REF.CHM from the deployment tools for information about what settings to change (look in the unattend.txt section, in IEBranding or whatever it was called)

did you delete the old compressed winnt.si_ file? are you booting from the CD? winnt.sif only used when you boot from the CD

I just did a "Quick Restore" on a Compaq 5000 series WinXP machine... I think it's really funny that they call it a "Quick Restore" *laugh* It's a 3CD Set, that used Drive Image to extract a 2CD image (never uses the 3rd disk during any section) onto the hard drive, which took about 30-40 minutes... then it tells you to reboot and I was thinking "ahh, its finished finally" only to discover that after the first 30-40 minute process, all it has done is extract the drive image of an unattended windows installation to the hard drive... now I have to wait another 30-40 minutes for that to finish! What part of "Quick" don't they understand? The disk set is specific to this model of computer, so why not just have a straight unattended install that uses 1 or 2 disks? How gay I thought!

hrmm... now you got me thinking... why not just run a CMD file as DetachedProgram? That would work.. why didn't i think of that before (I just finished burning a new copy of my CD that has compressed Drivers.exe but it gets copied during the $OEM$ copy) DetachedProgram=%systemdrive%\install\driver.cmd driver.cmd = @echo off for %%i in (C: D: E: F: G:) do if exist %%i\cd.set start %%i\Stuff\Drivers.exe

ok... so running DetachedProgram="%systemdrive%\Install\Drivers.exe" will work OK, assuming the Drivers.exe is copied from the $OEM$ directory... what if I want to run it off the CD? will DetachedProgram="Drivers.exe" look in the $OEM$ base folder? (like cmdlines.txt) ?

I must admit, I wasn't too keen on having drivers extracted using DetachedProgram but now that I have compressed the drivers folder and seen just how much smaller it is! wow! i originally wanted to run the WPI program as DetachedProgram but now that I have given up on that idea, I compressed my drivers to SFX archive my Drivers folder used to be 163MB now it is only 37.2MB

it's not possible to add a monitor in the same way as a SATA driver... you have to put the monitor INF files into a Drivers\Monitor folder, and add that path to the OEMPnPDrivers section... if that doesn't work, you can't do it

if you select an already existing partition, you cannot select to have it formatted or converted to ntfs.... the only way you can format the drive is 1) Delete the partition (in setup) and re-create it, it will ask what filesystem you want 2) Set FileSystem=ConvertNTFS , this way if you select a FAT32 partition it will be converted to NTFS, if you select an NTFS partition it will stay NTFS without format. But you don't get a choice it just does this automatically.

interesting... must be that i've never quoted things i'm running i always make sure i don't have long path names for my unattend disks to avoid any such confusion