Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

TEXTMODE MassStorageDrivers Method

- - - - -

  • Please log in to reply
139 replies to this topic

#76
minigun

minigun

    Member

  • Member
  • PipPip
  • 141 posts
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 :-/


How to remove advertisement from MSFN

#77
anyanka

anyanka
  • Member
  • 2 posts
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

afamgt.sys
cerccin.dll
cercmgt.inf
cercsr6.cat
cercsr6.inf
cercsr6.sys
raidisk1
txtsetup.oem

the txtsetup.oem file

[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"


the unattend file:

[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


I would appreciate any suggestion. Thank a lot,

#78
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • OS:none specified
  • Country: Country Flag

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\


Are you sure you did this as well?

#79
anyanka

anyanka
  • Member
  • 2 posts
I tried with cerccin.dll in \$oem$\$$\system32 . The driver files are ok.

just several windows 2000 files are missing.

#80
Bilou_Gateux

Bilou_Gateux

    Powered by Windows Embedded

  • Member
  • PipPipPipPipPip
  • 768 posts
Have you nLite'd your 2K source CD ?
The missing files are not related to Mass Storage Drivers
OS Version = 5.1.2600 Service Pack 3
Platform ID = 2 (NT)
Service Pack = 3.0
Suite = 0x0140
Product Type = 1
Architecture = x86

#81
john0452

john0452

    Newbie

  • Member
  • 19 posts
trainee 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

#82
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • OS:none specified
  • Country: Country Flag
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:

everything to:

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

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

    * $OEM$\$$\OemDir\

Now I'm guessing... wouldn't this be possible:

everything to:

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

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

    * I386\$OEM$\$$\OemDir\


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 source (win 2k3) and source 2 (win2k)

AND

- that I386\$OEM$\$$\OemDir\ should work and that you WON'T need I386\$OEM$ source

other useful link: http://www.microsoft...t/gdautset.mspx



EDIT: according to this article, you don't have to include the .cat files!

Catalog files (.cat) are not used during text-mode setup.

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

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.


source

Edited by Bâshrat the Sneaky, 09 February 2005 - 06:26 AM.


#83
muevelonyc

muevelonyc

    USB Key Freak

  • Member
  • Pip
  • 67 posts
sweet. This is the portion that WinPE needs to detect mass storage drivers, so this would work REALLY well!

*edit* confirmed:
http://www.nu2.nu/pe...elp/drivers.htm

*edit2* Bashrat, might want to also look here at this driver pack that someone made for BartPE:
http://home.earthlin...eDriversNEW.htm

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.

#84
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • OS:none specified
  • Country: Country Flag

sweet.  This is the portion that WinPE needs to detect mass storage drivers, so this would work REALLY well!

*edit* confirmed:
http://www.nu2.nu/pe...elp/drivers.htm

*edit2* Bashrat, might want to also look here at this driver pack that someone made for BartPE:
http://home.earthlin...eDriversNEW.htm

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.

: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, 09 February 2005 - 05:32 PM.


#85
trainee

trainee

    ThunderWalker

  • Member
  • PipPip
  • 108 posts
I could say something profound. *BUT*....wooo hooo stickied!!!!

If someone confirms this:

everything to:

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

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

    * I386\$OEM$\$$\OemDir\

I would certianly implement it in RASOR. [RANT]I'm swamped otherwise I would try it out[/RANT]
Posted Image

#86
W2Kuser

W2Kuser
  • Member
  • 2 posts

EDIT: woohooow  found some confirmations:

- that I386\$OEM$\TEXTMODE\ should work source (win 2k3) and source 2 (win2k)

http://support.micro...b/288344/EN-US/

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



http://greenmachine....PCREATE/faq.htm

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.


Distribution folder means install over network and not CD??

We must stil use ? :unsure:

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

#87
Bâshrat the Sneaky

Bâshrat the Sneaky

    aka Wim Leers

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,214 posts
  • OS:none specified
  • Country: Country Flag
Dunno... Please test. I don't have the time ATM.

#88
Major

Major

    Advanced Member

  • Member
  • PipPipPip
  • 308 posts
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 IATA3000.CAT
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 IATA3000.CAT,
must i put it in the same directory like the 4 files?
must i write it in the list of [OEMBootFiles]?

Thanks

#89
trainee

trainee

    ThunderWalker

  • Member
  • PipPip
  • 108 posts
@major: It might be helpful to post the txtsetup.oem file. I am not familiar with the Primary IDE Channel & Secondary IDE Channel you have listed. I don't know of people having to list both channels. I recommend you use this instead:
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

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

#90
Major

Major

    Advanced Member

  • Member
  • PipPipPip
  • 308 posts
@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:

************************************************************
* 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:

http://support.micro...b/articles/Q275
/3/34.ASP?LN=EN-US&SD=gn&FR=0&qry=Q275334&rnk=1&src=
DHCS_MSPSS_gn_SRCH&SPR=CHS


Thanks

#91
trainee

trainee

    ThunderWalker

  • Member
  • PipPip
  • 108 posts
@major: well did you try it? Without seeing the txtsetup.oem I wouldn't have known that all 3 were listed. I would use the entries they have for your unattend.txt file, but then I would also add the line I suggested. I believe the instructions they provide are for network based installs which require the changes listed in this guide to work for CD-based installs.

The generic IDE driver is usually important to have for installation following reboot. You should probably try it both ways, but I still advise you to include it to give yourself the best possible shot at success. Also still copy all of the files to the directories indicated in the guide. If it doesnt work it most probably won't be able to even find your hard drives, let alone format them.
Posted Image

#92
Hirudin

Hirudin

    Newbie

  • Member
  • 23 posts
(I tried to include many keywords to help searches.)
Welp, I made it work, thanks mostly to this guide.

I've successfully included the Via "8237 Integrated Serial ATA RAID controller" drivers in my Windows 2000 CD. I no longer need to hit F6, no more driver disk. The SATA controller is on my Abit KV7 motherboard and the HDD is a Maxtor Y120M0 (if it somehow matters).

Here's what I did (as best as I can remember).

*Copied Files*
I copied the following files to my ROOT\I386\$OEM$ and ROOT\$OEM$\TEXTMODE folders:
TXTSETUP.OEM
VIAMRAID.CAT
VIAMRAID.INF
VIAMRAID.SYS

(After extracting the file downloaded off the Via Arena website the txtsetup.oem file was in EXTRACTION-ROOT\DriverDisk and viamraid.cat , viamraid.inf , and viamraid.sys were in EXTRACTION-ROOT\DriverDisk\RAID\Win2000 .)

*Modified both TXTSETUP.OEM files*
I also modified both TXTSETUP.OEM files, I'm pretty sure this needed to be done... In the [disks] section I replaced the path after the last " , " (comma) with " \ " (backslash).
The original [disks] section looked like this:

[Disks]d1 = "VIA RAID Combo Driver Diskette", \RAID\winxp\VIAMRAID.SYS, \RAID\winxp
d2 = "VIA RAID Combo Driver Diskette", \RAID\win2000\VIAMRAID.SYS, \RAID\win2000
d3 = "VIA RAID Combo Driver Diskette", \RAID\Winnt40\VIAMRAID.SYS, \RAID\Winnt40
d4 = "VIA RAID Combo Driver Diskette", \RAID\2003ia32\VIAMRAID.SYS, \RAID\2003ia32
#d9 = "VIA RAID Combo Driver Diskette", \RAID\x64\VIAMRAID.SYS, \RAID\x64

d5 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\winxp\viapdsk.sys, \PIDE\winxp
d6 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\win2000\viapdsk.sys, \PIDE\win2000
d7 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\winnt40\viapdsk.sys, \PIDE\winnt40
d8 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\2003ia32\viapdsk.sys, \PIDE\2003ia32

Now the [disks] section looks like this:

[Disks]d1 = "VIA RAID Combo Driver Diskette", \RAID\winxp\VIAMRAID.SYS, \
d2 = "VIA RAID Combo Driver Diskette", \RAID\win2000\VIAMRAID.SYS, \
d3 = "VIA RAID Combo Driver Diskette", \RAID\Winnt40\VIAMRAID.SYS, \
d4 = "VIA RAID Combo Driver Diskette", \RAID\2003ia32\VIAMRAID.SYS, \
#d9 = "VIA RAID Combo Driver Diskette", \RAID\x64\VIAMRAID.SYS, \

d5 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\winxp\viapdsk.sys, \
d6 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\win2000\viapdsk.sys, \
d7 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\winnt40\viapdsk.sys, \
d8 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\2003ia32\viapdsk.sys, \



*Modified the WINNT.SIF file*
I added the following lines to the bottom of my WINNT.SIF file in my I386 directory.
(Yes, it works without the driver filenames, at least in my case.)

[MassStorageDrivers]"VIA RAID Controller(Windows 2000)" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OEMBootFiles]
TXTSETUP.OEM

BTW, I got the string: "VIA RAID Controller(Windows 2000)" from this section of the txtsetup.oem file:

[scsi]VIARAID_MULTIPLE_2003IA32 = "VIA RAID Controller(Windows 2003 IA32)"
VIARAID_MULTIPLE_XP = "VIA RAID Controller(Windows XP)"
VIARAID_MULTIPLE_2K = "VIA RAID Controller(Windows 2000)"
VIARAID_MULTIPLE_NT = "VIA RAID Controller(Windows NT4)"
#VIARAID_MULTIPLE_2003K864 = "VIA RAID Controller(Windows 2003 AMDx86-64)"

VIAPDSK_VT4149_2003IA32 = "VIA ATA/ATAPI Host Controller(Windows 2003IA32)"
VIAPDSK_VT4149_XP = "VIA ATA/ATAPI Host Controller(Windows XP)"
VIAPDSK_VT4149_2K = "VIA ATA/ATAPI Host Controller(Windows 2000)"
VIAPDSK_VT4149_NT = "VIA ATA/ATAPI Host Controller(Windows NT4)"


I think that's about it... (I'll check this thread periodicly for a couple weeks, so if you have any questions for me, ask them soon).

