Thanks so much for helping us to help you. It truely makes DriverPacks better for everyone!

Your hard work and time invested is greatly apprecieated.

Welcome again to DriverPacks, we are glad your here!

Jeff
DriverPacks admin.

CODE posted by OverFlow 2009-05-25 11:32:06 (above) integrated

Link to new DriverPack_MassStorage_wnt5_x86-32.ini  and  DP_MassStorage_wnt5_x86-32_901.7z
http://computerfixpro.com/DP_MassStorag … 901.7z.zip

DriverPacks BASE v8.12.4

Hardware: SpaceWalker-Shuttle-AI61-motherboard

Source: W2K3 SP1 R2

UBCD4Win 3.22 -- PASS

UBCD4Win 3.50 -- PASS

DriverPacks into a source for DISC install of W2K3 SP1 R2 -- PASS

________________________________________________________

In all cases the original   amdide.sys 7,680 bytes version 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
is replaced by                amdide.sys 29,696 bytes version AMD 8.2.8 (original name - amdbusdr.sys)

Confirmed by Device Manager new amdide.sys 29,696 bytes version AMD 8.2.8 is LOADED properly.

AMDEIDE.SYS  -- LOADED

--------------------------------------------------------------

AMDIDE1.SY_   --  correctly exists at %windir%\SYSTEM32\DRIVERS\  (original name - amdide.sys)

.
#############################################

BSOD
STOP: 0X0000007B (0XFA2F3528, 0XC0000034, 0X00000000, 0X00000000)

STILL occurs with W2K3 ONLY IF  original DriverPack_MassStorage_wnt5_x86-32.ini
is used --> UBCD4Win 3.22, UBCD4Win 3.50, and DISC install of W2K3 SP1 R2.

#############################################

Should be able to test with SpaceWalker-Shuttle-AI61-motherboard late next week I hope...

Will promptly post results once testing commences.

Windows 2003 uses / includes a driver with the file name amdide.sys...
- so we must 'tag' our driver with the same name, and add the replace tag too... (for 2k3)
if a driver upgrades existing support then the driver must be named (Tag name) the same as the driver it is replacing...

Your code is valid for xp but probably fails at 2k3...
the corrected code above should work for 2K, XP and 2K3...

Code in my last post is now corrected ....

I have a couple of questions about OverFlow's  code above and testing with  BartPE - Win 2K3 source.

1)
   

but I see in  \M\AM1\amdhdc.inf:

what is line?  --  LoadOrderGroup = System Bus Extender  --

2)
   

Does this mean that that the code I wrote on   2009-05-25 00:00:02  is valid for XP (it tested nicely with XP - as noted),
but invalid for W2K3,
or is it invalid for both???

If I'm understanding correctly my code of  2009-05-25 00:00:02  would be valid in XP (it tested nicely- as noted) but would not function correctly with W2K3 and that OverFlow's code above would properly function for both.

Let me know about this and I will try to get access to the hardware for testing.

there is another mistake not mentioned... AM1 is NOT a bus extender. ***(correction below, AM1 IS a bus extender)***

so applying what we know...

[AM]
ms_count=2
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="amdbusdr.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7409,PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"
ms_2_deviceName="AMD IDE Channel"
ms_2_tag="AmdEide"
ms_2_sysFile="AmdEide.sys"
ms_2_hwids="AMD_Primary_IDE_Channel,AMD_Secondary_IDE_Channel"
ms_2_isBusExtender=false

[AM1]
ms_count=1  
ms_1_deviceName="AMD PCI SATA/IDE"   
ms_1_tag="amdide1"   
ms_1_sysFile="amdide.sys"   
ms_1_hwids="PCI\VEN_1002&DEV_4390,PCI\VEN_1002&DEV_439C,PCI\VEN_1002&DEV_438C,PCI\VEN_1002&DEV_4376"
ms_1_isBusExtender=true

If you were really, really motivated to help us...
Could you please test this @ BartPE - Win 2K3 source?

edit...

Problem SOLVED!

Thank's for testing.

XP dosn't use file name amdide.sys by default.
Contrary Windows 2003 use file name amdide.sys by default. HardwareID is as in [AM].
Hence the ms_1_exc_replaceifOS="w2k3". And 2003 filename is used for replace.
[AM] use file name amdide.sys at XP and 2003.

If [AM] is renamed, [AM1] has to be renamed too.
Yes, it's confusing at first glance. It does make sense.

Good idea.

That's nice results.

Here is edited mass storage INI file [AM] and [AM1] sections:

cdob, your idea worked! I made a couple of changes just so things were easier to follow.

1) Changed   [AM]   ms_1_tag="amdide"   to   ms_1_tag="amdbusdr"
     so that the \i386\  file amdbusdr.sys is not renamed to amdide.sys

2) Changed   [AM1]   ms_1_tag="amdide1"   to   ms_1_sysFile="amdide.sys"   
     so that  the \i386\  file amdide.sys is not renamed to amdide1.sys

Although everything works fine with the files renamed, it was less confusing  if files kept the same names as that in the original driver's directory in \D\M\AM\  and \D\M\AM1\ that ended up in \i386\ and to see things in txtsetup.sif.

3) Removed a space int the line:
    ms_2_hwids="AMD_Primary_IDE_Channel, AMD_Secondary_IDE_Channel"
    ms_2_hwids="AMD_Primary_IDE_Channel,AMD_Secondary_IDE_Channel"

The new DriverPack_MassStorage_wnt5_x86-32.ini file was put in the DP_MassStorage_wnt5_x86-32_901.7z file and BASE v8.12.4 was used.

No STOP errors with UBCD4win v3.50, v3.22 or with XP service pack 3 slip-streamed.  In UBCD4win Device Manager everything looked good with IDE controller and the two IDE channels.

Here is link to new DriverPack_MassStorage_wnt5_x86-32.ini  and  DP_MassStorage_wnt5_x86-32_901.7z

http://computerfixpro.com/DP_MassStorag … 901.7z.zip

only someone with the hardware can tell us the answer for certain !

[AM]
ms_count=1
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="amdbusdr.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"

I don't hardware to test.
Contrary I doubt mentioned HardwareID works that way.
Remove all HardwareIDs from amdbusdr.sys.

No, the correct file is referenced.
However there is a missing second one: AmdEide.sys.
And there are missing two addional HardwareIDs: AMD_Primary_IDE_Channel and AMD_Secondary_IDE_Channel

Idea, not tested

[AM]
ms_count=2
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="amdbusdr.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7409,PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"
ms_2_deviceName="AMD IDE Channel"
ms_2_tag="AmdEide"
ms_2_sysFile="AmdEide.sys"
ms_2_hwids="AMD_Primary_IDE_Channel, AMD_Secondary_IDE_Channel"
ms_2_isBusExtender=false

And I've no idea,

this is accomplished in the mass storage pack by removing the HWID from the list in the mass storage INI file [AM] section

[AM]
ms_count=1
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="amdbusdr.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"

-
We will implement this fix in a nightly
if you get to the machine before we post the fix...
you can customize your local pack and test / report .

Thanks again for helping us to help you (and everyone else!)

PS I also think the wrong file is referenced it may be that it will also work If it is written like this.

[AM]
ms_count=1
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdide"
ms_1_sysFile="AmdEide.sys"
ms_1_hwids="PCI\VEN_1022&DEV_7409,PCI\VEN_1022&DEV_7411,PCI\VEN_1022&DEV_7441,PCI\VEN_1022&DEV_7469"
ms_1_isBusExtender=true
ms_1_exc_replaceifOS="w2k3"

http://ubcd4win.com/forum/index.php?sho … entry73451

Yes it is a slot A motherboard and some years old.

I work with quite a lot of very old slot A motherboards and most are fine, but this one is a little confusing, as mentioned above.

I have worked with another slot A board with some unusual problems which would only boot XP with a small customized CD bootable that then loaded XP. Win ME on this same machine needed a similar start-up disk on Floppy. That machine has now been running this way stably for over two years.

Point is that some of these types of hardware faults (broken hardware) and hardware deficiencies,  once remedied in software are quite stable and keep these machine in use and out of the landfill.

I can do some more tests with different approaches on this motherboard (SpaceWalker-Shuttle-AI61) once I have physical access to it again, probably in about two weeks +-, ... if anyone desires more information on this matter. Just let me know and tell me what types of testing you'd like.

--- SpaceWalker-Shuttle-AI61-motherboard ---

Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_1022&DEV_7409&CC_0101

I'm confused:

DP_MassStorage_wnt5_x86-32_905r2

MassStorage ini

D\M\AM\amdeide.ínf

PCI\VEN_1022&DEV_7409 is connected to amdbusdr.sys. So does MassStorage ini file.

There are addional HardwareIDs: AMD_Primary_IDE_Channel and AMD_Secondary_IDE_Channel. The driver AmdEide.sys is used.
MassStorage ini file doesn't mention AMD_Primary_IDE_Channel or AMD_Secondary_IDE_Channel.

Windows may use Compatible ID *pnp0600 and load atapi.sys.
Does windows load amdbusdr.sys and atapi.sys. Hence the BSOD?

Does amdbusdr.sys require AmdEide.sys?

Another approach:
disable amdbusdr.sys as textmode driver, use at PNP only.
Default windows support hardware already.

That's a slot A motherboard. This is some years old.
Most likely this is a hardware issue, not a software issue.
Maybe there are leaking capacitors at motherboard or PSU.
Replace the broken hardware.

Well done! we will address this issue soon!

Also got the same stop error after v8.12.4 DPsBASE utility for MassStorage v9.01 drivers DriverPacks into a source for DISC install of XP sp3. When tried to install XP proceeded OK through ' SetUp is Loading Files (.....) ' and ' SetUp is starting Windows ',  but then immediately the stop error. Tried about 10 times or so and then a DIFFERENT stop error ' 0X000000A5 (0X00000011 0X00000006 0X00000000 0X00000000) with message about 'BIOS not fully ACPI compliant' ... turn off ACPI during text mode setup with the F7 key. So tried again and used the F7 key and install proceeded properly and finished.

Installed XP again after removing the line ' ' PCI\VEN_1022&DEV_7409="amdide" ' from the TXTSETUP.SIF file and install proceeded without any problems at all.

Hope this is a help to those who debug the DrivePacks MassStorage.
Let me know if you need more information.