MSFN Forum: TEXTMODE MassStorageDrivers Method - MSFN Forum

Jump to content



  • 7 Pages +
  • 1
  • 2
  • 3
  • 4
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

TEXTMODE MassStorageDrivers Method How my 3ware drivers wiggled onto the CD Rate Topic: -----

#36 User is offline   rcordorica 

  • Windows Hacker
  • Group: Members
  • Posts: 26
  • Joined: 10-August 04

  Posted 10 September 2004 - 09:55 PM

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.

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


#37 User is offline   rcordorica 

  • Windows Hacker
  • Group: Members
  • Posts: 26
  • Joined: 10-August 04

Posted 10 September 2004 - 11:18 PM

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.

Posted Image
Posted Image

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.

#38 User is offline   trainee 

  • ThunderWalker
  • PipPip
  • Group: Members
  • Posts: 108
  • Joined: 04-May 04

  Posted 12 September 2004 - 06:19 AM

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

#39 User is offline   cfeedback 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 05-September 04

Posted 13 September 2004 - 10:56 AM

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

#40 User is offline   big poppa pump 

  • Damn Newbies!!
  • PipPipPip
  • Group: Members
  • Posts: 406
  • Joined: 10-September 03

Posted 13 September 2004 - 11:10 AM

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

#41 User is offline   trainee 

  • ThunderWalker
  • PipPip
  • Group: Members
  • Posts: 108
  • Joined: 04-May 04

  Posted 13 September 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.

@big poppa pump:

Quote

What really surprises me is that the **** error 18 crops up randomly.
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!

#42 User is offline   cfeedback 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 05-September 04

Posted 13 September 2004 - 07:30 PM

trainee, on Sep 13 2004, 12:36 PM, said:

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

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.

#43 User is offline   trainee 

  • ThunderWalker
  • PipPip
  • Group: Members
  • Posts: 108
  • Joined: 04-May 04

  Posted 13 September 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.

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.

#44 User is offline   cfeedback 

  • Newbie
  • Group: Members
  • Posts: 23
  • Joined: 05-September 04

Posted 13 September 2004 - 08:38 PM

trainee, on Sep 13 2004, 08:29 PM, said:

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

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

#45 User is offline   rcordorica 

  • Windows Hacker
  • Group: Members
  • Posts: 26
  • Joined: 10-August 04

Posted 22 September 2004 - 02:48 AM

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.

#46 User is offline   Bâshrat the Sneaky 

  • aka Wim Leers
  • PipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 2,214
  • Joined: 29-October 03
  • OS:none specified
  • Country: Country Flag

Posted 22 September 2004 - 05:51 AM

rcordorica, on Sep 22 2004, 10:48 AM, said:

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.

Good job!!!

P.S.: I think I'll use this method in DriverPack MassStorage! :P

#47 User is offline   big poppa pump 

  • Damn Newbies!!
  • PipPipPip
  • Group: Members
  • Posts: 406
  • Joined: 10-September 03

Posted 22 September 2004 - 07:52 AM

I think I will have another go at this method when I get back home from work this evening.

#48 User is offline   rcordorica 

  • Windows Hacker
  • Group: Members
  • Posts: 26
  • Joined: 10-August 04

Posted 01 October 2004 - 06:12 PM

i think somebody should stickey this thread. And update it to reflect the new info

#49 User is offline   trainee 

  • ThunderWalker
  • PipPip
  • Group: Members
  • Posts: 108
  • Joined: 04-May 04

  Posted 01 October 2004 - 08:36 PM

@rcordorica: woah...hint, hint, hint to me? Did you get my email? I am looking to update the guide but I was hoping you could help me create/debug a utility I have been writing. If you didn't get my email: Congrats on moving the TEXTMODE method to the next level. My email is shown in my signature, drop me a line.

#50 User is offline   rcordorica 

  • Windows Hacker
  • Group: Members
  • Posts: 26
  • Joined: 10-August 04

Posted 01 October 2004 - 11:03 PM

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.

#51 User is offline   rcordorica 

  • Windows Hacker
  • Group: Members
  • Posts: 26
  • Joined: 10-August 04

Posted 01 October 2004 - 11:29 PM

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.

#52 User is offline   trainee 

  • ThunderWalker
  • PipPip
  • Group: Members
  • Posts: 108
  • Joined: 04-May 04

  Posted 02 October 2004 - 02:38 AM

@rcordorica: no offense taken at all, the guide really needs to be updated. As far as a sticky goes thats bashrat's department. Hopefully if we can get this program to work, M2 will be extremely easy to use for a wide range of people.

We can discuss more about the code via email or PM, I'm hoping to draw on your expertise in validating the output of the program (ie. does it make the correct directories?, copy the correct files?, and write the correct winnt.sif/textsetup.oem entries?). I'm debugging something for work right now so I may not have a chance to get it to you for a couple of days though...

#53 User is offline   rcordorica 

  • Windows Hacker
  • Group: Members
  • Posts: 26
  • Joined: 10-August 04

Posted 02 October 2004 - 03:43 PM

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.

#54 User is offline   DisabledTrucker 

  • The truck or you is disabled?
  • PipPip
  • Group: Members
  • Posts: 274
  • Joined: 02-July 04

Posted 05 October 2004 - 08:38 PM

Ok, as I have mentioned in other threads, I have a Chaintech 7NJS Zenith, which will also use the MSI drivers, much the same as other boards, the MSI ones are just better.

I have done all kinds of different ways of doing these drivers, (including but not limited to putting the driver entries into the Txtsetup.sif file, which is what I am trying to avoid here, even it does not work that way.) Now from what I have gathered from reading M$ own documents, you have to put your files in a couple places:
$OEM$\Textmode\ (copy all files here from driver folder, remove them from any WinXP folder, but not subfolders within the WinXP folder, you will need those in your textmode folder, (replace folder name for your O/S.))
ie: $OEM$\Textmode\raidtool is fine but $OEM$\Textmode\WinXP\raidtool isn't.
$OEM$\Inf (copy *.inf files here)
$OEM$\$$\System32\ (copy any other files here not listed elsewhere from Textmode folder, such as *.exe, *.nvu, etc.)
$OEM$\$$\System32\dllcache (make hidden and copy *.dll files in here)
$OEM$\$$\System32\Drivers (copy *.sys files here)
Remove any *.txt files as they shouldn't be needed especially readme's.

Now make sure you dont include any internal folders from your driver set. For example if your download includes a WinXP folder pull out the files from that folder and put them all into your Textmode folder, your going to edit your Txtsetup.oem file to make it work correctly. If you have a Disk1 file without an extension, or a disk1.tag file, or something to that sort, make sure it's in the Textmode folder. Now place your Txtsetup.oem file there as well, then open it cause you need to make sure it reads similar to:
;textsetup.oem
[Disks]
;includes settings for NVRaid, NVATA, as well as Promise Fasttrak 376 from MSI.
;For NTFS use (WinNT32.sif):
    d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\Textmode\
;For Fat use (WinNT.sif):
    d2 = "NVIDIA RAID DRIVER (SCSI)",\disk1,.\Textmode\
    d3 = "Promise FastTrak 376/378 Driver Diskette",\fasttx2k,\Textmode\
    d4 = "Promise FastTrak 376/378 Driver Diskette",\fasttx2k,.\Textmode\
    d5 = "Promise SATA378 Driver Diskette", \ulsata,\Textmode\
    d6 = "Promise SATA378 Driver Diskette", \ulsata,.\Textmode\
[Defaults]
    scsi = RAIDCLASS
    scsi = FastTrak_TX2K_xp
[scsi]
     RAIDCLASS = "NVIDIA RAID CLASS DRIVER (required)"
     BUSDRV = "NVIDIA NForce Storage Controller (required)"
     UlSata_xp   = "WinXP Promise SATA378 (tm) Controller", UlSata
     FastTrak_TX2K_xp   = "WinXP Promise FastTrak 376/378 (tm) Controller", fasttx2k
[Files.scsi.RAIDCLASS]
     driver  = d1,nvraid.sys,RAIDCLASS
     inf     = d1,nvraid.inf
     dll     = d1,nvraidco.dll
     catalog = d1,nvraid.cat
     driver  = d2,nvraid.sys,RAIDCLASS
     inf     = d2,nvraid.inf
     dll     = d2,nvraidco.dll
     catalog = d2,nvraid.cat
[Files.scsi.BUSDRV]
     driver = d1,nvatabus.sys,BUSDRV
     inf    = d1, nvatabus.inf
     dll    = d1,idecoi.dll
     catalog = d1, nvata.cat
     driver = d2,nvatabus.sys,BUSDRV
     inf    = d2, nvatabus.inf
     dll    = d2,idecoi.dll
     catalog = d2, nvata.cat
[Files.scsi.FastTrak_TX2K_xp]
     driver = d3, fasttx2k.sys, fasttx2k
     dll    = d3, ptipbmf.dll
     inf    = d3, fasttx2k.inf
     catalog= d3, fasttx2k.cat
     driver = d4, fasttx2k.sys, fasttx2k
     dll    = d4, ptipbmf.dll
     inf    = d4, fasttx2k.inf
     catalog= d4, fasttx2k.cat
[Files.scsi.UlSata_xp]
     driver = d5, UlSata.sys, UlSata
     dll    = d5, ptipbm.dll
     inf    = d5, UlSata.inf
     catalog= d5, UlSata.cat
     driver = d6, UlSata.sys, UlSata
     dll    = d6, ptipbm.dll
     inf    = d6, UlSata.inf
     catalog= d6, UlSata.cat
[Config.RAIDCLASS]
[Config.BUSDRV]
[Config.UlSata]
    value = "", Tag, REG_DWORD, 1
[Config.fasttx2k]
    value = "", Tag, REG_DWORD, 1
[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.FastTrak_TX2K_xp]
    id="PCI\VEN_105A&DEV_3376", "fasttx2k"
    id="PCI\VEN_105A&DEV_3373", "fasttx2k"
[HardwareIds.scsi.UlSata_xp]
    id = "PCI\VEN_105A&DEV_3373","UlSata"
Now make sure in your WinNT.sif file you have:
;SetupMgrTag
[Data]
    AutoPartition=No
    MsDosInitiated="0"
    UnattendedInstall="Yes"
[Unattended]
    DriverSigningPolicy=Ignore
    NonDriverSigningPolicy=Ignore
    DUStopOnError=Yes
    Filesystem=*
    ForceHALDetection=Yes
    KeyboardLayout=US
    OverwriteOemFilesOnUpgrade=No
    OemFilesPath=".\$OEM$\"
    OemPnPDriversPath="PNPDriver";"PNPDriver\AudioDrv";"PNPDriver\AudioUtl";"PNPDriver\Display";"PNPDriver\Ethernet";"PNPDriver\GART";"PNPDriver\MemCtl";"PNPDriver\Modem";"PNPDriver\Mouse";"PNPDriver\Printer";"PNPDriver\SMBus";"PNPDriver\UPS";"PNPDriver\Video"
;Only need OemPnPDriversPath, if you have PNP Drivers set up to install, if you want to have the stuff you copy to the hard drive using the $OEM$ folder, you can place that in i386 and make the above path: ".\i386\$OEM$\" without the quotes, and when the O/S is done installing it's supposed to remove the folders for you, though not even that way worked when trying to install these drivers.
    OemSkipEula=Yes
    OemPreinstall=Yes
    OEMSkipWelcome=1
    TargetPath=\WINDOWS
    Unattendmode=ProvideDefault 
;In case later I need to change settings for different computer, can be several different settings, FullyUnattended is most used in forum, others are DefaultHide (default setting), GuiAttended, and ReadOnly.
    UnattendSwitch=Yes
    WaitForReboot=No

...Only Neccessary lines listed here...

[MassStorageDrivers]
    "NVIDIA RAID CLASS DRIVER (required)"=OEM
    "NVIDIA NForce Storage Controller (required)"=OEM
    "WinXP   Promise SATA378 (tm) Controller"=OEM
    "WinXP   Promise FastTrak 376/378 (tm) Controller"=OEM
    "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"=RETAIL
[OEMBootFiles]
    txtsetup.oem
    nvraid.sys
    nvraidco.dll
    NvAtaBus.sys
    idecoi.dll
    ulsata.sys
    ptipbm.dll
    fasttx2k.sys
    ptipbmf.dll
    nvraid.inf
    nvatabus.inf
    ULSata.inf
    Fasttx2k.inf
    nvata.cat
    nvraid.cat
    fasttx2k.cat
    ulsata.cat

I have also figured out that you need to set up all your drivers, other files, and anything else your adding to your UXPCD prior to doing your WinNT.sif file from SetupManager, this will give you all the $Restore$ files you will need to make and in them it will automatically rename all the files and paths that you will need to go back and rename so they will be recognized on the CD. Once you have opened each of those files and noted what names in the folder they are in need changing and change those names, you are ready to burn your CD, if you do not do this step, Windows XP will miss a lot of the files, or your CD writer program will attempt to rename them incorrectly, prior to burning the files. (Roxio version 6 was severly bad about doing this, even with a regular WinXP disk, after you already clicked the "Burn" button, and if you cancelled it wouldn't let you burn the disk. If you didn't change the names and add the $Restore$ file with the names inserted in them in the proper folders, XP wouldn't find them later!)

Now according to M$'s obscure instructions on this, under Windows XP, it should work, but to this point I keep getting that dreaded error 18 in line 1747 error, which is driving me up the friggen wall... I should also mention that I have tested these drivers and they work perfectly when using them through F-6, although the only one which loads is the Fasttrak at this point. The NForce, I have never tried to do prior to loading the operating system before, but the fasttrak should be the one which takes as it's necessary for the SATA drives to be recognized with my motherboard. Alas, to my dismay, none of these drivers either take nor will work when trying to do this through unattended. Yes, I have tried every way mentioned so far in these threads, but I still haven't gotten them to work.

#55 User is offline   DisabledTrucker 

  • The truck or you is disabled?
  • PipPip
  • Group: Members
  • Posts: 274
  • Joined: 02-July 04

Posted 06 October 2004 - 11:03 AM

I've considered using this method: XP Basic CD Unattended SATA/RAID Install , How to avoid hitting F6 for CD Install. , but I don't particualarly want it set up this way as I need for the entire CD to be there for other computers I may use this on. All I want is to be able to slipstream the mass storage drivers and have them work when installing to my other system. I have even tried using that method and sort of integrating it into the regular UXPCD that I am trying to make, but that doesn't work either. I am about to give up on getting these things to work correctly, and just hope that my floppy drives will hold up until M$ gets off their a$$es and does away with the floppy drive altogether for installations, and fixes their unattended files.

Share this topic:


  • 7 Pages +
  • 1
  • 2
  • 3
  • 4
  • Last »
  • 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