#93
Hirudin

Hirudin

    Newbie

  • Member
  • 23 posts

Distribution folder means install over network and not CD??

We must stil use ? :unsure:

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

<{POST_SNAPBACK}>


I hope I understand your question...

When they say "distribution folders" they're talking about the $OEM$ directories. The $OEM$ folders are used to "distribute" other files. (I think so anyway)

#94
ccfly

ccfly
  • Member
  • 6 posts

Interesting post!

One remark, in fact an addition:

driver.cat (I believe this is the PnP information)


I'm quite sure this is the WHQL license.

Further no remarks! Nice guide!

<{POST_SNAPBACK}>


Does this Method work in Multi-Boot Unattened CD ?

#95
berrick

berrick

    Junior

  • Member
  • Pip
  • 75 posts
**DOH** having bad day

just to clear up a few points raised in this post... from experience

$OEM$\TEXTMODE\
Is the only place you need to add the files for installation from a CD

*.cat files are for WHQL

dsik1 refers to a "tagfile" not a directory and is required to identify the correct diskette is inserted when ask for by setup. For correctness it should be included on the CD but will work if not.

Under the [MassStorageDrivers] heading in the winnt.sif file you have to include "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" else you will get a BSOD at some point after first reboot. The other enteries MUST match those take from the TXTsetup.oem file.

