However, as no good deed goes unpunished, I've listed 2 other minor issues:
]]>see posts 23 and 27 - it was just an outline aimed at an experienced user if you need more help
like detailed instructions let us know or...
if you subscribe to this thread there may be a test pack in the works
]]>So my suspicion was right
Kurt_Aust, could you please tell us which ones you disabled? So we can make the same changes - or changes with the same driver size. Then you won't have to bother doing this next time.
Since Kurt says he did not know which would be best candidat for disabling in Windows 2000, I guess we'll have to find infrequently used with same footstamp.
Highpoint was frequently used, and probably still is... and Kurt disabled them all?
]]>AM
AR
H-1
H-1-R
H-2
H-3
H-4
H-5
H-6
H-7
H-8
AD-1
IN-1
Note that I just worked my way down the list as I have no idea which mass storage devices are more common.
As I knocked out drivers the error changed from "ntfs.sys is corrupt" to "insufficient memory for ntfs.sys".
A vanilla Win2000 sp4 install disk only needs 12 drivers removed, my setup needed one more.
Unrelated minor bug (I doubt this is worth starting a topic on):
Due to the method I use to create an updated Win2000 install CD, I have to use the Custom Finisher method. However it always shows that I have selected GUI Run Once on the settings overview page (it's correct in the .ini file).
]]>
Kurt_Aust, could you please tell us which ones you disabled? So we can make the same changes - or changes with the same driver size. Then you won't have to bother doing this next time.
]]>I also tried BASE 7052 / Mass Storage 705 on an unadulterated copy of Win2000 sp4, just in case my sp5 version uses more memory on setup (possible as sp5 supports large {>137GB} hard drives), however the same error occurs.
]]>pick a couple of them you won't need.
the following actions will make it work again since this error happens when too much ram is consumed by loading text mode drivers. Additionaly this error may show up on one of your systems but not another.
add this line to some unused driver sections of DriverPack_MassStorage_wnt5_x86-32.ini in the mass storage pack. adding the below line will prevent that driver from being loaded during text mode.
The driver will still be available as a plug and play driver for windows - just not for text mode.
ms_1_exc_disableIfOS= "w2k"
]]>Mass Storage 7.05 but no textmode >> OK
Mass Storage 7.05 >> ntfs.sys is corrupt
Mass Storage 7.04 >> Insufficient memory for ntfs.sys
Jeff: he was substituteing 7.04 pack for the 7.05 pack he needed to otherwise it would have used the 705 again?
Bâshrat the Sneaky: it isn't neccessary to delete the QSC stuff for that
Just move the 7.05 DP out of the DriverPacks directory
so only 7.04 would be present there. The base would then detect 7.04 as the newest version
Jeff: I see
Bâshrat the Sneaky: The base uses the version detected in the DriverPacks directory as the version for the QSC scanning.
So...
Jeff: OK, Thank You Sir!
edited for clarity from a recent chat
]]>Kurt_Aust wrote:I would suggest changing the text on the settings page to
QuickStream Cache
Enable (recommended for Slipstream method 1)
Disable (recommended for Slipstream method 2)I belive that is a good suggestion, and not presumptuous at all. I'll add it to 7.05.2 english version
Ill have to get with the translations team to get it fixed for the other languages
Actually it's not.
QSC is still useful for text mode MassStorage drivers. So it should stay the way it is.
]]>