1 Reply by gordon

(7 replies, posted in DriverPack Mass Storage)

Here are my results since my last post.
Start with SP3 already integrated

Successful unattended installer:
nlite integrates hotfixes, removes components, and sets unattended options
slipstream DriverPacks
make iso

UNSUCCESSFUL repair option installer:
nlite integrates hotfixes, removes components, and sets unattended options, prompt repair
slipstream DriverPacks
make iso
The problem is there is no repair option, DriverPacks prevents it apparently.

SUCCESSFUL repair option installer:
nlite integrates hotfixes and removes components
slipstream DriverPacks
nlite sets unattended options, prompt repair
make iso

Thanks for all the input. I'll check out the tutorial.

I make the repair installer to use as a last resort before a clean install. Sometimes it works.
I remove components so the installer will fit on a cd. Perhaps I'll graduate to dvd next time.
(I still might remove IIS.)
Removing components seems to cause sfc /scannow to discover many files are missing.

DriverPacks and nLite are both great software and they have helped me maintaining 160 XP systems since 2005, I think.

Jerry

Go to forum: DriverPack Mass Storage

2 Reply by gordon

(7 replies, posted in DriverPack Mass Storage)

Maybe I didn't get it. You said don't remove drivers with nLite. Does that mean don't remove ANY drivers with nLite?

I still would like the two clarifications I requested in my last post. Namely does DriverPacks need to be the very last thing before creating the iso or can non-driver components be removed and unattended configuration be set.

Thanks for your patience.
Jerry

Go to forum: DriverPack Mass Storage

3 Reply by gordon

(7 replies, posted in DriverPack Mass Storage)

Overflow,
OK, I get the idea. I shouldn't remove drivers after DriverPacks. Can I remove other types of components after DriverPacks such as IIS? Can I set the unattended configuration after DriverPacks?
Thanks very much for your prompt reply.
Jerry Gordon

Go to forum: DriverPack Mass Storage

4 Topic by gordon

(7 replies, posted in DriverPack Mass Storage)

Hello,
        I have been getting error msgs from nLite saying these three files are corrupt: symc810.sys, symc8xx.sys, and viaide.sys. If I proceed my XP install dies with viaide.sys corrupt. Am I doing something wrong? Here is what I am doing:
1)use nLite to slipstream XP SP3 to a disk copy of my install cd (sp2)
2)use nLite to integrate hotfixes since sp3 (from Windows Updates Downloader)
3)use the latest driverpacks base to slipstream the latest driver packs
    DriverPacks: Chipset, CPU, Graphics A+B, LAN, Storage, Sound A, WLAN
    Mass Storage in text mode (so will see sata at boot)
    Slipstream Method 2 (allows more drivers though I don't know the limit on 1)
    Finisher Method: GUIRunOnce
    Disable KTD (default)
    Enable QSC (default) (this default has changed since last I did this)
    DriverPack Graphics A, DISABLE BOTH: ATI Control Panel (Control Center needs .NET)
4)use nLite to remove many components including these drivers:
        drivers: ATM 150 KB
        drivers: ISDN 5.77 MB
        drivers: Scanners 7.22 MB
4)use nLite to configure unattended install and create iso
        This is the step that produces the corrupt file errors

        Can you tell what is happening to produce the errors and how I might avoid the errors?
        Thanks very much,
Jerry Gordon

Go to forum: DriverPack Mass Storage