The backslah at the end of this line is important d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\

this is why

Directory = \
Directory on the diskette where the installation files are located. The directory must be specified as a full path from the root and must not specify a drive. This must be a period if you have partitioned or formatted your hard drive with (FAT) or FAT32 file system and you initiate setup with Winnt.exe from DOS or a backslash If you have partitioned or formatted your hard drive with the NTFS and you initiate Windows Setup with Winnt32.exe (like with an uacd), You will get an error if you get it wrong!

Error message
illegal or missing file type specified in [Files.scsi.yourhardware] is as a result of a known issue - see KB275334

Okay you need to open up your txtsetup.oem file (notepad or any text editor will do) and change any reference to "DLL = " to "INF = " (thanks to rcordorica for figuring this out). For some reason textsetup chokes on these entries. These entries should be easy to find and replace in the file. Save the modified file and close it. Again if you don't have any "DLL = " references in your txtsetup.oem then you don't need to change anything and you read this entire section of the guide for nothing

distibution folders refer to the directory structure used to carry out unattended CD installs or installs from a network share. The structure is identical apart from one important fact, on a uacd the distribution folders are not under the i386 dirctory but are on a network share.

I hope this does not come over wrong but am in a rush :huh:

Any how did a complete guide to the txtsetup.oem and what each bit means etc if any1 is interested i will post it, as you can install other drivers this way! I even think another member has an extensive post on how to do it

hope this is helpful

Edited by berrick, 21 September 2005 - 10:50 AM.


#96
Incroyable HULK

Incroyable HULK

    Slowly Turning Green...

  • Super Moderator
  • 1,257 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Well well well,

the time has finally come to integrate some MassStorageDrivers to my CD! I have some notebook with Intel SATA controller and I need to add theses drivers to my installation CD.

So I took a look at this whole topic and unfortunatly, it doesn't work for me.

Here is what I've got:
txtsetup.oem

[Disks]disk1 = "Intel Application Accelerator driver", iaStor.sys, \

[Defaults]
scsi = iaStor_ICH6R

;----------- Component Section -----------

[scsi]
iaStor_ICH6R = "Intel® 82801FR SATA RAID Controller (Desktop ICH6R)"
iaAHCI_ICH6R = "Intel® 82801FR SATA AHCI Controller (Desktop ICH6R)"
iaAHCI_ICH6M = "Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)"
iaStor_ICH5R = "Intel® 82801ER SATA RAID Controller (Desktop ICH5R)"
iaStor_ICH5RHR = "Intel® 6300ESB SATA RAID Controller"

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

[Files.scsi.iaStor_ICH6R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH6R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaAHCI_ICH6M]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ICH5R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaStor_ICH5RHR]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat


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

[Config.iaStor]
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

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

[HardwareIds.scsi.iaStor_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6M]
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH5R]
id = "PCI\VEN_8086&DEV_24DF&CC_0104","iaStor"

[HardwareIds.scsi.iaStor_ICH5RHR]
id = "PCI\VEN_8086&DEV_25B0&CC_0104","iaStor"


winnt.sif

[MassStorageDrivers]"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
"Intel® 82801FR SATA RAID Controller (Desktop ICH6R)" = "OEM"
"Intel® 82801FR SATA AHCI Controller (Desktop ICH6R)" = "OEM"
"Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)" = "OEM"
"Intel® 82801ER SATA RAID Controller (Desktop ICH5R)" = "OEM"
"Intel® 6300ESB SATA RAID Controller" = "OEM"

[OEMBootFiles]
txtsetup.oem
iaahci.inf
iaahci.cat
iastor.cat
iastor.inf
iastor.sys



Of course, I added the files to \$OEM$\TEXTMODE and \I386\$OEM$ folder

Here's the error I get during setup: (translated from french)

The txtsetup.oem file has caused an unexpected error (18) at line 1747 in d:\xpsprtm\base\boot\setup\oemdisk.c.

Press any key to continue

also, after pressing any key a few times, I get this one:

The Entry

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

doesn't exist in the unattended installation script file in the [SCSI] section of the INF txtsetup.sif

The installation program cannot continue
Press any key to quit


Keep in mind I have a multiboot CD and the path to the source file is:
\SYSTEME\XPSP2FR... this means my $OEM$ and I386 folders are there and not at the root of the CD

Any help?

Edited by Incroyable HULK, 07 October 2005 - 02:04 PM.


#97
Bilou_Gateux

Bilou_Gateux

    Powered by Windows Embedded

  • Member
  • PipPipPipPipPip
  • 768 posts

winnt.sif

[MassStorageDrivers]
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
"Intel® 82801FR SATA RAID Controller (Desktop ICH6R)" = "OEM"
"Intel® 82801FR SATA AHCI Controller (Desktop ICH6R)" = "OEM"
"Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)" = "OEM"
"Intel® 82801ER SATA RAID Controller (Desktop ICH5R)" = "OEM"
"Intel® 6300ESB SATA RAID Controller" = "OEM"

[OEMBootFiles]
txtsetup.oem
iaahci.inf
iaahci.cat
iastor.cat
iastor.inf
iastor.sys


Keep in mind I have a multiboot CD and the path to the source file is:
\SYSTEME\XPSP2FR... this means my $OEM$ and I386 folders are there and not at the root of the CD

Any help?


As you build an uA CD with French language, you must use the french string from your txtsetup.sif to add in WINNT.SIF
go back to post #7 and you will get the french string (avec l'accent circonflexe) :hello:

Edited by Bilou_Gateux, 08 October 2005 - 10:53 AM.

OS Version = 5.1.2600 Service Pack 3
Platform ID = 2 (NT)
Service Pack = 3.0
Suite = 0x0140
Product Type = 1
Architecture = x86

#98
Incroyable HULK

Incroyable HULK

    Slowly Turning Green...

  • Super Moderator
  • 1,257 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Thanks Bilou but this doesn't solve the problem completly... altought I don't get the second error anymore

Here's the error I get during setup: (translated from french)

The txtsetup.oem file has caused an unexpected error (18) at line 1747 in d:\xpsprtm\base\boot\setup\oemdisk.c.

Press any key to continue

also, after pressing any key a few times, I get this one: (translated from french)

The file given by the manufacturer that setup is trying to use is corrupt or invalid:

Line 1 contain a syntax error.

The setup program cannot continue.
To quit the setup program, press F3


:}

#99
Bilou_Gateux

Bilou_Gateux

    Powered by Windows Embedded

  • Member
  • PipPipPipPipPip
  • 768 posts

Thanks Bilou but this doesn't solve the problem completly... altought I don't get the second error anymore


Would you like to try this method described here

It will skip the possible issue with your multiboot CD which doesn't use standard \I386 path for source.

If you don't plan to add multiple MassStorage drivers to your multibootcd, it takes less than 2 mn to do the dosnet.inf and txtsetup.sif editing and add the compressed binary file to the source.

for the [SCSI] section of TXTSETUP.SIF, use a single generic string for description:
iaStor = "Intel RAID/AHCI SATA storage controller"

Edited by Bilou_Gateux, 09 October 2005 - 04:08 AM.

OS Version = 5.1.2600 Service Pack 3
Platform ID = 2 (NT)
Service Pack = 3.0
Suite = 0x0140
Product Type = 1
Architecture = x86

#100
Incroyable HULK

Incroyable HULK

    Slowly Turning Green...

  • Super Moderator
  • 1,257 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Well, I think I'll consider using the method described in the "official" guide...
http://unattended.ms...rivers/raid.htm

To thing I liked about the method in this topic is that I didn't have to edit any other file than winnt.sif and I didn't have to directly put any files in the I386 folder...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN