O.K. - nearly there, however the 'HowTo' in this link (courtesy of Theo):

http://maximumpc.com/2005/01/how_to_slipstre.html

in Step 3. Says:

Open the folder to which you copied your Windows XP CD (C:\xpsetupcd) and
create a subfolder called $OEM$. Then, create a subfolder of $OEM$ called $1
and a subfolder of $1 called drivers. The resulting path should be
C:\xpsetupcd\$OEM$\$1\drivers.

Later, in step 5, this is referenced as:

You'll need to customize the OemPnPDriversPath line by entering the path to
the INF file for your RAID/SATA driver (for instance if your drivers are in
C:\xpsetupcd\i386\$OEM$\$1\drivers\RAID use:
OemPnPDriversPath=drivers\RAID\FastTrack\WinXP).

I tend to think the second version should be correct - any comments?



Also, the text only deals with the driver consisting of only 'one' SYS
file - mine has two, and as I recall, both where listed as (Required) when I
installed the last time. The text also only deals with one instance of the
CPI/VEN_ description, while making a note about inserting all instances
(which I did). There are five - does this mean that I should insert those
five ID's twice, each for the two SYS files?

I hope someone has this in fresh memory - but for these minor
inconsistencies, I am ready to burn!



Tony. . .

Re: Issues emerging while slipstreaming. . . by Theo

Theo
Sat Feb 10 06:49:11 CST 2007

I really can't give you a good answer since I haven't played
with Maximum's procedure recently. I did build a couple CDs
that worked, but my current motherboard has the SATA IDE
option in the BIOS (SATA or RAID) and I don't need to use F6
anymore.

Another possibility is nLite at:
http://www.nliteos.com/nlite.html It lists 'Driver
integration' as one of their features and it's menu driven.
Actually, with nLite you can do both the SP4 integration
and driver integration.

Tony Sperling wrote:
> O.K. - nearly there, however the 'HowTo' in this link (courtesy of Theo):
>
> http://maximumpc.com/2005/01/how_to_slipstre.html
>
> in Step 3. Says:
>
> Open the folder to which you copied your Windows XP CD (C:\xpsetupcd) and
> create a subfolder called $OEM$. Then, create a subfolder of $OEM$ called $1
> and a subfolder of $1 called drivers. The resulting path should be
> C:\xpsetupcd\$OEM$\$1\drivers.
>
> Later, in step 5, this is referenced as:
>
> You'll need to customize the OemPnPDriversPath line by entering the path to
> the INF file for your RAID/SATA driver (for instance if your drivers are in
> C:\xpsetupcd\i386\$OEM$\$1\drivers\RAID use:
> OemPnPDriversPath=drivers\RAID\FastTrack\WinXP).
>
> I tend to think the second version should be correct - any comments?
>
>
>
> Also, the text only deals with the driver consisting of only 'one' SYS
> file - mine has two, and as I recall, both where listed as (Required) when I
> installed the last time. The text also only deals with one instance of the
> CPI/VEN_ description, while making a note about inserting all instances
> (which I did). There are five - does this mean that I should insert those
> five ID's twice, each for the two SYS files?
>
> I hope someone has this in fresh memory - but for these minor
> inconsistencies, I am ready to burn!
>
>
>
> Tony. . .
>
>
>
>
>
>

Re: Issues emerging while slipstreaming. . . by Tony

Tony
Sat Feb 10 07:58:28 CST 2007

I might do that, I tried 'nLite' once and it had many tricks - it finishes
by producing your ISO for you, and you can configure it to use tweakui
settings and lots of useful stuff. I thought at the time it had weak
documentation and a somewhat confusing interface much along the line of what
I'm confronted with at the moment - 'questions', and then I didn't even had
the RAID to consider. But you are right - I should probably do that!


Tony. . .


