MSFN Forum: Replacing Driver On Win2003 - MSFN Forum

Jump to content



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

Replacing Driver On Win2003 Rate Topic: -----

#1 User is offline   xrated 

  • Newbie
  • Group: Members
  • Posts: 11
  • Joined: 18-February 05

Posted 18 February 2005 - 06:14 AM

hi guys!

i did a unattended cd with win2003 and winnt.sif file, included some drivers:

[Data]
AutoPartition=0
MsDosInitiated=0
UnattendedInstall="Yes"
AutomaticUpdates="No"

[Unattended]
UnattendMode="FullUnattended"
OemSkipEula="Yes"
OemPreinstall="Yes"
TargetPath="\WINDOWS"
Repartition="No"
UnattendSwitch="Yes"
WaitForReboot="No"
DriverSigningPolicy="Ignore"
AutoActivate="No"
KeyboardLayout="US-International"
OemPnPDriversPath="install\drv\broadcom\Base_Drivers;install\drv\intel\Base_Drivers;install\drv\rac"

Unfortunately the raid controller is not detected with the old driver, so i replaced the mraid35x.sy_ file in the i386 folder. I used the makecab command to create the mraid35x.sy_ file out of the new driver file mraid35.sys

then i edited the txtsetup.inf file and added some pci devices:

PCI\VEN_101E&DEV_9010 = "mraid35x"
PCI\VEN_101E&DEV_9060 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_0438101E = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_0466101E = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_0467101E = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_0490101E = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_04671028 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_11111028 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_10C6103C = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_10C7103C = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_10CC103C = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_10CD103C = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_11111028 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_11111111 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_11121111 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_03A2113C = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_0471101E = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_0471101E = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_0493101E = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_0493101E = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_0475101E = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_0475101E = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_04751028 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_04711028 = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_04711028 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_04931028 = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_04931028 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_09A0101E = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_60E7103C = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_60E8103C = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_60E3103C = "mraid35x"
PCI\VEN_1028&DEV_000E&SUBSYS_01231028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_016C1028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_016D1028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_016E1028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_016F1028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_01701028 = "mraid35x"
PCI\VEN_1000&DEV_1960&SUBSYS_05201028 = "mraid35x"
PCI\VEN_1000&DEV_1960&SUBSYS_05181028 = "mraid35x"
PCI\VEN_1000&DEV_0408&SUBSYS_00011028 = "mraid35x"
PCI\VEN_1000&DEV_0408&SUBSYS_00021028 = "mraid35x"
PCI\VEN_1000&DEV_1960&SUBSYS_05181028 = "mraid35x"
PCI\VEN_1000&DEV_1960&SUBSYS_05201028 = "mraid35x"
PCI\VEN_1028&DEV_000F&SUBSYS_013B1028 = "mraid35x"
PCI\VEN_1028&DEV_000F&SUBSYS_014A1028 = "mraid35x"
PCI\VEN_1028&DEV_000F&SUBSYS_014C1028 = "mraid35x"
PCI\VEN_1028&DEV_000F&SUBSYS_014D1028 = "mraid35x"

when i install from this cd under vmware everything is fine, but this specific controller is not used there.

Then i installed it on a real server, the controller is detected right then and everything will be installed until the last reboot. But on the start of Windows its loading only about 2-3seconds and does a reboot without asking after this. Not even the Safe Mode is working.

Any idea why this happens? Or is there a different way to do it?


#2 User is offline   tguy 

  • Senior Member
  • PipPipPipPip
  • Group: Members
  • Posts: 698
  • Joined: 19-May 04

Posted 18 February 2005 - 09:22 AM

Add the RAID controller drivers to a directory in your install\drv\raid directory, then add that directory to the OEMPnPDriversPath= statement in the WINNT.SIF.

That should do it.

If not, search my id on the forum, I wrote a post on how to do it with those drivers. A Dell server needed them.

#3 User is offline   xrated 

  • Newbie
  • Group: Members
  • Posts: 11
  • Joined: 18-February 05

Posted 18 February 2005 - 10:32 AM

i tried that before but doesnt work

i think windows is prefering then its own driverfile

#4 User is offline   GreenMachine 

  • ineXPlicable
  • Group: Developers
  • Posts: 3,062
  • Joined: 22-August 03

