Hi,

I've been having a real hard time getting this to work. I've been able to
create an administrative installation point and slipstream SP4 with Win2k.
When I go to install Windows using my admin install share it works perfectly
and SP4 is installed. However, if I've integrated any additional
hotfixes/updates in to the admin install point and run the install over the
network (using a TCP/IP boot disk)it fails to copy some files (it says its
unable to copy the file and gives me the option of skipping them). This is
happening with updates that use the update.exe version 5.4.15.0 or later
(which includes the option to integrate the update in to an admin install
point). When I run the update using the "/integrate:<admin install point>"
switch it claims to integrate successfully but when I try an over-the-network
install it errors out again while copying files. I've only been able to test
this by running the install over-the-network with a network boot disk so I'm
not sure if that has anything to do with it. Is there a reason why I'm
unable to install Windows after applying these updates and how do I resolve
it?

Also...

Since I was unsuccessfull in installing the "integratable" updates I decided
to try manually slipstreaming the "unintegratable" updates (i.e., the updates
that do not come with update.exe 5.4.15.0 or later.) to see if I could at
least get those to install. Unfortunately, I've not been able to get this to
work either. I've tried followed the instructions provided by article ID
828930 on how to include these updates in a Windows install I'm not able to
follow all the instructions. Basically, it states that every update should
have a catalog file (not the empty.cat file) that needs to be referenced in
the dosnet.inf file in order for the update to work. However, for most of
the updates there are no .cat files included except the empty.cat file which
it states to disregard. I skipped this step as it didn't apply and followed
the rest to a tee but after Windows installs seamlessly and I run Windows
Update the updates still show as needing to be installed. So how in the
world do I integrate updates and hotfixes that don't come with update.exe
version 5.4.15.0? The instructions Microsoft provides are not making sense.

If anyone can help me out with this issue I would be very appreciative. I
just need to know if anyone has successfully been able to create a bootable,
slipstreamed win2k CD with all critical updates and service packs
preinstalled. If someone has been able to successfully do this please let me
know the steps you took! Thank you very much!

"mike" wrote:

> Hi,
>
> I've been having a real hard time getting this to work. I've been able to
> create an administrative installation point and slipstream SP4 with Win2k.
> When I go to install Windows using my admin install share it works perfectly
> and SP4 is installed. However, if I've integrated any additional
> hotfixes/updates in to the admin install point and run the install over the
> network (using a TCP/IP boot disk)it fails to copy some files (it says its
> unable to copy the file and gives me the option of skipping them). This is
> happening with updates that use the update.exe version 5.4.15.0 or later
> (which includes the option to integrate the update in to an admin install
> point). When I run the update using the "/integrate:<admin install point>"
> switch it claims to integrate successfully but when I try an over-the-network
> install it errors out again while copying files. I've only been able to test
> this by running the install over-the-network with a network boot disk so I'm
> not sure if that has anything to do with it. Is there a reason why I'm
> unable to install Windows after applying these updates and how do I resolve
> it?
>
> Also...
>
> Since I was unsuccessfull in installing the "integratable" updates I decided
> to try manually slipstreaming the "unintegratable" updates (i.e., the updates
> that do not come with update.exe 5.4.15.0 or later.) to see if I could at
> least get those to install. Unfortunately, I've not been able to get this to
> work either. I've tried followed the instructions provided by article ID
> 828930 on how to include these updates in a Windows install I'm not able to
> follow all the instructions. Basically, it states that every update should
> have a catalog file (not the empty.cat file) that needs to be referenced in
> the dosnet.inf file in order for the update to work. However, for most of
> the updates there are no .cat files included except the empty.cat file which
> it states to disregard. I skipped this step as it didn't apply and followed
> the rest to a tee but after Windows installs seamlessly and I run Windows
> Update the updates still show as needing to be installed. So how in the
> world do I integrate updates and hotfixes that don't come with update.exe
> version 5.4.15.0? The instructions Microsoft provides are not making sense.

neo [mvp outlook] provided this link not too long ago and says he likes it:

Making a Bootable Windows 2000 CD with Service Pack Integrated
http://old.bink.nu/bootcd/

and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
http://www.neowin.net/forum/index.ph...&#entry2453585

Search the newsgroup and you will find others...

John

mike wrote:
> If anyone can help me out with this issue I would be very appreciative. I
> just need to know if anyone has successfully been able to create a bootable,
> slipstreamed win2k CD with all critical updates and service packs
> preinstalled. If someone has been able to successfully do this please let me
> know the steps you took! Thank you very much!
>
> "mike" wrote:
>
>
>>Hi,
>>
>>I've been having a real hard time getting this to work. I've been able to
>>create an administrative installation point and slipstream SP4 with Win2k.
>>When I go to install Windows using my admin install share it works perfectly
>>and SP4 is installed. However, if I've integrated any additional
>>hotfixes/updates in to the admin install point and run the install over the
>>network (using a TCP/IP boot disk)it fails to copy some files (it says its
>>unable to copy the file and gives me the option of skipping them). This is
>>happening with updates that use the update.exe version 5.4.15.0 or later
>>(which includes the option to integrate the update in to an admin install
>>point). When I run the update using the "/integrate:<admin install point>"
>>switch it claims to integrate successfully but when I try an over-the-network
>>install it errors out again while copying files. I've only been able to test
>>this by running the install over-the-network with a network boot disk so I'm
>>not sure if that has anything to do with it. Is there a reason why I'm
>>unable to install Windows after applying these updates and how do I resolve
>>it?
>>
>>Also...
>>
>>Since I was unsuccessfull in installing the "integratable" updates I decided
>>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
>>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
>>least get those to install. Unfortunately, I've not been able to get this to
>>work either. I've tried followed the instructions provided by article ID
>>828930 on how to include these updates in a Windows install I'm not able to
>>follow all the instructions. Basically, it states that every update should
>>have a catalog file (not the empty.cat file) that needs to be referenced in
>>the dosnet.inf file in order for the update to work. However, for most of
>>the updates there are no .cat files included except the empty.cat file which
>>it states to disregard. I skipped this step as it didn't apply and followed
>>the rest to a tee but after Windows installs seamlessly and I run Windows
>>Update the updates still show as needing to be installed. So how in the
>>world do I integrate updates and hotfixes that don't come with update.exe
>>version 5.4.15.0? The instructions Microsoft provides are not making sense.

Thanks, but this doesn't address my problem at hand. I'll worry about
creating a bootable CD after I've been able to verify that Windows 2000
installs with SP4 and all hotfixes in place.

Again, I've followed the instructions provided by Article number 828930 and
the instructions are incomplete. There are no .cat files for most of the
hotfixes which the instructions insist on copying to the i386\svcpack folder.
I'm sure this is of significance and probably explains why its not working
but I don't know of a workaround -- how do I integrate these updates if there
are no .cat files????

Also, regarding the updates that use update.exe version 5.4.15.0 or later:
After integrating these updates to the install share for win2k and attempting
to run an over-the-network install it errors out while copying files (in the
blue, text-based part of setup). It does this only after I've integrated
these updates because it will copy all files fine after integrating SP4. Why
is this? Is it related to installing over the network?? I do not have a CD
burner at present as mine is broken. Would I need to run the install off a
CD in order for all files to be copied? Please help!!!!!!!!!!!!!!!

"John John" wrote:

> neo [mvp outlook] provided this link not too long ago and says he likes it:
>
> Making a Bootable Windows 2000 CD with Service Pack Integrated
> http://old.bink.nu/bootcd/
>
> and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
> http://www.neowin.net/forum/index.ph...&#entry2453585
>
> Search the newsgroup and you will find others...
>
> John
>
> mike wrote:
> > If anyone can help me out with this issue I would be very appreciative. I
> > just need to know if anyone has successfully been able to create a bootable,
> > slipstreamed win2k CD with all critical updates and service packs
> > preinstalled. If someone has been able to successfully do this please let me
> > know the steps you took! Thank you very much!
> >
> > "mike" wrote:
> >
> >
> >>Hi,
> >>
> >>I've been having a real hard time getting this to work. I've been able to
> >>create an administrative installation point and slipstream SP4 with Win2k.
> >>When I go to install Windows using my admin install share it works perfectly
> >>and SP4 is installed. However, if I've integrated any additional
> >>hotfixes/updates in to the admin install point and run the install over the
> >>network (using a TCP/IP boot disk)it fails to copy some files (it says its
> >>unable to copy the file and gives me the option of skipping them). This is
> >>happening with updates that use the update.exe version 5.4.15.0 or later
> >>(which includes the option to integrate the update in to an admin install
> >>point). When I run the update using the "/integrate:<admin install point>"
> >>switch it claims to integrate successfully but when I try an over-the-network
> >>install it errors out again while copying files. I've only been able to test
> >>this by running the install over-the-network with a network boot disk so I'm
> >>not sure if that has anything to do with it. Is there a reason why I'm
> >>unable to install Windows after applying these updates and how do I resolve
> >>it?
> >>
> >>Also...
> >>
> >>Since I was unsuccessfull in installing the "integratable" updates I decided
> >>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
> >>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
> >>least get those to install. Unfortunately, I've not been able to get this to
> >>work either. I've tried followed the instructions provided by article ID
> >>828930 on how to include these updates in a Windows install I'm not able to
> >>follow all the instructions. Basically, it states that every update should
> >>have a catalog file (not the empty.cat file) that needs to be referenced in
> >>the dosnet.inf file in order for the update to work. However, for most of
> >>the updates there are no .cat files included except the empty.cat file which
> >>it states to disregard. I skipped this step as it didn't apply and followed
> >>the rest to a tee but after Windows installs seamlessly and I run Windows
> >>Update the updates still show as needing to be installed. So how in the
> >>world do I integrate updates and hotfixes that don't come with update.exe
> >>version 5.4.15.0? The instructions Microsoft provides are not making sense.
>
>

One comment regarding the Autostreamer program mentioned in the second link:
is this program for use only with service packs or will it work with
updates/hotfixes as well?

"John John" wrote:

> neo [mvp outlook] provided this link not too long ago and says he likes it:
>
> Making a Bootable Windows 2000 CD with Service Pack Integrated
> http://old.bink.nu/bootcd/
>
> and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
> http://www.neowin.net/forum/index.ph...&#entry2453585
>
> Search the newsgroup and you will find others...
>
> John
>
> mike wrote:
> > If anyone can help me out with this issue I would be very appreciative. I
> > just need to know if anyone has successfully been able to create a bootable,
> > slipstreamed win2k CD with all critical updates and service packs
> > preinstalled. If someone has been able to successfully do this please let me
> > know the steps you took! Thank you very much!
> >
> > "mike" wrote:
> >
> >
> >>Hi,
> >>
> >>I've been having a real hard time getting this to work. I've been able to
> >>create an administrative installation point and slipstream SP4 with Win2k.
> >>When I go to install Windows using my admin install share it works perfectly
> >>and SP4 is installed. However, if I've integrated any additional
> >>hotfixes/updates in to the admin install point and run the install over the
> >>network (using a TCP/IP boot disk)it fails to copy some files (it says its
> >>unable to copy the file and gives me the option of skipping them). This is
> >>happening with updates that use the update.exe version 5.4.15.0 or later
> >>(which includes the option to integrate the update in to an admin install
> >>point). When I run the update using the "/integrate:<admin install point>"
> >>switch it claims to integrate successfully but when I try an over-the-network
> >>install it errors out again while copying files. I've only been able to test
> >>this by running the install over-the-network with a network boot disk so I'm
> >>not sure if that has anything to do with it. Is there a reason why I'm
> >>unable to install Windows after applying these updates and how do I resolve
> >>it?
> >>
> >>Also...
> >>
> >>Since I was unsuccessfull in installing the "integratable" updates I decided
> >>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
> >>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
> >>least get those to install. Unfortunately, I've not been able to get this to
> >>work either. I've tried followed the instructions provided by article ID
> >>828930 on how to include these updates in a Windows install I'm not able to
> >>follow all the instructions. Basically, it states that every update should
> >>have a catalog file (not the empty.cat file) that needs to be referenced in
> >>the dosnet.inf file in order for the update to work. However, for most of
> >>the updates there are no .cat files included except the empty.cat file which
> >>it states to disregard. I skipped this step as it didn't apply and followed
> >>the rest to a tee but after Windows installs seamlessly and I run Windows
> >>Update the updates still show as needing to be installed. So how in the
> >>world do I integrate updates and hotfixes that don't come with update.exe
> >>version 5.4.15.0? The instructions Microsoft provides are not making sense.
>
>

I think these .cat files are in the Qnnnnnn.exe, you have to expand them.

How to Slipstream Hotfixes That Replace Pre-Existing Driver Files
http://support.microsoft.com/default...b;en-us;814847

John

mike wrote:


mike wrote:

> Thanks, but this doesn't address my problem at hand. I'll worry about
> creating a bootable CD after I've been able to verify that Windows 2000
> installs with SP4 and all hotfixes in place.
>
> Again, I've followed the instructions provided by Article number 828930 and
> the instructions are incomplete. There are no .cat files for most of the
> hotfixes which the instructions insist on copying to the i386\svcpack folder.
> I'm sure this is of significance and probably explains why its not working
> but I don't know of a workaround -- how do I integrate these updates if there
> are no .cat files????
>
> Also, regarding the updates that use update.exe version 5.4.15.0 or later:
> After integrating these updates to the install share for win2k and attempting
> to run an over-the-network install it errors out while copying files (in the
> blue, text-based part of setup). It does this only after I've integrated
> these updates because it will copy all files fine after integrating SP4. Why
> is this? Is it related to installing over the network?? I do not have a CD
> burner at present as mine is broken. Would I need to run the install off a
> CD in order for all files to be copied? Please help!!!!!!!!!!!!!!!
>
> "John John" wrote:
>
>
>>neo [mvp outlook] provided this link not too long ago and says he likes it:
>>
>>Making a Bootable Windows 2000 CD with Service Pack Integrated
>>http://old.bink.nu/bootcd/
>>
>>and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
>>http://www.neowin.net/forum/index.ph...&#entry2453585
>>
>>Search the newsgroup and you will find others...
>>
>>John
>>
>>mike wrote:
>>
>>>If anyone can help me out with this issue I would be very appreciative. I
>>>just need to know if anyone has successfully been able to create a bootable,
>>>slipstreamed win2k CD with all critical updates and service packs
>>>preinstalled. If someone has been able to successfully do this please let me
>>>know the steps you took! Thank you very much!
>>>
>>>"mike" wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>I've been having a real hard time getting this to work. I've been able to
>>>>create an administrative installation point and slipstream SP4 with Win2k.
>>>>When I go to install Windows using my admin install share it works perfectly
>>>>and SP4 is installed. However, if I've integrated any additional
>>>>hotfixes/updates in to the admin install point and run the install over the
>>>>network (using a TCP/IP boot disk)it fails to copy some files (it says its
>>>>unable to copy the file and gives me the option of skipping them). This is
>>>>happening with updates that use the update.exe version 5.4.15.0 or later
>>>>(which includes the option to integrate the update in to an admin install
>>>>point). When I run the update using the "/integrate:<admin install point>"
>>>>switch it claims to integrate successfully but when I try an over-the-network
>>>>install it errors out again while copying files. I've only been able to test
>>>>this by running the install over-the-network with a network boot disk so I'm
>>>>not sure if that has anything to do with it. Is there a reason why I'm
>>>>unable to install Windows after applying these updates and how do I resolve
>>>>it?
>>>>
>>>>Also...
>>>>
>>>>Since I was unsuccessfull in installing the "integratable" updates I decided
>>>>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
>>>>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
>>>>least get those to install. Unfortunately, I've not been able to get this to
>>>>work either. I've tried followed the instructions provided by article ID
>>>>828930 on how to include these updates in a Windows install I'm not able to
>>>>follow all the instructions. Basically, it states that every update should
>>>>have a catalog file (not the empty.cat file) that needs to be referenced in
>>>>the dosnet.inf file in order for the update to work. However, for most of
>>>>the updates there are no .cat files included except the empty.cat file which
>>>>it states to disregard. I skipped this step as it didn't apply and followed
>>>>the rest to a tee but after Windows installs seamlessly and I run Windows
>>>>Update the updates still show as needing to be installed. So how in the
>>>>world do I integrate updates and hotfixes that don't come with update.exe
>>>>version 5.4.15.0? The instructions Microsoft provides are not making sense.
>>
>>
> Thanks, but this doesn't address my problem at hand. I'll worry about
> creating a bootable CD after I've been able to verify that Windows 2000
> installs with SP4 and all hotfixes in place.
>
> Again, I've followed the instructions provided by Article number 828930 and
> the instructions are incomplete. There are no .cat files for most of the
> hotfixes which the instructions insist on copying to the i386\svcpack folder.
> I'm sure this is of significance and probably explains why its not working
> but I don't know of a workaround -- how do I integrate these updates if there
> are no .cat files????
>
> Also, regarding the updates that use update.exe version 5.4.15.0 or later:
> After integrating these updates to the install share for win2k and attempting
> to run an over-the-network install it errors out while copying files (in the
> blue, text-based part of setup). It does this only after I've integrated
> these updates because it will copy all files fine after integrating SP4. Why
> is this? Is it related to installing over the network?? I do not have a CD
> burner at present as mine is broken. Would I need to run the install off a
> CD in order for all files to be copied? Please help!!!!!!!!!!!!!!!
>
> "John John" wrote:
>
>
>>neo [mvp outlook] provided this link not too long ago and says he likes it:
>>
>>Making a Bootable Windows 2000 CD with Service Pack Integrated
>>http://old.bink.nu/bootcd/
>>
>>and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
>>http://www.neowin.net/forum/index.ph...&#entry2453585
>>
>>Search the newsgroup and you will find others...
>>
>>John
>>
>>mike wrote:
>>
>>>If anyone can help me out with this issue I would be very appreciative. I
>>>just need to know if anyone has successfully been able to create a bootable,
>>>slipstreamed win2k CD with all critical updates and service packs
>>>preinstalled. If someone has been able to successfully do this please let me
>>>know the steps you took! Thank you very much!
>>>
>>>"mike" wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>I've been having a real hard time getting this to work. I've been able to
>>>>create an administrative installation point and slipstream SP4 with Win2k.
>>>>When I go to install Windows using my admin install share it works perfectly
>>>>and SP4 is installed. However, if I've integrated any additional
>>>>hotfixes/updates in to the admin install point and run the install over the
>>>>network (using a TCP/IP boot disk)it fails to copy some files (it says its
>>>>unable to copy the file and gives me the option of skipping them). This is
>>>>happening with updates that use the update.exe version 5.4.15.0 or later
>>>>(which includes the option to integrate the update in to an admin install
>>>>point). When I run the update using the "/integrate:<admin install point>"
>>>>switch it claims to integrate successfully but when I try an over-the-network
>>>>install it errors out again while copying files. I've only been able to test
>>>>this by running the install over-the-network with a network boot disk so I'm
>>>>not sure if that has anything to do with it. Is there a reason why I'm
>>>>unable to install Windows after applying these updates and how do I resolve
>>>>it?
>>>>
>>>>Also...
>>>>
>>>>Since I was unsuccessfull in installing the "integratable" updates I decided
>>>>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
>>>>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
>>>>least get those to install. Unfortunately, I've not been able to get this to
>>>>work either. I've tried followed the instructions provided by article ID
>>>>828930 on how to include these updates in a Windows install I'm not able to
>>>>follow all the instructions. Basically, it states that every update should
>>>>have a catalog file (not the empty.cat file) that needs to be referenced in
>>>>the dosnet.inf file in order for the update to work. However, for most of
>>>>the updates there are no .cat files included except the empty.cat file which
>>>>it states to disregard. I skipped this step as it didn't apply and followed
>>>>the rest to a tee but after Windows installs seamlessly and I run Windows
>>>>Update the updates still show as needing to be installed. So how in the
>>>>world do I integrate updates and hotfixes that don't come with update.exe
>>>>version 5.4.15.0? The instructions Microsoft provides are not making sense.
>>
>>

I don't know, I never used it, I just posted the link provided by Jim.
I know that there are hotfix managers out there but I don't know if they
do slipstreaming because I never tried them either.

John

mike wrote:

> One comment regarding the Autostreamer program mentioned in the second link:
> is this program for use only with service packs or will it work with
> updates/hotfixes as well?
>
> "John John" wrote:
>
>
>>neo [mvp outlook] provided this link not too long ago and says he likes it:
>>
>>Making a Bootable Windows 2000 CD with Service Pack Integrated
>>http://old.bink.nu/bootcd/
>>
>>and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
>>http://www.neowin.net/forum/index.ph...&#entry2453585
>>
>>Search the newsgroup and you will find others...
>>
>>John
>>
>>mike wrote:
>>
>>>If anyone can help me out with this issue I would be very appreciative. I
>>>just need to know if anyone has successfully been able to create a bootable,
>>>slipstreamed win2k CD with all critical updates and service packs
>>>preinstalled. If someone has been able to successfully do this please let me
>>>know the steps you took! Thank you very much!
>>>
>>>"mike" wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>I've been having a real hard time getting this to work. I've been able to
>>>>create an administrative installation point and slipstream SP4 with Win2k.
>>>>When I go to install Windows using my admin install share it works perfectly
>>>>and SP4 is installed. However, if I've integrated any additional
>>>>hotfixes/updates in to the admin install point and run the install over the
>>>>network (using a TCP/IP boot disk)it fails to copy some files (it says its
>>>>unable to copy the file and gives me the option of skipping them). This is
>>>>happening with updates that use the update.exe version 5.4.15.0 or later
>>>>(which includes the option to integrate the update in to an admin install
>>>>point). When I run the update using the "/integrate:<admin install point>"
>>>>switch it claims to integrate successfully but when I try an over-the-network
>>>>install it errors out again while copying files. I've only been able to test
>>>>this by running the install over-the-network with a network boot disk so I'm
>>>>not sure if that has anything to do with it. Is there a reason why I'm
>>>>unable to install Windows after applying these updates and how do I resolve
>>>>it?
>>>>
>>>>Also...
>>>>
>>>>Since I was unsuccessfull in installing the "integratable" updates I decided
>>>>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
>>>>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
>>>>least get those to install. Unfortunately, I've not been able to get this to
>>>>work either. I've tried followed the instructions provided by article ID
>>>>828930 on how to include these updates in a Windows install I'm not able to
>>>>follow all the instructions. Basically, it states that every update should
>>>>have a catalog file (not the empty.cat file) that needs to be referenced in
>>>>the dosnet.inf file in order for the update to work. However, for most of
>>>>the updates there are no .cat files included except the empty.cat file which
>>>>it states to disregard. I skipped this step as it didn't apply and followed
>>>>the rest to a tee but after Windows installs seamlessly and I run Windows
>>>>Update the updates still show as needing to be installed. So how in the
>>>>world do I integrate updates and hotfixes that don't come with update.exe
>>>>version 5.4.15.0? The instructions Microsoft provides are not making sense.
>>
>>

Okay, these updates aren't hotfixes I realize now... I shouldn't have called
them that accidentally. They're regular updates, with names like
"win2000-kbnnnnnn-en-enu.exe." These are not the hotfixes you're talking
about. There are no .cat files in these updates. The only .cat file is the
empty.cat file which the article specifically states to disregard.

Here's a link to the article I'm getting my instructions from:
http://support.microsoft.com/kb/828930

Does this shed any additional light on the subject?


"John John" wrote:

> I think these .cat files are in the Qnnnnnn.exe, you have to expand them.
>
> How to Slipstream Hotfixes That Replace Pre-Existing Driver Files
> http://support.microsoft.com/default...b;en-us;814847
>
> John
>
> mike wrote:
>
>
> mike wrote:
>
> > Thanks, but this doesn't address my problem at hand. I'll worry about
> > creating a bootable CD after I've been able to verify that Windows 2000
> > installs with SP4 and all hotfixes in place.
> >
> > Again, I've followed the instructions provided by Article number 828930 and
> > the instructions are incomplete. There are no .cat files for most of the
> > hotfixes which the instructions insist on copying to the i386\svcpack folder.
> > I'm sure this is of significance and probably explains why its not working
> > but I don't know of a workaround -- how do I integrate these updates if there
> > are no .cat files????
> >
> > Also, regarding the updates that use update.exe version 5.4.15.0 or later:
> > After integrating these updates to the install share for win2k and attempting
> > to run an over-the-network install it errors out while copying files (in the
> > blue, text-based part of setup). It does this only after I've integrated
> > these updates because it will copy all files fine after integrating SP4. Why
> > is this? Is it related to installing over the network?? I do not have a CD
> > burner at present as mine is broken. Would I need to run the install off a
> > CD in order for all files to be copied? Please help!!!!!!!!!!!!!!!
> >
> > "John John" wrote:
> >
> >
> >>neo [mvp outlook] provided this link not too long ago and says he likes it:
> >>
> >>Making a Bootable Windows 2000 CD with Service Pack Integrated
> >>http://old.bink.nu/bootcd/
> >>
> >>and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
> >>http://www.neowin.net/forum/index.ph...&#entry2453585
> >>
> >>Search the newsgroup and you will find others...
> >>
> >>John
> >>
> >>mike wrote:
> >>
> >>>If anyone can help me out with this issue I would be very appreciative. I
> >>>just need to know if anyone has successfully been able to create a bootable,
> >>>slipstreamed win2k CD with all critical updates and service packs
> >>>preinstalled. If someone has been able to successfully do this please let me
> >>>know the steps you took! Thank you very much!
> >>>
> >>>"mike" wrote:
> >>>
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>I've been having a real hard time getting this to work. I've been able to
> >>>>create an administrative installation point and slipstream SP4 with Win2k.
> >>>>When I go to install Windows using my admin install share it works perfectly
> >>>>and SP4 is installed. However, if I've integrated any additional
> >>>>hotfixes/updates in to the admin install point and run the install over the
> >>>>network (using a TCP/IP boot disk)it fails to copy some files (it says its
> >>>>unable to copy the file and gives me the option of skipping them). This is
> >>>>happening with updates that use the update.exe version 5.4.15.0 or later
> >>>>(which includes the option to integrate the update in to an admin install
> >>>>point). When I run the update using the "/integrate:<admin install point>"
> >>>>switch it claims to integrate successfully but when I try an over-the-network
> >>>>install it errors out again while copying files. I've only been able to test
> >>>>this by running the install over-the-network with a network boot disk so I'm
> >>>>not sure if that has anything to do with it. Is there a reason why I'm
> >>>>unable to install Windows after applying these updates and how do I resolve
> >>>>it?
> >>>>
> >>>>Also...
> >>>>
> >>>>Since I was unsuccessfull in installing the "integratable" updates I decided
> >>>>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
> >>>>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
> >>>>least get those to install. Unfortunately, I've not been able to get this to
> >>>>work either. I've tried followed the instructions provided by article ID
> >>>>828930 on how to include these updates in a Windows install I'm not able to
> >>>>follow all the instructions. Basically, it states that every update should
> >>>>have a catalog file (not the empty.cat file) that needs to be referenced in
> >>>>the dosnet.inf file in order for the update to work. However, for most of
> >>>>the updates there are no .cat files included except the empty.cat file which
> >>>>it states to disregard. I skipped this step as it didn't apply and followed
> >>>>the rest to a tee but after Windows installs seamlessly and I run Windows
> >>>>Update the updates still show as needing to be installed. So how in the
> >>>>world do I integrate updates and hotfixes that don't come with update.exe
> >>>>version 5.4.15.0? The instructions Microsoft provides are not making sense.
> >>
> >>
> > Thanks, but this doesn't address my problem at hand. I'll worry about
> > creating a bootable CD after I've been able to verify that Windows 2000
> > installs with SP4 and all hotfixes in place.
> >
> > Again, I've followed the instructions provided by Article number 828930 and
> > the instructions are incomplete. There are no .cat files for most of the
> > hotfixes which the instructions insist on copying to the i386\svcpack folder.
> > I'm sure this is of significance and probably explains why its not working
> > but I don't know of a workaround -- how do I integrate these updates if there
> > are no .cat files????
> >
> > Also, regarding the updates that use update.exe version 5.4.15.0 or later:
> > After integrating these updates to the install share for win2k and attempting
> > to run an over-the-network install it errors out while copying files (in the
> > blue, text-based part of setup). It does this only after I've integrated
> > these updates because it will copy all files fine after integrating SP4. Why
> > is this? Is it related to installing over the network?? I do not have a CD
> > burner at present as mine is broken. Would I need to run the install off a
> > CD in order for all files to be copied? Please help!!!!!!!!!!!!!!!
> >
> > "John John" wrote:
> >
> >
> >>neo [mvp outlook] provided this link not too long ago and says he likes it:
> >>
> >>Making a Bootable Windows 2000 CD with Service Pack Integrated
> >>http://old.bink.nu/bootcd/
> >>
> >>and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
> >>http://www.neowin.net/forum/index.ph...&#entry2453585
> >>
> >>Search the newsgroup and you will find others...
> >>
> >>John
> >>
> >>mike wrote:
> >>
> >>>If anyone can help me out with this issue I would be very appreciative. I
> >>>just need to know if anyone has successfully been able to create a bootable,
> >>>slipstreamed win2k CD with all critical updates and service packs
> >>>preinstalled. If someone has been able to successfully do this please let me
> >>>know the steps you took! Thank you very much!
> >>>
> >>>"mike" wrote:
> >>>
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>I've been having a real hard time getting this to work. I've been able to
> >>>>create an administrative installation point and slipstream SP4 with Win2k.
> >>>>When I go to install Windows using my admin install share it works perfectly
> >>>>and SP4 is installed. However, if I've integrated any additional
> >>>>hotfixes/updates in to the admin install point and run the install over the
> >>>>network (using a TCP/IP boot disk)it fails to copy some files (it says its
> >>>>unable to copy the file and gives me the option of skipping them). This is
> >>>>happening with updates that use the update.exe version 5.4.15.0 or later
> >>>>(which includes the option to integrate the update in to an admin install
> >>>>point). When I run the update using the "/integrate:<admin install point>"
> >>>>switch it claims to integrate successfully but when I try an over-the-network
> >>>>install it errors out again while copying files. I've only been able to test
> >>>>this by running the install over-the-network with a network boot disk so I'm
> >>>>not sure if that has anything to do with it. Is there a reason why I'm
> >>>>unable to install Windows after applying these updates and how do I resolve
> >>>>it?
> >>>>
> >>>>Also...
> >>>>
> >>>>Since I was unsuccessfull in installing the "integratable" updates I decided
> >>>>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
> >>>>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
> >>>>least get those to install. Unfortunately, I've not been able to get this to
> >>>>work either. I've tried followed the instructions provided by article ID
> >>>>828930 on how to include these updates in a Windows install I'm not able to
> >>>>follow all the instructions. Basically, it states that every update should
> >>>>have a catalog file (not the empty.cat file) that needs to be referenced in
> >>>>the dosnet.inf file in order for the update to work. However, for most of
> >>>>the updates there are no .cat files included except the empty.cat file which
> >>>>it states to disregard. I skipped this step as it didn't apply and followed
> >>>>the rest to a tee but after Windows installs seamlessly and I run Windows
> >>>>Update the updates still show as needing to be installed. So how in the
> >>>>world do I integrate updates and hotfixes that don't come with update.exe
> >>>>version 5.4.15.0? The instructions Microsoft provides are not making sense.
> >>
> >>
>
>

I can't offer any further suggestions for your specific problem. In
regards to the ""unintegratable" updates (i.e., the updates
that do not come with update.exe" my understanding from reading on the
MS site somewhere is that they can't be done regardless of what q828930
says, or at least not by using MS instructions. Quite frankly you're
way more knowledgeable than I am on the subject so I can't add anything.

However... I have stumbled across this little script, well not so
little, about 81kb (269kb total download) and from a quick try out it
looks like dynamite! You might want to look into it, it could be the
ticket to what you are trying to do:

http://greenmachine.msfnhosting.com/XPCREATE/

And on Jerold Schulman's site I ran across a link to a similar utility
that might be useful but I haven't looked into it any further, but if
Jerold thinks that it works I would not have any hesitation giving it a
try. http://www.jsiinc.com/SUBO/TIP7300/RH7376.htm

Regards;

John

mike wrote:

> Okay, these updates aren't hotfixes I realize now... I shouldn't have called
> them that accidentally. They're regular updates, with names like
> "win2000-kbnnnnnn-en-enu.exe." These are not the hotfixes you're talking
> about. There are no .cat files in these updates. The only .cat file is the
> empty.cat file which the article specifically states to disregard.
>
> Here's a link to the article I'm getting my instructions from:
> http://support.microsoft.com/kb/828930
>
> Does this shed any additional light on the subject?
>
>
> "John John" wrote:
>
>
>>I think these .cat files are in the Qnnnnnn.exe, you have to expand them.
>>
>>How to Slipstream Hotfixes That Replace Pre-Existing Driver Files
>>http://support.microsoft.com/default...b;en-us;814847
>>
>>John
>>
>>mike wrote:
>>
>>
>>mike wrote:
>>
>>
>>>Thanks, but this doesn't address my problem at hand. I'll worry about
>>>creating a bootable CD after I've been able to verify that Windows 2000
>>>installs with SP4 and all hotfixes in place.
>>>
>>>Again, I've followed the instructions provided by Article number 828930 and
>>>the instructions are incomplete. There are no .cat files for most of the
>>>hotfixes which the instructions insist on copying to the i386\svcpack folder.
>>> I'm sure this is of significance and probably explains why its not working
>>>but I don't know of a workaround -- how do I integrate these updates if there
>>>are no .cat files????
>>>
>>>Also, regarding the updates that use update.exe version 5.4.15.0 or later:
>>>After integrating these updates to the install share for win2k and attempting
>>>to run an over-the-network install it errors out while copying files (in the
>>>blue, text-based part of setup). It does this only after I've integrated
>>>these updates because it will copy all files fine after integrating SP4. Why
>>>is this? Is it related to installing over the network?? I do not have a CD
>>>burner at present as mine is broken. Would I need to run the install off a
>>>CD in order for all files to be copied? Please help!!!!!!!!!!!!!!!
>>>
>>>"John John" wrote:
>>>
>>>
>>>
>>>>neo [mvp outlook] provided this link not too long ago and says he likes it:
>>>>
>>>>Making a Bootable Windows 2000 CD with Service Pack Integrated
>>>>http://old.bink.nu/bootcd/
>>>>
>>>>and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
>>>>http://www.neowin.net/forum/index.ph...&#entry2453585
>>>>
>>>>Search the newsgroup and you will find others...
>>>>
>>>>John
>>>>
>>>>mike wrote:
>>>>
>>>>
>>>>>If anyone can help me out with this issue I would be very appreciative. I
>>>>>just need to know if anyone has successfully been able to create a bootable,
>>>>>slipstreamed win2k CD with all critical updates and service packs
>>>>>preinstalled. If someone has been able to successfully do this please let me
>>>>>know the steps you took! Thank you very much!
>>>>>
>>>>>"mike" wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I've been having a real hard time getting this to work. I've been able to
>>>>>>create an administrative installation point and slipstream SP4 with Win2k.
>>>>>>When I go to install Windows using my admin install share it works perfectly
>>>>>>and SP4 is installed. However, if I've integrated any additional
>>>>>>hotfixes/updates in to the admin install point and run the install over the
>>>>>>network (using a TCP/IP boot disk)it fails to copy some files (it says its
>>>>>>unable to copy the file and gives me the option of skipping them). This is
>>>>>>happening with updates that use the update.exe version 5.4.15.0 or later
>>>>>>(which includes the option to integrate the update in to an admin install
>>>>>>point). When I run the update using the "/integrate:<admin install point>"
>>>>>>switch it claims to integrate successfully but when I try an over-the-network
>>>>>>install it errors out again while copying files. I've only been able to test
>>>>>>this by running the install over-the-network with a network boot disk so I'm
>>>>>>not sure if that has anything to do with it. Is there a reason why I'm
>>>>>>unable to install Windows after applying these updates and how do I resolve
>>>>>>it?
>>>>>>
>>>>>>Also...
>>>>>>
>>>>>>Since I was unsuccessfull in installing the "integratable" updates I decided
>>>>>>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
>>>>>>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
>>>>>>least get those to install. Unfortunately, I've not been able to get this to
>>>>>>work either. I've tried followed the instructions provided by article ID
>>>>>>828930 on how to include these updates in a Windows install I'm not able to
>>>>>>follow all the instructions. Basically, it states that every update should
>>>>>>have a catalog file (not the empty.cat file) that needs to be referenced in
>>>>>>the dosnet.inf file in order for the update to work. However, for most of
>>>>>>the updates there are no .cat files included except the empty.cat file which
>>>>>>it states to disregard. I skipped this step as it didn't apply and followed
>>>>>>the rest to a tee but after Windows installs seamlessly and I run Windows
>>>>>>Update the updates still show as needing to be installed. So how in the
>>>>>>world do I integrate updates and hotfixes that don't come with update.exe
>>>>>>version 5.4.15.0? The instructions Microsoft provides are not making sense.
>>>>
>>>>
>>>Thanks, but this doesn't address my problem at hand. I'll worry about
>>>creating a bootable CD after I've been able to verify that Windows 2000
>>>installs with SP4 and all hotfixes in place.
>>>
>>>Again, I've followed the instructions provided by Article number 828930 and
>>>the instructions are incomplete. There are no .cat files for most of the
>>>hotfixes which the instructions insist on copying to the i386\svcpack folder.
>>> I'm sure this is of significance and probably explains why its not working
>>>but I don't know of a workaround -- how do I integrate these updates if there
>>>are no .cat files????
>>>
>>>Also, regarding the updates that use update.exe version 5.4.15.0 or later:
>>>After integrating these updates to the install share for win2k and attempting
>>>to run an over-the-network install it errors out while copying files (in the
>>>blue, text-based part of setup). It does this only after I've integrated
>>>these updates because it will copy all files fine after integrating SP4. Why
>>>is this? Is it related to installing over the network?? I do not have a CD
>>>burner at present as mine is broken. Would I need to run the install off a
>>>CD in order for all files to be copied? Please help!!!!!!!!!!!!!!!
>>>
>>>"John John" wrote:
>>>
>>>
>>>
>>>>neo [mvp outlook] provided this link not too long ago and says he likes it:
>>>>
>>>>Making a Bootable Windows 2000 CD with Service Pack Integrated
>>>>http://old.bink.nu/bootcd/
>>>>
>>>>and Jim Byrd, MS-MVP provided this link and he says it works like a charm:
>>>>http://www.neowin.net/forum/index.ph...&#entry2453585
>>>>
>>>>Search the newsgroup and you will find others...
>>>>
>>>>John
>>>>
>>>>mike wrote:
>>>>
>>>>
>>>>>If anyone can help me out with this issue I would be very appreciative. I
>>>>>just need to know if anyone has successfully been able to create a bootable,
>>>>>slipstreamed win2k CD with all critical updates and service packs
>>>>>preinstalled. If someone has been able to successfully do this please let me
>>>>>know the steps you took! Thank you very much!
>>>>>
>>>>>"mike" wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I've been having a real hard time getting this to work. I've been able to
>>>>>>create an administrative installation point and slipstream SP4 with Win2k.
>>>>>>When I go to install Windows using my admin install share it works perfectly
>>>>>>and SP4 is installed. However, if I've integrated any additional
>>>>>>hotfixes/updates in to the admin install point and run the install over the
>>>>>>network (using a TCP/IP boot disk)it fails to copy some files (it says its
>>>>>>unable to copy the file and gives me the option of skipping them). This is
>>>>>>happening with updates that use the update.exe version 5.4.15.0 or later
>>>>>>(which includes the option to integrate the update in to an admin install
>>>>>>point). When I run the update using the "/integrate:<admin install point>"
>>>>>>switch it claims to integrate successfully but when I try an over-the-network
>>>>>>install it errors out again while copying files. I've only been able to test
>>>>>>this by running the install over-the-network with a network boot disk so I'm
>>>>>>not sure if that has anything to do with it. Is there a reason why I'm
>>>>>>unable to install Windows after applying these updates and how do I resolve
>>>>>>it?
>>>>>>
>>>>>>Also...
>>>>>>
>>>>>>Since I was unsuccessfull in installing the "integratable" updates I decided
>>>>>>to try manually slipstreaming the "unintegratable" updates (i.e., the updates
>>>>>>that do not come with update.exe 5.4.15.0 or later.) to see if I could at
>>>>>>least get those to install. Unfortunately, I've not been able to get this to
>>>>>>work either. I've tried followed the instructions provided by article ID
>>>>>>828930 on how to include these updates in a Windows install I'm not able to
>>>>>>follow all the instructions. Basically, it states that every update should
>>>>>>have a catalog file (not the empty.cat file) that needs to be referenced in
>>>>>>the dosnet.inf file in order for the update to work. However, for most of
>>>>>>the updates there are no .cat files included except the empty.cat file which
>>>>>>it states to disregard. I skipped this step as it didn't apply and followed
>>>>>>the rest to a tee but after Windows installs seamlessly and I run Windows
>>>>>>Update the updates still show as needing to be installed. So how in the
>>>>>>world do I integrate updates and hotfixes that don't come with update.exe
>>>>>>version 5.4.15.0? The instructions Microsoft provides are not making sense.
>>>>
>>>>
>>