1 Reply by djzn

(4 replies, posted in Feedback and Support - DriverPacks Base)

Thank you.
Nice job of yours doing the DVP.
Keep the GOOD work.

I chose M1 for the CD install because I assumed if M2 was used, some of the drivers couldn't be seen in some "rare" cases...(as I read) and SATA support is vital nowadays to run a XP installation, so M1 gives the option of all possible drivers available to be loaded. (right?)

Go to forum: Feedback and Support - DriverPacks Base

2 Reply by djzn

(4 replies, posted in Feedback and Support - DriverPacks Base)

ANSWERING THE QUESTION MYSELF:
Just in case you might also wonder, if you do the Slipstream like I did, there will be a line in log file:

2009-11-03 11:20:27 : <SLIP> Created OemPnpDriversPath entry. The length is 2395, which does not exceed the 4096 characters limit.

That answers that I achieved what I wanted.

Go to forum: Feedback and Support - DriverPacks Base

3 Topic by djzn

(4 replies, posted in Feedback and Support - DriverPacks Base)

Hi folks,

I am doing a XP Slipstreamed CD, however, I want to integrate ONLY Mass Storage Driverpacks with Text-Mode included - so that I can say bye bye to floppy in Windows installs. I have learnet that M1 will make drivers available very early for Windows setup, but there is a 4096 limit path with M1 method.

The question is, by selecting only Mass Storage + Text Mode Mass Storage, will that limit exceed - or is it by far no where near it? If it is by far no where near it, could I integrate also LAN drivers, CPU drivers and Chipset drivers and still not come across that 4096 limit path, using M1 method?

Please advise on the situation.

This is going to be a CD.

I will also make a DVD with all driverpacks but with M2 method.

You never know what machine you will come across, right?

Thanks for any answer!

Go to forum: Feedback and Support - DriverPacks Base