[Spinman]

If I may hijack this thread - I'm totally confused about RAID and PCI Hard Disk Controllers....

From reading bits and pieces, I've setup my ATA/133 controller as follows:

[MassStorageDrivers]
"Intel® 82801BA Ultra ATA Controller" = OEM
"Primary IDE Channel" = OEM
"Secondary IDE Channel" = OEM

[OEMBootFiles]
idechndr.inf
IdeBusDr.sys
IdeChnDr.sys
Txtsetup.oem


[Unattended] OemPnPDriversPath="Drivers\000_Intel_Inf;Drivers\001_Promise_FullRaid;Drivers\002_Intel_AppAcc;Drivers\004_Intel_Lan;Drivers\005_Nec97f;Drivers\009_Maxtor_ATA

In 009_maxtor_ATA -I've included:
readme.bat
txtsetup.oem
ulcoins.dll
ultra
ultra.cat
ultra.inf
ultra.sys

I am installing windows on Drive C:\
I am installing my Documents and Settings Directory on D:\ (mirror raid)

[MassStorageDrivers]
"Intel® 82801BA Ultra ATA Controller" = OEM
"Primary IDE Channel" = OEM
"Secondary IDE Channel" = OEM
"WinXP Promise FastTrak TX2000 ™ Controller (PDC20276)" = OEM

[OEMBootFiles]
idechndr.inf
IdeBusDr.sys
IdeChnDr.sys
Txtsetup.oem
Fasttrak.sys
Fasttrak.inf
Fasttrak.cat
TXTsetup.oem

In 001_Promise_FullRaid I've included:

fasttrak
fasttrak.cat
fasttrak.inf
fasttrak.sys
readme.txt
txtsetup.oem

Because the raid is not being used for windows installation, but only for D & S setup - will I be able to install the drivers this way?

Do I have a problem with (2) txtsetup.oem references under [oembootfiles]?

I'm totally confused---

[trainee]

Hey, I know there has been quite a bit of activity in this thread and I want to respond to all of your posts ASAP, but I'm on vacation through the end of the long weekend (Monday = labor day in the USA). I am reading the posts, but I don't know if I will be able to respond or research them until Tuesday at the earliest. Sorry

[trainee]

@EDDI: Thanks for posting all of your installation details. As far as I know this is the only method that will work for the 3ware card so I'm glad you found it! Your experience is another great reference! Thanks again.

@rcordorica: Great! We now have the first confirmed non-3ware driver case! I am going to list the confirmation for the SiL 3112r drivers at the top of the thread. The .cpl file is the control panel file that is installed in GUI mode. This is a little utility that shows up in the control panel in windows. This is actually the same file that the TXTSETUP.OEM chokes on and why you have to remove the "dll=" line. If you could provide us with a copy of your winnt.sif and some more information on what files you put in each directory we might be able to better address this problem.

Quote

I think the rest of the directories you posted aren't really needed.

Which directories are you referring to? If you are installing from a CD you absolutely need to have a $OEM$\TEXTMODE and a I386\$OEM$\ directory. I know that you don't have to have a $OEM\Driver\* directories or reference the drivers in the winnt.sif oempnpdriverspath variable for the 3ware cards. However if properly referenced this might fix the .cpl file problem with the SiL3112 drivers. Anyway thank you for confirming the relative working state of this method with your hardware.

@Spinman: Don't worry about hijaking, your post is quite pertinent to this thread. And thank you for posting so much information, but please, please use CODE tags around your winnt.sif and other file information, it is *much* easier to read. And please post your entire winnt.sif (with personal information removed) and the TXTSETUP.OEM file (which is just plain text) so we can see if your problem is somewhere else and not directly with the driver files/setup. Okay first you have some problems with your [MassStorageDrivers] section. You don't need the primary/secondary channel stuff and you haven't listed your CD. (I am assuming you are doing a CD based install).