Posted 18 February 2005 - 02:35 PM

I'm not sure it will help ... but did you read THIS KB article?

Just a thought ...

#5 User is offline   xrated 

  • Newbie
  • Group: Members
  • Posts: 11
  • Joined: 18-February 05

Posted 18 February 2005 - 03:50 PM

good one ! :thumbup

now, do you think i need still the custom txtsetup.sif ? Its in fact a Dell server and i think the controller ist not recognized by setup with its PCI Vendor ID ...

i hope also the mraid35x.sys will be copied right in place with this dosnet.inf file, wonīt help me if this happens after recognizing the RAID controller

i saw here these lines for winnt.sif:

DetachedProgram="%systemdrive%\DP.exe"
Arguments="-y /q /r:n"

Is it also to specify here more exe files to unpack?

#6 User is offline   GreenMachine 

  • ineXPlicable
  • Group: Developers
  • Posts: 3,062
  • Joined: 22-August 03

Posted 18 February 2005 - 04:05 PM

I think ...

- As you are just updating an existing file, there should be no problem having it copied correctly.

- If the PCI Venor ID is not already in TXTSETUP.SIF, you WILL need to add it.

- The DetachedProgram entry above is to add more drivers. (Only PART of the process.) You should not need it. If you have a Dell Server, I would only add that which you know you need.

I believe the real key is in ForceCopyDriverCabFiles. That is all you were missing from your initial attempt.

#7 User is offline   xrated 

  • Newbie
  • Group: Members
  • Posts: 11
  • Joined: 18-February 05

Posted 19 February 2005 - 03:01 PM

GreenMachine, on Feb 18 2005, 11:05 PM, said:

- The DetachedProgram entry above is to add more drivers. (Only PART of the process.) You should not need it. If you have a Dell Server, I would only add that which you know you need.


just wanted to compress the applications a bit, guess have to use a cmd file then

i tried also adding the driver with dosnet.inf and txtsetup.sif but the install is hanging on "registering components" then (12% to go state)

i saw on my old unattended cd that you can also use the $OEM$\textmode path, do i just place the driver there?

and i saw this in winnt.sif:
http://www.msfn.org/board/index.php?showtopic=30231&st=20

[MassStorageDrivers]
   "NVIDIA RAID CLASS DRIVER (required)" = "OEM"
   "NVIDIA NForce Storage Controller (required)" = "OEM"
   "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OemBootFiles]
   TXTSETUP.OEM
   nvraid.sys
   nvraid.inf
   nvraidco.dll
   nvraid.cat
   nvatabus.sys
   nvatabus.inf
   idecoi.dll
   nvata.cat
   nvuide.exe
   nvide.nvu
   nvcoi.dll
   NvRaidEnu.dll
   NvRaidMan.exe
   nvraidservice.exe
   NvRaidSvEnu.dll
   NvRaidWizard.dll
   NvRaidWizardEnu.dll
   RegRaid.bat


but i have no clue if i need that

#8 User is offline   xrated 

  • Newbie
  • Group: Members
  • Posts: 11
  • Joined: 18-February 05

Posted 21 February 2005 - 07:58 AM

its really a crap !

now i tried it with inserting the driverfiles into $oem$\textmode

then i modified the txtsetup.oem a bit (removed the win2000 section):

[Disks]

PERC32 = "DELL PERC RAID Products for Windows 2003 (x86)", \mraid,\

[Defaults]

scsi = PERC32

[scsi]

PERC32 = "DELL PERC RAID Products for Windows 2003 (x86)", mraid35x

[Files.scsi.PERC32]

driver  = PERC32, mraid35x.sys, mraid35x
inf     = PERC32, oemsetup.inf, mraid35x
inf     = PERC32, nodev.inf
catalog = PERC32, percraid.cat

