Discussion:
Old computer, slipstream..
(too old to reply)
Robert Baer
2014-06-20 03:48:35 UTC
Permalink
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
Win2K:
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.

This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
Location:
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]

So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?

Also found in archive, 126663_ENU_i386_zip.exe which i must have
found online. Is that an "official" SP5 and applied after the KB891861
rollup?
That would be #4 in list above, i take it.
Paul
2014-06-20 05:20:07 UTC
Permalink
Post by Robert Baer
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.
This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]
So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?
Also found in archive, 126663_ENU_i386_zip.exe which i must have found
online. Is that an "official" SP5 and applied after the KB891861 rollup?
That would be #4 in list above, i take it.
"The Windows XP Low Fragmentation Heap Algorithm Feature
Is Available for Windows 2000 - June 20, 2003"

http://support.microsoft.com/kb/816542

That's just a single hotfix. Typically a hotfix, you
request it and it is emailed to you.

The Update Rollup, this comes after SP4 on Win2K. This
is version 2 of the Update Rollup, and replaces
version 1.

"Update Rollup V2 - September 13, 2005"
http://www.microsoft.com/en-us/download/details.aspx?id=18997

There is a list of KB numbers that are included in the Rollup,
on the following page. And your heap thing doesn't appear
to be in there.

http://support.microsoft.com/kb/891861

The Hotfix would have been included in SP5, it there is
one. Since the Rollup is not a service pack, it's as if
Service Packs stopped at SP4. You would be able to do the
Heap one, either before or after the Rollup. That's just
a guess on my part. The dates on these things, surely are
strange.

The Rollup appears to contain mainly Security patches, but
it's also possible that non-security things got included,
and they just aren't documented. The Low Fragmentation Heap
is a "Feature", and not a Security Update, which is why
it is outside the Rollup. And why I feel you could run it before
or after the Rollup. If they had made an actual SP5, the heap
thing would have been included in there, and you could then
throw the Heap one away. But since they never made an SP5, the
heap one is still valid and usable.

Paul
Robert Baer
2014-06-20 07:25:44 UTC
Permalink
Post by Paul
Post by Robert Baer
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.
This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]
So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?
Also found in archive, 126663_ENU_i386_zip.exe which i must have found
online. Is that an "official" SP5 and applied after the KB891861 rollup?
That would be #4 in list above, i take it.
"The Windows XP Low Fragmentation Heap Algorithm Feature
Is Available for Windows 2000 - June 20, 2003"
http://support.microsoft.com/kb/816542
That's just a single hotfix. Typically a hotfix, you
request it and it is emailed to you.
The Update Rollup, this comes after SP4 on Win2K. This
is version 2 of the Update Rollup, and replaces
version 1.
"Update Rollup V2 - September 13, 2005"
http://www.microsoft.com/en-us/download/details.aspx?id=18997
There is a list of KB numbers that are included in the Rollup,
on the following page. And your heap thing doesn't appear
to be in there.
http://support.microsoft.com/kb/891861
The Hotfix would have been included in SP5, it there is
one. Since the Rollup is not a service pack, it's as if
Service Packs stopped at SP4. You would be able to do the
Heap one, either before or after the Rollup. That's just
a guess on my part. The dates on these things, surely are
strange.
The Rollup appears to contain mainly Security patches, but
it's also possible that non-security things got included,
and they just aren't documented. The Low Fragmentation Heap
is a "Feature", and not a Security Update, which is why
it is outside the Rollup. And why I feel you could run it before
or after the Rollup. If they had made an actual SP5, the heap
thing would have been included in there, and you could then
throw the Heap one away. But since they never made an SP5, the
heap one is still valid and usable.
Paul
Thanks(i think).
Got on the site,and found the archive they made.
So much stuff!
Rather long list of KBs ("hot"fixes).
Even the author of USP5.1 complained about the long list.

In any event,it looks like a reasonable path is (using my folder names):

1) Original Win2K SP2, copy of disk in folder Win2K-SP2.

2) W2KSP4.EXE in folder SP4.
Dated 6/20/2003.

3) After SP4, comes Update Rollup 1;
Windows2000-KB891861-v2-x86-ENU.EXE in folder KB891861.
Dated 9/15/2012. ?? SP5.000?

4) Windows2000-KB816542-x86-ENU.exe in folder 126663.
Dated 6/11/2003. ?? SP5.001?

5) Windows2000-UURollup-v10d-x86-ENU.exe in folder Win2000Archive\Unofficial
Dated 6/19/2014 SP5.1

Is it safe to assume the Windows XP Low Fragmentation Heap Algorithm
is part of that KB816542?
Am guessing the lo frag bit is to control the gobbling of memory.
Paul
2014-06-20 12:48:32 UTC
Permalink
Post by Robert Baer
Post by Paul
Post by Robert Baer
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.
This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]
So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?
Also found in archive, 126663_ENU_i386_zip.exe which i must have found
online. Is that an "official" SP5 and applied after the KB891861 rollup?
That would be #4 in list above, i take it.
"The Windows XP Low Fragmentation Heap Algorithm Feature
Is Available for Windows 2000 - June 20, 2003"
http://support.microsoft.com/kb/816542
That's just a single hotfix. Typically a hotfix, you
request it and it is emailed to you.
The Update Rollup, this comes after SP4 on Win2K. This
is version 2 of the Update Rollup, and replaces
version 1.
"Update Rollup V2 - September 13, 2005"
http://www.microsoft.com/en-us/download/details.aspx?id=18997
There is a list of KB numbers that are included in the Rollup,
on the following page. And your heap thing doesn't appear
to be in there.
http://support.microsoft.com/kb/891861
The Hotfix would have been included in SP5, it there is
one. Since the Rollup is not a service pack, it's as if
Service Packs stopped at SP4. You would be able to do the
Heap one, either before or after the Rollup. That's just
a guess on my part. The dates on these things, surely are
strange.
The Rollup appears to contain mainly Security patches, but
it's also possible that non-security things got included,
and they just aren't documented. The Low Fragmentation Heap
is a "Feature", and not a Security Update, which is why
it is outside the Rollup. And why I feel you could run it before
or after the Rollup. If they had made an actual SP5, the heap
thing would have been included in there, and you could then
throw the Heap one away. But since they never made an SP5, the
heap one is still valid and usable.
Paul
Thanks(i think).
Got on the site,and found the archive they made.
So much stuff!
Rather long list of KBs ("hot"fixes).
Even the author of USP5.1 complained about the long list.
1) Original Win2K SP2, copy of disk in folder Win2K-SP2.
2) W2KSP4.EXE in folder SP4.
Dated 6/20/2003.
3) After SP4, comes Update Rollup 1;
Windows2000-KB891861-v2-x86-ENU.EXE in folder KB891861.
Dated 9/15/2012. ?? SP5.000?
4) Windows2000-KB816542-x86-ENU.exe in folder 126663.
Dated 6/11/2003. ?? SP5.001?
5) Windows2000-UURollup-v10d-x86-ENU.exe in folder
Win2000Archive\Unofficial
Dated 6/19/2014 SP5.1
Is it safe to assume the Windows XP Low Fragmentation Heap Algorithm
is part of that KB816542?
Am guessing the lo frag bit is to control the gobbling of memory.
I would not slipstream the low fragmentation one, without
some understanding of how the "password" issue will be handled.

When you slipstream, the "input format" has to be
something the tool understands. For example, slipstreaming
drivers, there are a few different driver formats. The
TXTSETUP.OEM method of an F6 floppy, is an example of a
supported format. Some .exe formatted drivers would not
be appropriate. Read the documentation to understand
more about this.

The low fragmentation one, is an EXE, is probably a
self-extracting archive, but may require the user to input
a userid and password to open the archive. This is not
likely to be suitable.

Since the output of a slipstream tool is an ISO9660 file,
you have an opportunity to evaluate your handiwork, without
wasting CD media. Using VPC2007 under a WinXP operating
system, I would ask the ISO9660 disc to install a copy
of Win2K on a blank virtual machine, and see what happens.
That's a way to verify the ISO9660 was successful to some
extent. If all looks good, you can burn a CD, and work on
a real machine with it.

Paul
Robert Baer
2014-06-20 15:13:05 UTC
Permalink
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.
This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]
So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?
Also found in archive, 126663_ENU_i386_zip.exe which i must have found
online. Is that an "official" SP5 and applied after the KB891861 rollup?
That would be #4 in list above, i take it.
"The Windows XP Low Fragmentation Heap Algorithm Feature
Is Available for Windows 2000 - June 20, 2003"
http://support.microsoft.com/kb/816542
That's just a single hotfix. Typically a hotfix, you
request it and it is emailed to you.
The Update Rollup, this comes after SP4 on Win2K. This
is version 2 of the Update Rollup, and replaces
version 1.
"Update Rollup V2 - September 13, 2005"
http://www.microsoft.com/en-us/download/details.aspx?id=18997
There is a list of KB numbers that are included in the Rollup,
on the following page. And your heap thing doesn't appear
to be in there.
http://support.microsoft.com/kb/891861
The Hotfix would have been included in SP5, it there is
one. Since the Rollup is not a service pack, it's as if
Service Packs stopped at SP4. You would be able to do the
Heap one, either before or after the Rollup. That's just
a guess on my part. The dates on these things, surely are
strange.
The Rollup appears to contain mainly Security patches, but
it's also possible that non-security things got included,
and they just aren't documented. The Low Fragmentation Heap
is a "Feature", and not a Security Update, which is why
it is outside the Rollup. And why I feel you could run it before
or after the Rollup. If they had made an actual SP5, the heap
thing would have been included in there, and you could then
throw the Heap one away. But since they never made an SP5, the
heap one is still valid and usable.
Paul
Thanks(i think).
Got on the site,and found the archive they made.
So much stuff!
Rather long list of KBs ("hot"fixes).
Even the author of USP5.1 complained about the long list.
1) Original Win2K SP2, copy of disk in folder Win2K-SP2.
2) W2KSP4.EXE in folder SP4.
Dated 6/20/2003.
3) After SP4, comes Update Rollup 1;
Windows2000-KB891861-v2-x86-ENU.EXE in folder KB891861.
Dated 9/15/2012. ?? SP5.000?
4) Windows2000-KB816542-x86-ENU.exe in folder 126663.
Dated 6/11/2003. ?? SP5.001?
* This EXE was one of the 3 files in the 126663_ENU_i386_zip.exe file,
so her the ZIP problem is solved.
Post by Paul
Post by Robert Baer
5) Windows2000-UURollup-v10d-x86-ENU.exe in folder
Win2000Archive\Unofficial
Dated 6/19/2014 SP5.1
Is it safe to assume the Windows XP Low Fragmentation Heap Algorithm
is part of that KB816542?
Am guessing the lo frag bit is to control the gobbling of memory.
I would not slipstream the low fragmentation one, without
some understanding of how the "password" issue will be handled.
When you slipstream, the "input format" has to be
something the tool understands. For example, slipstreaming
drivers, there are a few different driver formats. The
TXTSETUP.OEM method of an F6 floppy, is an example of a
supported format. Some .exe formatted drivers would not
be appropriate. Read the documentation to understand
more about this.
* See above; have unzipped all EXEs that had the ZIP designation, so
should be safe on that score.
* OK; i give up; i have seen the file TXTSETUP.OEM mentioned elsewhere
as well.
I have yet to see/find that elusive file, much less any documentation.
Did a search for that text string on the file collection i have for
slipstream, and found 3 matches in the Win2K-SP2 folder, and "bingo" in
the F:\UURollup_path\support\tools folder is unattend.doc with that string.
Doing a snoop in that DOC file, i find the non-useful sentence
"Txtsetup.oem
This file contains descriptions of all the OEM-supplied drivers listed
in this section and includes instructions on how to install them. This
file must exist if this section is listed."
Searching in my Win2K partition was of zero help.

So, i used the baby bird, GooGull and BINGO! i may be in business there.
Post by Paul
The low fragmentation one, is an EXE, is probably a
self-extracting archive, but may require the user to input
a userid and password to open the archive. This is not
likely to be suitable.
Since the output of a slipstream tool is an ISO9660 file,
you have an opportunity to evaluate your handiwork, without
wasting CD media. Using VPC2007 under a WinXP operating
system, I would ask the ISO9660 disc to install a copy
of Win2K on a blank virtual machine, and see what happens.
That's a way to verify the ISO9660 was successful to some
extent. If all looks good, you can burn a CD, and work on
a real machine with it.
* MORE complication! A virtual machine.
Urrgh!
First i would have to find that software, then find out how to
(safely) install and use it.
Are you not asking a lot for a software doofus?
Got plenty of DVD disks; "standard" way is good enough for me.
Post by Paul
Paul
Paul
2014-06-20 16:16:08 UTC
Permalink
Post by Robert Baer
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.
This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]
So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?
Also found in archive, 126663_ENU_i386_zip.exe which i must have found
online. Is that an "official" SP5 and applied after the KB891861 rollup?
That would be #4 in list above, i take it.
"The Windows XP Low Fragmentation Heap Algorithm Feature
Is Available for Windows 2000 - June 20, 2003"
http://support.microsoft.com/kb/816542
That's just a single hotfix. Typically a hotfix, you
request it and it is emailed to you.
The Update Rollup, this comes after SP4 on Win2K. This
is version 2 of the Update Rollup, and replaces
version 1.
"Update Rollup V2 - September 13, 2005"
http://www.microsoft.com/en-us/download/details.aspx?id=18997
There is a list of KB numbers that are included in the Rollup,
on the following page. And your heap thing doesn't appear
to be in there.
http://support.microsoft.com/kb/891861
The Hotfix would have been included in SP5, it there is
one. Since the Rollup is not a service pack, it's as if
Service Packs stopped at SP4. You would be able to do the
Heap one, either before or after the Rollup. That's just
a guess on my part. The dates on these things, surely are
strange.
The Rollup appears to contain mainly Security patches, but
it's also possible that non-security things got included,
and they just aren't documented. The Low Fragmentation Heap
is a "Feature", and not a Security Update, which is why
it is outside the Rollup. And why I feel you could run it before
or after the Rollup. If they had made an actual SP5, the heap
thing would have been included in there, and you could then
throw the Heap one away. But since they never made an SP5, the
heap one is still valid and usable.
Paul
Thanks(i think).
Got on the site,and found the archive they made.
So much stuff!
Rather long list of KBs ("hot"fixes).
Even the author of USP5.1 complained about the long list.
1) Original Win2K SP2, copy of disk in folder Win2K-SP2.
2) W2KSP4.EXE in folder SP4.
Dated 6/20/2003.
3) After SP4, comes Update Rollup 1;
Windows2000-KB891861-v2-x86-ENU.EXE in folder KB891861.
Dated 9/15/2012. ?? SP5.000?
4) Windows2000-KB816542-x86-ENU.exe in folder 126663.
Dated 6/11/2003. ?? SP5.001?
* This EXE was one of the 3 files in the 126663_ENU_i386_zip.exe file,
so her the ZIP problem is solved.
Post by Paul
Post by Robert Baer
5) Windows2000-UURollup-v10d-x86-ENU.exe in folder
Win2000Archive\Unofficial
Dated 6/19/2014 SP5.1
Is it safe to assume the Windows XP Low Fragmentation Heap Algorithm
is part of that KB816542?
Am guessing the lo frag bit is to control the gobbling of memory.
I would not slipstream the low fragmentation one, without
some understanding of how the "password" issue will be handled.
When you slipstream, the "input format" has to be
something the tool understands. For example, slipstreaming
drivers, there are a few different driver formats. The
TXTSETUP.OEM method of an F6 floppy, is an example of a
supported format. Some .exe formatted drivers would not
be appropriate. Read the documentation to understand
more about this.
* See above; have unzipped all EXEs that had the ZIP designation, so
should be safe on that score.
* OK; i give up; i have seen the file TXTSETUP.OEM mentioned elsewhere
as well.
I have yet to see/find that elusive file, much less any documentation.
Did a search for that text string on the file collection i have for
slipstream, and found 3 matches in the Win2K-SP2 folder, and "bingo" in
the F:\UURollup_path\support\tools folder is unattend.doc with that string.
Doing a snoop in that DOC file, i find the non-useful sentence
"Txtsetup.oem
This file contains descriptions of all the OEM-supplied drivers listed
in this section and includes instructions on how to install them. This
file must exist if this section is listed."
Searching in my Win2K partition was of zero help.
So, i used the baby bird, GooGull and BINGO! i may be in business there.
Post by Paul
The low fragmentation one, is an EXE, is probably a
self-extracting archive, but may require the user to input
a userid and password to open the archive. This is not
likely to be suitable.
Since the output of a slipstream tool is an ISO9660 file,
you have an opportunity to evaluate your handiwork, without
wasting CD media. Using VPC2007 under a WinXP operating
system, I would ask the ISO9660 disc to install a copy
of Win2K on a blank virtual machine, and see what happens.
That's a way to verify the ISO9660 was successful to some
extent. If all looks good, you can burn a CD, and work on
a real machine with it.
* MORE complication! A virtual machine.
Urrgh!
First i would have to find that software, then find out how to
(safely) install and use it.
Are you not asking a lot for a software doofus?
Got plenty of DVD disks; "standard" way is good enough for me.
Post by Paul
Paul
I have 32 virtual machines stored in Virtual PC 2007 setup.
And like you, I had to learn from scratch. One step at a time.

If you want to waste CDs, slipstreaming, burning CD,
doing test install, that's your business :-) I do
simulations, so I can remain online and work on
stuff at the same time. That's why I do it. The
only OS I cannot run this way with my current setup,
is Windows 8/8.1. For that, I must reboot (PITA).
If I had started with VirtualBox for hosting, I could
run Windows 8, but then Win2K would screw up. VirtualBox
does not like Win2K. VPC2007 likes Win2K, but can't stand
Win8/8.1. You cannot win :-)

*******

http://www.biostar-usa.com/app/en-us/mb/introduction.php?S_ID=640#dl

This is an example of an F6 TXTSETUP.OEM package. It's under
drivers, then

Intel SATA AHCI/RAID F6 Disk

http://www.biostar-usa.com/upload/Driver/Chipset/Intel/SATA/Disk/Sandybridge/F6flpy32.zip

When that download is unzipped, I get

iaAHCI.cat
iaAHCI.inf
iaStor.cat
iaStor.inf
iaStor.sys
TXTSETUP.OEM

Placing those six files so that NLite can see them,
allows adding an AHCI/RAID driver to the slipstreamed
CD. That's an example of a driver format, most likely
to work with slipstreamers. Check the documentation
about any additional formats that work.

Paul
Robert Baer
2014-06-20 17:22:15 UTC
Permalink
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.
This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]
So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?
Also found in archive, 126663_ENU_i386_zip.exe which i must have found
online. Is that an "official" SP5 and applied after the KB891861 rollup?
That would be #4 in list above, i take it.
"The Windows XP Low Fragmentation Heap Algorithm Feature
Is Available for Windows 2000 - June 20, 2003"
http://support.microsoft.com/kb/816542
That's just a single hotfix. Typically a hotfix, you
request it and it is emailed to you.
The Update Rollup, this comes after SP4 on Win2K. This
is version 2 of the Update Rollup, and replaces
version 1.
"Update Rollup V2 - September 13, 2005"
http://www.microsoft.com/en-us/download/details.aspx?id=18997
There is a list of KB numbers that are included in the Rollup,
on the following page. And your heap thing doesn't appear
to be in there.
http://support.microsoft.com/kb/891861
The Hotfix would have been included in SP5, it there is
one. Since the Rollup is not a service pack, it's as if
Service Packs stopped at SP4. You would be able to do the
Heap one, either before or after the Rollup. That's just
a guess on my part. The dates on these things, surely are
strange.
The Rollup appears to contain mainly Security patches, but
it's also possible that non-security things got included,
and they just aren't documented. The Low Fragmentation Heap
is a "Feature", and not a Security Update, which is why
it is outside the Rollup. And why I feel you could run it before
or after the Rollup. If they had made an actual SP5, the heap
thing would have been included in there, and you could then
throw the Heap one away. But since they never made an SP5, the
heap one is still valid and usable.
Paul
Thanks(i think).
Got on the site,and found the archive they made.
So much stuff!
Rather long list of KBs ("hot"fixes).
Even the author of USP5.1 complained about the long list.
1) Original Win2K SP2, copy of disk in folder Win2K-SP2.
2) W2KSP4.EXE in folder SP4.
Dated 6/20/2003.
3) After SP4, comes Update Rollup 1;
Windows2000-KB891861-v2-x86-ENU.EXE in folder KB891861.
Dated 9/15/2012. ?? SP5.000?
4) Windows2000-KB816542-x86-ENU.exe in folder 126663.
Dated 6/11/2003. ?? SP5.001?
* This EXE was one of the 3 files in the 126663_ENU_i386_zip.exe file,
so her the ZIP problem is solved.
Post by Paul
Post by Robert Baer
5) Windows2000-UURollup-v10d-x86-ENU.exe in folder
Win2000Archive\Unofficial
Dated 6/19/2014 SP5.1
Is it safe to assume the Windows XP Low Fragmentation Heap Algorithm
is part of that KB816542?
Am guessing the lo frag bit is to control the gobbling of memory.
I would not slipstream the low fragmentation one, without
some understanding of how the "password" issue will be handled.
When you slipstream, the "input format" has to be
something the tool understands. For example, slipstreaming
drivers, there are a few different driver formats. The
TXTSETUP.OEM method of an F6 floppy, is an example of a
supported format. Some .exe formatted drivers would not
be appropriate. Read the documentation to understand
more about this.
* See above; have unzipped all EXEs that had the ZIP designation, so
should be safe on that score.
* OK; i give up; i have seen the file TXTSETUP.OEM mentioned elsewhere
as well.
I have yet to see/find that elusive file, much less any documentation.
Did a search for that text string on the file collection i have for
slipstream, and found 3 matches in the Win2K-SP2 folder, and "bingo"
in the F:\UURollup_path\support\tools folder is unattend.doc with that
string.
Doing a snoop in that DOC file, i find the non-useful sentence
"Txtsetup.oem
This file contains descriptions of all the OEM-supplied drivers listed
in this section and includes instructions on how to install them. This
file must exist if this section is listed."
Searching in my Win2K partition was of zero help.
So, i used the baby bird, GooGull and BINGO! i may be in business there.
Post by Paul
The low fragmentation one, is an EXE, is probably a
self-extracting archive, but may require the user to input
a userid and password to open the archive. This is not
likely to be suitable.
Since the output of a slipstream tool is an ISO9660 file,
you have an opportunity to evaluate your handiwork, without
wasting CD media. Using VPC2007 under a WinXP operating
system, I would ask the ISO9660 disc to install a copy
of Win2K on a blank virtual machine, and see what happens.
That's a way to verify the ISO9660 was successful to some
extent. If all looks good, you can burn a CD, and work on
a real machine with it.
* MORE complication! A virtual machine.
Urrgh!
First i would have to find that software, then find out how to
(safely) install and use it.
Are you not asking a lot for a software doofus?
Got plenty of DVD disks; "standard" way is good enough for me.
Post by Paul
Paul
I have 32 virtual machines stored in Virtual PC 2007 setup.
And like you, I had to learn from scratch. One step at a time.
If you want to waste CDs, slipstreaming, burning CD,
doing test install, that's your business :-) I do
simulations, so I can remain online and work on
stuff at the same time. That's why I do it. The
only OS I cannot run this way with my current setup,
is Windows 8/8.1. For that, I must reboot (PITA).
If I had started with VirtualBox for hosting, I could
run Windows 8, but then Win2K would screw up. VirtualBox
does not like Win2K. VPC2007 likes Win2K, but can't stand
Win8/8.1. You cannot win :-)
*******
http://www.biostar-usa.com/app/en-us/mb/introduction.php?S_ID=640#dl
This is an example of an F6 TXTSETUP.OEM package. It's under
drivers, then
Intel SATA AHCI/RAID F6 Disk
http://www.biostar-usa.com/upload/Driver/Chipset/Intel/SATA/Disk/Sandybridge/F6flpy32.zip
When that download is unzipped, I get
iaAHCI.cat
iaAHCI.inf
iaStor.cat
iaStor.inf
iaStor.sys
TXTSETUP.OEM
* L O N G file...not easily understandable. And this is an _example_?
How messy would it be if it were a real-life file?
* Documentation? I see a dizzing mess of stuff now, and the more i see,
the less it makes sense and the confusion is going up rapidly.
Post by Paul
Placing those six files so that NLite can see them,
allows adding an AHCI/RAID driver to the slipstreamed
CD. That's an example of a driver format, most likely
to work with slipstreamers. Check the documentation
about any additional formats that work.
Paul
Paul
2014-06-20 17:25:43 UTC
Permalink
Post by Robert Baer
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.
This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]
So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?
Also found in archive, 126663_ENU_i386_zip.exe which i must have found
online. Is that an "official" SP5 and applied after the KB891861 rollup?
That would be #4 in list above, i take it.
"The Windows XP Low Fragmentation Heap Algorithm Feature
Is Available for Windows 2000 - June 20, 2003"
http://support.microsoft.com/kb/816542
That's just a single hotfix. Typically a hotfix, you
request it and it is emailed to you.
The Update Rollup, this comes after SP4 on Win2K. This
is version 2 of the Update Rollup, and replaces
version 1.
"Update Rollup V2 - September 13, 2005"
http://www.microsoft.com/en-us/download/details.aspx?id=18997
There is a list of KB numbers that are included in the Rollup,
on the following page. And your heap thing doesn't appear
to be in there.
http://support.microsoft.com/kb/891861
The Hotfix would have been included in SP5, it there is
one. Since the Rollup is not a service pack, it's as if
Service Packs stopped at SP4. You would be able to do the
Heap one, either before or after the Rollup. That's just
a guess on my part. The dates on these things, surely are
strange.
The Rollup appears to contain mainly Security patches, but
it's also possible that non-security things got included,
and they just aren't documented. The Low Fragmentation Heap
is a "Feature", and not a Security Update, which is why
it is outside the Rollup. And why I feel you could run it before
or after the Rollup. If they had made an actual SP5, the heap
thing would have been included in there, and you could then
throw the Heap one away. But since they never made an SP5, the
heap one is still valid and usable.
Paul
Thanks(i think).
Got on the site,and found the archive they made.
So much stuff!
Rather long list of KBs ("hot"fixes).
Even the author of USP5.1 complained about the long list.
1) Original Win2K SP2, copy of disk in folder Win2K-SP2.
2) W2KSP4.EXE in folder SP4.
Dated 6/20/2003.
3) After SP4, comes Update Rollup 1;
Windows2000-KB891861-v2-x86-ENU.EXE in folder KB891861.
Dated 9/15/2012. ?? SP5.000?
4) Windows2000-KB816542-x86-ENU.exe in folder 126663.
Dated 6/11/2003. ?? SP5.001?
* This EXE was one of the 3 files in the 126663_ENU_i386_zip.exe file,
so her the ZIP problem is solved.
Post by Paul
Post by Robert Baer
5) Windows2000-UURollup-v10d-x86-ENU.exe in folder
Win2000Archive\Unofficial
Dated 6/19/2014 SP5.1
Is it safe to assume the Windows XP Low Fragmentation Heap Algorithm
is part of that KB816542?
Am guessing the lo frag bit is to control the gobbling of memory.
I would not slipstream the low fragmentation one, without
some understanding of how the "password" issue will be handled.
When you slipstream, the "input format" has to be
something the tool understands. For example, slipstreaming
drivers, there are a few different driver formats. The
TXTSETUP.OEM method of an F6 floppy, is an example of a
supported format. Some .exe formatted drivers would not
be appropriate. Read the documentation to understand
more about this.
* See above; have unzipped all EXEs that had the ZIP designation, so
should be safe on that score.
* OK; i give up; i have seen the file TXTSETUP.OEM mentioned elsewhere
as well.
I have yet to see/find that elusive file, much less any documentation.
Did a search for that text string on the file collection i have for
slipstream, and found 3 matches in the Win2K-SP2 folder, and "bingo"
in the F:\UURollup_path\support\tools folder is unattend.doc with that
string.
Doing a snoop in that DOC file, i find the non-useful sentence
"Txtsetup.oem
This file contains descriptions of all the OEM-supplied drivers listed
in this section and includes instructions on how to install them. This
file must exist if this section is listed."
Searching in my Win2K partition was of zero help.
So, i used the baby bird, GooGull and BINGO! i may be in business there.
Post by Paul
The low fragmentation one, is an EXE, is probably a
self-extracting archive, but may require the user to input
a userid and password to open the archive. This is not
likely to be suitable.
Since the output of a slipstream tool is an ISO9660 file,
you have an opportunity to evaluate your handiwork, without
wasting CD media. Using VPC2007 under a WinXP operating
system, I would ask the ISO9660 disc to install a copy
of Win2K on a blank virtual machine, and see what happens.
That's a way to verify the ISO9660 was successful to some
extent. If all looks good, you can burn a CD, and work on
a real machine with it.
* MORE complication! A virtual machine.
Urrgh!
First i would have to find that software, then find out how to
(safely) install and use it.
Are you not asking a lot for a software doofus?
Got plenty of DVD disks; "standard" way is good enough for me.
Post by Paul
Paul
I have 32 virtual machines stored in Virtual PC 2007 setup.
And like you, I had to learn from scratch. One step at a time.
If you want to waste CDs, slipstreaming, burning CD,
doing test install, that's your business :-) I do
simulations, so I can remain online and work on
stuff at the same time. That's why I do it. The
only OS I cannot run this way with my current setup,
is Windows 8/8.1. For that, I must reboot (PITA).
If I had started with VirtualBox for hosting, I could
run Windows 8, but then Win2K would screw up. VirtualBox
does not like Win2K. VPC2007 likes Win2K, but can't stand
Win8/8.1. You cannot win :-)
*******
http://www.biostar-usa.com/app/en-us/mb/introduction.php?S_ID=640#dl
This is an example of an F6 TXTSETUP.OEM package. It's under
drivers, then
Intel SATA AHCI/RAID F6 Disk
http://www.biostar-usa.com/upload/Driver/Chipset/Intel/SATA/Disk/Sandybridge/F6flpy32.zip
When that download is unzipped, I get
iaAHCI.cat
iaAHCI.inf
iaStor.cat
iaStor.inf
iaStor.sys
TXTSETUP.OEM
* L O N G file...not easily understandable. And this is an _example_?
How messy would it be if it were a real-life file?
* Documentation? I see a dizzing mess of stuff now, and the more i see,
the less it makes sense and the confusion is going up rapidly.
Post by Paul
Placing those six files so that NLite can see them,
allows adding an AHCI/RAID driver to the slipstreamed
CD. That's an example of a driver format, most likely
to work with slipstreamers. Check the documentation
about any additional formats that work.
Paul
F6flpy32.zip is 342KB, and contains a handful of files.
What are you complaining about ?

