Jito463

pskill? Shouldn't that be taskkill? Or are you using some other program to kill the process?

Or, check this posting I just made http://www.msfn.org/board/index.php?showto...ndpost&p=201671

Here's a Rar SFX for Ad-Aware SE 1.05 Personal with the 9/28 defs including shortcuts sent to the All Users Desktop and Start Menu. http://rockent.brinkster.net/Files/aawsefr.exe It will create one extraneous file in your Ad-Aware directory, this is another SFX for the desktop icons. It won't hurt anything to be there, but you can delete it if you like after installing. The install is 100% silent, so just run it and wait for the icons to appear, then it's done.

Dagnabit. I figured out my problem (not sure about ajs though). Somehow my loader files for XP Home and XP Pro got crossed. Well, at the very least my Winnt.sif file from my XP Home preinstall got moved into my XP Pro preinstall section. *imagine a smiley here smacking it's head*

Yeah, it went away but why it happens is anyone's guess. It seems hit-and-miss. I've swapped out the i386 directory a couple times to get rid of it, but every so often it comes back.

Actually, I've had that happen too. I used the same setup files for my standard install and my preinstall, the only difference was I only copied the i386 directory for my preinstall and I had all the folders for my standard install. Very odd indeed.

What is the exact error message you get? Also, make sure you use the exact same name (only 4 characters long, too) for the i386 directory and when hex-editing the boot.bin and setupldr.bin.

Snood?

Either I'm blind or that's a bad screenshot, because I don't see anything.

Look up. I already posted what you need 4 posts above yours. i386 Documents And Settings Support However, like I said a little further up, I personally don't think it's worth it. Even the AV scan is turning out to be useless. Scanned a machine using updated virus defs from BartPE using the prescanner from Ghost 9. It found 2 infected files and deleted them. I took the HDD to another computer and ran NAV 2k4 from there (since I knew it had more viruses than that) and it found another 144 infected files. Kind of pointless to have a virus scanner in PE from the disc when it finds barely any infected files.

And how, praytell, do you get this batch file to run before the file copy phase?

Hmm, well a hex-edit comparison of the two files seems to indicate that this may be real, but it looks like the /? help section has been severely pruned. The options still work, but most of the help listings are now MIA. Also, the order of several listings within the program are now changed, which would be extremely hard, if not impossible, to do with hex-editing. The file sizes are quite different too. 2.47 is 107K, and "2.52" is 74K. However, having said that, even if this version 2.52 of CDImage is valid, who cares? Like prathapml said, v2.47 works great without any problems and there's no features we need that it doesn't already support. You guys can keep chasing this elusive 2.52 version if you like, I'll stick with 2.47 until it no longer does what I need it to.

Theoretically, yes. Just modify it like so: [DiskConfig] Disk1="Disk1.config" Disk2="Disk2.config" [Disk1.config] Size1="*" PartitionType1="primary" FileSystem1="ntfs" Quickformat1="yes" [Disk2.config] Size1="*" PartitionType1="primary" FileSystem1="ntfs" Quickformat1="yes" Etc, etc. Keep in mind that according to MS, if you specify multiple drives and only one exists, it WILL gripe at you and setup will not complete.

It's a simple matter to hex-edit the files yourself. Open them in any hex editor and do a Find & Replace on i386 and replace it with GHV9 in both boot.bin (ghv9.bin) and setupldr.bin.

Well, I work for a small OEM, so we have WinPE for use during preinstalls if we wanted to, but I much prefer the CD-based install over the network install (especially so it doesn't tie up our internal bandwidth). I may have just copied it from the winbom.ini, but I can't recall for certain. All I do remember is I just used the setupmgr that comes in deploy.cab to create the answer file.

Hmm, come to think of it you may be right kenedy. I may have copied that from my winbom.ini...I can't remember now. In any case, here's my winnt.sif so someone else can play with the options. ;SetupMgrTag [Data] AutoPartition="1" MsDosInitiated="0" UnattendedInstall="Yes" AutomaticUpdates="Yes" [Unattended] AutoActivate="No" UnattendMode="FullUnattended" UnattendSwitch="Yes" OemSkipEula="Yes" Repartition="Yes" OemPreinstall="Yes" TargetPath="\WINDOWS" DriverSigningPolicy="Ignore" OemPnPDriversPath="<too long to list>" [DiskConfig] Disk1="Disk1.config" [Disk1.config] Size1="*" PartitionType1="primary" FileSystem1="ntfs" Quickformat1="yes" [GuiUnattended] AdminPassword="*" EncryptedAdminPassword="No" AutoLogon="No" AutoLogonCount="0" OEMSkipRegional="1" TimeZone="20" OemSkipWelcome="1" [UserData] ProductID="<shhhh, it's a secret>" FullName="DIT Customer" OrgName="" ComputerName="*" [Display] BitsPerPel="32" Xresolution="1024" YResolution="768" [Shell] DefaultStartPanelOff="Yes" [Components] AutoUpdate="on" [TapiLocation] CountryCode="1" Dialing="Tone" AreaCode="515" [Branding] BrandIEUsingUnattended="Yes" [URL] Home_Page="http://www.ditcomputers.com" [Proxy] Proxy_Enable="0" Use_Same_Proxy="1" [Identification] JoinWorkgroup="WORKGROUP" [Networking] InstallDefaultComponents="No" [NetAdapters] Adapter1="params.Adapter1" [params.Adapter1] INFID="*" [NetClients] MS_MSClient="params.MS_MSClient" [NetServices] MS_SERVER="params.MS_SERVER" [NetProtocols] MS_TCPIP="params.MS_TCPIP" [params.MS_TCPIP] DNS="Yes" UseDomainNameDevolution="No" EnableLMHosts="Yes" AdapterSections="params.MS_TCPIP.Adapter1" [params.MS_TCPIP.Adapter1] SpecificTo="Adapter1" DHCP="Yes" WINS="No" NetBIOSOptions="0" [GuiRunOnce] Command0="%SystemDrive%\OEM\Commands\OEMPrep.bat" Command1="%SystemDrive%\OEM\Commands\Adobe.cmd"

1) Try not to double-post 2) He simply means that he - in his own automated install - changed from the start.cmd method to using RunOnceEx. However, you don't need to worry about that unless you know what you're doing. Just use start.cmd like suggested and it will work fine.

Here's my section from winnt.sif that automates creating the partition and formatting. I assume it could be modified to automate creating multiple partitions and/or formatting multiple drives. [DiskConfig] Disk1="Disk1.config" [Disk1.config] Size1="*" PartitionType1="primary" FileSystem1="ntfs" Quickformat1="yes"

Whatever installer he's using, he's probably just letting it monitor the install and create the MSI automatically.

*stands off to the side shouting* FIGHT! FIGHT! FIGHT! *looks around* I didn't say that.

The autologon.reg file sets one user as the default to ALWAYS log in when the computer starts. If you set each one to automatically log in, then the last one will be the default that will always be logged in upon boot and everyone else will have to log out to log into their account. I assume this is not what you want. Just don't use the autologon reg file and the rest should work fine.

Here's all the WUv5 files compressed with makecab and RAR'ed up into a single, tidy package that just needs to be extracted to your i386 directory. http://rockent.brinkster.net/Files/WUv5.rar

Hard to help just based on that. Exactly what steps did you take?

Here's my structure: \ Win51 Win51IP Win51IP.SP1 winbom.ini Boot <--CD Shell menu dir which launches SGH9 boot loader | SGH9 <-- Renamed i386 dir from Ghost CD |__setupldr.bin <--- hex-edited to point to SGH9 instead of i386 | Documents And Settings | Support | Isolinux |__sgh9.dat <-- Boot loader for Ghost 9 hex-edited to point to SGH9 instead of i386 Well, it was my structure until I implemented Ghost into my BartPE (the version that allows me to clone disks, not the castrated version from the Ghost 9 CD). Since I did that, no need for Ghost9 anymore so it went bye-bye. But the structure is still sound and works.

Anothing to keep in mind, if you have any USB card readers or ZIP drives in the machine, it will take priority over Windows for drive letter. Stupid, I know. But it's true. If that happened, your only option is another format/reload without the ZIP/USB reader plugged in.