[HardwareIds.scsi.PERC32]
PERC32 = "PCI\VEN_8086&DEV_1960&SUBSYS_11121111", "mraid35x"
PERC32 = "PCI\VEN_8086&DEV_1960&SUBSYS_11111111", "mraid35x"
PERC32 = "PCI\VEN_8086&DEV_1960&SUBSYS_09A0101E", "mraid35x"
PERC32 = "PCI\VEN_8086&DEV_1960&SUBSYS_11111028", "mraid35x"
PERC32 = "PCI\VEN_8086&DEV_1960&SUBSYS_04671028", "mraid35x"
PERC32 = "PCI\VEN_101E&DEV_1960&SUBSYS_04711028", "mraid35x"
PERC32 = "PCI\VEN_101E&DEV_1960&SUBSYS_04931028", "mraid35x"
PERC32 = "PCI\VEN_101E&DEV_1960&SUBSYS_04751028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_000E&SUBSYS_01231028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_000F&SUBSYS_013B1028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_000F&SUBSYS_014A1028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_000F&SUBSYS_014C1028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_000F&SUBSYS_014D1028", "mraid35x"
PERC32 = "PCI\VEN_101E&DEV_1960&SUBSYS_05111028", "mraid35x"
PERC32 = "PCI\VEN_1000&DEV_1960&SUBSYS_05181028", "mraid35x"
PERC32 = "PCI\VEN_1000&DEV_1960&SUBSYS_05201028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_0013&SUBSYS_016C1028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_0013&SUBSYS_016D1028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_0013&SUBSYS_016E1028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_0013&SUBSYS_016F1028", "mraid35x"
PERC32 = "PCI\VEN_1028&DEV_0013&SUBSYS_01701028", "mraid35x"
PERC32 = "PCI\VEN_1000&DEV_0408&SUBSYS_00011028", "mraid35x"
PERC32 = "PCI\VEN_1000&DEV_0408&SUBSYS_00021028", "mraid35x"

[Config.mraid35x]
value=parameters\PnpInterface,5, REG_DWORD,1


put this in winnt.sif

[MassStorageDrivers]
    "DELL PERC RAID Products for Windows 2003 (x86)" = "OEM"
    "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OemBootFiles]
    TXTSETUP.Oem
    mraid
    MRAID2K.sys
    Mraid35x.sys
    nodev.inf
    Oemsetup.inf
    percraid.cat


and i fire it up then i get some error d:\...something.... .c canīt remember now, press Enter to continue and it doesnīt recognize the driver and cant find any disc :wacko:

when i remove the storage sections from winnt.sif i also cannot even add this driver manually with F6 because on the installation it searches the driverfiles on the bloody cdrom and not on the floppy

and when the storage sections are included on winnt.sif i cannot add a driver with F6

so any hints on this?

how did you do it with this LSI logic mraid35x.sys driver?

#9 User is offline   Br4tt3 

  • World famous sausage eater...
  • PipPipPipPip
  • Group: Members
  • Posts: 566
  • Joined: 20-April 04

Posted 21 February 2005 - 08:14 AM

I changed my mraid35x.sys file included in native win2003 to a newer one using txtsetup.sif and nothing more... worked like a charm for me.

link:

DELL PERC 4/Di RAID On Motherboard Driver" using TXTSETUP.SIF
http://wug.lutteman.se/articles/ris-add-st...g_TXTSETUP.SIF_

#10 User is offline   xrated 

  • Newbie
  • Group: Members
  • Posts: 11
  • Joined: 18-February 05

Posted 21 February 2005 - 10:45 AM

aaah thanks

this here:

Quote

"Delete any referances to the same PCI/VEN as mraid35x.sys (mraid35x.sy_) is also supplied natively by Win2003"
normaly this shouldnt hurt when i install it or?

this is different than the existing entry:

Quote

[SourceDisksFiles]
mraid35x.sys = 1,,,,,,_x,2,0,0


existing:

Quote

mraid35x.sys = 1,,,,,,4_,4,1,,,1,4
and this is more or less the same:

Quote

[SCSI.Load]
mraid35x = mraid35x.sys,4

[SCSI]
mraid35x = "DELL PERC 4/Di RAID On Motherboard Driver"


and this is the important one:

Quote

Copy the mraid35x.sys to the RemoteInstall\Setup\Eng\Images\MyHappyServer\i386 folder.


so just copy this extracted file to there? normaly it should take then the old packed file or is it so smart that it always takes the unextracted file?

mraid35x.sys new driver
mraid35x.sy_ old driver

i am just asking because it installs now but on the final reboot it fails, i left all old PCI entries in txtsetup.sif and compressed the new mraid35x.sys to mraid35x.sy_ with replacing the existing file

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