You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 7 of 10)
Topics by cdob User defined search
Posts found [ 151 to 175 of 232 ]
azcoder wrote:It had 4 drives
Which drives and sizes did you used?
Which mass storage windows drivers did you used in the past?
Did you set EnableBigLBA at Win2k?
azcoder wrote:I used two new SATA drives.
Which drives and sizes do you use now?
azcoder wrote:I downloaded and built UBCD4WIN 3.5 and tried the plugin to write the SATA drivers to the Win2k system, but it did not work.
How did you called fix_hdc? Did you offer proper Win2k source files? Be aware, this won't set EnableBigLBA. Integrate this manually.
azcoder wrote:I downloaded and built a Win2k system with SP4 and all the latest updates using HFSLIP (http://www.vorck.com/windows/2ksp5.html). When booting the install CD, the drive information is incorrect and the installer can not find a valid Win2k partition.
Does this approach set EnableBigLBA at Win2k install CD? Add the setting to setupreg.hiv.
azcoder wrote:============
RAID Devices
============
PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00\3&61AAA01&0&88
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_1002&DEV_4390&SUBSYS_B0021458&REV_00
PCI\VEN_1002&DEV_4390&SUBSYS_B0021458
PCI\VEN_1002&DEV_4390&CC_01018F
PCI\VEN_1002&DEV_4390&CC_0101
Compatible ID's:
PCI\VEN_1002&DEV_4390&REV_00
PCI\VEN_1002&DEV_4390
PCI\VEN_1002&CC_01018F
PCI\VEN_1002&CC_0101
PCI\VEN_1002
PCI\CC_01018F
PCI\CC_0101
PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00\3&61AAA01&0&A1
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_1002&DEV_439C&SUBSYS_50021458&REV_00
PCI\VEN_1002&DEV_439C&SUBSYS_50021458
PCI\VEN_1002&DEV_439C&CC_01018A
PCI\VEN_1002&DEV_439C&CC_0101
Compatible ID's:
PCI\VEN_1002&DEV_439C&REV_00
PCI\VEN_1002&DEV_439C
PCI\VEN_1002&CC_01018A
PCI\VEN_1002&CC_0101
PCI\VEN_1002
PCI\CC_01018A
PCI\CC_0101
2 matching device(s) found.
This is SATA drives at IDE emulation mode. Default 2000 and XP pciide.sys sould support this.
There are no addional mass storage drivers required.
Default Win2k fails at big drives, atapi.sys requires EnableBigLBA.
Addional Win2k drivers maybe nice, to circumvent EnableBigLBA requirement.
mr_smartepants wrote:Not the target system.
This leads to the next idea:
include SaveHWIDs.cmd to a PE. That way there are reports from the target system possible.
Both DriverPacks.net and UBCD4Win benefit from the user reports.
The same user report makes easier understanding.
Do we have permission to include SaveHWIDs.cmd to PE systems, like UBCD4Win?
In addition some RAID drivers use the HardwareID *SCSI*. Can you add *SCSI*?
ECHO RAID Devices >> %Out%
ECHO ============ >> %Out%
DEVCON hwids *CC_01* *Raid* *SCSI*>> %Out%
OverFlow wrote:"Nobody ever clicks the help button"
This leads to a idea:
Add HWID's Tool to DriverPacks BASE.
A user may click: report HWIDS
cheebster wrote:I've got only a WD drive connected to it in Sata, dvd-rom is PATA.
Name: IDE Controller
PCI\VEN_11AB&DEV_6101&CC_0101
PCI\VEN_8086&DEV_3A20&CC_0101
PCI\VEN_8086&DEV_3A26&CC_0101
Which connectors do you use?
Is dvd-rom connected to PCI\VEN_11AB&DEV_6101&CC_0101 device?
DriverPacks use PCI\VEN_11AB&DEV_6101="mv61xx"
Maybe that's the BSOD reason.
D\M\M\MV61XX.INF
[Marvell]
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6101
mv61xxDesc= "Marvell 61xx RAID Controller"
Another strange driver manufacturer:
a generic HarwareId for a RAID controller at IDE mode.
awesomeo wrote:It boots fine on another system I have with an NForce 2, but on the Intel machine, it doesn't load at all. I get a message right away that says:
INF file txtsetup.sif is corrupt or missing, status 8192.
Do you use the same CD? Then there is a hardware failure.
Bad burned media, difficult to read. Try good qualitiy media and use imgburn.
Half broken CD drive. Half broken RAM. Bad cable. Bad capacitors.
I got a BSOD at 0x7e at a ICH7-M, 8086 27C5, in the meatime too.
UBCD4Win does boot to desktop. There is the BSOD Reading and writing data to hard disk.
Removing KR10N.sy_ did resolve this. No more BSOD.
There is a driver conflict between KR10N.sy_ and iastor70.sy_
awesomeo wrote:Intel D925XCV motherboard. It loads to the desktop background with a working mouse, but after that it blue screens with
STOP: 0x0000007E. (0xC0000005, 0xF7D579EF, 0xF8A6D730, 0xF8A6D42C)
There is a possible driver conflict.
KR10N.sy_ and MegaINTL.sy_ are loaded first, iastor70.sy_ are loaded next.
Try a addon plugin\drivers\bts_addon.inf
[Version]
Signature="$Windows NT$"
[PEBuilder]
Name="Driver: addon PnpInterface"
Enable=1
[DelLine]
;possible conflict iastor70.sy_
"txtsetup.sif", "SCSI.LOAD", "KR10N"
"txtsetup.sif", "SCSI.LOAD", "MegaINTL"
cfp wrote:Problem SOLVED!
Thank's for testing.
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
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.
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"
Good idea.
No STOP errors with UBCD4win v3.50, v3.22 or with XP service pack 3 slip-streamed.
That's nice results.
OverFlow wrote:[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.
OverFlow wrote:I also think the wrong file is referenced
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,
cfp wrote:--- 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
[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_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"
D\M\AM\amdeide.ínf
[AMD_HDC]
%PCI\VEN_1022&DEV_7409.DeviceDesc%=amdbusdr_Inst, PCI\VEN_1022&DEV_7409 ; AMD
%PCI\VEN_1022&DEV_7411.DeviceDesc%=amdbusdr_Inst, PCI\VEN_1022&DEV_7411 ; AMD
%PCI\VEN_1022&DEV_7441.DeviceDesc%=amdbusdr_Inst, PCI\VEN_1022&DEV_7441 ; AMD
%PCI\VEN_1022&DEV_7469.DeviceDesc%=amdbusdr_Inst, PCI\VEN_1022&DEV_7469 ; AMD
%*PNP0600.PriDeviceDesc% = Amd_Inst_primary, AMD_Primary_IDE_Channel ; Primary Channel
%*PNP0600.SecDeviceDesc% = Amd_Inst_secondary, AMD_Secondary_IDE_Channel ; Secondary Channel
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.
cfp wrote: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.
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.
@dangerfreak
Can you clarify:
do you use drivers
nForce_5.10_WinXP2K_WHQL_international\Ethernet\
or drivers
nForce_5.10_WinXP2K_WHQL_international\Ethernet\PreNRM\Win2K\
nForce_5.10_WinXP2K_WHQL_international\Ethernet\PreNRM\WinXP\
ef wrote:So what's next step: is it expected an updated MassStorage DP?
Well, next step, next question: Is the FSC OEM driver compatible with old Promise driver?
Does anybody use a Promise S150 SX4 and Promise drivers 05/20/2004, 2.00.00.25?
Can you try a FSC OEM fastsx.sys ver. 2.0.64.23? Do you get access to hard disk still?
ef wrote:Or is there a working way to both enable MassStorage plug-in and add myself this driver in the "Drivers" folder before building the boot disk?
In the meantime let's assume driver is compatible.
Create a file UBCD4Win\plugin\Drivers\FSC_FastTrakS150SX4\FSC_FastTrakS150SX4.inf
;PE Builder v3 plug-in INF file
[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="Driver: FSC FastTrak S150 SX4 - Bâshrat the Sneaky MassStorage addon"
Enable=1
[SourceDisksfiles.3790] ;2003
;cab compressed file: makecab.exe fastsx.sys
files\FASTSX.SY_=4,FASTSXK3.SY_,3 ;v2.0.64.23
Copy a cab compressed file fastsx.sy_ to UBCD4Win\plugin\Drivers\FSC_FastTrakS150SX4\files\
ef wrote:It works fine: Device management shows Promise 4 Disk RAID5 SCSI Disk Device (although an unknown RAID controller with the Promise HWID is still listed), Disk Management shows logical volumes and I can browse disks content.
That's nice, RAID is available.
Ignore the device manager, mass storage drivers are loaded at textmode.
I'm convinced now: only the updated OEM fastsx.sys support your hardware.
The current Promise distributed driver dosn't support your hardware.
probably because I forgot adding also the txtsetup.oem file
Yes, the txtsetup.oem is required in that case.
ef wrote:- Windows Promise FastTrak S150 SX4 (tm) Controller
HWID PCI\VEN_105A&DEV_6622&SUBSYS_6622105A&REV_01\4&5A988DE&0&28F0
Driver Promise Technology 27/09/2004 ver. 2.0.64.23
Promise offers FastTrak S150 SX4 Windows Driver 2.00.0.25 6/15/2004
http://www.promise.com/support/download … amp;os=100
Driverpacks does use this drivers.
You use Driver Promise Technology 27/09/2004 ver. 2.0.64.23
That's strange. Let's investigate:
FSC does use a fastsx.sys ver. 2.0.64.23.
There are two different FastTrak S150 SX4:
Promise FastTrak S150 SX4 (tm) Controller X
Promise FastTrak S150 TX4 SATA RAID Controller (PDC20319)
http://download.ts.fujitsu.com/server/D … exFile.htm
Does FSC use a Promise OEM driver, not distributed by Promise?
Try FSC OEM Promise drivers:
Device Driver - PRIMERGY TX150 SATA
Title: PROMISE FASTTRAK S150 TX4 SOFTWAREKIT 3.10
Date: 09.12.2004
http://support.ts.fujitsu.com/download/ … 42D957337D
Device Driver - PRIMERGY TX150 SATA
Title: Driver (SWK 4.03)
Date: 10.04.2006
http://support.ts.fujitsu.com/download/ … D27D059654
Edited:
At second glance: TX4 HardwareID dosn't match SX4.
Most likely the driver fails.
@ef
Do you have a download URL for Driver Promise Technology 27/09/2004 ver. 2.0.64.23 ?
ef wrote:What else could I try? Any help appreciated.
Do you run Windows 2003 at Promise S150 SX4 machine?
Which driver does your running windows use?
Do you have a floppy drive?
Can you load drivers at F6 floppy?
However I wonder: is there another reason?
Do you use a busmater capable PCI slot?
ef wrote:Promise FastTrak S150 SX4:even with W2k3Sp2 as source, the attached disks aren't found as previously reported using WinXpSp3. In the boot disk System event log, I have the following errors:
- Source fastsxk3, Event Id 4, Description: "The description for Event ID ( 4 ) in Source (fastsxk3) cannot be found.
This event log message reminds to PnpInterface at nvgst.sys.
Strange:
Promise txtsetup.oem dosn't set PnpInterface.
And fastsy.inf does set PnpInterface.
There are used different driver names: fastsx.sys and fastsxk3.sys.
Adjust previous plugin.
[Version]
Signature="$Windows NT$"
[PEBuilder]
Name="Driver: addon PnpInterface"
Enable=1
[SetupReg.AddReg]
0x4, "ControlSet001\Services\3wareDrv\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\3wDrv100\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvgts\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvgts5\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvgts6\Parameters\PnpInterface", "5", 0x1
[SetupReg.AddReg.2600] ;XP
0x4, "ControlSet001\Services\FastSx\Parameters\PnpInterface", "5", 0x1
[SetupReg.AddReg.3790] ;2003
0x4, "ControlSet001\Services\FastSxK3\Parameters\PnpInterface", "5", 0x1
Regarding the suggested test of creating a UBCD4WIN disk with only Promise FastTrak S150 SX4 drivers, what should be the procedure?
http://www.nu2.nu/pebuilder/help/english/drivers.htm
However, this won't include PnpInterface. Most likely this won't solve the problem.
Try the above plugin first.
ef wrote:I updated to UBCD4WIN 3.50, WinXpSP3 as source, Base 8.12.4, MassStorage DP 9.03r1.
the x:\i386\system32\vds.exe file is missing. Could it be the cause of my issue?
Does XP contains vds.exe? What about 2003 source files?
Well I don't pocess a FastTrak S150 SX4, can't test and can't answer that.
As for a possible driver conflicts:
Create a testing UBCD4WIN, include as less mass storage drivers as possible, add Promise FastTrak S150 SX4 only.
SmallAnt1976 wrote:id = "PCI\VEN_10DE&DEV_03F6", "nvgts"
Do you use driver nvgts.sys?
Try Post #4 from http://forum.driverpacks.net/viewtopic.php?id=3638
@Larryb
Do you require hotfix KB943545?
MS offers to download KB943295
http://support.microsoft.com/kb/943295
stefan7 wrote:how can i be 100% sure that my motherboard supports ahci ?in the manual it dosent say
Try all BIOS settings.
Watch hardwareIDs:
PCI\VEN_8086&CC_0106 indicates Intel AHCI mode.
http://www.msfn.org/board/index.php?s=& … p;p=846625
There is NO CC_0101 AHCI mode at linked thread.
BIOS may disable AHCI mode.
Ask the motherboard manufacturer about AHCI mode.
JakeLD wrote:From QLogic web site:
# For Windows Server 2003 SP2, you must also install Microsoft fixes KB932755 and KB939315 (or later).
# For Windows Server 2003 SP1, you must also install Microsoft fixes KB932755 and KB939315 (or later).
I will verify the sys file
Good find, thanks.
I get:
2003 SP1 QL2300.SYS 9.0.0.2 is a scsiport.sys child device.
2003 SP2 QL2300.SYS 9.0.0.2 is a scsiport.sys child device. That's The same version.
QL2003.SYS 9.1.7.18 is a storport.sys child device.
A manufactuer changed the driver model, but keep the same file name.
2003 SP1:
storport.sys 5.2.3790.1830 dosn't support QL2300.SYS 9.1.7.18.
Hence the missing or corrupt.
A updated storport.sys is required.
KB932755 contains a storport.sys 5.2.3790.2880.
KB939315 contains a storport.sys 5.2.3790.2979.
Booting does work, no more missing ql2300.sys.
2003 SP2:
Default storport.sys 5.2.3790.3959 does support QL2300.SYS 9.1.7.18.
Booting does work, no missing ql2300.sys.
KB932755 contains a storport.sys 5.2.3790.4021.
KB939315 contains a storport.sys 5.2.3790.4121 too.
It maybe a nice idea to integrate storport.sys 5.2.3790.4121 to 2003 SP2.
@OverFlow
Yes, nvgts.sys is one of these PnpInterface driver.
I made a assumption:
add PnpInterface to all scsiport.sys and storport.sys device drivers.
Not verified at real hardware. Should work. No hardware to test.
Part of a batch
findstr.exe /m /I "scsiport.sys storport.sys" "%Target%\%%b.%%c" && (
reg.exe add "%Services%\%%b\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1 )
@kambing
Try run setPnpInterfaceNvgts.cmd at \I386 directory:
copy setupreg.hiv setupreg.hiv.%random%.sav
reg.exe unload HKLM\loaded_SYSTEM
reg.exe load HKLM\loaded_SYSTEM setupreg.hiv
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts5\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts6\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts7\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1
reg.exe unload HKLM\loaded_SYSTEM
Rodommoc wrote:For some reason the DLL & INF are not being copied during BartPE build.
That's fine. A massstorage driver dosn't require *.inf or *.dll at BartPE.
Also ULSATA2.sys new version does not work.
I understand: the new driver dosn't support old hardware.
I can manually copy the 3 files after the BartPE build then use Bart PE to create the ISO.
Can you try again, downgrade ULSATA2.sys only. Do you get acess to TX4302?
Question may relate to http://www.msfn.org/board/index.php?s=& … p;p=832507
Base does rename txtsetup.sif to txtsetup.org. A new file txtsetup.sif file is created.
Base does rename a existing winnt.sif to winnt.org. A new file winnt.sif file is created.
Search for *.org. There are more files renamed.
Approach is hard link friendly.
deadbug wrote:So does DriverPacks currently rewrite any files?
I don't know about editing existing files.
blankmonkey wrote:The system hangs right at the start of the white dos progress bar, is it possible this is not a driver issue?
Basic hardware cause hang too.
Half broken cable can hang too.
Strange partitions, non windows default, can cause hang too.
Press F7 at F6 message to disable ACPI.
Posts found [ 151 to 175 of 232 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.022 seconds, 5 queries executed ]