[TRCJudge]

Hi All.
Tearing my hair out here. I have a server with no floppy provision and am trying to slipstream. I have followed various instructions on slipstreaming even using n-lite but nothing works. The furthest I have got is loading the drives, rebooting then an error message saying that setup cannot continue as the files are corrupt (phase0).
Is there a simple definitive guide for this? I have followed Microsoft articles, several of the posts here including what is posted below. I get various levels of success from not finding the drivers to the reboot and setup failure. My board is an Intel system and I have the drivers from CD. Can anyone help, I have gone through about 20 DVD-R's so far!!

I don't have an Adaptec 2010S but I have sucessfully integrated several other SCSI drivers into my Windows 2003 install with no problems. Taking the OEM file that you provided here is what I would do to make it work on my systems...

1) Add the following to DOSNET.INF
[Files]
d1,dpti2o.sys


2) Add the following to TXTSETUP.SIF
[SourceDisksFiles]
dpti2o.sys = 1,,,,,,4_,4,1,,,1,4

[HardwareIdsDatabase]
; Adaptec I2O RAID Adapters
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"


3) Add the following to HIVESYS.INF
[AddReg]
; Adaptec I2O RAID Adapters
HKLM,"SYSTEM\CurrentControlSet\Services\dpti2o","ErrorControl",0x00010003,1
HKLM,"SYSTEM\CurrentControlSet\Services\dpti2o","Group",0x00000002,"SCSI miniport"
HKLM,"SYSTEM\CurrentControlSet\Services\dpti2o","Start",0x00010003,4
HKLM,"SYSTEM\CurrentControlSet\Services\dpti2o","Type",0x00010003,1
HKLM,"SYSTEM\CurrentControlSet\Services\dpti2o\Parameters",,0x00000012
HKLM,"SYSTEM\CurrentControlSet\Services\dpti2o\Parameters\Device","NumberOfRequests",0x00010001,0x40

; Adaptec I2O RAID Adapters
HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\dpti2o","EventMessageFile",0x00020002,"%SystemRoot%\System32\IoLogMsg.dll"
HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\dpti2o","TypesSupported",0x00010003,7


Be extremely careful to ensure that you don't change the wrapping of lines in HIVESYS.INF, I found that if I opened HIVESYS.INF in Notepad with word wrap on, that it would sometimes change the line wrapping upon saving, effectivly corrupting the file. So turn word wrap off! Or better yet use a better text editor like UltraEdit.

4) Create the following CD structure
+---$OEM$
| +---$1
| \---Drivers
| +---SCSI
| \---dpti2o
\---I386
+---SVCPACK
+---SYSTEM32
\---UNIPROC

Place all the Adaptec driver files in \$OEM$\$1\Drivers\SCSI\dpti2o
Copy dpti2o.sys to \i386
Copy dpti2o.cat to \i386\SVCPACK

5) Add the following to WINNT.SIF
[Unattended]
OemPreinstall=Yes
OemFilesPath="..\$OEM$"
; See http://support.micro...b;EN-US;q250380 for why this must be = Ignore
DriverSigningPolicy=Ignore
OemPnPDriversPath="Drivers\SCSI\dpti2o;"


Beware that lines posted here may possibly wrap! If you paste wrapped lines into your INF or SIF files they will NOT work.

[tomasz86]

You may want to consider a HDD or USB based installation. It will save you a lot of time and money.

Technically you should only need this:

• DOSNET.INF
  
  

  [Files]
  d1,dpti2o.sys
  

  
  
  
• TXTSETUP.SIF
  
  

  [SourceDisksFiles]
  dpti2o.sys = 1,,,,,,4_,4,1,,,1,4
  
  [HardwareIdsDatabase]
  ; Adaptec I2O RAID Adapters
  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"
  
  [FileFlags]
  dpti2o.sys = 16
  

  
  
  
• HIVESYS.INF
  
  

  [AddReg]
  ; Adaptec I2O RAID Adapters
  HKLM,"SYSTEM\CurrentControlSet\Services\dpti2o\Parameters",,0x00000012
  HKLM,"SYSTEM\CurrentControlSet\Services\dpti2o\Parameters\PnpInterface","5",0x00010003,1
  

Just copy "dpti2o.sys" to I386 (no need to use $OEM$).

[TRCJudge]

Nope. It gets me quite far. Drives are recognised, loads setup files, reboots and gives the windows 2003 slash screen. But then gives a blank screen and does not conclude the setup.

Whats the USB install like, not tried that before?

[tomasz86]

If the drives are detected then it means that the driver itself has been integrated properly and does work. Are you sure that the hardware is 100% fine? It would be useful if you checked the installation with a different controller.

[allen2]

I had this problem when i didn't add the driver .inf in txtsetup.sif in the [SourceDisksFiles] section after editing the inf to point in the files in the right folder:
For example \amd64 for x64 OS or \i386 for x86.

[SourceDisksNames]
1 = %DiskName%,,,\amd64

Other than that i use the method explained by tomasz86 and it is always working fine (i did it many times).