MSFN Forum: Rain Drivers Installation - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Rain Drivers Installation Rate Topic: -----

#1 User is offline   bagofbones 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 17-February 04

Posted 08 March 2004 - 12:24 PM

I am trying to install drivers for adaptec scsi raid 2015S. The original TXTSETUP file is as follows:
  • [SourceDisksFiles]
  • dpti2o.sys = 1,,,,,,4_,4,1,,,1,4
  • [HardwareIdsDatabase]
  • PCI\VEN_1044&DEV_A501&SUBSYS_C0471044 = "dpti2o"
  • PCI\VEN_1044&DEV_A501&SUBSYS_C03C1044 = "dpti2o"
  • PCI\VEN_1044&DEV_A501&SUBSYS_C05A1044 = "dpti2o"
  • [SCSI.LOAD]
  • dpti2o = dpti2o.sys,4
  • [SCSI]
  • dpti2o = "Adaptec 2000S/3000S Ultra160 SCSI RAID Controller"
Unfortunately , it does not work. I noticed that in driver.cab there is a dpti2o.sys file. But for some reason it is not the driver file for my machine. I downloaded the drivers , put them under I386, and changed TXTSETUP.SIF as follows:
  • [SourceDisksFiles]
  • dpti2o.sys = 1,,,,,,4_,4,1,,,1,4
  • [HardwareIdsDatabase]
    PCI\VEN_1044&DEV_A501&SUBSYS_C0011044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0021044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0031044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0041044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0051044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C00A1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C00B1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C00C1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C00D1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C00E1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C00F1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0141044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0151044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0161044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C01E1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C01F1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0201044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0211044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0281044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0291044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C02A1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C03C1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C03D1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C03E1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0461044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0471044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0481044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0501044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0511044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0521044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C05A1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C05B1044 = "dpti2o"
    PCI\VEN_1044&DEV_A511&SUBSYS_C05F1044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0641044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0651044 = "dpti2o"
    PCI\VEN_1044&DEV_A501&SUBSYS_C0661044 = "dpti2o"
    PCI\VEN_1044&DEV_A511&SUBSYS_C0321044 = "dpti2o"
    PCI\VEN_1044&DEV_A511&SUBSYS_C0331044 = "dpti2o"
    PCI\VEN_1044&DEV_A511&SUBSYS_C0661044 = "dpti2o"
    PCI\VEN_1044&DEV_A511&SUBSYS_C0341044 = "dpti2o"
    PCI\VEN_1044&DEV_A511&SUBSYS_C0351044 = "dpti2o"
  • [SCSI.LOAD]
  • dpti2o = dpti2o.sys,4
  • [SCSI]
  • dpti2o = "Adaptec I2O RAID Adapters for 32bit Windows 2000, XP, & 2003"
But it still does not work. Could any one tell me what is wrong?


#2 User is offline   bagofbones 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 17-February 04

Posted 08 March 2004 - 12:26 PM

Should be "Raid Drivers Installation". Sorry about that.

#3 User is offline   Alanoll 

  • CODE tags people, CODE tags!
  • Group: Patrons
  • Posts: 5,496
  • Joined: 25-September 03

Posted 08 March 2004 - 01:37 PM

you could try to call it something else.

like rename the driver as it might get overwritten with the one from driver.cab.

and try changing
dpti2o.sys = 1,,,,,,4_,4,1,,,1,4
to
dpti2o.sys = 1,,,,,,3_,4,1

i do believe that you'll also have to makecab your dpti20.sys file. Couldn't hurt if you had both :)

#4 User is offline   bagofbones 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 17-February 04

Posted 08 March 2004 - 01:54 PM

Thank you very much. If I put dpti2o.sys in I386, is it necessary to rename it as dpti2o.sy_? Actually, I find another dpti2o.sy_ that comes with original XP installation package. Thanks a lot.

#5 User is offline   Alanoll 

  • CODE tags people, CODE tags!
  • Group: Patrons
  • Posts: 5,496
  • Joined: 25-September 03

Posted 08 March 2004 - 01:59 PM

the _ is not because of renaming, but because of the makecab command

at a command prompt type
makecab dpti20s.sys
and you'll get your .sy_ file.

copy that to your i386 folder.

