• Marco
  • DriverPacks newbie
  • Offline
  • Registered: 2009-01-14
  • Posts: 8

Topic: [BUG] Memory error ntfs.sys during W2K installation 9.01

Hello, my first post here...

I do not know what I made wrong but I tried to slipstream latest Chipset 803 and MassStorage 901 package (+ textmode) to a Win 2000 pro SP4 Italian (method 2). It was a clean copy of W2K SP3 with only SP4 slipstreamed.

Then I made a bootable iso and I booted the ISO in a QEMU emulator machine. Result is that after few seconds (installation just starts to load some driver) the process stops saying:

    Il file ahci7xx.sys è danneggiato
    Premi un tasto qualsiasi per continuare

In english should sound (more or less):

   The file ahci7xx.sys is broken
   Press any key to continue

Pressing a key just stops intallation saying installation has failed.

What can it be? An error in the slipstreaming/installing process or a really broken driver?

Please let me know.

Last edited by Marco (2009-01-14 11:23:15)

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

did you verify the md5 checksum on the mass pack? (changelog for mass from the home page)

Did you try to reslipstream ?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Marco
  • DriverPacks newbie
  • Offline
  • Registered: 2009-01-14
  • Posts: 8

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Hi, thanks for answer.

I both checked md5 of the packs (were OK) and tried to re-slipstream them on the fresh W2K folder: same problem, ahci7xx.sys is reported as corrupted.

I tried also to make the iso just immediately before slipstreaming the drivers and the iso installs W2K in QEMU without problems.

Can I download an old MassStorage driver pack (if possible without the ahci7xx driver) to see if something change?

Ciao, Marco.


P.S. This is the slipstreaming log in case it might help...

2009-01-14 20:24:33 : <INIT> DriverPacks BASE 8.12.3 initialized.
2009-01-14 20:24:33 : <INIT> Host environment: WIN_2000 Service Pack 4 on X86 CPU.
2009-01-14 20:24:33 : <INIT> Created temporary working directory.
2009-01-14 20:24:33 : <INIT> Imported proxy settings from Internet Explorer.
2009-01-14 20:24:33 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-01-14 20:24:33 : <INIT>     Detected DriverPack Chipset 803!
2009-01-14 20:24:33 : <INIT>     Detected DriverPack CPU 804!
2009-01-14 20:24:33 : <INIT>     Detected DriverPack MassStorage 901!
2009-01-14 20:24:33 : <INIT>     Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2009-01-14 20:24:33 : <INIT>     Finished scanning.
2009-01-14 20:24:33 : <INIT> Detected settings file "C:\Archivio\DriverPack\DPs_BASE.ini".
2009-01-14 20:24:33 : <INIT> CD di Windows 2000 Professional -  SP4 detected.
2009-01-14 20:24:33 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2009-01-14 20:24:33 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2009-01-14 20:24:33 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2009-01-14 20:24:33 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2009-01-14 20:24:33 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-01-14 20:24:33 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-01-14 20:24:33 : <INIT> wnt5_x86-32_disc is the selected installation platform .
2009-01-14 20:24:33 : <INIT> Imported settings from settings file.
2009-01-14 20:24:33 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-01-14 20:24:33 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-01-14 20:24:33 : <GUI>  Initialized GUI.
2009-01-14 20:24:33 : <GUI>  Created a list of all available language files.
2009-01-14 20:24:33 : <GUI>  Set the last used language, English, as the GUI language.
2009-01-14 20:25:11 : <GUI>  Refreshed UpdateChecker with success.
2009-01-14 20:25:19 : <GUI>  Saved settings!
2009-01-14 20:25:19 : <GUI>  Closed GUI.
2009-01-14 20:25:19 : <SEL>  Selected module: mod_slip_w2k_x86-32_disc_m2.
2009-01-14 20:25:20 : <PREP> Removed all attributes from \I386.
2009-01-14 20:25:20 : <PREP> No previous DriverPacks installation found, Prep stage will be skipped
2009-01-14 20:25:20 : <SLIP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2009-01-14 20:25:31 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2009-01-14 20:25:31 : <SLIP> C:\Archivio\DriverPack\QSC\wnt5_x86-32_uni_DP_MassStorage_901_textmode\DriverPack_MassStorage_wnt5_x86-32.ini
2009-01-14 20:25:32 : <SLIP> Processing the files now. This may take a minute.
2009-01-14 20:25:51 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2009-01-14 20:25:51 : <SLIP> txtsetup.sif Backed-up Successfully
2009-01-14 20:25:51 : <SLIP> dosnet.inf Backed-up Successfully
2009-01-14 20:25:53 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2009-01-14 20:25:53 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2009-01-14 20:26:20 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2009-01-14 20:26:20 : <SLIP> Created necessary directory structure for method 2.
2009-01-14 20:26:20 : <SLIP> Copying files necessary for method 2.
2009-01-14 20:26:21 : <SLIP> Extracted additional files necessary for method 2.
2009-01-14 20:26:21 : <SLIP> expanded setup.ex_ to setuporg.exe
2009-01-14 20:26:21 : <SLIP> SETUP.EX_ Backed-up Successfully
2009-01-14 20:26:21 : <SLIP> Compressed setup.exe to SETUP.EX_.
2009-01-14 20:26:21 : <SLIP> Method 2 setup.ex_ installed
2009-01-14 20:26:21 : <SLIP> Created \I386\presetup.cmd file.
2009-01-14 20:26:21 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2009-01-14 20:26:21 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2009-01-14 20:26:21 : <SLIP> Copied DriverPack Chipset to \OEM.
2009-01-14 20:26:21 : <SLIP> Copied DriverPack MassStorage to \OEM.
2009-01-14 20:26:21 : <SLIP> Copied DriverPacks to \OEM.
2009-01-14 20:26:21 : <SLIP> Will not slipstream KB888111 because no Sound DriverPack is being slipstreamed
2009-01-14 20:26:21 : <SLIP> Will not slipstream KB883667 because no Graphics DriverPack is being slipstreamed
2009-01-14 20:26:21 : <SLIP> Updated \I386\winnt.sif to support method 2.
2009-01-14 20:26:21 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2009-01-14 20:26:21 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2009-01-14 20:26:22 : <SLIP> DP_Install_Tool was copied successfully
2009-01-14 20:26:22 : <SLIP> Slipstream finished in 1 minutes and 2 seconds.
2009-01-14 20:26:24 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang    = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons    = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI        = "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform    = "disc"
; trailing backslash is allowed, but not necessary
location    = "C:\Archivio\W2PFPP_IT_nLite"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks    = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod    = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod    = "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD        = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation    = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC        = "yes"


; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset    = "yes"
DP_CPU        = "no"
DP_MassStorage    = "yes"
DP_MassStorage_textmode = "yes"
2009-01-14 20:26:24 : <CLNP> Create a DPs_Base.log backup @ C:\Archivio\DriverPack\LogFiles\DPs_BASE_09-01-14_20-26.log
2009-01-14 20:26:24 : <CLNP> Program terminated.

Last edited by Marco (2009-01-15 07:14:06)

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

it is probably easier for you to just try something for us...

Extract DP_MassStorage_wnt5_x86-32_901.7z to \DP_MassStorage_wnt5_x86-32_90111\

Edit \DP_MassStorage_wnt5_x86-32_90111\DriverPack_MassStorage_wnt5_x86-32.ini

change the following

[AM2]
ms_count=0

and repack with 7zip (its in the bin folder with DriverPacks BASE)

the default action is to name the file to the folder name so it should be packed as DP_MassStorage_wnt5_x86-32_90111.7z
Base will see this as a new test version and use it instead of DP_MassStorage_wnt5_x86-32_901.

please test and report back!

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Marco
  • DriverPacks newbie
  • Offline
  • Registered: 2009-01-14
  • Posts: 8

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Well, things have changed.

