rcordorica
Content Type
Profiles
Forums
Events
Posts posted by rcordorica
-
-
yeah, makes perfect sense, but i was just wondering if you could put in the extra return for us... it's no big deal anyways, it still works great.
btw, when will you be back up and running?
0 -
everybody always test this in virtual pc... Why not just set aside a small empty partition for testing.... That is what I have been doing for a while now. i think virtual pc has some different requirements as far as files.
nevermind, don't listen to me, i'm too tired. night.
0 -
i tried method 2 recently (for the first time) and my computer ended up crasing right when it got to the GUI portion of the setup. However, i was testing a new Nlite and TEXTMODE setup, so there are a lot of factors there that could have caused the problems.
0 -
lol, me too, i wasted like 20 cd'r when i first got into Nlite'ing/Driverpack'ing/and now TEXTMODE'ing. I switched over to CDRW and now I don't have to worry about the waste. However, I should warn that you do keep a hard copy (CDR) of a working install once you have it, that way if you ever erase the CDRW you still have a good reference copy. (i forgot to do that and i recently had to remake all my older work). But trainee has made it much easier for me now with RASOR, maybe he can support your drivers (or does he already?).0
-
@trainee
Update: I hope you got my PM, i just got yours only 2 days ago.
Anyways, I got the newest version of RASOR and used it to create a new XPCD.
1. I made my original windows smaller first by using Nlite.
2. I used RASOR next to add both NVRAID and the 3114 drivers.
3. I see that it created all the correct $OEM$ and OemDir directories like expected.
4. I checked the winnt.sif and it put all that info in correctly. One little thing i would like to see changed though is to add a space in between the [MassStorageDrivers] and the previous last entry. It's just for easy reading sake.
For example:
[Networking]
InstallDefaultComponents=Yes
[MassStorageDrivers]
"3ware Escalade 7000/8000 Series ATA RAID Controller" = "OEM"
to this:
[Networking]
InstallDefaultComponents=Yes
[MassStorageDrivers]
"3ware Escalade 7000/8000 Series ATA RAID Controller" = "OEM"
It's purely a trivial change, but I like to be able to differentiate my winnt.sif file easily.
5. I applied Bashrat's driverpack ontop of the Nlite'd/RASOR'd cd. His pack has bugs of its own, but I got around them for the time being.
6. I used Nlite to make a bootable ISO.
7. First time i ran the setup i tried installing this new XPCD onto a single drive and everything went perfectly. No GUI errors or popups.. No freezes. It worked great. I checked the device manager and both the 3114 and NVRAID were detected and installed correctly. I also had access to my 3 hard drives connected on them.
8. The second time I made a Stripped RAID 0 array using my two 160GB SATA drives on the NVRAID. I booted up the setup and when I got to the partition manager it saw my drives as a single array!
9. I jumped for joy that I didn't have to do any hard work this time, and it worked BEAUTIFULLY! Windows installed just fine on my NVRAID array without any errors.
So hopefully this utility will work for more people.
I am using:
Athlon64 3200+
Asus K8N-E Deluxe - Bios 1005 beta
NVRAID - 2x160GB SATA Western Digital, 64K Stripe
3114 - 1x80GB IDE to SATA converted WD.
Windows XP Pro - SP2, Nlite'd.
.NET 1.1 with SP1
Thank You trainee.
0 -
yeah, it's no problem. windows will only use and install the driver for the system it's on. I wrote a bit about combining txtsetup.oem files. Look for it in this thread.0
-
@TheAccuser - i see that you have a "dll" entry in your txtsetup.oem. That might be the cause of your problem. Read the updated guide for help.0
-
hey, i am willing to test.
Abit nf7-s with 3112r.
Asus K8n-e with 3114 and NVRAID.
Although I should probably mention that it's kind of weird because it seems like the same thing is happening in two different forums.
http://www.msfn.org/board/index.php?showto...ndpost&p=134691
Trainee has been working on it for a while (so have I). A lot of answers to you BSOD and other things are probably in that thread. the TEXTMODE method is ok in my opinion, but only if you plan to integrate a few drivers. The other driverpacks (Bashrat's) are much better because they load faster and are easier to set up.
Anyways, thanks for working on Nlite. It's always getting better.
0 -
i just checked the Nlite forum, and guess what... Nuhi has started working on a driver integration (textmode method). He already has a beta program for it thats works in some instances (although I don't believe he has tested it all the way, like trying to actually reinstall a system; because if done incorrectly, then there will be problems, like the GUI errors). anyways, i'll email/pm you when i get the chance.0
-
alright, i just found the email.... I'd be happy to test it out for you. Right now I am visiting home (until sunday) and I have access to the 3112. But the 3112 is already fixed in Bashrat's driverpack, so I don't know if that is necessary now.
At college I have access to the 3114 and NVRAID which Bashrat's driverpack doesn't work with. So those are good canidates.
If it's a simple script, or java language I might be able to help somewhat. Sorry about that message, i meant no offense by it.0 -
oh, i haven't gotten any email from you. I've just moved into my college and it's been my first two weeks there. Sorry, my parents probably intercepted the email, i'll have to dig it up somewhere.
btw, i didn't mean for you, but maybe one of the mod's could stick the topic; seeing how there are a lot of people out there who try this method, but without a really good guide as this one. I owe my success to the method you laid out.0 -
i think somebody should stickey this thread. And update it to reflect the new info0
-
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 -
thanx for the info and the hard work. I have been working on the textmode method to achieve the same thing, although my method requires more wasted space and is still a bit buggy. (or is it Nvidia that is buggy?)
@Bâshrat - Can you please fix the NVRAID within your driverpack with this.. Thanx.
0 -
dude, don't show your install key!
anyways, you can copy the entire contents of that cd to a folder on your hard drive. Lets say C:\xpcd
now, delete the winnt.sif
Now you need to remake the cd again. THe easiest way I can think of is to download Nlite
then use it to "make an Iso". Basically just select your XPCD folder and make an iso, you don't have to use Nlite to reduce your windows unless you want too.
Now burn your iso. use it to install.
0 -
that could be the problem, you may be using an unattended disc that alienware made. How can you check? look in the i386 directory for a file called winnt.sif. That should only exist if you are using an unattended cd.
0 -
yeah, an unattended install can/"should" fix your problem.
I would use this method described in this post:
http://www.msfn.org/board/index.php?showtopic=19792
Read through the whole post, and make sure to read my post at the end of it too.
Honestly though, if you are using a regular windows xp cd then you shouldn't have any problems with the F6. My problem started once I tried using an unattended cd to do my install.
0 -
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 -
are you using an unattended install? because F6 does not work with an unattended install (it gives the same error you are describing)
0 -
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.
(running off my NVRAID happily right now on a new system).0 -
you actually don't need the setup.exe for the canon drivers. I install my Canon S750 using this method
http://unattended.msfn.org/xp/drivers.htm
Just place your drivers (without .exe's and other non essential files if you like) into a directory in a $OEM$ folder. Well, you'll have to read the guide.
0 -
1. 3112 SATA RAID
2. PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02\4&3B1D9AB8&0&5840: Silicon Image SiI 3112 SATARaid Controller
3. Method 1 did not work, Method 2 did not work. The TextMode method worked.
Another thing... The TextMode method does work, and may be a viable alternative for stubborn drivers, but I don't think it should be implemented for all the drivers because it does required a longer loading time during the Windows XP textmode setup (assuming you are getting the driver pack for a single driver). Nevermind, i really don't know.
0 -
Your method works! I have a Si3112r and your method allowed me to install windows onto my raid installation. However, during the GUI install portion where windows normally searches for drivers, a window pop up and tells you that it can't find the .cpl file. (actually, i am not to sure exactly which file it is). To correct the problem i just pointed to my install CD with the file. Maybe i forgot to include it in the windows $OEM$ path in the first place.
I noticed that during my first attemp at your method, i copied the wrong 3112 files (i got the 3112, not the 3112r) and the textmode setup complained that it couldn't find i386/$OEM$/si3112r.sys. So I guess that is where windows is looking for files. I think the rest of the directories you posted aren't really needed. I fixed that, but then i forgot to remove the dll= line so i got an illegal file type message.
thanx0 -
i have the same problem with my Silicon Image 3112 raid. I can load it using F6 from a floppy and it will detect my drive or raid. But, when it comes time to actually copy the files, it says it can't find it.
I have tried using different versions of the drivers, but i still can't find one that works. I am also trying the integrated cd method, but that doesn't seem to work either. Maybe it's something wrong with the driver itself?
0
(running off my NVRAID happily right now on a new system).
Nlite Driver Integrate Question
in Device Drivers
Posted
you can do what rgreen said and make sure that the older nvidia drivers are removed so that windows next best choice is your non whql certified drivers. Or, get the newest whql lab drivers and windows will automatically install them.