trainee

TEXTMODE MassStorageDrivers Method

140 posts in this topic

@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.[code]"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"[/code]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[/quote]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"?
0

Share this post


Link to post
Share on other sites
[url="http://www.msfn.org/board/index.php?showtopic=10877&hl=Pure+Chrome"]http://www.msfn.org/board/index.php?showto...&hl=Pure+Chrome[/url]

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.
0

Share this post


Link to post
Share on other sites
@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).
0

Share this post


Link to post
Share on other sites
The ide drives are disabled and the boot order is also changed when I am installing windows on my SATA Raid array.
0

Share this post


Link to post
Share on other sites
[quote name='big poppa pump' date='Sep 7 2004, 02:31 AM'][quote]
[Display]
    BitsPerPel=32
    Xresolution=12804
    YResolution=1024
    Vrefresh=85[/quote][/quote]
Hello,

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

Share this post


Link to post
Share on other sites
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:

[code][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[/code]

Next you asked about my txtsetup.oem:

[code][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][/code]

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.

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

Share this post


Link to post
Share on other sites
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.

[img]http://ordorica.org/misc/error1.jpg[/img]
[img]http://ordorica.org/misc/error2.jpg[/img]

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.
0

Share this post


Link to post
Share on other sites
@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?[/quote]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.
0

Share this post


Link to post
Share on other sites
[quote name='trainee' date='Sep 12 2004, 06:19 AM']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.[/quote]
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
0

Share this post


Link to post
Share on other sites
@cfeedback: do you have the same problem as rcordorica now? In other words does nvraid install but you have to point it to the DLL files during gui-install? I think that the two of you solved the same problem in different ways: you by copying the DLL's to XPCD\I386\$OEM$\$$\System32\ and rcordorica by changing his TXTSETUP.OEM 'DLL=' entried to 'INF='. Hopefully this is the case so that everyone is now working on the same problem.

@big poppa pump: [quote]What really surprises me is that the **** error 18 crops up randomly.[/quote]What really surprises me is that **** Microsoft couldn't give us a few more numbers to troubleshoot this problem. What about error 19 & 20? :P They must be assigned to something really important!
0

Share this post


Link to post
Share on other sites
[quote name='trainee' date='Sep 13 2004, 12:36 PM']@cfeedback: do you have the same problem as rcordorica now?  In other words does nvraid install but you have to point it to the DLL files during gui-install?  I think that the two of you solved the same problem in different ways: you by copying the DLL's to XPCD\I386\$OEM$\$$\System32\ and rcordorica by changing his TXTSETUP.OEM 'DLL=' entried to 'INF='.  Hopefully this is the case so that everyone is now working on the same problem.[/quote]
I might've jumped the gun a bit there - I was desperate for any ray of hope after working this for a day and a night. I don't remember the exact error but it wouldn't get very far in the GUI install (VPC).

It now seems to me that the GreenMachine's txtsetup.sif method is the way to go, even with NV RAID and their multitude of DLLs. Everything looks good in VPC, so it's time to format....again.

I've been using some info from the DriverPack thread so I'll post my results there.
0

Share this post


Link to post
Share on other sites
@cfeedback: Okay I'm a little disappointed that you won't be working on this method but I wish you the best of luck. It appears that rcordorica was able to get the NVRaid working, but only with some 'locate file' dialogs. This method (M2) is currently the least understood and I think most people are working on it to try and find a single way to install *all* drivers and edit as few files as possible. There is no known way to get the TXTSETUP.SIF method (M1) to work for 3ware drivers, so for people with 3ware cards this is currently the only way to slipstream.

On a related note: this thread has seen a lot of activity recently and some significant progress forward, and I hope that people stay interested in making the method work for as many drivers as possible. As always I will be here to provide as much help as I can to those who try.
0

Share this post


Link to post
Share on other sites
[quote name='trainee' date='Sep 13 2004, 08:29 PM']@cfeedback: Okay I'm a little disappointed that you won't be working on this method but I wish you the best of luck.  It appears that rcordorica was able to get the NVRaid working, but only with some 'locate file' dialogs.  This method (M2) is currently the least understood and I think most people are working on it to try and find a single way to install *all* drivers and edit as few files as possible.  There is no known way to get the TXTSETUP.SIF method (M1) to work for 3ware drivers, so for people with 3ware cards this is currently the only way to slipstream.[/quote]
FWIW when I get a sec I will certainly let you know everything I tried. :)

hell I might be trying this again in 30 minutes if this doesn't work...
0

Share this post


Link to post
Share on other sites
update:

I added the drivers into the %OEM%\$$\OemDir directory and everything installed perfectly using the method i posted before. No more errors about missing files.
0

Share this post


Link to post
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

  • Recently Browsing   0 members

    No registered users viewing this page.