trainee

TEXTMODE MassStorageDrivers Method

140 posts in this topic

can this work with external hard drive?? i just bought an external hard drive case... is it possible to get textsetup to recognise it so i can install an OS to it?? the case didnt come with any drivers it uses the ones from the winXP CD :-/
0

Share this post


Link to post
Share on other sites
Hello,

happy year for you all.

I tried and had many troubles to install a Dell Cerc Sata 1.5/6ch Raid controler on a Dell optiplex gx270 on windows 2000. been working on this for a week whitout sucess. I read all your messages and it helped a lot.

The trouble is that the raid controller driver could be installed on the computer but several windows 2000 files couldn't be copied during windows 2000 setup. The files are ; compatws.onf, compmgmt.chm,compmgmt.msc, dsctl.dll, compobj.dll, fp4.cat, mswrd832.cnv. And i have no idea.

I have no trouble for all the computer with ide disk, with the same \i386, which is on network.

i copied the driver files on
$OEM$\TEXTMODE
$OEM$\
which are
[quote]afamgt.sys
cerccin.dll
cercmgt.inf
cercsr6.cat
cercsr6.inf
cercsr6.sys
raidisk1
txtsetup.oem[/quote]the txtsetup.oem file
[quote][Disks]
d1 = "DELL CERC SATA 1.5/6ch Windows 2000/XP/2003 Device Drivers", \raidisk1, \


[Defaults]
scsi = cercsr6

[Scsi]
cercsr6 = "DELL CERC SATA 1.5/6ch RAID Controller", cercsr6

[Files.Scsi.cercsr6]
driver = d1, cercsr6.sys, cercsr6
driver = d1, afamgt.sys, afamgt
catalog = d1, cercsr6.cat
inf = d1, cercsr6.inf
inf = d1, cercmgt.inf
inf = d1, cerccin.dll, none


[Config.cercsr6]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 0
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1
value = Parameters\Device, NumberOfRequests, REG_DWORD, 0fe
value = Parameters\Device, UncachedExtAlignment, REG_DWORD, e
value = parameters\PnpInterface,5,REG_DWORD,1

[HardwareIds.scsi.cercsr6]
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02911028", "cercsr6"[/quote]

the unattend file:
[quote][MassStorageDrivers]"DELL CERC SATA 1.5/6ch RAID Controller" = "OEM"
"CD-ROM IDE (ATAPI 1.2)/Contr“leur IDE PCI" = "RETAIL"
[OEMBootFiles]
Txtsetup.oem
afamgt.sys
cercmgt.inf
cercsr6.cat
cercsr6.inf
cercsr6.sys[/quote]

I would appreciate any suggestion. Thank a lot,
0

Share this post


Link to post
Share on other sites
[quote name='first post']If you have .cpl,.dll,.exe,.vxd files you need to copy these to a third location (A really big thank you goes to rcordorica for his tireless work figuring this out). Copy these additional files to:

    * $OEM$\$$\OemDir\[/quote]

Are you sure you did this as well?
0

Share this post


Link to post
Share on other sites
I tried with cerccin.dll in \$oem$\$$\system32 . The driver files are ok.

just several windows 2000 files are missing.
0

Share this post


Link to post
Share on other sites
Have you nLite'd your 2K source CD ?
The missing files are not related to Mass Storage Drivers
0

Share this post


Link to post
Share on other sites
[b]trainee[/b] you are the man. B)

Thanks for your great little program.

RASOR ROCKS !!!

I have been looking for a way to include both the nvRaid and SiL 3114 Raid drivers into my UA Windows DVD.

Using your program and instructions I have no problems.

It works on my rig anyway:

ASUS A8N - SLI Deluxe
2 x Seagate 200GB SATA HDD

Thanks again. :D
0

Share this post


Link to post
Share on other sites
As you guys may know, I'm switching to this method for DriverPack MassStorage. So I'm re-reading the entire topic to get a clear view on it.

And I *think* that we can simplify the structure. Can anyone try this:

[quote]everything to:

    * $OEM$\TEXTMODE\
    * I386\$OEM$\

.cpl, .dll, .exe, .vxd to

    * $OEM$\$$\OemDir\

Now I'm guessing... wouldn't this be possible:[/quote][quote]everything to:

    * I386\$OEM$\TEXTMODE\
    * I386\$OEM$\