#6 User is offline   bagofbones 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 17-February 04

Posted 08 March 2004 - 02:18 PM

Do you mean that I should make dpti2o.sy_ file by makecab command and replace the old dpti2o.sy_ with the new one ? I think the original dpti2o.sy_ in I386 does not work.

#7 User is offline   Alanoll 

  • CODE tags people, CODE tags!
  • Group: Patrons
  • Posts: 5,496
  • Joined: 25-September 03

Posted 08 March 2004 - 02:36 PM

yes.

the old file is what's making your new entries not work.

makecab the new one, and REPLACE the old one in i386.


FYI- it didn't work before, because it NEVER copied over you new driver. It tried to keep using the old one, and it didn't register the new devices. Just so you know.

#8 User is offline   bagofbones 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 17-February 04

Posted 08 March 2004 - 05:00 PM

I changed TXTSETUP.SIF AS
[SourceDisksFiles]
dpti2o.sys = 1,,,,,,3_,4,1
[HardwareIdsDatabase]
PCI\VEN_1044&DEV_A501&SUBSYS_C0011044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0021044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0031044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0041044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0051044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C00A1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C00B1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C00C1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C00D1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C00E1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C00F1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0141044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0151044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0161044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C01E1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C01F1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0201044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0211044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0281044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0291044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C02A1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C03C1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C03D1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C03E1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0461044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0471044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0481044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0501044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0511044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0521044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C05A1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C05B1044 = "dpti2o"
PCI\VEN_1044&DEV_A511&SUBSYS_C05F1044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0641044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0651044 = "dpti2o"
PCI\VEN_1044&DEV_A501&SUBSYS_C0661044 = "dpti2o"
PCI\VEN_1044&DEV_A511&SUBSYS_C0321044 = "dpti2o"
PCI\VEN_1044&DEV_A511&SUBSYS_C0331044 = "dpti2o"
PCI\VEN_1044&DEV_A511&SUBSYS_C0661044 = "dpti2o"
PCI\VEN_1044&DEV_A511&SUBSYS_C0341044 = "dpti2o"
PCI\VEN_1044&DEV_A511&SUBSYS_C0351044 = "dpti2o"
[SCSI.LOAD]
dpti2o = dpti2o.sys,4
[SCSI]
dpti2o = "Adaptec I2O RAID Adapters for 32bit Windows 2000, XP, & 2003"

Additionally, I update dpti2o.sy_ in 386. I also create XPCD\$OEM\$1\RAID\01 folder that contains all driver files for dpti2o except TXTSETUP.OEM file.
My winnt.sif is as follows:
[Unattended]
UnattendMode=FullUnattended
Repartition = Yes
FileSystem = ConvertNTFS
UnattendSwitch="yes"
WaitForReboot="No"
OemSkipEula=Yes
OemPreinstall=Yes
DriverSigningPolicy = Ignore
OemPnPDriversPath = RAID\01
TargetPath=\WINDOWS
......

This unattended installation CD passed both textmode setup (blue screen) and GUI mode setup. Unfortunately, it crashed when it started after GUI mode setup. It gave some error message about possible damage of driver controller. My guess is that the setup program did not find correct drivers . But I have no idea how to solve this problem. By the way, the driver files included in $OEM definitely work if I use F6 and instruct setup program to find them in A:.

#9 User is offline   Alanoll 

  • CODE tags people, CODE tags!
  • Group: Patrons
  • Posts: 5,496
  • Joined: 25-September 03

Posted 08 March 2004 - 05:07 PM

well, atleast you got past Textmode...thats always a start.

in my Driver folder, i leave the txtsetup.oem file there, but meh.

I have no idea why you get the error of possible damage besides maybe it's using a Microsoft driver instead of yours. That's my only guess.

#10 User is offline   bagofbones 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 17-February 04

Posted 08 March 2004 - 05:12 PM

Thank you very much. Passing text mode is a big win. Is possible to delete dpti2o.sys from DRIVER.cab? Never tried that. People in this forum seem not to recommend others to do that.

#11 User is offline   Alanoll 

  • CODE tags people, CODE tags!
  • Group: Patrons
  • Posts: 5,496
  • Joined: 25-September 03

Posted 08 March 2004 - 05:35 PM

dunno

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy