[Pure Krome]

cyr3x, on Nov 14 2003, 03:26 AM, said:

hmm sorry pure krome but that isent the whole truth plz see the post off scankurban this way to implemet the raid drivers in the XP Install havent you explain.

hmm..

all people/posts i've seen on this site (and others) modify the TXTSETUP.SIF and another one (hive-something). they don't use the two sections in Winnt.sif which MS provided for this intended job.

but i must conceede, i cannot understand scankurban's directions at all so could someone please explain with a bit more detail what he is trying to do?

[scankurban]

Dear Pure Chrome;

I suppose You know what is txtsetsup.sif and $oem$ dir.
Now you have two ways.Its works too

One;
Adding to txtsetup.sif
This file contain xp installations files list.If insert correctly raid drivers.Setup don't searching any needed driver files.You can add but with some rules.

Example for the txtsetup.sif;

[SourceDisksFiles] <Search and find this section ( [SourceDisksFiles] )>
viasraid.sys = 100,,,,,,3_,4,1,,,1,4 <add your driver file name with (100,,,,,,3_,4,1,,,1,4)

[SCSI.Load] <Search and find this section ( [SCSI.Load] )>
viasraid = viasraid.sys,4 <Here is textmode setup scsi drivers loading section>

[SCSI] <Search and find this section ( [SCSI] )>
viasraid = "Asus A7V600 VIA Serial ATA RAID Controller Driver" <Here is scsi driver explanation section for txtmode setup.


Two.Using $oem$ dir.;
This is so easy other way.

Your xp cd root contains must have these 3 directories.Create them
1-$oem$ (side of the i386)
2-$1 (under $oem$)
3-txtmode (under $1)

Cdroot---\$oem$\$1\txtmode
Add all raid drivers to txtmode dir.

If;
You can't succes.Post drivers list here

[Pure Krome]

scankurban, thanks for the reply.

with the SECOND method, i've never gotton the drivers to load, nor has anyoene else i've aksed/researched.

i -HAVE- gotten the second method to work with a ~modified~ CD file structure (http://forum.abit-us...&threadid=29161)

now, what i tried was
\\CDROOT\$OEM$
\\CDROOT\$OEM$\$1
\\CDROOT\$OEM$\$1\Drivers\Lan

\\CDROOT\$OEM$\Txtmode

the contents of '\\CDROOT\$OEM$\$1\Drivers\Lan' and '\\CDROOT\$OEM$\Txtmode' were identical.

the drivers i used were from http://www.highpoint...rivers_down.htm the 3.03 drivers[Driver_BIOS_374_v303.zip]

this means winnt.sif needs to be updated, and the TxtSetup.oem file (found in the xp drivers directory) needs to be updated also.

is this all the info you need? i can test something out, if u post some results....

[cyberdiamond]

scankurban:

I have never had your way work.
I believe that if the driver files aren't microsoft certified then it won't work at all!

I would love to be wrong about this though.

I tried hpt370/372 drivers.

[scankurban]

Please guys.Pleae try method 1.Just try.You can do that!.I sad need only sys files,no driver singing no other wait reason.This is unattended installation.Many driver doesn't have microsoft's certified.Because they paying for this to microsoft.
Using txtsetup.sif.Xp installlation suppose these are my files I should load.And loading,executing.Method 1 so easy believe me.Just try...

[Pure Krome]

agreed scankurban, that method 1 (hacking txtsetup.sif) works perfectly. I've done that nearly 10-12 months ago with some help from a friend on another website.

but your method 2 is what worries me. no one (except you) seems to have succeeded in doing that.

the closest i've got, is to do it via the LITE XP Setup method -> ie. burn a copy of a fresh install to cd, minus all the unsued stuff like Upgrade files, etc, by running winnt32 in windows, and renaming/copying the temp files that winnt32.exe file creates, then doing some adjustements, etc and burn iso.

[scankurban]

Thanks...

LiteXP editing already installed system isn't it?

[jamesagmoore]

Pure Krome, on Nov 19 2003, 04:12 AM, said:

but your method 2 is what worries me. no one (except you) seems to have succeeded in doing that.

The method 2 works for me also, using the latest Intel ICHR5 SATA RAID drivers, which are not signed. They are not present in the OEMPnPDriversPath, just the 2 directories as specified above.

;SetupMgrTag
[Data]
    AutoPartition=0
    MsDosInitiated="0"
    UnattendedInstall="Yes"

[Unattended]
    CrashDumpSetting=0
    Repartition = No
    UnattendMode=FullUnattended
    OemSkipEula=Yes
    OemPreinstall=Yes
    TargetPath=\WINDOWS
    UnattendSwitch=Yes
    KeyboardLayout="United Kingdom"
    WaitForReboot = No
    OEMPnPDriversPath = "drivers\REALTEK\audio;drivers\ATI;drivers\IntelINF;drivers\LINKSYS"
    DriverSigningPolicy = Ignore

[MassStorageDrivers]
    "Intel(R) 82801ER SATA RAID Controller" = "OEM"
    "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

;[OEMBootFiles]
;    txtsetup.oem

[Pure Krome]

@jamesagmoore - could u please list the following information in a post / screen image?

1. CD File Structure
2. File listing where u put the drivers.
3. a listing of your .oem driver file

secondly, i noticed you only listed ONE file in your OEMBootFiles, and more so, that section and file were commented out? How does the [MassStorageDrivers] know which files are which? does it auto-search in the hardcoded directory?

thank you kindly.

-PK-

[jamesagmoore]

I attach a gif of the file structure. The drivers as in the right hand explorer pane are in both red directories.

The txtsetup.oem is just the default. No driver files were hacked. I believe some raid controller drivers may need editing if there are subdirectories but Intel's seem OK:

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

[Defaults]
scsi = iaStor

[scsi]
iaStor = "Intel(R) 82801ER SATA RAID Controller"

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

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

;-------------------------------------------------------
; Uncomment appropriate ID string by removing semi-colon
;-------------------------------------------------------
[HardwareIds.scsi.iaStor]
id = "PCI\VEN_8086&DEV_24DF&CC_0104","iaStor"

I found that OEMBootFiles was unnecessary, so I commented it out.

MassStorageDrivers OEM string was just copied from the txtsetup.oem.

Attached File(s)

•  Clip.gif (41.19K)
  Number of downloads: 198

[Pure Krome]

wow. this is interesting.

i've always been led to believe the structure should be (based on your image above) :-

D:\XP\$OEM$\Textmode <- Txtsetup.oem and sata/raid drivers here, used in Blue TextMode part.
D:\XP\$OEM$\$1\Drivers \Sata <- same drivers as above, but these are used in GUI part.


i've also heard a rumour that the folder should be called txtmode, not textmode, but that's unconfirmed and unsansiated.

hmm. i'm definatly going to have to try this out....

[Jens T]

This is what i did to get my highpoint 370 controller
to work whitout pressing F6

I first added some values to the TXTSETUP.SIF from the I386 dir

Like this:......the ones in brackets should be there allready




[SourceDisksFiles]
hpt3xx.sys = 1,,,,,,4_,4,1,,,1,4

[HardwareIdsDatabase]
PCI\VEN_1103&DEV_0004&SUBSYS_00051103&REV_03 = "hpt3xx"
PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_03 = "hpt3xx"
PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_04 = "hpt3xx"

[SCSI.Load]
hpt3xx = hpt3xx.sys,4

[SCSI]
hpt3xx = "HPT370 UDMA/ATA100 RAID-kontroller"



then i added the hpt3xx.sys for winXP (version v2.0.0919)
to the I386 directory

I ONLY HAVE Tested it for my 370 chip (Abit KT7a M-Board)

Hope some can find it useful.....

[bucketbuster]

Someone got WinXP Promise FastTrak100 ™ Lite Controller working?
How?

[bucketbuster]

kachaffeous,

I got the same problem with my WinXP Promise Fasttrak100 ™ Lite Controller.
What exactly did you do??
Did you keep the C:\XPCD\$OEM$\Textmode\Winxp directory??

Thanks

[llrda]

Has anyone managed to get the second method working yet? I want to have support for my HPT370/372 controller when I boot my PC and I want the second method to work

When I read the thread I got a little confused about where to put the drivers. I've tried a lot combinations but haven't succeeded so far.

Here is the directory structure of the HPT370/372 drivers (Directories are CAPITALS)

BIOS
DMASET
WIN2K
WIN9X
WINNT
WINXP
-hpt3xx.inf
-hpt3xx.sys
-rcm.inf
-readmexp.txt
disk1
txtsetup.oem

First Question: Which of these Files can I discard? I guess I don't need the other Win directories, what about txtsetup.oem, do I really need it for the textmode installation?

Next Question: Where do I put the files for the textmode intallation? And what structure do I use?
What I've tried so far:
1) CD/$OEM$/$1/TEXTMODE
2) CD/$OEM$/$1/TXTMODE
3) CD/$OEM$/TEXTMODE

Do I only put the .sys-file in the textmode directory? Can I use a sub-directory in TEXTMODE?

plz help