A floppy driver diskette, cannot take more than 1440 Kbytes,
right ? With compression (ZIP), the result is bound
to be less than that.

If you want to complain about something, look at the HP
printer driver I downloaded a few minutes ago, which is
1000x larger.

Paul
Robert Baer
2014-06-22 03:57:37 UTC
Permalink
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Post by Paul
Post by Robert Baer
Assembling files, etc for slipstream attempt to get result of Win2K
SP4++.
Programs: Autostreamer in its own folder, nLite exe.
1) original SP2 CD copied into its own folder,
2) SP4 exe in its folder,
3) Windows2000-KB891861-v2-x86-ENU.EXE in its folder.
This is what i have been using manually, and presumably gets me to SP5.
But i found in my archive, a file named 12663_Hotfix.txt with the
following contents [QUOTE]
KB Article Number(s): 816542
Language: English
Platform: i386
(http://hotfixv4.microsoft.com/Windows%202000/sp5/PKG38115/2195/free/126663_ENU_i386_zip.exe)
Password: pH{t-SozjY
Password Changes On: 01/12/2011
Next Password: g2LOH7noNf
[\QUOTE]
So...what is this, and do i apply it next before anything i might get
from that M$ org you mentioned that is doing Win2K extensions (hope i
can find it the org)?
Also found in archive, 126663_ENU_i386_zip.exe which i must have found
online. Is that an "official" SP5 and applied after the KB891861 rollup?
That would be #4 in list above, i take it.
"The Windows XP Low Fragmentation Heap Algorithm Feature
Is Available for Windows 2000 - June 20, 2003"
http://support.microsoft.com/kb/816542
That's just a single hotfix. Typically a hotfix, you
request it and it is emailed to you.
The Update Rollup, this comes after SP4 on Win2K. This
is version 2 of the Update Rollup, and replaces
version 1.
"Update Rollup V2 - September 13, 2005"
http://www.microsoft.com/en-us/download/details.aspx?id=18997
There is a list of KB numbers that are included in the Rollup,
on the following page. And your heap thing doesn't appear
to be in there.
http://support.microsoft.com/kb/891861
The Hotfix would have been included in SP5, it there is
one. Since the Rollup is not a service pack, it's as if
Service Packs stopped at SP4. You would be able to do the
Heap one, either before or after the Rollup. That's just
a guess on my part. The dates on these things, surely are
strange.
The Rollup appears to contain mainly Security patches, but
it's also possible that non-security things got included,
and they just aren't documented. The Low Fragmentation Heap
is a "Feature", and not a Security Update, which is why
it is outside the Rollup. And why I feel you could run it before
or after the Rollup. If they had made an actual SP5, the heap
thing would have been included in there, and you could then
throw the Heap one away. But since they never made an SP5, the
heap one is still valid and usable.
Paul
Thanks(i think).
Got on the site,and found the archive they made.
So much stuff!
Rather long list of KBs ("hot"fixes).
Even the author of USP5.1 complained about the long list.
1) Original Win2K SP2, copy of disk in folder Win2K-SP2.
2) W2KSP4.EXE in folder SP4.
Dated 6/20/2003.
3) After SP4, comes Update Rollup 1;
Windows2000-KB891861-v2-x86-ENU.EXE in folder KB891861.
Dated 9/15/2012. ?? SP5.000?
4) Windows2000-KB816542-x86-ENU.exe in folder 126663.
Dated 6/11/2003. ?? SP5.001?
* This EXE was one of the 3 files in the 126663_ENU_i386_zip.exe file,
so her the ZIP problem is solved.
Post by Paul
Post by Robert Baer
5) Windows2000-UURollup-v10d-x86-ENU.exe in folder
Win2000Archive\Unofficial
Dated 6/19/2014 SP5.1
Is it safe to assume the Windows XP Low Fragmentation Heap Algorithm
is part of that KB816542?
Am guessing the lo frag bit is to control the gobbling of memory.
I would not slipstream the low fragmentation one, without
some understanding of how the "password" issue will be handled.
When you slipstream, the "input format" has to be
something the tool understands. For example, slipstreaming
drivers, there are a few different driver formats. The
TXTSETUP.OEM method of an F6 floppy, is an example of a
supported format. Some .exe formatted drivers would not
be appropriate. Read the documentation to understand
more about this.
* See above; have unzipped all EXEs that had the ZIP designation, so
should be safe on that score.
* OK; i give up; i have seen the file TXTSETUP.OEM mentioned elsewhere
as well.
I have yet to see/find that elusive file, much less any documentation.
Did a search for that text string on the file collection i have for
slipstream, and found 3 matches in the Win2K-SP2 folder, and "bingo"
in the F:\UURollup_path\support\tools folder is unattend.doc with that
string.
Doing a snoop in that DOC file, i find the non-useful sentence
"Txtsetup.oem
This file contains descriptions of all the OEM-supplied drivers listed
in this section and includes instructions on how to install them. This
file must exist if this section is listed."
Searching in my Win2K partition was of zero help.
So, i used the baby bird, GooGull and BINGO! i may be in business there.
Post by Paul
The low fragmentation one, is an EXE, is probably a
self-extracting archive, but may require the user to input
a userid and password to open the archive. This is not
likely to be suitable.
Since the output of a slipstream tool is an ISO9660 file,
you have an opportunity to evaluate your handiwork, without
wasting CD media. Using VPC2007 under a WinXP operating
system, I would ask the ISO9660 disc to install a copy
of Win2K on a blank virtual machine, and see what happens.
That's a way to verify the ISO9660 was successful to some
extent. If all looks good, you can burn a CD, and work on
a real machine with it.
* MORE complication! A virtual machine.
Urrgh!
First i would have to find that software, then find out how to
(safely) install and use it.
Are you not asking a lot for a software doofus?
Got plenty of DVD disks; "standard" way is good enough for me.
Post by Paul
Paul
I have 32 virtual machines stored in Virtual PC 2007 setup.
And like you, I had to learn from scratch. One step at a time.
If you want to waste CDs, slipstreaming, burning CD,
doing test install, that's your business :-) I do
simulations, so I can remain online and work on
stuff at the same time. That's why I do it. The
only OS I cannot run this way with my current setup,
is Windows 8/8.1. For that, I must reboot (PITA).
If I had started with VirtualBox for hosting, I could
run Windows 8, but then Win2K would screw up. VirtualBox
does not like Win2K. VPC2007 likes Win2K, but can't stand
Win8/8.1. You cannot win :-)
*******
http://www.biostar-usa.com/app/en-us/mb/introduction.php?S_ID=640#dl
This is an example of an F6 TXTSETUP.OEM package. It's under
drivers, then
Intel SATA AHCI/RAID F6 Disk
http://www.biostar-usa.com/upload/Driver/Chipset/Intel/SATA/Disk/Sandybridge/F6flpy32.zip
When that download is unzipped, I get
iaAHCI.cat
iaAHCI.inf
iaStor.cat
iaStor.inf
iaStor.sys
TXTSETUP.OEM
* L O N G file...not easily understandable. And this is an _example_?
How messy would it be if it were a real-life file?
* Documentation? I see a dizzing mess of stuff now, and the more i
see, the less it makes sense and the confusion is going up rapidly.
Post by Paul
Placing those six files so that NLite can see them,
allows adding an AHCI/RAID driver to the slipstreamed
CD. That's an example of a driver format, most likely
to work with slipstreamers. Check the documentation
about any additional formats that work.
Paul
F6flpy32.zip is 342KB, and contains a handful of files.
What are you complaining about ?
A floppy driver diskette, cannot take more than 1440 Kbytes,
right ? With compression (ZIP), the result is bound
to be less than that.
If you want to complain about something, look at the HP
printer driver I downloaded a few minutes ago, which is
1000x larger.
Paul
That OEM file has 182 lines, which seems to be a lot.
First, there seems to be a bunch of comments,starting ";iaAHCI" ahd
(natch) i do not want to use AHCI; since this is a sample, ignore that
for the time being.
Ditto for RAID.
Then there are groups of 4 lines like:
[Files.scsi.iaAHCI_7MMDH]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat
and it seems that each of those comment lines refer to one of those groups.
Lastly,there seems to be registry entry stuff related to the above
groups.

And a dummy is supposed to fabricate a mess like this for his
[DIFFERENT] application - to be able to add in his drivers (_only_)?
Robert Baer
2014-06-22 04:03:41 UTC
Permalink
After looking at various groups of instructions, it seems that there
is a way that does not require extra programs.
Following them,and assume a drive with the various required files,i
get made a "sample" batch file as follows:

echo on
CD\Win2K-SP2
echo This is try.bat running from F:\Win2K-SP2
SP4\W2KSP4.EXE /integrate:F:\Win2K-SP2
rem above slipstreams SP4
pause
\KB891861\Windows2000-KB891861-v2-x86-ENU.EXE /integrate:F:\Win2K-SP2
rem above should then slipstream Update Rollup 1
pause
\Win2000Archive\Unofficial\Windows2000-UURollup-v10d-x86-ENU.exe
/integrate:F:\Win2K-SP2
rem above should then slipstream to SP5.1
pause
rem DONE!

Comments?
Paul
2014-06-22 05:20:44 UTC
Permalink
Post by Robert Baer
After looking at various groups of instructions, it seems that there
is a way that does not require extra programs.
Following them,and assume a drive with the various required files,i
echo on
CD\Win2K-SP2
echo This is try.bat running from F:\Win2K-SP2
SP4\W2KSP4.EXE /integrate:F:\Win2K-SP2
rem above slipstreams SP4
pause
\KB891861\Windows2000-KB891861-v2-x86-ENU.EXE /integrate:F:\Win2K-SP2
rem above should then slipstream Update Rollup 1
pause
\Win2000Archive\Unofficial\Windows2000-UURollup-v10d-x86-ENU.exe
/integrate:F:\Win2K-SP2
rem above should then slipstream to SP5.1
pause
rem DONE!
Comments?
I don't know why you insist on doing it the Microsoft way.

