Aaron

"no" will allow the Welcome to Windows XP screen, use "yes" to skip it.

Thanks for the compliments

yes, but thats a long way off, and my new PC is due in 1-2 weeks

eh, that's really strange!

No rush

I think mydomain would be the workgroup name if you're not on a domain

The recommended updates become part of the service pack.

if you have an already installed XP OS in Virtual PC, you can test your batch (hotfixes, applications), just dump everything in the c:\install\ folder. You can't test the deletion of shortcuts unless it exists on the test OS.

Does the monitor go on standby when this happens? Check in the game options (if there's an external app available) to see if the resolution/refresh isn't set to high. Does the DirectX 3D tests also blank your monitor? (Update your drivers if it does) If no luck, its a faulty monitor (I've got one that's doing what you're explaining)

Go into the root of the directory where you copied your windows XP CD files. and type this in command prompt: attrib -r /S /D

Might be possible, try to identify what installer package it uses by viewing the Install Types listed at http://www.MSFN.org/unattended/xp/applications.htm then you should be able to work your way from there.

Yes, drivers get installed during the Installing Drivers part of GUI-mode Setup, after that Setup installs the Network Settings.

Taken from the OPK.chm, hope its of some help: Preinstalling Mass-Storage DevicesPlug and Play installs most hardware devices, which can be loaded later in the Setup process. However, mass-storage devices, such as hard disks, must be properly installed for full Plug and Play support to be available during GUI-mode Setup. For this reason, their installation is handled differently from that of other hardware devices. When the [MassStorageDrivers] is used in Unattend.txt, no in-box mass-storage drivers are installed during text-mode Setup unless they are specified in this section. If this section is missing or empty, Setup attempts to detect the SCSI devices on the computer and install the corresponding in-box drivers. Note You don’t need to specify a device if it is already supported by Windows XP. To preinstall SCSI devices during text-mode Setup, before full Plug and Play support is available, you must provide a Txtsetup.oem file that describes how Setup should install the particular SCSI device. For more information about Txtsetup.oem, see the Microsoft Driver Development Kit (http://www.microsoft.com/ddk/). To preinstall a mass-storage device In the \$OEM$ subfolder of the distribution folder, create the \Textmode subfolder. Copy the files from the disks supplied by the device vendor to the \Textmode subfolder. These files normally include: Driver.sys Driver.dll Driver.inf Driver.cat Txtsetup.oem where Driver is the driver name. Notes You must also copy the driver files to the location you specified in the OemPnPDriversPath entry in the answer file(s). For example: OemPnPDriversPath = drivers\audio;drivers\net Some drivers, such as SCSI miniport drivers, may not include a .dll file. A catalog file (Driver.cat) must be included with mass-storage device drivers if it is listed in Txtsetup.oem. For more information about catalog files, see the Microsoft Windows Driver Development Kit at: http://www.microsoft.com/ddk/ In the Unattend.txt file, create a [MassStorageDrivers] section, and then type any driver entries in that section. For example, a possible entry in the [MassStorageDrivers] section is: "Adaptec 2940…" = "OEM" Obtain the information for this section from the Txtsetup.oem file provided by the hardware manufacturer. In the Unattend.txt file, create an [OEMBootFiles] section, and in it type a list of the files in the \$OEM$\Textmode folder. For example: [OEMBootFiles] Driver.sys Driver.dll Driver.inf Driver.cat Txtsetup.oem where Driver is the driver name. Important Only add driver entries to the [MassStorageDrivers] and [OEMBootFiles] sections for bootable mass-storage devices. Do not include secondary mass-storage devices. Instead, add the drivers for secondary mass-storage devices to the folder specified by the OemPnPDriversPath entry in your unattended Setup answer file. Including drivers for non-bootable mass-storage devices in the [MassStorageDrivers] or [OEMBootFiles] sections causes an error during Setup. If your mass-storage device is a Plug and Play device, verify that a Hardware Identification section and the name of the catalog file for the driver (Driver.cat) exist in the Txtsetup.oem file. For more information, see the Microsoft Windows Driver Development Kit at: http://www.microsoft.com/ddk/ If the Hardware Identification section does not exist, you must add [HardwareIds.scsi.yyyyy] to the Txtsetup.oem file and verify that the following information is included: id = "xxxxx" , "yyyyy" where xxxxx represents the device ID, and yyyyy represents the service associated with the device. For example, to preinstall the Symc810 driver, which has a device ID of PCI\VEN_1000&DEV_0001, verify that your Txtsetup.oem file contains the following additional section: [HardwareIds.scsi.symc810] id = "PCI\VEN_1000&DEV_0001","symc810" Drive and path references must be removed from Txtsetup.oem. For example, [disks] d1 = "Windows 2000 Driver Set v1.00", \w2kdsk1, \win2000\smy810\ must be: [disks] d1 = "Windows 2000 Driver Set v1.00", \w2kdsk1, . Note the period at the end of the line. Selecting and Loading the Correct Mass-Storage Driver If you are including new or updated drivers for mass-storage devices, you must add the new driver to both of these folders: \$OEM$\Textmode The location specified in the OemPnPDriversPath entry in the Unattend.txt file. For example: \$OEM$\$1\Pnpdrvrs\storage Loading Mass-Storage Drivers during Text-mode Setup If the driver for the mass-storage device is included with Windows XP, the Windows XP driver is chosen before any drivers in \$OEM$\Textmode. However, the driver you place in \$OEM$\Textmode is the first driver chosen during text-mode Setup only if: The driver that ships with Windows XP does not boot. The driver does not ship with Windows XP. Loading Mass-Storage Drivers During GUI-Mode Setup Windows XP loads an updated or new driver during GUI-mode Setup if the following criteria are met. If you are loading an updated mass-storage device driver for one that ships with Windows XP: The correct mass-storage driver is provided in the location specified by OemPnPDriversPath. The driver is signed and is a more recent version than the one provided with Windows XP. If you are loading a new mass-storage device driver that did not ship with Windows XP: The driver is new (not included with Windows XP), signed, and installs properly during text-mode Setup. For information about how Windows chooses the best driver during Plug and Play detection, see How Windows Selects a Particular Device Driver. For more information about managing operating system images that contain different mass-storage drivers, see Reducing the Number of Master Images for Computers with Different Mass-Storage Controllers.

It is in Quarantine at the moment but still get the message grr lol o well lol Should be deletable then

Most of the Adobe apps uses WISE, and Macromedia uses Installshield. Switches for these packages can be found on the Applications page. An exception is Adobe Reader which uses netopsystems, there is a dedicated page for Adobe Reader on the site.

in a different area of the winnt.sif file? No, it doesn't make a difference, but at least GuiRunOnce functions fine

Its correct, he means naming the folder so you know what drivers they are. He's not using a path directly to any INF files either, only the folder containing them, so all's OK

Method 2 @ http://www.MSFN.org/board/index.php?act=ST&f=70&t=7557 http://www.MSFN.org/unattended/xp/applicat...stallshield.htm

You are a TREE?!!

Some people in the forums have used winrar to compress office, and then using the unrar.exe tool to decompress to the systemdrive, with success Try searching for unrar.exe to find the relevant threads on this

So to all of you planning to distro a virus, hide it behind 11 levels of compression

Depends if your Antivirus software is able to scan inside compressed files. Norton Antivirus can scan 3 levels deep as default, and the limit is at 10.

If Norton AV says its a trojan, it should be in the quarantine? If not, CTRL-ALT-DEL and end task on script.exe

Good tip using vbs, now I know why QuickLaunch had no relevance to the registry when I monitored it.

The rumours that QoS steals your bandwidth have been disregarded by the top techies.