.cpl, .dll, .exe, .vxd to

    * I386\$OEM$\$$\OemDir\[/quote]

Just wondering... I think this would be better for the clarity of this method, *IF* this would work. I'll try to test it tomorrow.

BTW: finally stickied it... beat me for doin' that so late... :realmad:



EDIT: woohooow :D found some confirmations:

- that I386\$OEM$\TEXTMODE\ should work [url="http://support.microsoft.com/default.aspx?scid=kb;en-us;816299"]source[/url] (win 2k3) and [url="http://support.microsoft.com/kb/288344/EN-US/"]source 2[/url] (win2k)

AND

- that I386\$OEM$\$$\OemDir\ should work and that you WON'T need I386\$OEM$ [url="http://support.microsoft.com/kb/275334/EN-US/"]source[/url]

other useful link: [url="http://www.microsoft.com/technet/archive/winntas/deploy/depopt/gdautset.mspx"]http://www.microsoft.com/technet/archive/w...t/gdautset.mspx[/url]



EDIT: according to this [url="http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prbc_cai_qcxl.asp"]article[/url], you don't have to include the .cat files!

[quote]Catalog files (.cat) are not used during text-mode setup.[/quote]But, according to that same article, you have to use $OEM$\TEXTMODE, not I386\$OEM$\TEXTMODE... Note that this article is written specific for Windows XP, while the other ones were for win2k and win2k3...



EDIT: and I've found a possible cause for the setup is restarting bug...

[quote]When you are installing Microsoft Windows XP or Microsoft Windows Server 2003 on a new computer or on a computer that has the latest SCSI or IDE controller technology, you may have to use an OEM device driver to support, for example, a new mass storage controller, to continue with the installation. The symptoms that you have to install an OEM device driver include the following:
The computer may keep restarting and never start the GUI installation after the text mode Setup is finished.[/quote]

[url="http://support.microsoft.com/kb/310994"]source[/url] Edited by Bâshrat the Sneaky
0

Share this post


Link to post
Share on other sites
sweet. This is the portion that WinPE needs to detect mass storage drivers, so this would work REALLY well!

*edit* confirmed:
[url="http://www.nu2.nu/pebuilder/help/drivers.htm"]http://www.nu2.nu/pebuilder/help/drivers.htm[/url]

*edit2* Bashrat, might want to also look here at this driver pack that someone made for BartPE:
[url="http://home.earthlink.net/%7E1.414213563/PEplugins/MassStorageDrivers/MassStorageDriversNEW.htm"]http://home.earthlink.net/%7E1.414213563/P...eDriversNEW.htm[/url]

Just to compare drivers, to see if we have them all. I'm too lazy to compare it myself, but from the text, looks like a ton!

Your method is better in that it'll support both PE and XP, which is what I need since I'm using PE to install XP unattended.
0

Share this post


Link to post
Share on other sites
[quote name='muevelonyc' date='Feb 9 2005, 10:11 PM']sweet.  This is the portion that WinPE needs to detect mass storage drivers, so this would work REALLY well!

*edit* confirmed:
[url="http://www.nu2.nu/pebuilder/help/drivers.htm"]http://www.nu2.nu/pebuilder/help/drivers.htm[/url]

*edit2* Bashrat, might want to also look here at this driver pack that someone made for BartPE:
[url="http://home.earthlink.net/%7E1.414213563/PEplugins/MassStorageDrivers/MassStorageDriversNEW.htm"]http://home.earthlink.net/%7E1.414213563/P...eDriversNEW.htm[/url]

Just to compare drivers, to see if we have them all.  I'm too lazy to compare it myself, but from the text, looks like a ton!

Your method is better in that it'll support both PE and XP, which is what I need since I'm using PE to install XP unattended.[/quote]
:o Now THAT's a list! :o

I see they broke all driver signings... And they didn't remove tagfiles, txtsetup.oem files and readme's...

Maybe this will be useful, but you can't directly use it.. (other file format...)

EDIT: I *WILL* beat these guys (yes, it isn't one that did all the work) by providing you with more drivers :D Edited by Bâshrat the Sneaky
0

Share this post


Link to post
Share on other sites
I could say something profound. *BUT*....wooo hooo stickied!!!!

If someone confirms this:
[quote]everything to:

    * I386\$OEM$\TEXTMODE\
    * I386\$OEM$\

.cpl, .dll, .exe, .vxd to

    * I386\$OEM$\$$\OemDir\[/quote]
I would certianly implement it in RASOR. [RANT]I'm swamped otherwise I would try it out[/RANT]
0

Share this post


Link to post
Share on other sites
[quote]EDIT: woohooow  found some confirmations:

- that I386\$OEM$\TEXTMODE\ should work source (win 2k3) and source 2 (win2k)[/quote][url="http://support.microsoft.com/kb/288344/EN-US/"]http://support.microsoft.com/kb/288344/EN-US/[/url]

[quote]MORE INFORMATION
This example assumes that you are preinstalling the drivers by using a [b]distribution folder  [/b]and that the distribution folder has already been created.[/quote]


[url="http://greenmachine.msfnhosting.com/XPCREATE/faq.htm"]http://greenmachine.msfnhosting.com/XPCREATE/faq.htm[/url]
[quote]What is the difference between FILESCD\$OEM$ and FILESCD\I386\$OEM$?

In a CD installation, the $OEM$ directory is placed in the root of the CD. In a network installation, $OEM$ is placed inside the I386 directory. The corresponding directories in XPCREATE are FILESCD\$OEM$ and FILESCD\I386\$OEM$, respectivly. All examples and istructions on this site assume a CD installation. If you are creating a network distribution, please adjust these directories accordingly.[/quote]

Distribution folder means install over network and not CD??

We must stil use ? :unsure:

* I386\$OEM$\TEXTMODE\
* I386\$OEM$\
0

Share this post


Link to post
Share on other sites
after reading the post and the readme file of the intel application accelerator 2.3. I have extracted the setup.exe and i have found 6 files:
idechndr.inf IdeBusDr.sys IdeChnDr.sys Txtsetup.oem IprtCnst.dll and [b]IATA3000.CAT[/b]
i have to put this line in the unattended:

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

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

and also i must put these 4 files in the directory \$OEM$\TextMode and the file IprtCnst.dll in \$Oem$\$$\System32, but my question about the file [b]IATA3000.CAT[/b],
must i put it in the same directory like the 4 files?
must i write it in the list of [OEMBootFiles]?

Thanks
0

Share this post


Link to post
Share on other sites
@major: It might be helpful to post the txtsetup.oem file. I am not familiar with the [i]Primary IDE Channel[/i] & [i]Secondary IDE Channel[/i] you have listed. I don't know of people having to list both channels. I recommend you use this instead:
[code]"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"[/code]

As for the files you should put all of them in both place (including the .CAT). This won't take up much room on your CD and it will be your best bet that it will work. Remember this method *ONLY* works for unattended installs, you need to have the rest of your install working and *NOT* hit F6.

Hope this helps.
0

Share this post


Link to post
Share on other sites
@Trainee, here is my TxtSetup.oem

[Disks]
disk1 = "Intel Storage Driver", idechndr.sys, \

[Defaults]
scsi = idebusdr

[scsi]
idechndr0 = "Primary IDE Channel"
idechndr1 = "Secondary IDE Channel"
idebusdr = "Intel® 82801BA Ultra ATA Controller"

;-------------------------------------------

[Files.scsi.idechndr0]
driver = disk1, idechndr.sys, idechndr
inf = disk1, idechndr.inf
catalog = disk1, iata3000.cat

[Files.scsi.idechndr1]
driver = disk1, idechndr.sys, idechndr
inf = disk1, idechndr.inf
catalog = disk1, iata3000.cat

[Files.scsi.idebusdr]
driver = disk1, idebusdr.sys, idebusdr
inf = disk1, idechndr.inf
catalog = disk1, iata3000.cat

;-------------------------------------------

[Config.idechndr]
value = "", tag, REG_DWORD, 1b
value = "", ErrorControl, REG_DWORD, 1
value = "", Group, REG_SZ, "SCSI miniport"
value = "", Start, REG_DWORD, 0
value = "", Type, REG_DWORD, 1

[Config.idebusdr]
value = "", tag, REG_DWORD, 1a
value = "", ErrorControl, REG_DWORD, 1
value = "", Group, REG_SZ, "System Bus Extender"
value = "", Start, REG_DWORD, 0
value = "", Type, REG_DWORD, 1


;-------------------------------------------------------
; Only one HardwareID can be uncommented.
; Uncomment the appropriate ID string by removing the semi-colon.
; Then comment out the others.
;-------------------------------------------------------
[HardwareIds.scsi.idebusdr]
;id = "PCI\VEN_8086&DEV_2411&CC_0101","idebusdr"
;id = "PCI\VEN_8086&DEV_2421&CC_0101","idebusdr"
;id = "PCI\VEN_8086&DEV_244B&CC_0101","idebusdr"
id = "PCI\VEN_8086&DEV_24CB&CC_0101","idebusdr"

[HardwareIds.scsi.idechndr0]
id = "I_Primary_IDE_Channel","idechndr"

[HardwareIds.scsi.idechndr1]
id = "I_Secondary_IDE_Channel","idechndr"


And for listing both channels i have read it in the readme file of the intel application accelerator, here is the text:

[b]************************************************************
* 6. ADVANCED INSTALLATION INSTRUCTIONS
************************************************************

The following SETUP flags are available:
-? Help information for the setup flags
(shown below)
-S Silent install (no user prompts)
-B Forces a system reboot after installation
-P <path> Supplies target installation path
-A Extracts all driver files (does not install
driver) to <path> if -P is also supplied, or
the default directory otherwise
-N Installs all components except driver
-O <name> Supplies target Start Menu Program Folder
name if installing Companion applet
-L <lang code> Forces a particular language install (See
Section 3 for a table mapping <lang code>
to language)
-build Displays build number
-f2 <path\name> Creates a log file in <path> with <name>;
this is to be used during silent
installation.
-noqfe Prevents Microsoft patch from being
installed. The patch prevents a blue screen
from occurring when attempting to play audio
content from CDs in digital mode on
Windows 98, Windows 98 SE, and Windows Me.
-PIO_ALL Causes all devices installed in system to run
in standard PIO transfer mode rather than
optimal transfer mode. Useful for
troubleshooting device issues.


*** "Package-for-the-web" requires that an additional -A be
placed before any flag. Therefore, an example file extraction
would be IATA_CD -A -A -P C:\<path> ***

Notes: Flags and their parameters are not case-sensitive.
Flags may be supplied in any order, with the
exception of the -S and -L flags which must be
supplied last. When using the -A flag, a target
path may be specified via the -P flag, and the -O,
-L, -S, and -N flags are ignored. When using the -P
or -O flags, a space is required between the flag
and the argument; when using -L and -f2, however, there
should be no space. When using the -f2 flag,
a log file name and path must be specified.

To load just the driver as outlined in the Microsoft*
document, "Deployment Guide Automating Windows NT Setup,"
use the supplied TXTSETUP.OEM file included in this
package and insert the lines below into the UNATTEND.TXT
file. This method is available for Microsoft* Windows*
NT* 4.0, Windows 2000, and Windows XP. (For Windows NT 4.0,
the TXTSETUP.OEM, INTELATA.INF, and INTELATA.SYS files need to
first be extracted from the compressed .CAB file. For
Windows 2000 and Windows XP, the idechndr.inf, IdeBusDr.sys,
idechndr.sys, and Txtsetup.oem files need to be extracted.
To extract these files, run 'SETUP -A -P <path>' as described
above.)

Microsoft Windows NT 4.0:
// Insert the lines below into the UNATTEND.TXT file

[MassStorageDrivers]
"Intel Ultra ATA Controller" = OEM

[OEMBootFiles]
INTELATA.INF
INTELATA.SYS
TXTSETUP.OEM

Microsoft Windows 2000 and Windows XP:

// Insert the lines below into the UNATTEND.TXT file

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

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

The IprtCnst.dll file must be placed in the following
folder in your directory structure in order to be loaded
during driver installation:

C:\I386\$Oem$\$$\System32

Please refer to the following Microsoft Knowledge Base
article for information on why the IprtCnst.dll file
cannot be listed in the [OEMBootFiles] location in the
unattend.txt file:

[url="http://support.microsoft.com/support/kb/articles/Q275"]http://support.microsoft.com/support/kb/articles/Q275[/url]
/3/34.ASP?LN=EN-US&SD=gn&FR=0&qry=Q275334&rnk=1&src=
DHCS_MSPSS_gn_SRCH&SPR=CHS[/b]

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