[MassStorageDrivers]
"Intel® 82801BA Ultra ATA Controller" = OEM
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OemBootFiles]
Txtsetup.oem
idechndr.inf
IdeBusDr.sys
IdeChnDr.sys

As long as this is the complete file list (under oembootfiles), you have copied the files to the appropriate locations, and the supplied TXTSETUP.OEM doesn't have any invalid entries this should work for your primary drive. No one is exactly sure how important case-sensitivity is so it is best to try and use the *exact* naming of the files and sections.

Quote

In 009_maxtor_ATA -I've included:
readme.bat
txtsetup.oem
ulcoins.dll
ultra
ultra.cat
ultra.inf
ultra.sys

Are these files for your Intel controller, or for your maxtor HD? Does the maxtor need them to function, or do they just improve the performance/stability of the HD? If they are neccesary to the installation and are referenced in the TXTSETUP.OEM then they need to be with the other drivers in $OEM$\TEXTMODE and I386\$OEM$ directories and referenced in the [OemBootFiles] section.

Quote

I am installing windows on Drive C:\
I am installing my Documents and Settings Directory on D:\ (mirror raid)

Now, the real question is how many of your Hard drive controllers don't have built-in drivers? Do you have to install/update drivers for both your Intel controller and your fasttrack controller? I believe that you do need a floppy for your fasttrack, but it is quite possible that you don't need additional drivers for the onboard intel (if it is in fact onboard). So you might try something like this:

[MassStorageDrivers]
"Intel® 82801BA Ultra ATA Controller" = "RETAIL"
"WinXP Promise FastTrak TX2000 ™ Controller (PDC20276)" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OemBootFiles]
TXTsetup.oem
Fasttrak.sys
Fasttrak.inf
Fasttrak.cat

You cannot have more than 1 TXTSETUP.OEM file! If you follow the guide in the 1st post you will see that you would have to copy over 1 TXTSETUP.OEM file in the $OEM$\TEXTMODE and I386\$OEM$ directories to do this! If you have more than 1 raid/sata controller that requires additional drivers you will have to 'marry' the TXTSETUP.OEM files together to achieve this. It is quite do-able but requires more work on your part so it is best to figure out if you actually have to do this, before you go ahead and try to do it. Hope this helps, post back here with more information/questions/etc.

[big poppa pump]

I keep getting an error saying:

The Manufacturer provided file that setup is trying to use is corrupted or invalid:

Line1 contains a syntax error.

I even deleted the txtsetup.oem file from the iso and tried installing xp and still end up getting the same error.

I am literally banging my head on the wall trying to figure out what the hell this error means and which file it is talking about.

Edit.....an update

I deleted winnt.sif from I386 and it went through without an hitch.

Trying to sort out my winnt.sif file now.

[trainee]

@big poppa pump: sounds like you are on the right track. Why don't you post your winnt.sif and see if we can help you find the problem? (Don't forget the code tags ) I usually recommend using a very basic winnt.sif when trying to get the drivers working, so you may try to cut your winnt.sif down to basics if it has a lot of special settings. Hope this helps.

[big poppa pump]

Quote

[Unattended]UnattendMode=FullUnattended   
OemSkipEula=Yes
OemPreinstall=Yes   
AutoActivate="no"
FileSystem=LeaveAlone
TargetPath=\WINDOWS
Repartition=No
UnattendSwitch="Yes"
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
DriverSigningPolicy=Ignore
OemPnPDriversPath="\drivers\001_chipset;\drivers\002_network;\drivers\003_gart;\drivers\004_video\Driver\2KXP_INF;\drivers\005_sound;\drivers\006_monitor;\drivers\007_usb"
includecatalog=KB826939.cat

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

[GuiUnattended]
    AdminPassword="god"
    EncryptedAdminPassword=NO
    AutoLogon=No
    OEMSkipRegional=1
    TimeZone=20
    OemSkipWelcome=1

[Shell]
    CustomDefaultThemeFile = "%WinDir%\Resources\Themes\Crystal.Theme"
    DefaultStartPanelOff=No
    DefaultThemesOff=No

[UserData]
    ProductKey=xxxxxxxxx
    Fullname="xxxxx"
    Orgname="xxxxxx"
    ComputerName=xxxxxxxx

[Display]
    BitsPerPel=32
    Xresolution=12804
    YResolution=1024
    Vrefresh=85

[TapiLocation]
    CountryCode=1
    Dialing=Tone
    AreaCode=210

[SystemFileProtection]
    SFCQuota=0
    SFCDisable=2

[URL]
    Home_Page=about:blank

[IEPopupBlocker]
    AllowedSites=http://www.microsoft.com
    BlockPopups=Yes
    FilterLevel=Medium
    ShowInformationBar=No

[Identification]
    JoinWorkgroup=WORKGROUP

[MassStorageDrivers]
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"   
"Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003" = "OEM"
   

[OEMBootFiles]
    TxtSetup.oem
    Si3112r.inf
    si3112r.cat
    si3112r.sys
    siwinacc.sys
    siisupp.vxd
    silsupp.cpl

[Networking]
    InstallDefaultComponents=No

[NetAdapters]
    Adapter1=params.Adapter1
    Adapter2=params.Adapter2

[params.Adapter1]
    INFID="pci\ven_8086&dev_1229&subsys_10158086"
    NetCardAddress = 0x0002b3961595
    PciBusNumber = 2
    PciDeviceNumber = 5
    PciFunctionNumber = 0
    ConnectionName = "Number 1"

[params.Adapter2]
    INFID="pci\ven_8086&dev_1229&subsys_10158086"
    NetCardAddress = 0x0002b3961596
    PciBusNumber = 2
    PciDeviceNumber = 4
    PciFunctionNumber = 0
    ConnectionName = "Number 2"

[NetProtocols]
    MS_TCPIP=params.MS_TCPIP

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

[params.MS_TCPIP.Adapter1]
    SpecificTo=Adapter1
    DHCP=No
    IPAddress=192.168.1.68
    SubnetMask=255.255.255.0
    DefaultGateway=192.168.1.1
    DNSServerSearchOrder=xx.xx.xx.xx,xx.xx.xx.xx
    WINS=No
    NetBIOSOptions=2

[params.MS_TCPIP.Adapter2]
    SpecificTo=Adapter2
    DHCP=No
    IPAddress=192.168.1.69
    SubnetMask=255.255.255.0
    DefaultGateway=192.168.1.1
    DNSServerSearchOrder=xx.xx.xx.xx,xx.xx.xx.xx
    WINS=No
    NetBIOSOptions=2

[Homenet]
    Bridge = Adapter1,Adapter2
    EnableICS =  No
    ;ExternalAdapter = MyAdapter3
    ;InternalAdapter = MyAdapter4
    ;InternetConnectionFirewall = MyAdapter3
    ;InternalIsBridge = No
    ;ShowTrayIcon = Yes

[WindowsFirewall]
    Profiles = WindowsFirewall.TurnOffFirewall

[WindowsFirewall.TurnOffFirewall]
    Mode = 0

[Components]
    msmsgs=off
    msnexplr=off
    Media_Utopia=off
    OEAccess=Off
    WMAccess = Off

[GuiRunOnce]
    %systemdrive%\apps\bootlogo.cmd

[Bâshrat the Sneaky]

I see several errors in your winnnt.sif:

1.

;SetupMgrTag
[Data]

2.

UnattendMode=FullUnattend

3.

[GuiUnattended]
    AdminPassword=god

4.

[GuiRunOnce]
    Command0=%systemdrive%\apps\bootlogo.cmd

Hope this helps.... (I compared to my winnt.sif, which is working)

[big poppa pump]

I have been using this for past few months and never once had a problem. Why would I start having problems all of a sudden?

[Bâshrat the Sneaky]

big poppa pump, on Sep 7 2004, 05:25 PM, said:

I have been using this for past few months and never once had a problem. Why would I start having problems all of a sudden?

dunno then... Just try it...

[big poppa pump]

Update.....

Finally managed to get Textmode working using a slightly different method than the one posted above.
The CD boots and finds my Raptors and then the installation goes thru without a hitch all the way....not really!

All files get copied over and on the first reboot get that stupid message "Disk Read Error. Press CTRL+ALT+DEL to Reboot.

[trainee]

@big poppa pump: Sounds like you are making progress. I would definetly review Bâshrat's suggestions since he is very knowledgeable about these things. I still think that your winnt.sif is overly complex to try and diagnose your textmode problems, you can easily remove those additional settings and put them back in when textmode is totally working. With that said your problem sounds either bios or cd-rom related. Make sure your cd-rom entry is correct under [MassStorageDrivers]. I have provided mine below directly from my own winnt.sif.

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

I don't think this is your problem however.

Quote

2*74 WD Raptors on SATA Raid 0
2*250 Maxtors 8mb on PATA Raid 0

You should take a close look at your boot order and then make sure that you are trying to boot from the same array as you are installing your files to. If you don't see anything 'windows-like' after the first reboot then I very much suspect that you are booting to your PATA array after installing to your SATA array or visa-versa. If you see something *briefly* 'windows-like' then it is not finding your cd-rom drive after the first reboot (i have experienced this before). I suspect it is the former. Also what do you mean by "slightly different method"?

[big poppa pump]

http://www.msfn.org/board/index.php?showto...&hl=Pure+Chrome

I used this one which is a slight variation to the one state here.

Anyway I got it working with this method too. So basically I have sata drivers slipstreamed working with 3 different methods. But neither method lets me install xpsp2 unattended on a raid 0 setup on a si3112r raid setup %#$^%^$%. However I am easily able to install windows on a single SATA drive off the si3112r chipset.

[Bâshrat the Sneaky]

@big poppa pump: I agree with trainee. Please disconnect (not remove!) the other RAID array when installing Windows. After installing re-connect the cables. There's a good chance it will work then. (or just try to change your boot order).

[big poppa pump]

The ide drives are disabled and the boot order is also changed when I am installing windows on my SATA Raid array.

[EDDI]

big poppa pump, on Sep 7 2004, 02:31 AM, said:

Quote

[Display]
    BitsPerPel=32
    Xresolution=12804
    YResolution=1024
    Vrefresh=85

Hello,

i think you should overthink your Xresolution
12804 is very much too high.

[rcordorica]

ok, i've been working on this stuff trying to get it work with my different controllers. I think I have made a few "breakthroughs"!

1. You asked to see my winnt.sif:

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

[Unattended]
    UnattendMode=DefaultHide
    OemPreinstall=Yes
    TargetPath=\WINDOWS
    UnattendSwitch="yes"
    FileSystem=*
    OemSkipEula=Yes
    WaitForReboot="No"
    DriverSigningPolicy=Ignore
OemPnPDriversPath="Drivers\nvidia;Drivers\intelv92;Drivers\nforce440\;Drivers\nforce440\ide;
Drivers\nforce440\gart;Drivers\nforce440\ethernet;Drivers\nforce440\smbus;Drivers\nforce440\memctl;
Drivers\nforce440\AudioUtl;Drivers\nforce440\AudioDrv;Drivers\canons750;Drivers\006_MassStorage;
Drivers\006_MassStorage\acard;Drivers\006_MassStorage\acard\6280;Drivers\006_MassStorage\acard\6290;
Drivers\006_MassStorage\acard\67160;Drivers\006_MassStorage\acard\671x;Drivers\006_MassStorage\acard\6880;
Drivers\006_MassStorage\acard\6890;Drivers\006_MassStorage\acard\68x5;Drivers\006_MassStorage\adaptec;
Drivers\006_MassStorage\adaptec\aac;Drivers\006_MassStorage\adaptec\aar1210;Drivers\006_MassStorage\adaptec\i2o;
Drivers\006_MassStorage\adaptec\u160;Drivers\006_MassStorage\adaptec\u320;Drivers\006_MassStorage\adaptec\u320r;
Drivers\006_MassStorage\ali;Drivers\006_MassStorage\amd;Drivers\006_MassStorage\highpoint;
Drivers\006_MassStorage\highpoint\hpt366;Drivers\006_MassStorage\highpoint\hpt371;
Drivers\006_MassStorage\highpoint\hpt374;Drivers\006_MassStorage\highpoint\hpt3xx;
Drivers\006_MassStorage\highpoint\rr182x;Drivers\006_MassStorage\intel;Drivers\006_MassStorage\intel\eide;
Drivers\006_MassStorage\intel\sataraid;Drivers\006_MassStorage\intel\u320r;Drivers\006_MassStorage\ite;
Drivers\006_MassStorage\lsilogic;Drivers\006_MassStorage\lsilogic\megaide;Drivers\006_MassStorage\lsilogic\mraid35x;
Drivers\006_MassStorage\lsilogic\mylex;Drivers\006_MassStorage\lsilogic\symmpi;Drivers\006_MassStorage\nvidia;
Drivers\006_MassStorage\promise;Drivers\006_MassStorage\promise\fasttrak;Drivers\006_MassStorage\promise\fasttx2k;
Drivers\006_MassStorage\promise\sx4000;Drivers\006_MassStorage\promise\sx6000;
Drivers\006_MassStorage\promise\ulsata;Drivers\006_MassStorage\promise\ultra;Drivers\006_MassStorage\qlogic;
Drivers\006_MassStorage\qlogic\12160;Drivers\006_MassStorage\siimage;Drivers\006_MassStorage\siimage\3112r;
Drivers\006_MassStorage\siimage\3114;Drivers\006_MassStorage\siimage\3114r;Drivers\006_MassStorage\siimage\3124;
Drivers\006_MassStorage\siimage\3124r;Drivers\006_MassStorage\siimage\649r;Drivers\006_MassStorage\siimage\680;
Drivers\006_MassStorage\siimage\680r;Drivers\006_MassStorage\sis;Drivers\006_MassStorage\sis\eide;
Drivers\006_MassStorage\sis\raid;Drivers\006_MassStorage\via;Drivers\006_MassStorage\via\eide;
Drivers\006_MassStorage\via\ideraid;Drivers\006_MassStorage\via\miniport;Drivers\006_MassStorage\via\sataraid"


[GuiUnattended]
    AdminPassword=*
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    TimeZone=4
    OemSkipWelcome=1
    
[UserData]
    ProductKey=xxxx
    FullName="Microsoft"
    OrgName="Windows"

[TapiLocation]
    CountryCode=1
    Dialing=Tone

[RegionalSettings]
    LanguageGroup=1

[Identification]
    JoinWorkgroup=WORKGROUP

[Networking]
    InstallDefaultComponents=Yes

[URL]
    Home_Page = http://www.google.com

[TapiLocation]
    Dialing=Tone

[Display]
    BitsPerPel=16
    Xresolution=1024
    YResolution=768
    Vrefresh=60

[MassStorageDrivers]
"Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
"NVIDIA RAID CLASS DRIVER" = "OEM"
"NVIDIA NForce Storage Controller" = "OEM"

[OEMBootFiles]
TxtSetup.oem
Si3112r.inf
si3112r.cat
Si3112r.sys
SiiSupp.vxd
SilSupp.cpl
SIWinAcc.sys
idecoi.dll
nvatabus.inf
nvata.cat
NvAtaBus.sys
nvide.nvu
nvcoi.dll
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
NvRaidEnu.dll
nvraidservice.exe
NvRaidSvEnu.dll
NvRaidWizard.dll
NvRaidWizardEnu.dll
nvuide.exe
RegRaid.bat

Next you asked about my txtsetup.oem:

[Disks]
disk1 = "Silicon Image SiI 3x12 SATARaid Driver Installation Disk",\Si3112r.sys,\
d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\

[Defaults]
SCSI = Si3112r_XP
scsi = RAIDCLASS
scsi = BUSDRV

[SCSI]                ; HwComponent section
Si3112r_XP = "Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003"
RAIDCLASS = "NVIDIA RAID CLASS DRIVER"
BUSDRV = "NVIDIA NForce Storage Controller"

[Files.SCSI.Si3112r_XP]
driver = disk1,si3112r.sys, Si3112r
driver = disk1,SiWinAcc.sys, SiFilter
inf = disk1,Si3112r.inf
catalog = disk1, Si3112r.cat

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

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

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

[HardwareIds.scsi.BUSDRV]
id = "PCI\VEN_10DE&DEV_008E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0085", "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_00E5", "nvatabus"
id = "PCI\VEN_10DE&DEV_0035", "nvatabus"
id = "PCI\VEN_10DE&DEV_0036", "nvatabus"
id = "PCI\VEN_10DE&DEV_003E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0053", "nvatabus"
id = "PCI\VEN_10DE&DEV_0054", "nvatabus"
id = "PCI\VEN_10DE&DEV_0055", "nvatabus"

[HardwareIds.SCSI.Si3112r_XP]
id = "PCI\VEN_1095&DEV_3112&SUBSYS_61121095", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_611215D9", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_34228086", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_B0031458", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0111019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0121019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0131019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0141019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0151019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1014147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_100B147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1402147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1404147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1802147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1804147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1C00147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_5930107D", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_249510F1", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_809D1043", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0270A0A0", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_044DA0A0", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_044CA0A0", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_92011905", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_92151905", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_904C1905", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_904B1905", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A41810FD", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A41910FD", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A71910FD", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_90171695", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_C2001297", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_C2011297", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_15D40035", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_340217F2", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_100415BD", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_F641270F", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C0F105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C13105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C58105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C40105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C41105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C42105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C43105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C44105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C22105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C2A105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_2A1E103C", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_65121095", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_B0031458", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1014147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1021147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_100B147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1C06147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1C00147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1C03147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1C04147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1406147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1407147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_90191695", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_C2021297", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_C2031297", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_C2041297", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_534D108E", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_02B71014", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_02C51095", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_2A1E103C", "Si3112r"
id = "PCI\VEN_1002&DEV_436E&SUBSYS_436E1002", "Si3112r"
id = "PCI\VEN_1002&DEV_436E&SUBSYS_0A44174B", "Si3112r"
id = "PCI\VEN_1002&DEV_436E&SUBSYS_0A45174B", "Si3112r"
id = "PCI\VEN_1002&DEV_436E&SUBSYS_00301462", "Si3112r"
id = "PCI\VEN_1002&DEV_4379&SUBSYS_43791002", "Si3112r"
id = "PCI\VEN_1002&DEV_437A&SUBSYS_437A1002", "Si3112r"

[Config.Si3112r]
;value = Parameters, NT40WorkAround, REG_DWORD, 1
;value = Parameters\PnpInterface, 5, REG_DWORD, 1
value = ProblemDevices, "", REG_SZ, ""
value = ProblemDevices, "Maxtor 4D060H3                          DAK05GK0", REG_SZ, "MaxMode = UDMA-5"
value = ProblemDevices, "ST320012AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST330013AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST340017AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST360015AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST380023AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST3120023AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST340014ASL", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST360014ASL", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST380011ASL", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST3120022ASL", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST3160021ASL", REG_SZ, "Mod15Write"

[Config.RAIDCLASS]

[Config.BUSDRV]

Now here are some things I discovered along the way.

1. You can combine more than one set of textmode drivers into a single txtsetup.oem file. So what I did is use the same headers as the orignal file, and just copied over the info under the headers into a single txtsetup.oem file. In my example, I merged together my 3112r and NVRAID/NV Storage txtsetup.oem file to create a single file.

2. You can integrate DLL = files into your TEXTMODE installtion. In fact, this is necessary for some things like the NVRAID files that refuse to work without the .dll's. So what I did is simply rename the DLL = to INF =. Why? Because INF and DLL get copied to the same folder: %systemroot%/system32. The Textmode setup allows the use of INF, but not the DLL header.

3. You only need the /i386/$OEM$ and /$OEM/TEXTMODE folders to work. I didn't copy to the /i386 or other directories.

4. If you notice, I am using your method as well as the Storage driver pack method. They work nicely together. I consider your method good incase of stubborn drivers that don't work with RyanVM's method.

There are some other things I need to go over, as well as some pics that i have. I'll get back to you shortly.

(running off my NVRAID happily right now on a new system).

[rcordorica]

Part two:

Well, at least I got it working, but there were some problems. Similar to what happened with the si3112r. I got these kind of errors.




Now, maybe the 3112r can be fixed by adding the .cpl file using the INF method I described above, but I don't know because I don't want to reinstall my system right now. But the nvidia drivers still has the above problem. To allow the installation to continue I had to point to my install CD where the .dll was located. Even then, I had to manually type in the .dll extention or else it would not continue (simply clicking on the missing file didn't work). I had to do this about 4 times.
it says it can't find it in OEMDir. Where do we need to place the files in order for it to get there?

Now I know that by adding the INF it at least allowed me to get into the windows installation with the NVRAID where as before I would only come to a black screen stating my disk configuration was wrong. So I did something right, although it may not be the best way.

[trainee]

@rcordorica: First let me say thank you for all of your effort working on this, especially for taking the time to post your experience and insight. I think most people figure out how to get things to work and then never bother to try and help other people out. Now for the *bad* news: I have no way of diagnosing this problem. I have been trying and to recreate a scenario like this with dummied up txtsetup.oem files but haven't had any luck with it yet. I simply don't have access to any nvraid/silicon image/etc. hardware.

Quote

it says it can't find it in OEMDir. Where do we need to place the files in order for it to get there?

YES! I think this is absolutely the key to it. Probably the biggest breakthrough I made with this method was when I made an I386\$OEM$\ directory. A network installation doesn't require this additional directory, but a CD based install does. Similarily I have no Idea why using a floppy allows DLL lines to be processed correctly and using M2 slipstreaming doesn't. You might try searching for those files now that windows is installed just to see where they are copied to. If you still have a floppy drive and are willing to do an attended install (in the name of science?), you might see if it copies the files to any different/additional locations when using the drivers from the floppy instead of M2 slipstreaming.

I could come up with directory suggestions until I'm blue in the face, but I would have no way of testing them. I would probably try to generate about 50+ directories that seem plausible and just stick the dll files there. An example would be $OEM$\OemDir\*.dll or I386\$OEM$\OemDir\*.dll. This is how I found I386\$OEM$\. By putting it in so many different directories you can find out if it works very quickly and then later find out which was the actual directory that made it work. I will keep searching and thinking about this problem, but until then best of luck and thanks again.

[cfeedback]

trainee, on Sep 12 2004, 06:19 AM, said:

I could come up with directory suggestions until I'm blue in the face, but I would have no way of testing them.  I would probably try to generate about 50+ directories that seem plausible and just stick the dll files there.  An example would be $OEM$\OemDir\*.dll or I386\$OEM$\OemDir\*.dll.  This is how I found I386\$OEM$\.  By putting it in so many different directories you can find out if it works very quickly and then later find out which was the actual directory that made it work.  I will keep searching and thinking about this problem, but until then best of luck and thanks again.

XPCD\I386\$OEM$\$$\System32\ is where I had to put my DLLs for NV RAID (MSI K8N Neo Platinum) in order to get past the error 18 oemdisk.c problem mentioned by others earlier in this thread. Still not making a lot of progress though.

rcordorica - your posts have been very helpful. I will share my experiences to see if they offer any insight after I have a chance to get some sleep - been working on this for a good 12 hours.

-cfeedback

[big poppa pump]

What really surprises me is that the **** error 18 crops up randomly.