Use a third-party tool. I presented the link to the guide
before, but this is the "About" page for it.

http://www.nliteos.com/nlite.html

"nLite supports Windows 2000, XP x86/x64 and 2003 x86/x64
in all languages. It needs .NET Framework 2.0 in order
to run... Check if you have it already, maybe on some of
your CDs before downloading if your connection is slow."

As long as you have an OS that can run .NET 2.0, you
can use that tool. It integrates service packs and
also drivers. Drivers of the TXTSETUP.OEM type, without
writing any scripts.

I haven't used it, but assume it's as easy to use as
Autostreamer was.

Paul
Robert Baer
2014-06-22 15:44:15 UTC
Permalink
Post by Paul
.NET Framework 2.0
Looks like jumping into a swamp or worse.
Well, that states:
Supported Operating System

Windows Server 2003, Datacenter x64 Edition, Windows Server 2003,
Enterprise x64 Edition, Windows Server 2003, Standard x64 Edition,
Windows XP 64-bit
[[*i do not have; says nil about Win7]]

Required Software:

o Windows Installer 3.0 is required. Windows Installer 3.1 or
later is recommended.
[[*software 1 wants software 2 which wants software 3 which ... MESS]]

o IE 5.01 or later: You must also be running Microsoft Internet
Explorer 5.01 or later for all installations of the .NET Framework.
o 64-bit support: 64-bit CPU support requires the latest 64-bit
version of either Windows XP Professional \Windows Server 2003. This
framework is designed for the supported 64-bit Operating System. It
contains both the 64-bit and 32-bit runtime in one convenient setup. For
32-bit operating systems, please click the related resource link for the
32-bit framework download page.
[[* sorry, does not exist..]]

Additional Information

Server Installation Requirements:

If you have been directed to do a server installation, you must
have the following software installed in addition to the typical
installation requirements:

• Microsoft Data Access Components 2.8 is recommended.
• Internet Information Services (IIS) version 5.0 or later. To
access the features of ASP.NET, IIS with the latest security updates
must be installed prior to installing the .NET Framework. ASP.NET is
supported only on the following platforms: Microsoft Windows 2000
Professional (Service Pack 3 recommended), Microsoft Windows 2000 Server
(Service Pack 3 recommended), Microsoft Windows XP Professional, and
Microsoft Windows Server 2003 family.
[[* Well! Win2K! But, like i said, "software 1 wants software 2 which
wants..."]]
Robert Baer
2014-06-22 16:09:57 UTC
Permalink
The BabyBird, GooGull, proffers a dizzying variety/flavors of .NET
and the descriptions of each one does not seem favorable.
Exception:
Microsoft .NET Framework Redistributable Package (x86 ...
download.cnet.com › ... › Developer Tools › .NET
Download.com
Rating: 2.5 - ‎12 reviews - ‎Windows
Aug 16, 2007 - NET Framework version 2 redistributable package installs
the . ..... Net Framework 2.0 is needed to make certain program's
function properly.

So i got that.
The crap of it is one of those shit downloaders.
Will have to VERY CAREFULLY try it, but later, after breakfast.
Paul
2014-06-22 19:58:03 UTC
Permalink
The BabyBird, GooGull, proffers a dizzying variety/flavors of .NET and
the descriptions of each one does not seem favorable.
Microsoft .NET Framework Redistributable Package (x86 ...
download.cnet.com › ... › Developer Tools › .NET
Download.com
Rating: 2.5 - ‎12 reviews - ‎Windows
Aug 16, 2007 - NET Framework version 2 redistributable package installs
the Net Framework 2.0 is needed to make certain program's
function properly.
So i got that.
The crap of it is one of those shit downloaders.
Will have to VERY CAREFULLY try it, but later, after breakfast.
Well, first you can check and see what .NET versions
you already have.

This is the description page for .NET Setup Verifier.
Don't get too focused on details :-) I know you'd like to
try all the command line options, but that is simply
not necessary. It's a lot easier than that.

http://blogs.msdn.com/b/astebner/archive/2008/03/03/8015158.aspx

The download is on skydrive. It comes as a ZIP.

http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-99-90-04/netfx_5F00_setupverifier_5F00_new.zip

Extract "netfx_setupverifier.exe" (279,040 bytes) from that.

Double click on it.

Answer "Yes" and "Yes" to the two dialog box prompts.

The menu should display the currently installed
versions. (The window has a menu bar in the middle of it.)
Clicking the "Verify" button runs a short test program,
that attempts to load library components from the installation.
It's a basic check that there is more than just
a Registry entry saying you have .NET. It does
a functional check.

You may have .NET 2.0 already. And all this fussin and
feudin is for nuttin. Remember, we're setting up .NET 2.0
on the technician computer, so that NLite can run. Not
trying to stuff .NET 2.0 into the attempt to make a
slipstream CD. This is purely to get NLite to run on
the technician (Preparation) computer.

*******

http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS002897

The first link there has

Microsoft .NET Framework Version 2.0 dotnetfx.exe 22.42 MB

That one has the same SHA1SUM as the one I downloaded from
the lame people at Microsoft, years ago. 23,510,720 bytes

a3625c59d7a2995fb60877b5f5324892a1693b2a dotnetfx.exe

That gives you a basic .NET 2.0 without any service packs.
And should be sufficient to get this project going...

Paul
Robert Baer
2014-06-23 17:44:42 UTC
Permalink
I tried my BATch file for slipstream.
echo on
CD\Win2K-SP2
echo This is try.bat running from F:\Win2K-SP2
F:\SP4\W2KSP4.EXE /integrate:F:\Win2K-SP2
rem above slipstreams SP4
* got message window, NDX013.png attached.
Isn't it "nice" that NONE of those options were given?
In any event it seems i can safely assume SP4 is done.

pause
F:\KB891861\Windows2000-KB891861-v2-x86-ENU.EXE /integrate:F:\Win2K-SP2
rem above should then slipstream Update Rollup 1
* got message window, NDX014.png attached.
Seems like _official_ rollup 1 does not cut the mustard.
Killed the batch file at this point.
Robert Baer
2014-06-23 18:45:05 UTC
Permalink
Post by Robert Baer
I tried my BATch file for slipstream.
echo on
CD\Win2K-SP2
echo This is try.bat running from F:\Win2K-SP2
F:\SP4\W2KSP4.EXE /integrate:F:\Win2K-SP2
rem above slipstreams SP4
* got message window, NDX013.png attached.
Isn't it "nice" that NONE of those options were given?
In any event it seems i can safely assume SP4 is done.
pause
F:\KB891861\Windows2000-KB891861-v2-x86-ENU.EXE /integrate:F:\Win2K-SP2
rem above should then slipstream Update Rollup 1
* got message window, NDX014.png attached.
Seems like _official_ rollup 1 does not cut the mustard.
Killed the batch file at this point.
After running it, i looked at the contents of my F:\Win2K-SP2 and was
not able to find any changes in file dates.
I take that as strong evidence that NOTHING was done!

wonderful! (NOT)
Robert Baer
2014-06-23 21:58:13 UTC
Permalink
Well, after _that_ fiasco, i ran dotnetfx.exe and it came up in
Maintenance Mode with 2 radio button choices: Repair and Uninstall.
Selected repair, and after doing a bit of stuff,it reported .NET
Framework 2.0 as success.
So, had it in some form or other. Never mind the list of installed
programs does not show anything like that.

Well.

Ran Nlite, told it where to find Win2k SP2 for starters.
Then told it where SP4 was, and it seemed to integrate it...
Folders CDLAUNCH, Support and VALUEADD all had today's date and time
of run (good sign?).
Nlite reported Win2K ver 5.0.2195.6717 .
Properties of MyComputer icon shows Win2K ver 5.00.2195 , SP4.
So..one might think all is OK at this point.

Well, i then tried rollup 1; Nlite again did a lot of work and an
error message showed: "Rollup1: Slipstream error,please report".

So,now what?
Paul
2014-06-23 22:43:24 UTC
Permalink
Post by Robert Baer
Well, after _that_ fiasco, i ran dotnetfx.exe and it came up in
Maintenance Mode with 2 radio button choices: Repair and Uninstall.
Selected repair, and after doing a bit of stuff,it reported .NET
Framework 2.0 as success.
So, had it in some form or other. Never mind the list of installed
programs does not show anything like that.
Well.
Ran Nlite, told it where to find Win2k SP2 for starters.
Then told it where SP4 was, and it seemed to integrate it...
Folders CDLAUNCH, Support and VALUEADD all had today's date and time
of run (good sign?).
Nlite reported Win2K ver 5.0.2195.6717 .
Properties of MyComputer icon shows Win2K ver 5.00.2195 , SP4.
So..one might think all is OK at this point.
Well, i then tried rollup 1; Nlite again did a lot of work and an
error message showed: "Rollup1: Slipstream error,please report".
So,now what?
Rollup 1 is not a service pack.

I mentioned including it as a "loose" file on the CD, but
not trying to integrate it. The idea of making an SP4 CD,
is to get around this 137GB capacity issue. Rollup 1 is
not a part of that.

Check the NLite forums, and see if this has been discussed.

OK, all I could find is a suggestion that SP4 and Rollup 1
must be done at the same time, in one step. The release notes
for NLite, say it supported Rollup 1 long ago, so support
for doing this is supposed to be there.

http://forums.overclockers.com.au/showthread.php?t=389926

If they only mentioned the Rollup in the guide, we'd know
what it was classed as. An Update Pack perhaps ? All I can
tell you, is it is not a Service Pack.

http://www.nliteos.com/guide/part1.html

Paul
Robert Baer
2014-06-24 00:39:43 UTC
Permalink
Post by Paul
Post by Robert Baer
Well, after _that_ fiasco, i ran dotnetfx.exe and it came up in
Maintenance Mode with 2 radio button choices: Repair and Uninstall.
Selected repair, and after doing a bit of stuff,it reported .NET
Framework 2.0 as success.
So, had it in some form or other. Never mind the list of installed
programs does not show anything like that.
Well.
Ran Nlite, told it where to find Win2k SP2 for starters.
Then told it where SP4 was, and it seemed to integrate it...
Folders CDLAUNCH, Support and VALUEADD all had today's date and time
of run (good sign?).
Nlite reported Win2K ver 5.0.2195.6717 .
Properties of MyComputer icon shows Win2K ver 5.00.2195 , SP4.
So..one might think all is OK at this point.
Well, i then tried rollup 1; Nlite again did a lot of work and an
error message showed: "Rollup1: Slipstream error,please report".
So,now what?
Rollup 1 is not a service pack.
I mentioned including it as a "loose" file on the CD, but
not trying to integrate it. The idea of making an SP4 CD,
is to get around this 137GB capacity issue. Rollup 1 is
not a part of that.
Check the NLite forums, and see if this has been discussed.
OK, all I could find is a suggestion that SP4 and Rollup 1
must be done at the same time, in one step. The release notes
for NLite, say it supported Rollup 1 long ago, so support
for doing this is supposed to be there.
http://forums.overclockers.com.au/showthread.php?t=389926
If they only mentioned the Rollup in the guide, we'd know
what it was classed as. An Update Pack perhaps ? All I can
tell you, is it is not a Service Pack.
http://www.nliteos.com/guide/part1.html
Paul
MMmmmm.....
The "build" i have been using was done manually: SP2 initial install,
clean drive; SP4; "update rollup 1 for win2K sp4"; Win2K hotfix KB816542.
Do not ask order i used for the last two.
*
Gives me the idea to start with the (new?) SP4 it made, and try the
hotfix/update route for the rollup, etc.
Robert Baer
2014-06-23 19:02:09 UTC
Permalink
Post by Paul
The BabyBird, GooGull, proffers a dizzying variety/flavors of .NET and
the descriptions of each one does not seem favorable.
Microsoft .NET Framework Redistributable Package (x86 ...
download.cnet.com › ... › Developer Tools › .NET
Download.com
Rating: 2.5 - ‎12 reviews - ‎Windows
Aug 16, 2007 - NET Framework version 2 redistributable package
installs the Net Framework 2.0 is needed to make certain program's
function properly.
So i got that.
The crap of it is one of those shit downloaders.
Will have to VERY CAREFULLY try it, but later, after breakfast.
Well, first you can check and see what .NET versions
you already have.
This is the description page for .NET Setup Verifier.
Don't get too focused on details :-) I know you'd like to
try all the command line options, but that is simply
not necessary. It's a lot easier than that.
http://blogs.msdn.com/b/astebner/archive/2008/03/03/8015158.aspx
The download is on skydrive. It comes as a ZIP.
http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-99-90-04/netfx_5F00_setupverifier_5F00_new.zip
Extract "netfx_setupverifier.exe" (279,040 bytes) from that.
Double click on it.
* "Error creating process" Reason <sic>: C:\WINNT\system32\advpack.dll
Post by Paul
Answer "Yes" and "Yes" to the two dialog box prompts.
The menu should display the currently installed
versions. (The window has a menu bar in the middle of it.)
Clicking the "Verify" button runs a short test program,
that attempts to load library components from the installation.
It's a basic check that there is more than just
a Registry entry saying you have .NET. It does
a functional check.
You may have .NET 2.0 already. And all this fussin and
feudin is for nuttin. Remember, we're setting up .NET 2.0
on the technician computer, so that NLite can run. Not
trying to stuff .NET 2.0 into the attempt to make a
slipstream CD. This is purely to get NLite to run on
the technician (Preparation) computer.
*******
http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS002897
The first link there has
Microsoft .NET Framework Version 2.0 dotnetfx.exe 22.42 MB
That one has the same SHA1SUM as the one I downloaded from
the lame people at Microsoft, years ago. 23,510,720 bytes
a3625c59d7a2995fb60877b5f5324892a1693b2a dotnetfx.exe
That gives you a basic .NET 2.0 without any service packs.
And should be sufficient to get this project going...
Paul
Paul
2014-06-24 00:04:21 UTC
Permalink
Post by Robert Baer
Post by Paul
Extract "netfx_setupverifier.exe" (279,040 bytes) from that.
Double click on it.
* "Error creating process" Reason <sic>: C:\WINNT\system32\advpack.dll
It appears Aaron fell into the usual trap. He updated
his Visual Studio setup, and it promptly made an
executable that won't run on Win2K.

http://blogs.msdn.com/b/astebner/archive/2008/03/07/8208332.aspx?PageIndex=750

*******

I have an older version here that works OK. I downloaded
it in 2009.

Only problem is, the Skydrive doesn't support versioning,
so I can't get an older one. And because the server uses
norobots.txt, I also cannot rely on archive.org to have an
old copy of it.

This one is slightly older than the one I've got,
but I have absolutely no way of establishing a trust
relationship with it. I don't know if Aaron actually
used this site before the Skydrive, or not. There's nothing
to say this is legit.

https://web.archive.org/web/*/http://astebner.sts.winisp.net/Tools/netfx_setupverifier_new.zip

And searching on checksums, for the one I've got, isn't locating
any other good candidates.

Paul
Robert Baer
2014-06-24 00:42:35 UTC
Permalink
Post by Paul
Post by Robert Baer
Post by Paul
Extract "netfx_setupverifier.exe" (279,040 bytes) from that.
Double click on it.
* "Error creating process" Reason <sic>: C:\WINNT\system32\advpack.dll
It appears Aaron fell into the usual trap. He updated
his Visual Studio setup, and it promptly made an
executable that won't run on Win2K.
http://blogs.msdn.com/b/astebner/archive/2008/03/07/8208332.aspx?PageIndex=750
*******
I have an older version here that works OK. I downloaded
it in 2009.
Only problem is, the Skydrive doesn't support versioning,
so I can't get an older one. And because the server uses
norobots.txt, I also cannot rely on archive.org to have an
old copy of it.
This one is slightly older than the one I've got,
but I have absolutely no way of establishing a trust
relationship with it. I don't know if Aaron actually
used this site before the Skydrive, or not. There's nothing
to say this is legit.
https://web.archive.org/web/*/http://astebner.sts.winisp.net/Tools/netfx_setupverifier_new.zip
And searching on checksums, for the one I've got, isn't locating
any other good candidates.
Paul
I think that may be a moot point,as it seems that i now have a
repaired .NET 2.0 .
Robert Baer
2014-06-24 01:36:56 UTC
Permalink
Post by Paul
Post by Robert Baer
Post by Paul
Extract "netfx_setupverifier.exe" (279,040 bytes) from that.
Double click on it.
* "Error creating process" Reason <sic>: C:\WINNT\system32\advpack.dll
It appears Aaron fell into the usual trap. He updated
his Visual Studio setup, and it promptly made an
executable that won't run on Win2K.
http://blogs.msdn.com/b/astebner/archive/2008/03/07/8208332.aspx?PageIndex=750
*******
I have an older version here that works OK. I downloaded
it in 2009.
Only problem is, the Skydrive doesn't support versioning,
so I can't get an older one. And because the server uses
norobots.txt, I also cannot rely on archive.org to have an
old copy of it.
This one is slightly older than the one I've got,
but I have absolutely no way of establishing a trust
relationship with it. I don't know if Aaron actually
used this site before the Skydrive, or not. There's nothing
to say this is legit.
https://web.archive.org/web/*/http://astebner.sts.winisp.net/Tools/netfx_setupverifier_new.zip
And searching on checksums, for the one I've got, isn't locating
any other good candidates.
Paul
I think that may be a moot point,as it seems that i now have a repaired
.NET 2.0 .
Well,,,,progress of some sort.
Nlite took F:\KB891861\Windows2000-KB891861-v2-x86-ENU.EXE (rollup 1)
and processed it without a peep.
Next was the
F:\Win2000Archive\Unofficial\Windows2000-UURollup-v10d-x86-ENU.exe; it
seemed to process it, but got an error message; see attached screen capture.

So i guess i have a "full" SP4, no SP5 rollup.
*
If i remember right, i make an ISO file from that file set, and from
the ISO make an install CD/DVD; no other flim-flam.

Continue reading on narkive:
Loading...