Search options (Page 49 of 58)

You could, theoretically, but I wouldn't recommend it unless you are very sure.
At least, only do manual changes so you know exactly what you latered.
If you use nLite AFTER DP slipstream it will mess up files such as WINNT.SIF and the like, causing the whole unattended installation procedure to break.

Just make it a habit to do the DP slipstreaming as a last step and you shouldn't encounter any issues.
Or is there any specific reason why you'd want to do any of the above after integrating the drivers?

I did, before I got around to using nLite which greatly speeds up the process.

If you need further info on that (you can also do the drivers manually but it's a real PITA), check out http://unattended.msfn.org/unattended.xp/
A really great guide and comes in three "difficulty" levels

Hm, personally, I don't see the big advantage in this.

Also, take note that I HATE when games (taking them as an example since they happen to have large patches most of the time) only offer incremental updates/patches.
I like to DL the ver. 1.0-current all-in-one update so I can delete the old one and won't have to apply several patches in case of reinstall to get to current state.

The driver updates aren't that big if you are on broadband (granted, it's quite a pain on modem but I don't think you'd be bothering with the whole UWXPCD then (creating one on your machine, that is, obviuously you'd even more like to USE it as it means you have to DL less on the once installed OS).

Having only the latest FULL version up on the server (or at least lined to), is my understanding of KISS.
You download the package and you can be sure it's up-to-date.
Nothing worse than having a DL page with several versions that all need to be applied in a certain order (IL2, can you hear me?!).

What I would like is either have the BASE auto-DL the newer packages once detected (much like it does with the BASE file itself) or at least provide you with a clickable link to the file/the DL website.
That would be most welcome because as of now it only informs me of a new version - the same can be achieved by visiting this Forum, something I do more often than opening BASE

Using incremental updates, you'd have to integrate them into the larger DriverPacks somehow, unless you want to split those up (say one pack for each device).
That, however, would be most unpractical, as that would mean hundreds, if not thousands of packs - hard to keep track of IMO.
Integrating them into the larger packs means you have to uncompress that pack, replace/update the respective files and repack it.
That takes quite some time, as you'd have to use 7-Zip high compression methods to achieve small filesize, and the requires CPU power and not to forget lots of RAM.

For me, it takes less time to DL a full new pack than uncompressing and recompressing would.
This is only a solution for a fast, powerful PC with a slow internet connection.

So, unless you want to save Bâshrat the Sneaky some bandwidth I fail to see the real advantage of an incremental update approach.

Yes, just DL the files and put them into the appropriate folder.
No need to extract anything, in fact you don't even need a program compatible with 7-ZIP files.

Just remember to put the official DriverPacks into \DriverPacks and any 3rd Party DriverPacks into \3rd party DriverPacks directory.

Yeah, that should be the preferred method (for any program actually) IMO.

Just the drivers, of course.
Everything else qould be pointless since everyone's UWXPCD installation would look different (nLite'ed, add-on packs, add. software)

Still, seeing as you'll have a hard time finding a prebuilt consumer model with less than 100GB as of now, those 1.7% space for drivers are easy to bear IMO.
Should customers complain, try selling them another drive or tell them not to DL so much pr0n ;P

Yeah, that version is already in the works, or so I think
Quite a welcome change, I can tell you!
(so far, applying KTD takes about as much time as installing XP+addons...)

Wonder where the next beta version is, it's been a while I tested one

Not sure what you mean by KTD default (the defualt setting is disabled, I think), but if the required drivers are onyour HDD through KTD Windows will include that folder as a source on its search for drivers so it should NOT ask for a XPCD.
(can't say for sure, as I haven't replaced any hardware so far but that's what I gathered ).

Crazy stuff as in drivers?
It doesn't take that much space to keep them (about 1.7GB for me including all official and 3rd party DriverPacks) so unless that's an older machine with a small HDD it shouldn't be a problem.
Saves you the trouble of having to reach for the driver disc or searching for the driver on the net next time you upgrade.
Though, obviously, it doesn't help with often updated driver such as for graphics cards...

Hm, I  know this sounds abstract but how I would do it:

Since I have a DVD-RAM drive, that can be accessed just like a floppy in XP, so I'd use that.
Alternatively, you could use an external HDD or a large enough USB stick.

Before you install, make sure it's plugged into your system.
In the BASE settings, use a custom path for KTD ALL and set it to the appropriate device.
You could also use a second partition/drive and exchange drive letters with your DVD drive (if you want to copy the drivers on a CD/DVD).

There's probably an easier way and this does not leave you with CAB but rather uncompressed files, but this is as far as I can help you

It's there to refresh to check whether new DriverPacks have been released in the meantime.

I guess you'd have to have BASE running for some time to ever have this occuring.

Then again, Bâshrat the Sneaky can be pretty fast releasing a new pack so it might have its use

Since it was cutom-made by your fried, we can only guess what he did exactly.

Best way would be to ask him about it I figure

In any case, this CANNOT be achieved with a vanilla nLite AFAIK, so have a look for another program (did you inspect your friend's DVD already for any clues as to what app he used?).

Yes, that's what I meant.
However, if you are doing other things to your source (you mentioned somehotfixes), this always has to be done BEFORE applying th DriverPacks.
So using the BASE is the last step before making the ISO.

Sure, but you need to include the bootimage somehow, else the CD won't be bootable.

Slipstream is what you call the integration of the SP1/2, the hotfixes or even the DriverPacks to your source CD.

Absolutely correct.

Check.

That's the whole point.
If there were any manual steps involved it wouldn't be a proper UWXPCD (Unattended WinXP CD).

Just as a sidenote:
KTD ALL will enable Windows to search in the DP drivers when you install new hardware after you've already installed Windows (eg new sound card).
Very handy if you change a lot of hardware, else you won't need it.
However, then, XP will only search in the MS supplied driver for the new hardware ignoring those that came with the DriverPacks.

The only downside is that it will take up a bit of HDD space.
Obviously it has to store those new drivers somewhere

Personally, I use nLite, because I need that anyway to slim my CD down.
Then I'm using nLite to integrate the German version of RyanVM (Sereby's Update Packs), hotfixes and addons.
You can do that with the Update Pack standalone, but since I have nLite running anyway, why not do it that way?
There's no difference in the ending result.

As I said, above, both methods are basically identical.
Use whatever you prefer.
If you use nLite anyway, just integrate the packs through that, saves you one step.

In fact, as I stated previously, you NEED to integrate all updates and hotfixes BEFORE applying the DriverPacks.
So yes, it is compatible, in fact, it's the only way to do it, if you try it the other way round you will screw things up.

All you basically need is to use the BASE to slipstream the DriverPacks into your source.

There is no decumentation pre se, yet, however, all options are pretty self-explanatory.

Judging by your comments, the best thing for you to do is using Method 2 and KTD ALL.
QSC is only needed when creating more than one CD - to speed up things.
Finishing method is arbitrary as long asyou don't chose custom.

Just give it a try on a Virtual Machine (VMware) or Virtual PC (MSFT).

Also, make sure integrating the drivers is the very last step before making the ISO (which cannot be done with the DriverPacks BASE, yet).