-
September 6th, 2007, 11:40 AM
#16
Let me say something else about the drivers as well...
This is fasttrak.inf for w2k:
; FASTTRAK.INF
; Copyright 2001 Promise Technology, Inc.
[Version]
CatalogFile=Fasttrak.cat
signature="$CHICAGO$"
Class=SCSIAdapter
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
Provider=%PROMISE%
DriverVer=09/19/2001, 2.0.0.18
[DestinationDirs]
DefaultDestDir = 12 ; DIRID_DRIVERS
MoveMiniPort.NT = 12;
[ControlFlags]
[Manufacturer]
%Promise%=Promise
[Promise]
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_4D331 05A
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_80421 043
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0001 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0011 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0021 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0031 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0041 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0051 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0061 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0071 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0081 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0091 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00A1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00B1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00C1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00D1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00E1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00F1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_0065A 0A0
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_30011 695
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_321D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_330D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_337D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_366D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_369D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_380D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_394D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_90011 509
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_07011 0FD
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_08661 6F3
[FasttrakPCI100.NT]
CopyFiles=MoveMiniPort.NT
Reboot
[FasttrakPCI100.NT.Services]
AddService = fasttrak, 2, FasttrakPCI_Service_Inst, Miniport_EventLog_Inst
[FasttrakPCI_Service_Inst]
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 0 ; SERVICE_BOOT_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\fasttrak.sys
LoadOrderGroup = SCSI Miniport
AddReg = pnpsafe_pci_addreg
[pnpsafe_pci_addreg]
HKR, "Parameters\PnpInterface", "5", 0x00010001, 0x00000001
[Miniport_EventLog_Inst]
AddReg = Miniport_EventLog_AddReg
[Miniport_EventLog_AddReg]
HKR,,EventMessageFile,%REG_EXPAND_SZ%,%IOLOGMSGDLL %
HKR,,TypesSupported,%REG_DWORD%,7
[MoveMiniPort.NT]
Fasttrak.sys
[SourceDisksFiles]
Fasttrak.inf = 1
Fasttrak.sys = 1
[SourceDisksNames]
1 = %DISKNAME1%,,,,
2 = %DISKNAME2%,,,,
[strings]
Promise="Promise Technology"
PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc=" Win2000 Promise FastTrak100 (tm) Lite Controller"
REG_EXPAND_SZ=0x00020000
REG_DWORD=0x00010001
IOLOGMSGDLL=%11%"\IoLogMsg.dll"
DISKNAME1="Promise FastTrak Family Driver Diskette"
DISKNAME2="Windows system"
NAME="PtiCache"
-
September 6th, 2007, 11:41 AM
#17
Here is fasttrak.inf for XP:
; FASTTRAK.INF
; Copyright 2001 Promise Technology, Inc.
[Version]
CatalogFile=Fasttrak.cat
signature="$CHICAGO$"
Class=SCSIAdapter
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
Provider=%PROMISE%
DriverVer=09/19/2001, 2.0.0.18
[DestinationDirs]
DefaultDestDir = 12 ; DIRID_DRIVERS
MoveMiniPort.NT = 12;
[ControlFlags]
[Manufacturer]
%Promise%=Promise
[Promise]
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_4D331 05A
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_80421 043
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0001 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0011 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0021 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0031 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0041 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0051 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0061 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0071 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0081 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B0091 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00A1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00B1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00C1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00D1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00E1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_B00F1 458
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_0065A 0A0
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_30011 695
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_321D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_330D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_337D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_366D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_369D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_380D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_394D1 462
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_90011 509
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_07011 0FD
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc% =FasttrakPCI100,PCI\VEN_105A&DEV_0D30&SUBSYS_08661 6F3
[FasttrakPCI100.NT]
CopyFiles=MoveMiniPort.NT
Reboot
[FasttrakPCI100.NT.Services]
AddService = fasttrak, 2, FasttrakPCI_Service_Inst, Miniport_EventLog_Inst
[FasttrakPCI_Service_Inst]
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 0 ; SERVICE_BOOT_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\fasttrak.sys
LoadOrderGroup = SCSI Miniport
AddReg = pnpsafe_pci_addreg
[pnpsafe_pci_addreg]
HKR, "Parameters\PnpInterface", "5", 0x00010001, 0x00000001
[Miniport_EventLog_Inst]
AddReg = Miniport_EventLog_AddReg
[Miniport_EventLog_AddReg]
HKR,,EventMessageFile,%REG_EXPAND_SZ%,%IOLOGMSGDLL %
HKR,,TypesSupported,%REG_DWORD%,7
[MoveMiniPort.NT]
Fasttrak.sys
[SourceDisksFiles]
Fasttrak.inf = 1
Fasttrak.sys = 1
[SourceDisksNames]
1 = %DISKNAME1%,,,,
2 = %DISKNAME2%,,,,
[strings]
Promise="Promise Technology"
PCI\VEN_105A&DEV_0D30&SUBSYS_4D39105A.DeviceDesc=" WinXP Promise FastTrak100 (tm) Lite Controller"
REG_EXPAND_SZ=0x00020000
REG_DWORD=0x00010001
IOLOGMSGDLL=%11%"\IoLogMsg.dll"
DISKNAME1="Promise FastTrak Family Driver Diskette"
DISKNAME2="Windows system"
-
September 6th, 2007, 11:48 AM
#18
Driver Terrier
You said W2K is not a valid upgrade path for 2K3 in post #12. Here is the MS document on upgrade paths
Never, ever approach a computer saying or even thinking "I will just do this quickly."
-
September 6th, 2007, 12:12 PM
#19
Driver Terrier
So what did you want to say about the drivers... apart from posting the infs again?
Do you still have a problem with the driver not copying?
Never, ever approach a computer saying or even thinking "I will just do this quickly."
-
September 6th, 2007, 12:57 PM
#20
2k3 Is not in my upgrade path. I have 2k SBS and 2k3 Enterprise.
The first time I posted txtsetup.oem which is what the installer reads. That second round are the .inf files. All I am saying is that they are identical. If I post the one from NT there are only a few registry keys different.
I am only suggesting 2k3 might need an additional entry in the .inf file to create an additional key somewhere and I posted it for anyone that might have the same controller working on 2k3 that would be able to post the following registry keys:
HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Control\Class\%Cl assGUID%\0000
ClassGUID is defined in .inf
or
HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\%PCI\Ven _...%
%PCI\Ven_...% defined in .inf
or
HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Enum\Services\Fas ttrak
add services defined in .inf
-
September 6th, 2007, 01:11 PM
#21
Driver Terrier
Originally Posted by Wizard of Wiring
2k3 Is not in my upgrade path. I have 2k SBS and 2k3 Enterprise.
Ah, so far you have only said 2k and 2k3, no mention of SBS.
But whether there is a registry key missing or not is not the question is it? The reported error is that it cannot copy fasttrak.sys. The error is quite specific. If there was a problem with the registry it would generate a different error.
Never, ever approach a computer saying or even thinking "I will just do this quickly."
-
September 6th, 2007, 01:28 PM
#22
Originally Posted by NooNoo
Do you still have a problem with the driver not copying?
The whole purpose of the thread or anything else I have posted in this thread is to fix the problem in post #1. Which is covered in this article:
http://support.microsoft.com/kb/314859
I am already working around the problem by installing 2k3 on an ide drive and creating my own resolution based on this article:
http://support.microsoft.com/kb/314082/
I installed XP because I wanted to know where the miniport driver is installed and have a snapshot of the installed registry keys. If you actually read that article you will see it is not a resolution for fasttrak, it was only intended for natively supported ide controllers. But I see no reason why I can't apply the same concept to my controller.
When I am done all I want to have is 2k3 installed and a clean install backup image that I can reuse in the event I run into any problems installing service packs or other updates like .net. This is mainly because I do not install this crap everyday and if there is a problem with something I am not going to know about it until I install it and see my event log populate.
-
September 6th, 2007, 02:31 PM
#23
Driver Terrier
Oh right, you are attempting to fix that which has defeated highly qualified and experienced techs. OK, I will leave you to blog your progress.
Never, ever approach a computer saying or even thinking "I will just do this quickly."
-
September 7th, 2007, 01:24 AM
#24
Originally Posted by NooNoo
Oh right, you are attempting to fix that which has defeated highly qualified and experienced techs. OK, I will leave you to blog your progress.
I would be nice to have a highly qualified and experienced tech to correspond with. However, I will continue by 'blogging' my way to your enlightenment.
Getting back to pertinent information I have been able to make good use of my xp home and pro installations and have analyzed a few log files.
[SetupAPI Log]
OS Version = 5.1.2600 Service Pack 2
Platform ID = 2 (NT)
Service Pack = 2.0
Suite = 0x0000
Product Type = 1
Architecture = x86
[2007/09/04 23:35:46 276.1]
...several lines then...
[2007/09/04 23:37:12 276.137]
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#E361 An unsigned or incorrectly signed file "C:\WINDOWS\OemDir\Fasttrak.cat" will be installed (Policy=Ignore). Error 0x80092003: An error occurred while reading or writing to a file.
Could it be that the default policy for 2k3 is not ignore? Maybe I was just typing yank when I suggested a WHCL problem. Anyway continuing on further in the log file...
[2007/09/04 23:38:28 276.1104 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_105a&dev_0d30&subsys_4d33105a&rev_02,pci\v en_105a&dev_0d30&subsys_4d33105a,pci\ven_105a&dev_ 0d30&cc_010400,pci\ven_105a&dev_0d30&cc_0104
#-018 Searching for compatible ID(s): pci\ven_105a&dev_0d30&rev_02,pci\ven_105a&dev_0d30 ,pci\ven_105a&cc_010400,pci\ven_105a&cc_0104,pci\v en_105a,pci\cc_010400,pci\cc_0104
#-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup
#I022 Found "PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A" in C:\WINDOWS\inf\oem0.inf; Device: "WinXP Promise FastTrak100 (tm) Lite Controller"; Driver: "WinXP Promise FastTrak100 (tm) Lite Controller"; Provider: "Promise Technology"; Mfg: "Promise Technology"; Section name: "FasttrakPCI100".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [FasttrakPCI100.NT]. Rank: 0x00008001. Effective driver date: 09/19/2001.
#-147 Loading class installer module for "RAID Controller".
#E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\SysSetup.Dll" for driver "RAID Controller" will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-148 Loading coinstaller modules for "RAID Controller".
#E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\SysSetup.Dll" for driver "RAID Controller" will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [FasttrakPCI100] in "c:\windows\inf\oem0.inf".
#I320 Class GUID of device remains: {4D36E97B-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A&REV_02\3&61 AAA01&0&88".
#E360 An unsigned or incorrectly signed file "c:\windows\inf\oem0.inf" for driver "WinXP Promise FastTrak100 (tm) Lite Controller" will be installed (Policy=Ignore). Error 1168: Element not found.
#-024 Copying file "C:\WINDOWS\OemDir\Fasttrak.sys" to "C:\WINDOWS\system32\DRIVERS\Fasttrak.sys".
#E360 An unsigned or incorrectly signed file "C:\WINDOWS\OemDir\Fasttrak.sys" for driver "WinXP Promise FastTrak100 (tm) Lite Controller" will be installed (Policy=Ignore). Error 1168: Element not found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-148 Loading coinstaller modules for "WinXP Promise FastTrak100 (tm) Lite Controller".
#E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\SysSetup.Dll" for driver "WinXP Promise FastTrak100 (tm) Lite Controller" will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [FasttrakPCI100.NT.Interfaces] from "c:\windows\inf\oem0.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A&REV_02\3&61 AAA01&0&88".
#W102 Device "PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A&REV_02\3&61 AAA01&0&88" required reboot: "Reboot" in section: [FasttrakPCI100.NT].
#I121 Device install of "PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A&REV_02\3&61 AAA01&0&88" finished successfully.
There are several more entries in the log but its too long to post here.
-
September 7th, 2007, 01:28 AM
#25
Now on to setupact.log
GUI mode Setup has started.
several lines then...
------------------------------------------------------------------------
Volume: C:\
Device Path: \\?\scsi#disk&ven_promise&prod_2+0_stripe#raid0&re v_1.10#4&f5ac60c&0&000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
1. Promise 2+0 Stripe/RAID0 SCSI Disk Device - \Device\Scsi\Fasttrak1Port2Path0Target0Lun0
HardwareId:
SCSI\DiskPromise_2+0_Stripe/RAID01.10
SCSI\DiskPromise_2+0_Stripe/RAID0
SCSI\DiskPromise_
SCSI\Promise_2+0_Stripe/RAID01
Promise_2+0_Stripe/RAID01
GenDiskSCSI\DiskPromise_2+0_Stripe/RAID01.10
Location: Bus Number 0, Target ID 0, LUN 0
2. RAID Controller - \Device\NTPNP_PCI0009
HardwareId:
PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A&REV_02
PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A
PCI\VEN_105A&DEV_0D30&CC_010400
PCI\VEN_105A&DEV_0D30&CC_0104PCI\VEN_105A&DEV_0D30 &SUBSYS_4D33105A&REV_02
Location: PCI bus 0, device 17, function 0
3. HardwareId:
3. ACPI\PNP0A03
3. *PNP0A03ACPI\PNP0A03
PhysicalDeviceObjectName: \Device\0000000c
HardwareId:
ACPI_HAL\PNP0C08
*PNP0C08ACPI_HAL\PNP0C08
5. HardwareId: acpipic_up
----------------------------------------------------------------------
several more lines then...
NetSetup: Status of InitFromAnswerFile: 0x0
C:\WINDOWS\OemDir\Fasttrak.sys was copied to C:\WINDOWS\system32\DRIVERS\Fasttrak.sys.
-
September 7th, 2007, 01:31 AM
#26
Now on to setup.log
[Paths]
TargetDirectory = "\WINDOWS"
TargetDevice = "\Device\Harddisk0\Partition1"
SystemPartitionDirectory = "\"
SystemPartition = "\Device\Harddisk0\Partition1"
[Signature]
Version = "WinNt5.1"
[Files.SystemPartition]
NTDETECT.COM = "NTDETECT.COM","eee8"
ntldr = "ntldr","48477"
[Files.WinNt]
several lines then...
\WINDOWS\OemDir\oemscs01.inf = "Fasttrak.inf","2cec","\WinXP","Promise FastTrak Family Driver Diskette","\fasttrak"
\WINDOWS\system32\drivers\Fasttrak.sys = "Fasttrak.sys","1f823","\WinXP","Promise FastTrak Family Driver Diskette","\fasttrak"
"\WINDOWS\system32\DRIVERS\Fasttrak.sys"="Fasttrak .sys","1f823"
-
September 7th, 2007, 01:41 AM
#27
Now unfortunately I am not an installation expert and am not able to just look at the log files, compare them to the .inf and setup files and know what is going on. But that doesn't mean I am not capable. I am going to have to do some heavy duty reading but I will point you in the right direction while I am blogging. Here are a couple of links:
Windows Setup and Device Installation Logging
http://www.microsoft.com/whdc/driver.../setupapi.mspx
Troubleshooting Device Installation with the SetupAPI Log File
http://www.microsoft.com/whdc/driver...tupapilog.mspx
NooNoo, maybe will read and comprehend it all before I do and come back and post something brilliant.
-
September 7th, 2007, 01:59 AM
#28
Driver Terrier
Wizard, if you read my posts, you will find that for the most part, I do not get involved in no win scenarios. I do not have the time for projects such as this. You obviously have and I am leaving your posts up in case other people are interested in your project. I would suggest though that if you want people to make comment or contribute in any way to your project, you should take what you consider to be bad comments with better grace than you have so far.
I wish you luck in your endeavour.
Never, ever approach a computer saying or even thinking "I will just do this quickly."
-
September 7th, 2007, 02:49 AM
#29
I can think of plenty of ways to spend my time other than this but it is in my nature to understand the root cause of a problem. For me, it's either create the time to solve it or let my lack of understanding haunt me. I have posted this thread in only two forums. Not because I can't solve a problem. But because I was hoping someone might be able to save me a little time troubleshooting. I have tried to endure and exercise as you say... grace, but after carefully reading each of your replies I felt like you did not actually read my post(s). Bad floppy? Bad partition? Bad driver? I sought out forums where I thought there might be a chance of interacting with people that might already be very familiar topics like setupapi or the installer sdk. After all this is windrivers.com. If my lack of grace is a character flaw that has prevented the caliber of collaberation I have been seeking in this forum, I gracefully exit. Yes, I was a little peeved about the blogging remark as evidenced by my followup post(s). Obviously I felt the .inf and txtsetup.oem files were very pertinent to the discussion. The remark to you specifically in my last post however, was over the top and you should remove it from the thread since I can no longer edit it.
Regards,
Sean
-
September 7th, 2007, 03:20 AM
#30
Driver Terrier
Why troubleshoot, when there is a work around? The caliber of a tech is not necessarily their ability to understand the inner workings of some gadget. A good tech knows about the cost/benefit trade off. Clearly, this is a situation where the cost of the time out weighs the benefit of being able to directly install on to the array.
There are dozens of situations where hardware incompatibility prevents a tech using a favoured solution. Annoying but if this sort of thing is going to haunt you, I think perhaps you ought to consider the serenity prayer. By all means, take it on as a personal project, learn how to read the files and what they do, you might even write a new driver that solves the problem which would be great... but don't be disappointed if people are apparently uninterested in helping you with it.
You are using an old domestic motherboard designed to run raid 0 (+1) which essentially aimed at the gamers market and not designed for a production environment. You wouldn't have this problem if you used a pci raid card that is known to be compatible with 2k3 or a motherboard with onboard raid that is 2k3 compatible.
Never, ever approach a computer saying or even thinking "I will just do this quickly."
Similar Threads
-
By 061070 in forum BIOS/Motherboard Drivers
Replies: 6
Last Post: February 21st, 2002, 03:46 AM
-
By jtestrrixom in forum Hard Drive/IDE/SCSI Drivers
Replies: 6
Last Post: July 24th, 2001, 02:53 PM
-
By BladeRnR in forum BIOS/Motherboard Drivers
Replies: 1
Last Post: May 23rd, 2001, 10:32 PM
-
By Dannigan123 in forum BIOS/Motherboard Drivers
Replies: 1
Last Post: May 3rd, 2001, 08:49 PM
-
Replies: 11
Last Post: April 12th, 2001, 07:42 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks