Jump to content

mass storage device driver integration (textmode or txtsetup.sif)


 Share

Recommended Posts

Hi all,

i'm working for weeks to solve this problem but i can't get my unattended cd running with mass storage device drivers included. I found many sites explaining how to integrate msd drivers, also checked some microsoft articles but none was complete (or i just don't understand what exactly to do).

I hopy someone here can help me so i can finish my cd!

This is what i have:

<cdroot>:\$OEM$\$1\driver\raid\nvidia\

idecoi.dll
nvata.cat
nvatabus.inf
nvatabus.sys
nvcoi.dll
nvide.nvu
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
nvuide.exe
txtsetup.oem

<cdroot>:\$OEM$\Textmode\*

idecoi.dll
nvata.cat
nvatabus.inf
nvatabus.sys
nvcoi.dll
nvide.nvu
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
nvuide.exe
txtsetup.oem

* = \$OEM$\Textmode\ is a 1:1 copy of \$OEM\$1\driver\raid\nvidia\

txtsetup.oem

[Disks]
d1 = "NVIDIA RAID DRIVER (SCSI)",\nvraid.sys,\

[Defaults]
scsi = RAIDCLASS

[scsi]
RAIDCLASS = "NVIDIA RAID CLASS DRIVER (required)"
BUSDRV = "NVIDIA nForce Storage Controller (required)"

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,nvraid
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvraid.cat

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,nvatabus
inf = d1,nvatabus.inf
dll = d1,idecoi.dll
dll = d1,nvcoi.dll
catalog = d1,nvata.cat

[Config.nvraid]

[Config.nvatabus]

[HardwareIds.scsi.RAIDCLASS]
id = "GenNvRaidDisk","nvraid"
id = "*_NVRAIDBUS","nvraid"
id = "*NVRAIDBUS","nvraid"

[HardwareIds.scsi.BUSDRV]
id = "PCI\VEN_10DE&DEV_008E","nvatabus"
id = "PCI\VEN_10DE&DEV_00D5","nvatabus"
id = "PCI\VEN_10DE&DEV_00EE","nvatabus"
id = "PCI\VEN_10DE&DEV_00E3","nvatabus"
id = "PCI\VEN_10DE&DEV_0036","nvatabus"
id = "PCI\VEN_10DE&DEV_003E","nvatabus"
id = "PCI\VEN_10DE&DEV_0054","nvatabus"
id = "PCI\VEN_10DE&DEV_0055","nvatabus"
id = "PCI\VEN_10DE&DEV_0266","nvatabus"
id = "PCI\VEN_10DE&DEV_0267","nvatabus"
id = "PCI\VEN_10DE&DEV_036F","nvatabus"
id = "PCI\VEN_10DE&DEV_037E","nvatabus"
id = "PCI\VEN_10DE&DEV_037F","nvatabus"
id = "PCI\VEN_10DE&DEV_03F6","nvatabus"
id = "PCI\VEN_10DE&DEV_03F7","nvatabus"
id = "PCI\VEN_10DE&DEV_03E7","nvatabus"

WINNT.SIF*

[Branding]
BrandIEUsingUnattended = Yes

[Components]
AccessOpt = Off
deskpaper = On
dialer = Off
freecell = Off
hearts = Off
hypertrm = Off
IEAccess = Off
indexsrv_system = On
media_clips = Off
minesweeper = Off
msmsgs = Off
msnexplr = Off
pinball = Off
rec = Off
spider = Off
templates = Off
zonegames = Off

[Data]
AutomaticUpdates = 0
AutoPartition = 1
MsDosInitiated = 0
UnattendedInstall = Yes

[Display]
BitsPerPel = 32
Xresolution = 1680
YResolution = 1050
Vrefresh = 60

[GuiUnattended]
AdminPassword = *
EncryptedAdminPassword = No
OEMSkipRegional = 1
OEMSkipWelcome = 1
TimeZone = 110

[Identification]
JoinWorkgroup = home

[IEPopupBlocker]
BlockPopups = No

[MassStorageDrivers]
"NVIDIA RAID CLASS DRIVER (required)" = OEM
"NVIDIA nForce Storage Controller (required)" = OEM

[Networking]
InstallDefaultComponents = No

[NetAdapters]
Adapter1 = params.Adapter1

[NetClients]
MS_MSClient = params.MS_MSClient

[NetProtocols]
MS_TCPIP = params.MS_TCPIP

[NetServices]
MS_SERVER = params.MS_SERVER
MS_PSched = params.MS_PSched

[OEMBootFiles]
idecoi.dll
nvata.cat
nvatabus.inf
nvatabus.sys
nvcoi.dll
nvide.nvu
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
nvuide.exe
txtsetup.oem

[params.Adapter1]
INFID = *

[params.MS_TCPIP]
DNS = Yes
UseDomainNameDevolution = No
EnableLMHosts = Yes
AdapterSections = params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]
SpecificTo = Adapter1
DHCP = Yes
WINS = No
NetBIOSOptions = 0

[Proxy]
Proxy_Enable = 0
Use_Same_Proxy = 1

[RegionalSettings]
Language = 00000407
LanguageGroup = 2,7

[Shell]
DefaultStartPanelOff = Yes

[SystemRestore]
CreateFirstRunRp = 0
DisableSR = 1

[TapiLocation]
CountryCode = 49
Dialing = Tone

[Unattended]
AutoActivate = Yes
DriverSigningPolicy = Ignore
FileSystem = ConvertNTFS
OemFilesPath = "..$OEM$"
OEMPnPDriversPath = "driver\audio\cmedia_cmi9761;driver\audio\realtek_alc850;driver\lan\intel_pro-1000mt;driver\lan\netgear_ga311;driver\other\atk0110;driver\other\smbus;driver\raid\nvidia;driver\vga\nvidia"
OemPreinstall = Yes
OemSkipEula = Yes
Repartition = Yes
UnattendMode = DefaultHide
UnattendSwitch = Yes
WaitForReboot = No

[URL]
Home_Page = about:blank

[UserData]
OrgName = "home"

[WindowsFirewall]
Profiles = WindowsFirewall.TurnOffFirewall

[WindowsFirewall.TurnOffFirewall]
Mode = 0

* = OEMPnPDriversPath is one line in local WINNT.SIF

This will not work, if i boot with this cd, i'll get the error "in file txtsetup.oem an unexpected error (18) in line 1747 in d:\xpsprtm\base\boot\setup\oemdisk.c occured. Press any key to continue the installation." (Translated; i'm using the german version).

The drivers are working if i set OemPreinstall = No and use F6 Floppy, so i guess i messed up the winnt.sif/txtsetup.oem?

I really would love if someone could explain me how to add the driver to txtsetup.sif based on the informations above so i don't need the \$OEM$\Textmode directory anymore and to be able to run the cd on other hardware as well!

Link to comment
Share on other sites


First thing I would do is checking WHAT is in line 1747 of d:\xpsprtm\base\boot\setup\oemdisk.c

Can you post a snippet of the file (from a couple of lines before to a couple of lines after line 1747) with line numbers?

jaclaz

Link to comment
Share on other sites

I don't know. Its a windows file, not one of mine, also its temporary while in textmode of the windows setup.

I think the problem is in txtsetup.oem, nvraid.inf, nvatabus.inf or winnt.sif.

Link to comment
Share on other sites

checked some microsoft articles but none was complete (or i just don't understand what exactly to do).

Well a hint is http://support.microsoft.com/kb/816299/en-us

However

This procedure cannot be used in conjunction with a Winnt.sif file when starting up from a CD for installation.

Generally follow KB816299, but use different directory names.

Textmode winnt.sif [MassStorageDrivers] require files twice at CD:

\I386\$OEM$

\$OEM$\Textmode

Then winnt.sif [unattended] OEMPnPDriversPath is not required for MassStorageDrivers.

Be aware: The name \I386\$OEM$ has to be at ISO9660 file system.

ISO9660 Level 1 dosn't allow a $ sign. Adjust your ISO creation tool to break ISO9660.

IsoBuster list ISO file system.

In addition: do you boot from IDE CD-ROM?

Add

[MassStorageDrivers]
"IDE CD-ROM (ATAPI 1.2)/PCI IDE-Controller" = "RETAIL"

Setting is language specific and should match your case.

Another approach is txtsetup.sif [sCSI.LOAD] and [*.LOAD] sections.

Nlite and driverlacks use this approach.

Link to comment
Share on other sites

I'm not sure if it matters at all .. but the use "QUOTATIONMARKS" could be an answer - especially when it concerns the TEXTMODE (that uses a different redendering engine than SetupAPI. For this reason it's very picky and "dumb" - Troubleshooting Section of gosh's site)

// hardly remembering similiar problems (quotationmarks and tagfiles :puke:) some time ago that can really turn into a pain in the peep

- so i compared syntax .. what winnt.sif concerns .. instead of

[MassStorageDrivers]

"NVIDIA RAID CLASS DRIVER (required)" = OEM

"NVIDIA nForce Storage Controller (required)" = OEM

you might try:

[MassStorageDrivers]

"NVIDIA RAID CLASS DRIVER (required)" = "OEM"

"NVIDIA nForce Storage Controller (required)" = "OEM"

good luck

(edited for better readability)

Edited by mukke
Link to comment
Share on other sites

Hi and thank you all for your reply!

I stopped working on integrating the drivers in Textmode and started integrating them into the txtsetup.sif directly. I used a nice guide and checked what dell did (i have a dell unattended setup cd with sata-drivers integrated).

If i use the cd to boot a computer without any raid-controller, everything is fine (setup is loading both MSD devices shortly after the F6 info), the setup works. But if i use the cd on the computer with the nvidia raid device, setup still loads the devices but it does not find any hdd.

what's wrong?

I used http://forums.nvidia.com/index.php?showtopic=18189 and compared to my dell unattended cd this should work.

In the meanwhile I'll try mukke's tip.

Link to comment
Share on other sites

Ok, i tried it now but it does not work :(

I copied <cdroot>:\$OEM$\Textmode\ to <cdroot>:\I386\$OEM$\Textmode\, added the devices to [MassStorageDrivers] and used mukke's tip. Now, if i boot from the CD setup shows the information that the txtsetup.oem is missig. The file is in <cdroot>:\$OEM$\Textmode\ and <cdroot>:\I386\$OEM$\Textmode\

I really would like to integrate all drivers into txtsetup.sif directly so recovery console and F6 is working but like i wrote before this doesn't work too (setup does not load the drivers for my MSD).

Link to comment
Share on other sites

my unattended setup cd with sata-raid-drivers integrated into txtsetup.sif (OEMPreinstall = No in WINNT.SIF = F6 while setup works and recovery console is available) is working now.

In short, no guide told to add the sys files to DOSNET.inf, after i did that, setup recognizes my raid controller! ... Ok, one of 15 guides told! (thanks gosh!!)

I'll write a nice guide next time which will include all steps and many tweaks. Hope someone needs it ;)

Edited by an3k
Link to comment
Share on other sites

Now, if i boot from the CD setup shows the information that the txtsetup.oem is missig. The file is in <cdroot>:\$OEM$\Textmode\ and <cdroot>:\I386\$OEM$\Textmode\
Setup search file <cdroot>:\I386\$OEM$\TXTSETUP.OEM

Don't use <cdroot>:\I386\$OEM$\Textmode\.

my unattended setup cd with sata-raid-drivers integrated into txtsetup.sif (OEMPreinstall = No in WINNT.SIF = F6 while setup works and recovery console is available) is working now.
Congratulations.
In short, no guide told to add the sys files to DOSNET.inf, after i did that, setup recognizes my raid controller!
How do you install windows? Do you boot from CD?

Do you use winnt32.exe?

Link to comment
Share on other sites

Can you explain, step by step (for dummies), how to integrate SATA/RAID drivers directly into TXTSETUP.SIF without disabling the Recovery Console? I'm very, very interested.

Thanks.

Edited by ponghy
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...