"Theo" <theo@discussions.microsoft.com> wrote in message
news:OzlKmHRTHHA.5060@TK2MSFTNGP06.phx.gbl...
> I really can't give you a good answer since I haven't played
> with Maximum's procedure recently. I did build a couple CDs
> that worked, but my current motherboard has the SATA IDE
> option in the BIOS (SATA or RAID) and I don't need to use F6
> anymore.
>
> Another possibility is nLite at:
> http://www.nliteos.com/nlite.html It lists 'Driver
> integration' as one of their features and it's menu driven.
> Actually, with nLite you can do both the SP4 integration
> and driver integration.
>
> Tony Sperling wrote:
> > O.K. - nearly there, however the 'HowTo' in this link (courtesy of
Theo):
> >
> > http://maximumpc.com/2005/01/how_to_slipstre.html
> >
> > in Step 3. Says:
> >
> > Open the folder to which you copied your Windows XP CD (C:\xpsetupcd)
and
> > create a subfolder called $OEM$. Then, create a subfolder of $OEM$
called $1
> > and a subfolder of $1 called drivers. The resulting path should be
> > C:\xpsetupcd\$OEM$\$1\drivers.
> >
> > Later, in step 5, this is referenced as:
> >
> > You'll need to customize the OemPnPDriversPath line by entering the path
to
> > the INF file for your RAID/SATA driver (for instance if your drivers are
in
> > C:\xpsetupcd\i386\$OEM$\$1\drivers\RAID use:
> > OemPnPDriversPath=drivers\RAID\FastTrack\WinXP).
> >
> > I tend to think the second version should be correct - any comments?
> >
> >
> >
> > Also, the text only deals with the driver consisting of only 'one' SYS
> > file - mine has two, and as I recall, both where listed as (Required)
when I
> > installed the last time. The text also only deals with one instance of
the
> > CPI/VEN_ description, while making a note about inserting all instances
> > (which I did). There are five - does this mean that I should insert
those
> > five ID's twice, each for the two SYS files?
> >
> > I hope someone has this in fresh memory - but for these minor
> > inconsistencies, I am ready to burn!
> >
> >
> >
> > Tony. . .
> >
> >
> >
> >
> >
> >



RE: Issues emerging while slipstreaming. . . by Rich

Rich
Wed Feb 28 22:57:03 CST 2007

Tony,

I just got this working myself. I used an alternate set of instructions
from Maximums. The correct OEM path is divers\RAID assuming that this is the
folder where the drivers are located. Also, be sure to use the makecab
utility to compress the .sys files before you put them in the I386 folder.
BTW, I also put them in the AMD64 folder. I don't know your configuration so
I can not advise on the TXTSETUP.SIF file. I have a Foxconn Motherboard with
an AMD 4600 cpu

Hope this helps some.

Rich

"Tony Sperling" wrote:

> O.K. - nearly there, however the 'HowTo' in this link (courtesy of Theo):
>
> http://maximumpc.com/2005/01/how_to_slipstre.html
>
> in Step 3. Says:
>
> Open the folder to which you copied your Windows XP CD (C:\xpsetupcd) and
> create a subfolder called $OEM$. Then, create a subfolder of $OEM$ called $1
> and a subfolder of $1 called drivers. The resulting path should be
> C:\xpsetupcd\$OEM$\$1\drivers.
>
> Later, in step 5, this is referenced as:
>
> You'll need to customize the OemPnPDriversPath line by entering the path to
> the INF file for your RAID/SATA driver (for instance if your drivers are in
> C:\xpsetupcd\i386\$OEM$\$1\drivers\RAID use:
> OemPnPDriversPath=drivers\RAID\FastTrack\WinXP).
>
> I tend to think the second version should be correct - any comments?
>
>
>
> Also, the text only deals with the driver consisting of only 'one' SYS
> file - mine has two, and as I recall, both where listed as (Required) when I
> installed the last time. The text also only deals with one instance of the
> CPI/VEN_ description, while making a note about inserting all instances
> (which I did). There are five - does this mean that I should insert those
> five ID's twice, each for the two SYS files?
>
> I hope someone has this in fresh memory - but for these minor
> inconsistencies, I am ready to burn!
>
>
>
> Tony. . .
>
>
>
>
>
>
>