1 Reply by cfp

(17 replies, posted in DriverPack Mass Storage)

Test Results:

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.

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

Go to forum: DriverPack Mass Storage

2 Reply by cfp

(17 replies, posted in DriverPack Mass Storage)

OK, everything looks good to me. Putting together -> BartPE - Win 2K3 source -->  right now!

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

Will promptly post results once testing commences.

Go to forum: DriverPack Mass Storage

3 Reply by cfp

(17 replies, posted in DriverPack Mass Storage)

I will see if I can get access to SpaceWalker-Shuttle-AI61-motherboard with the AMD harware but I don't know? it may be a little while before I can.

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

1)
   

OverFlow wrote:

AM1 is NOT a bus extender

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

[amdide_Service_Inst]
ServiceType    = %SERVICE_KERNEL_DRIVER%
StartType      = %SERVICE_BOOT_START%
ErrorControl   = %SERVICE_ERROR_NORMAL%
LoadOrderGroup = System Bus Extender
ServiceBinary  = %12%\amdide.sys

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


2)
   

cdob wrote:

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.

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???

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

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.

Go to forum: DriverPack Mass Storage

4 Reply by cfp

(17 replies, posted in DriverPack Mass Storage)

Problem SOLVED!

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

[AM]
ms_count=2
ms_1_deviceName="AMD PCI Bus Master IDE"
ms_1_tag="amdbusdr"
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="amdide"   
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

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

Go to forum: DriverPack Mass Storage

5 Reply by cfp

(17 replies, posted in DriverPack Mass Storage)

Thanks! for the plugin fix back at ubcd4win.com forum.

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.

Go to forum: DriverPack Mass Storage

6 Reply by cfp

(17 replies, posted in DriverPack Mass Storage)

So I try lots of things and finally got past the STOP error by deleting just the single line ' PCI\VEN_1022&DEV_7409="amdide" ' from the TXTSETUP.SIF file. Then all OK.

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.

Go to forum: DriverPack Mass Storage

7 Reply by cfp

(17 replies, posted in DriverPack Mass Storage)

Answers to above questions:

did you use nlite or somthing to remove drivers from your source?

Answer --  No nlite or somthing, no did not remove drivers from source XP service pack 3 slip-streamed.  UBCD4win v3.50 straight from the download. If I remove the MassStorage plugin no problems, If I use the mass-storage plugin (MassStorage, 8.05) from UBCD4Win v3.22  NO problems, boots fine. If I use the current DriverPacks BASE v8.12.4 with v9.01 - DriverPack MassStorage on UBCD4Win v3.22 the STOP error DOES occur.

If you need more or I missed something you'd like to know I try to post tomorrow morning.

Go to forum: DriverPack Mass Storage

8 Topic by cfp

(17 replies, posted in DriverPack Mass Storage)

Original title:Stop: 0x0000007b (0xfa2f3528, 0xc0000034, 0x00000000, 0x00000000)

Have bean VERY busy, many prodjects going on, but here is Hardware of the troublemaker;
--- SpaceWalker-Shuttle-AI61-motherboard ---

Blue screen
STOP: 0X0000007B (0XFA2F3528, 0XC0000034, 0X00000000, 0X00000000)

BART's/UBCD4WIn
is fine with older DriverPacks, no crashes on boot at all.

RAID Devices
============
PCI\VEN_1022&DEV_7409&SUBSYS_00000000&REV_07\3&61AAA01&0&39
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_1022&DEV_7409&SUBSYS_00000000&REV_07
PCI\VEN_1022&DEV_7409&SUBSYS_00000000
PCI\VEN_1022&DEV_7409&REV_07
PCI\VEN_1022&DEV_7409
PCI\VEN_1022&DEV_7409&CC_01018A
PCI\VEN_1022&DEV_7409&CC_0101
Compatible ID's:
PCI\VEN_1022&CC_01018A
PCI\VEN_1022&CC_0101
PCI\VEN_1022
PCI\CC_01018A
PCI\CC_0101
1 matching device(s) found.


Blue screen
STOP: 0X0000007B (0XFA2F3528, 0XC0000034, 0X00000000, 0X00000000)

BART's/UBCD4WIn
is fine with older DriverPacks, no crashes on boot at all.

note: aside from the hard-drive Controller problem there is also a problem with
the keyboard if use the standard keyboard which crashes after a few minutes
of use???? , so must use USB keyboard, Also about 1 in 10 XP boots will reboot/crash
during reboots but other wise is a stable machine once booted to XP.

BART's/UBCD4WIn
is fine with older DriverPacks, no crashes on boot at all, but keyboard problem still exists.

===========
PCI Devices
===========
PCI\VEN_1002&DEV_4754&SUBSYS_47541002&REV_41\3&61AAA01&0&48 : ATI Technologies Inc. 3D RAGE II PCI
PCI\VEN_1013&DEV_6005&SUBSYS_00000000&REV_01\3&61AAA01&0&58 : Crystal SoundFusion™ CS4281 WDM Audio
PCI\VEN_1022&DEV_7006&SUBSYS_00000000&REV_25\3&61AAA01&0&00 : PCI standard host CPU bridge
PCI\VEN_1022&DEV_7007&SUBSYS_00000000&REV_01\3&61AAA01&0&08 : AMD-751 Processor to AGP Controller
PCI\VEN_1022&DEV_7408&SUBSYS_00000000&REV_01\3&61AAA01&0&38 : PCI standard ISA bridge
PCI\VEN_1022&DEV_7409&SUBSYS_00000000&REV_07\3&61AAA01&0&39 : Standard Dual Channel PCI IDE Controller
PCI\VEN_1022&DEV_740B&SUBSYS_00000000&REV_03\3&61AAA01&0&3B : AMD-756 Power Management Controller
PCI\VEN_1022&DEV_740C&SUBSYS_00000000&REV_06\3&61AAA01&0&3C : AMD 756 PCI to USB Open Host Controller
8 matching device(s) found.