With the mod you suggest, the installation goes just a bit further. I see loading a number of drivers (in the bottom line) that are not in the W2K original CD (among others that I cannot read I see for an instant ... ULI/ALI ...). I think this result puts some bad light on the ahci7xx.sys driver in W2K...

Unfortunately the installation stops just few seconds after saying (again I try to translate):

   not enough memory for ntfs.sys
   press any key to continue

(the same configuration for the virtual machine, just linking as CD the original W2KSP4.iso instead of the slipstreamed one, continues and install)

Is there some limit in W2K on the number/size/overallsize of drivers it can load in textmode? Maybe there are too many...

Let me know if you have any idea.

Ciao, Marco.

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

What has happend is there is a limit on the number of drivers that can be loaded by win2k (also XP and 2k3 but the limit is higher).

I guess nobody tested this with w2k before we released it... (YIKES!)

if you disable a few more of them that you don't need you will be able to finish.
This qualifies as a BUG and i will update your title to reflect that...

this is a well known issue and we actually have a mechanisim to avoid it
you will see many of the drivers tagged with

ms_1_exc_disableIfOS="w2k"

add that line to several drivers you don't think you will need...
you will see examples in the file wink
(you could do the same for the [AM2] and set the ms_count=1 setting back)

Thanks for reporting - you caught us with our pants down this time wink

Welcome to DriverPacks

Thank You !

You have helped make DriverPacks better for everybody!

jeff

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Wow, I don't even have my w2k source anymore! sad

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

We should poll the testing team for users who can test and report for 2k...
I have a copy, that is one wink

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Marco
  • DriverPacks newbie
  • Offline
  • Registered: 2009-01-14
  • Posts: 8

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Thanks.

Do you have an idea which could be the most "rare/exotic" drivers one can "safely" discard?

I know it's a bad question but... which HW/Brand has the lowest probability to be really met in a lifetime? Just in your experience. (the only must for me is nForce4, my mobo)

If you need some testing on W2K, I can help a little.

Marco.

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

I would kill the expensive ones wink if you are not working on a lot of high end machines (AutoCad)
you could kill stuff like 3ware and adaptec (SCSI & SAS)  wink we don't know what you do wink it is a subjective question. big_smile

the thing of it is no matter what we pick it will be wrong for somone... that is why is easy to alter wink

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • JakeLD
  • Moderator, Sysprep & BartPE Master
  • Offline
  • From: Montreal, Canada
  • Registered: 2007-07-05
  • Posts: 872

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

I will disable the ones I judge "less important" for the next pack.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/n4W97qgvXb9IR64MNwT_BbnsRgjGDd0hpeGIqqmpZZ0/perpetual:forever/userbar/team-2.png

Donate!

JakeLD's Website

  • Marco
  • DriverPacks newbie
  • Offline
  • Registered: 2009-01-14
  • Posts: 8

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

I know, there will always be someone that uses computers with other brands HW...

Maybe its too work just for the old (but really beloved) w2k, but why not to divide the drivers in:

1) most used in "HOMEPC",
2) most used in High-end "WORKSTATIONS",
3) most used in "SERVERS"

and put a switch at the beginning of the .ini file? Default would be 1, but who needs could simply change the switch to 2 or 3

Anyway, when you reduce the number of drivers for w2k in the official version of MassStorage Pack, I think you should keep enough room in memory to still be able to load a further driver throug F6/floppy during installation.

Many thanks to you.

Ciao, Marco.

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Hi,

first of all, a big hooray.
A well meant congratulation to all those having a/final hand in release of latest releases.

To Erik I mentioned we need his knowledge on how things are done publicised in the proper fora, to Jeff I mentioned that open source cannot rely on small team, to myself I vowed I will never again spend 80 percent of available 'free' time to a single project.
We've always stressed that we do not expect you invest in hardware for long term tests.
(And..SOME hard core testers ignored that warning. I personally got bitten for almost 1500 euro on equipment value loss for machines I kept for peculiar tests. Heed thy peers? I now say I will have to heed my own warnings..)

Hi,
I have one long term hard metal machine to test mettle to kettle.
(doesn't sound like me?)

Hi, I tested DriverPack MassStorage 901 with 901.3 and had a conflict on this type MOTHERBOARD and had this (fully described to detail we need.).
That has always had more weight than "I tested that in VM."

Where do I stand now? (jan 2009)
In practice? Far behind any sysprep guru, because I seldom if ever get to do (even smallish) roll-outs.
In theory? I leave development to the guru. Yet test their and my theory against real metal.
The kettle drumm makes a rolling sound, and is our soul.
I sing a song of discomfort when I feel blue.

These days, with the things people in the teams here do, I saw team have new bloodlines well established and mingled with old.
To that, I say welcome  to DriverPacks 2009, and I also say that you guys KNEW november 2007 was but key to the changeover year.

IF november was great, what about 2008. I said that, and we get the answer.
2008 was benign.

2011 is going to be easy.
MDOP won't probably fully make it to mass. (full MDOP is only available to soft assurance and premium msdn.)
Hey? Maybe DriverPacks won't be needed. .bleh.

Last edited by Jaak (2009-01-17 11:23:34)

The answer was 42?
Kind regards, Jaak.
  • Marco
  • DriverPacks newbie
  • Offline
  • Registered: 2009-01-14
  • Posts: 8

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Hi, I made some experiments.

I deleted some w2k txtmode drivers from 901 and at last I was able to proceed the w2k installation without memory error.

I add the list that works in a Virtual PC. (the previous experiment, with only the 3132R5C4.sys more -252KByte-, gave the memory error)
I also listed the dimension of the .sys driver (just as a possible guide in the driver deletion from w2k txtsetup)

I'd like you to note that in txtsetup.sif there are listed a numer of driver.sys that does not exist: first in alpha order is 3112Rx47.sys and all are marked in size column as ???. I'm not an expert, I do not even know if it is a bug, but it seems the integrator uses the ms_1_tag+.sys instead of ms_1_sysFile in building txtsetup.sif

Ciao, Marco.

******************

FROM: DriverPack_MassStorage_wnt5_x86-32.ini

..........

[S5]
ms_count=1
ms_1_deviceName="Silicon Image 3112 SATARaid"
ms_1_tag="3112Rx47"
ms_1_sysFile="Si3112r.sys"
ms_1_hwids="PCI\VEN_1095&DEV_3112&SUBSYS_61121095,PCI\VEN.....

..........

******************

FROM: txtsetup.sif

Driver 901.2 txtmode x w2k       Kbyte (added, not in txtsetup.sif)

.............
2310_00.sys=1,,,,,,4_,4,1,,,1,4    100
3112Rx47.sys=1,,,,,,4_,4,1,,,1,4    ???
ahci6xx.sys=1,,,,,,4_,4,1,,,1,4    123
amdide.sys=1,,,,,,3_,4,1,,,1,4    9
amdide1.sys=1,,,,,,3_,4,1,,,1,4    ???
cpqarry2.sys=1,,,,,,4_,4,1,,,1,4    14
dac960nt.sys=1,,,,,,4_,4,1,,,1,4    175
fast2k2k.sys=1,,,,,,4_,4,1,,,1,4    ???
fasttk2k.sys=1,,,,,,4_,4,1,,,1,4    ???
fst376kk.sys=1,,,,,,4_,4,1,,,1,4    ???
fttxr52P.sys=1,,,,,,4_,4,1,,,1,4    160
hpt3xx.sys=1,,,,,,4_,4,1,,,1,4    44
hptmv6.sys=1,,,,,,4_,4,1,,,1,4    94
hptmvK.sys=1,,,,,,4_,4,1,,,1,4    ???
ide376kk.sys=1,,,,,,4_,4,1,,,1,4    78
jraid.sys=1,,,,,,4_,4,1,,,1,4            84
m5228.sys=1,,,,,,4_,4,1,,,1,4    45
m5281.sys=1,,,,,,4_,4,1,,,1,4    51
m5287.sys=1,,,,,,4_,4,1,,,1,4    104
m5288.sys=1,,,,,,4_,4,1,,,1,4    210
m5289.sys=1,,,,,,4_,4,1,,,1,4    52
MegaIDE.sys=1,,,,,,4_,4,1,,,1,4    163
MegaINTL.sys=1,,,,,,4_,4,1,,,1,4    177
megasas.sys=1,,,,,,4_,4,1,,,1,4    20
Mraid2k.sys=1,,,,,,4_,4,1,,,1,4    25
msasdell.sys=1,,,,,,4_,4,1,,,1,4    ???
nvatabus.sys=1,,,,,,4_,4,1,,,1,4    101
nvraid.sys=1,,,,,,3_,4,1,,,1,4    83
prfsx42k.sys=1,,,,,,4_,4,1,,,1,4    ???
SI3112.sys=1,,,,,,4_,4,1,,,1,4    74
si3114.sys=1,,,,,,4_,4,1,,,1,4    62
si3114r.sys=1,,,,,,4_,4,1,,,1,4    117
si3114r5.sys=1,,,,,,4_,4,1,,,1,4    209
si3531.sys=1,,,,,,4_,4,1,,,1,4    210
symmpi2k.sys=1,,,,,,4_,4,1,,,1,4    ???
ulsata.sys=1,,,,,,4_,4,1,,,1,4    74
ulsata2.sys=1,,,,,,4_,4,1,,,1,4    126
ultra.sys=1,,,,,,4_,4,1,,,1,4            36
viamraid.sys=1,,,,,,4_,4,1,,,1,4    117
VIAPDSK.sys=1,,,,,,4_,4,1,,,1,4    29
VMSCSI.sys=1,,,,,,4_,4,1,,,1,4    18
......

******************
   
Drivers deleted from 901 to 901.2     Kbyte
   
3132R5C4.sys                                     252
3wareDrv.SYS                                     82
ahci7xx                                             176
fastsx.sys (or fastsxkk.sys ???)             ???

******************

Last edited by Marco (2009-01-17 12:43:38)

  • Marco
  • DriverPacks newbie
  • Offline
  • Registered: 2009-01-14
  • Posts: 8

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Hello,

I'd like to know if the "strange" presence in txtsetup of some drivers[.sys] that do not really exist (se the previous post) is a bug of the slipstreamer or not.

Thanks, Marco

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

it depends on weather you deleted the drivers or if you disabled them as outlined above...

You said you deleted them, if that is so then it is user error...

When i sliptream this pack i get 3112RX47.SY_ as expected...

if you deleted that folder without removeing it from the mass.ini file then you screwed the pooch yourself wink

the directions to edit the mass pack correctly are above... or you can wait fo rus to have time to fix it for you wink

Yes user error is a bug but not one we have any control over tongue
Don't sweat it too much we will fix it soon im sure big_smile

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Marco
  • DriverPacks newbie
  • Offline
  • Registered: 2009-01-14
  • Posts: 8

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Thanks for anwer OverFlow.

Sorry for the misusage of the word "delete".

I did follow your instructions. I actually did not touch the drivers folder but I added the row ms_1_exc_disableIfOS="w2k" in the mass.ini file to disable the 4 drivers I mentioned above and I re-7z the drivers pack.

As I said before, everything has gone fine with last try. The only thing I noticed was the presence in the txtsetup.sif of drivers missing in the massstorage.7z archive (so I rose the point). I've understood now that in the slipstreamed CD the drivers are named correctly...

Only last point: when you fix the package for w2k, please keep room in memory to add a further driver through F6/floppy.

So Thank you again and have a nice day (or night, or whatever)...

Ciao, Marco.

Last edited by Marco (2009-01-21 03:59:02)

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

you will not be able to use F6 drivers...

The entries BASE creates in your winnt.sif are mutualy exclusive to f6 drivers and repair options. wink

if you remove sections / entries from winnt.sif then you will not have a fully unattended install.

So you can have one or the other - fully unattended install or f6 drivers... not both...
Put another way...
if you remove the entries in your .sif you may then use f6 but your installation may/will stop for user input... wink

Jeff

if you discover we don't have a driver, just ask, we will add it... that is the best thing to do wink

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2008-04-02
  • Posts: 26

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

i see this issue still exists,

further more i am trying to build Winbuilder LiveXP "Offlinesysprep"

i'm getting this error,

"failed to cab compress"
............DPMtmp\D\M\AM2\ahci7xx.sys TO
............AHCI7XX.SY_.

the thing is, i can't find ahci7xx.sys in the pack,

seems strange how Windows 2k thinks ahci7xx.sys is corrupt, and now "MakeCab" which i assume Winbuilder uses is also complaining about ahci7xx.sys,

what is up with this bloody ahci7xx.sys ?

and why does every search of every-kind i do for the file/string for "ahci7xx" turns up with nothing?


the only time ahci7xx is actually mentioned, and that is in the file
"DriverPack_MassStorage_wnt5_x86-32.ini"

[AM2]
ms_count=1
ms_1_deviceName="AMD AHCI Compatible RAID 7xx"
ms_1_tag="ahci7xx"
ms_1_sysFile="ahci7xx.sys"
ms_1_hwids="PCI\VEN_1002&DEV_4380&SUBSYS_280A103C,PCI\VEN_1002&DEV_4380&SUBSYS_2814103C,PCI\VEN_1002&DEV_4392&SUBSYS_3029103C,PCI\VEN_1002&DEV_4391&SUBSYS_3029103C,PCI\VEN_1002&DEV_4391&SUBSYS_OE08105B,PCI\VEN_1002&DEV_4392&SUBSYS_OE08105B,PCI\VEN_1002&DEV_4391&SUBSYS_C2151631,PCI\VEN_1002&DEV_4392&SUBSYS_C2151631,PCI\VEN_1002&DEV_4391&SUBSYS_E2191631,PCI\VEN_1002&DEV_4392&SUBSYS_E2191631,PCI\VEN_1002&DEV_4391&SUBSYS_E2171631,PCI\VEN_1002&DEV_4392&SUBSYS_E2171631,PCI\VEN_1002&DEV_4393&SUBSYS_OE10105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE11105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE13105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE14105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE0E105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE0F105B,PCI\VEN_1002&DEV_4391&SUBSYS_76401558,PCI\VEN_1002&DEV_4391&SUBSYS_76411558,PCI\VEN_1002&DEV_4391&SUBSYS_2A6E103C,PCI\VEN_1002&DEV_4392&SUBSYS_2A6E103C,PCI\VEN_1002&DEV_4391&SUBSYS_0E13105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E13105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E14105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E14105B,PCI\VEN_1002&DEV_4391&SUBSYS_A7051478,PCI\VEN_1002&DEV_4392&SUBSYS_A7051478,PCI\VEN_1002&DEV_4391&SUBSYS_55021565,PCI\VEN_1002&DEV_4392&SUBSYS_55021565,PCI\VEN_1002&DEV_4391&SUBSYS_700116F3,PCI\VEN_1002&DEV_4392&SUBSYS_700116F3,PCI\VEN_1002&DEV_4391&SUBSYS_31331297,PCI\VEN_1002&DEV_4392&SUBSYS_31331297,PCI\VEN_1002&DEV_4391&SUBSYS_100415BD,PCI\VEN_1002&DEV_4392&SUBSYS_100415BD,PCI\VEN_1002&DEV_4391&SUBSYS_014C1025,PCI\VEN_1002&DEV_4392&SUBSYS_014C1025,PCI\VEN_1002&DEV_4391&SUBSYS_75011462,PCI\VEN_1002&DEV_4392&SUBSYS_75011462,PCI\VEN_1002&DEV_4391&SUBSYS_73021462,PCI\VEN_1002&DEV_4392&SUBSYS_73021462,PCI\VEN_1002&DEV_4391&SUBSYS_73041462,PCI\VEN_1002&DEV_4392&SUBSYS_73041462,PCI\VEN_1002&DEV_4391&SUBSYS_01551025,PCI\VEN_1002&DEV_4392&SUBSYS_01551025,PCI\VEN_1002&DEV_4391&SUBSYS_02591028,PCI\VEN_1002&DEV_4392&SUBSYS_02591028,PCI\VEN_1002&DEV_4392&SUBSYS_027E1028,PCI\VEN_1002&DEV_4391&SUBSYS_82EF1043,PCI\VEN_1002&DEV_4392&SUBSYS_82EF1043,PCI\VEN_1002&DEV_4391&SUBSYS_FF6A1179,PCI\VEN_1002&DEV_4391&SUBSYS_FF621179,PCI\VEN_1002&DEV_4391&SUBSYS_113E1734,PCI\VEN_1002&DEV_4392&SUBSYS_113E1734,PCI\VEN_1002&DEV_4391&SUBSYS_113A1734,PCI\VEN_1002&DEV_4392&SUBSYS_113A1734,PCI\VEN_1002&DEV_4391&SUBSYS_113B1734,PCI\VEN_1002&DEV_4392&SUBSYS_113B1734,PCI\VEN_1002&DEV_4391&SUBSYS_113D1734,PCI\VEN_1002&DEV_4392&SUBSYS_113D1734,PCI\VEN_1002&DEV_4391&SUBSYS_88AD1033,PCI\VEN_1002&DEV_4391&SUBSYS_01471025,PCI\VEN_1002&DEV_4392&SUBSYS_01471025,PCI\VEN_1002&DEV_4391&SUBSYS_014B1025,PCI\VEN_1002&DEV_4392&SUBSYS_014B1025,PCI\VEN_1002&DEV_4391&SUBSYS_01481025,PCI\VEN_1002&DEV_4392&SUBSYS_01481025,PCI\VEN_1002&DEV_4391&SUBSYS_01491025,PCI\VEN_1002&DEV_4392&SUBSYS_01491025,PCI\VEN_1002&DEV_4391&SUBSYS_30E3103C,PCI\VEN_1002&DEV_4391&SUBSYS_30F2103C,PCI\VEN_1002&DEV_4392&SUBSYS_30F2103C,PCI\VEN_1002&DEV_4391&SUBSYS_3600103C,PCI\VEN_1002&DEV_4392&SUBSYS_3600103C,PCI\VEN_1002&DEV_4391&SUBSYS_30F1103C,PCI\VEN_1002&DEV_4391&SUBSYS_30E4103C,PCI\VEN_1002&DEV_4392&SUBSYS_30E4103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FB103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FB103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FE103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FE103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FC103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FC103C,PCI\VEN_1002&DEV_4391&SUBSYS_149210CF,PCI\VEN_1002&DEV_4391&SUBSYS_43901019,PCI\VEN_1002&DEV_4392&SUBSYS_43901019,PCI\VEN_1002&DEV_4391&SUBSYS_82881043,PCI\VEN_1002&DEV_4392&SUBSYS_82881043,PCI\VEN_1002&DEV_4391&SUBSYS_025B1028,PCI\VEN_1002&DEV_4391&SUBSYS_025A1028,PCI\VEN_1002&DEV_4391&SUBSYS_02571028,PCI\VEN_1002&DEV_4392&SUBSYS_02571028,PCI\VEN_1002&DEV_4391&SUBSYS_02551028,PCI\VEN_1002&DEV_4391&SUBSYS_43911849,PCI\VEN_1002&DEV_4392&SUBSYS_43921849,PCI\VEN_1002&DEV_4393&SUBSYS_43931849,PCI\VEN_1002&DEV_4391&SUBSYS_B0021458,PCI\VEN_1002&DEV_4392&SUBSYS_B0021458,PCI\VEN_1002&DEV_4391&SUBSYS_014E1025,PCI\VEN_1002&DEV_4391&SUBSYS_11171043,PCI\VEN_1002&DEV_4392&SUBSYS_014E1025,PCI\VEN_1002&DEV_4391&SUBSYS_014F1025,PCI\VEN_1002&DEV_4392&SUBSYS_014F1025,PCI\VEN_1002&DEV_4391&SUBSYS_303617AA,PCI\VEN_1002&DEV_4392&SUBSYS_303617AA,PCI\VEN_1002&DEV_4391&SUBSYS_303F17AA,PCI\VEN_1002&DEV_4392&SUBSYS_303F17AA,PCI\VEN_1002&DEV_4391&SUBSYS_FF501179,PCI\VEN_1002&DEV_4391&SUBSYS_02641028,PCI\VEN_1002&DEV_4391&SUBSYS_02651028,PCI\VEN_1002&DEV_4391&SUBSYS_0E0E105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E0E105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E0F105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E0F105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E10105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E10105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E11105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E11105B,PCI\VEN_1002&DEV_4391&SUBSYS_43911002,PCI\VEN_1002&DEV_4392&SUBSYS_43921002,PCI\VEN_1002&DEV_4393&SUBSYS_43931002,PCI\VEN_1002&DEV_4381&SUBSYS_43811002,PCI\VEN_1002&DEV_4380&SUBSYS_43821002,PCI\VEN_1002&DEV_4380&SUBSYS_43811002"
ms_1_isBusExtender=false



"ms_1_sysFile="ahci7xx.sys"

it mentions this file, but this not a tangible file, this reference points to something that does not exist,

i'm very confused, i'm not really on these forums, but i thought i should share with what i have observed in the past now that i have got a error with Winbuilder XPLive which is in relation to "ahci7xx.sys"

if ahci7xx.sys does exists, i can't find it in the driver pack,

  • Registered: 2007-08-21
  • Posts: 102

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

ahci7xx.sys is currently located in D\M\AM2 of masstorage pack 9.01.
maybe your download is corrupt.

  • Registered: 2008-04-02
  • Posts: 26

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

you were right, thanks, it took 5 attempts of download, strangely enough though 7Zip extracted without any errors?

anyway the file exists now, just about to create a LiveXP project, thanks bigfoot, I would have never imagined it was a corrupt download, I assumed that 7Zip would always do a full CRC32 check on extraction, any mismatch would lead to an error, clearly I was mistaken. thanks again,

Doesn't DriverPacks have a built in SHA5 or MD hash (or what ever it's called) validator, given the nature of how sensitive these driver packs are....

just checked, the 2K problem still exists though, file is considered corrupt every time,
as well as many others I have tried of the internet, my gut tells me that AHCI7xx just isn't 2K Compliant,


Winbuilder now works, thanks,

Last edited by Registered (2010-04-19 21:41:47)

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

nope MD5/CRC are not a function of un7zip that is why we post the MD5 hashes

the nightly version of DriverPacks BASE will check the MD5 if a pack is downloaded with DriverPacks BASE...

I suppose it is possible to run an MD5 hash on the packs that are already downloaded but it would still have to be done as a function of the update checker and an Internet connection would be required.

This would have no effect on packs after they were slipstreamed... IE if the packs were corrupted when copied to an ISO or ODD... nor during extraction when DriverPacks is installing

I am not sure if this is worth the extra time to invest given that ultimately the final stages can't be verified (during install).

thoughts / Ideas?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • aldsge
  • DriverPacks newbie
  • Offline
  • Registered: 2010-05-26
  • Posts: 1

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

hey guys,
just a short comment. actually this ms_1_exc_disableIfOS="w2k" stuff never worked for me, i got the same error message every time.
what finally let me succeed was that i inserted a semicolon in front of the filenames mentioned by Marco in dosnet.inf (so like ;d1,ahci7xx.sys etc.) and i removed every line which contained these driver names from txtsetup.sif. i mean after slipstreaming. and it actually works this way.

  • Registered: 2010-07-07
  • Posts: 3

Re: [BUG] Memory error ntfs.sys during W2K installation 9.01

Thanks for share !!!!!!