Jump to content

thefultonhow

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by thefultonhow

  1. So does that script automatically choose the multiprocessor ACPI HAL or the normal uniprocessor ACPI HAL based on what type of computer it's being installed on? Where in the setup process can I insert the script? Although I have used RIS in the past, I am new to WDS, and I'd like to not have to have two different images on the WDS server if possible.

    Well, the script doesn't choose the HAL, it updates sysprep.inf with whatever HAL is being used on the PC.

    I have the script set to run after I've loaded the image on the drive using imagex.

    I have one image for all the PC's I use and it works great for me.

    How do you trigger the script to run?

  2. I don't know about anyone else but I use the following script. It runs after the WIM has been copied to C:\ and updates sysprep.inf with the information for the appropiate HAL. So far it hasn't failed me yet.

    So does that script automatically choose the multiprocessor ACPI HAL or the normal uniprocessor ACPI HAL based on what type of computer it's being installed on? Where in the setup process can I insert the script? Although I have used RIS in the past, I am new to WDS, and I'd like to not have to have two different images on the WDS server if possible.

  3. I am trying to do an unattended install of SpywareBlaster 3.4. I have used InnoUnp to unpack and repack the InnoSetup, so now it is installing. However, when I first run the program, I still have to enable protection. Is there any way to do this automatically (e.g. with a reg file)?

  4. I'm having trouble getting the install of Windows 2000 SP4 Update Rollup 1 to work properly. I'm using RunOnceEx, and the rollup installs (shows up in Add/Remove Programs), but then when I run Windows Update, it prompts me to install it again. WTF mates? :thumbdown

    Here is my RunOnceEx line for the rollup install:

    REG ADD %KEY%\002 /V 7 /D "%systemdrive%\install\Updates\KB891861.exe /q /u /o /n /z" /f

  5. I just had a really wacky idea:

    1. At the T-12 stage, add RunOnceEx entries starting with 500 or some other high number of that sort.

    2. When RunOnceEx starts, it will start at the 500 entries.

    3. Add entries during RunOnceEx for 005 and onward.

    My theory is that the RunOnceEx processor thingee will not double back and start the list over, so when it reboots, it will have the rest of the list in there. Am I right?

×
×
  • Create New...