===========
USB Devices
===========
USB\ROOT_HUB\4&21A4534D&0 : USB Root Hub
USB\VID_049F&PID_000E\5&D84BCF5&0&1 : USB Composite Device
USB\VID_049F&PID_000E&MI_00\6&8421312&2&0000 : USB Human Interface Device
USB\VID_049F&PID_000E&MI_01\6&8421312&2&0001 : USB Human Interface Device
USB\VID_07A6&PID_8511\0001 : ADMtek ADM8511 USB To Fast Ethernet Converter
5 matching device(s) found.

=============
Input Devices
=============
HID\VID_049F&PID_000E&MI_00\7&230B4070&0&0000 : HID Keyboard Device
HID\VID_049F&PID_000E&MI_01&COL01\7&FDB2432&0&0000 : HID-compliant consumer control device
HID\VID_049F&PID_000E&MI_01&COL02\7&FDB2432&0&0001 : HID-compliant device
HID\VID_049F&PID_000E&MI_01&COL03\7&FDB2432&0&0002 : HID-compliant consumer control device
HID\VID_049F&PID_000E&MI_01&COL04\7&FDB2432&0&0003 : HID-compliant device
HID\VID_049F&PID_000E&MI_01&COL05\7&FDB2432&0&0004 : HID-compliant device
HID\VID_049F&PID_000E&MI_01&COL06\7&FDB2432&0&0005 : HID-compliant device
HID\VID_049F&PID_000E&MI_01&COL07\7&FDB2432&0&0006 : HID-compliant device
HID\VID_049F&PID_000E&MI_01&COL08\7&FDB2432&0&0007 : HID-compliant device
9 matching device(s) found.

============
ACPI Devices
============
ACPI\AUTHENTICAMD_-_X86_FAMILY_6_MODEL_4\_0 : AMD Athlon™ Processor
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\PNP0000\4&2DD9AEC8&0 : Programmable interrupt controller
ACPI\PNP0100\4&2DD9AEC8&0 : System timer
ACPI\PNP0200\4&2DD9AEC8&0 : Direct memory access controller
ACPI\PNP0400\1 : Printer Port (LPT1)
ACPI\PNP0501\1 : Communications Port (COM1)
ACPI\PNP0501\2 : Communications Port (COM2)
ACPI\PNP0700\4&2DD9AEC8&0 : Standard floppy disk controller
ACPI\PNP0800\4&2DD9AEC8&0 : System speaker
ACPI\PNP0A03\2&DABA3FF&0 : PCI bus
ACPI\PNP0B00\4&2DD9AEC8&0 : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0 : System board
ACPI\PNP0C02\1 : Motherboard resources
ACPI\PNP0C04\4&2DD9AEC8&0 : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\PNP0F13\4&2DD9AEC8&0 : PS/2 Compatible Mouse
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : Advanced Configuration and Power Interface (ACPI) PC
19 matching device(s) found.

============
HDA Audio
============
No matching devices found.

============
RAID Devices
============
PCI\VEN_1022&DEV_7409&SUBSYS_00000000&REV_07\3&61AAA01&0&39
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_1022&DEV_7409&SUBSYS_00000000&REV_07
PCI\VEN_1022&DEV_7409&SUBSYS_00000000
PCI\VEN_1022&DEV_7409&REV_07
PCI\VEN_1022&DEV_7409
PCI\VEN_1022&DEV_7409&CC_01018A
PCI\VEN_1022&DEV_7409&CC_0101
Compatible ID's:
PCI\VEN_1022&CC_01018A
PCI\VEN_1022&CC_0101
PCI\VEN_1022
PCI\CC_01018A
PCI\CC_0101
1 matching device(s) found.

Go to forum: DriverPack Mass Storage

9 Topic by cfp

(2 replies, posted in Feedback and Support - DriverPacks Base)

see http://bugtracker.driverpacks.net/view.php?id=515

I have found several bugs in DP_Install_Tool.cmd
from the BASE -- DPs_BASE_8124.exe

I have a new version I wrote without bugs (I hope...)
that also has more advanced messaging and logging with log backups

Feel free to use it, post it, or modify

download the re-write at: http://computerfixpro.com/DP_Install_Tool-SRS-new.zip


Hope this will be a help to others who want to use Stand-Alone.

Can't remember all of the bugs of original but this is what
I can remember:

line 26 --> %LOG should be %LOG%

line 64 --> `type F:\WINDOWS\DPINST.log` should be `type %SystemRoot%\DPINST.log`

also noted: DPsFnshr.exe deletes C:\TMP directory without WARNING

Other bugs -- ???

Go to forum: Feedback and Support - DriverPacks Base