well, what i'd do is do a non-unattended install (as in a 'manual' install)
to see if that works. That way you can at least rule out that there is
something really wrong with the driver u're trying to use... but maybe
you've already tried this?
Michael
On 10/16/07, Sebastian Mellmann <[EMAIL PROTECTED]> wrote:
>
> I've never ran into this problem to be honest ;-(
> Your txtsetup.sif looks fine for me.
> You could try to do this with a XP installation and see if it works.
> Maybe the syntax of the txtsetup.sif is different from the 2003 one (it
> was for windows 2000!).
>
>
> Sebastian
>
> ------------------------------
> *From:* Bryan Dunn [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, October 16, 2007 4:11 PM
> *To:* Sebastian Mellmann
> *Subject:* Re: [Unattended] Mass Storage Drivers
>
> Ok, making some progress here. I've used your method to add both the
> drivers for the qlogic card and the SAS HDD. I've also removed the
> [OemBootFiles] section from unattend.txt. I no longer get the
> txtsetup.oemerror. However, after the drivers load, I am presented with:
>
> insert the CD labeled:
> "Windows Server 2003, Enterprise Edition CD-ROM"
> into your CD-ROM drive
>
> A few posts I've read seem to indicate that this could be a problem with
> my source, or with txtsetup.sif. Do you have any suggestions? I made the
> following changes to txtsetup.sif:
>
> (diff txtsetup.sif txtsetup.sif.orig)
> 9543,9545d9542
> < lsi_sas.sys = 1,,,,,,3_,4,1,,,1,4
> < lsipseud.sys = 1,,,,,,4_,4,1,,,1,4
> <
> 19468,19542d19464
> < PCI\VEN_1077&DEV_2432&SUBSYS_01371077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01381077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01391077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_013D1077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01421077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01431077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01441077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01451077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01461077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_014B1077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_014C1077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01521077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01531077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01541077 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_01090E11 = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_7040103C = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_7041103C = "ql2300"
> < PCI\VEN_1077&DEV_2432&SUBSYS_1705103C = "ql2300"
> < PCI\VEN_1077&DEV_5432&SUBSYS_013E1077 = "ql2300"
> < PCI\VEN_1077&DEV_5432&SUBSYS_013F1077 = "ql2300"
> < PCI\VEN_1077&DEV_5432&SUBSYS_014E1077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_12D7103C = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_01331077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_01341077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_01351077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_01361077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_013A1077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_013B1077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_01401077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_01411077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_01471077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_01481077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_014A1077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_014D1077 = "ql2300"
> < PCI\VEN_1077&DEV_2422&SUBSYS_12DD103C = "ql2300"
> < PCI\VEN_1077&DEV_2322&SUBSYS_01171077 = "ql2300"
> < PCI\VEN_1077&DEV_2322&SUBSYS_01181077 = "ql2300"
> < PCI\VEN_1077&DEV_2322&SUBSYS_01701028 = "ql2300"
> < PCI\VEN_1077&DEV_2322&SUBSYS_82BF1033 = "ql2300"
> < PCI\VEN_1077&DEV_2322&SUBSYS_34BC8086 = "ql2300"
> < PCI\VEN_1077&DEV_6322&SUBSYS_012F1077 = "ql2300"
> < PCI\VEN_1077&DEV_6322&SUBSYS_01321077 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01001077 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01011077 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01021077 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_010A1077 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01491077 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01000E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01010E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01020E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01030E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01040E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01050E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01060E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01070E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01080E11 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_027D1014 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_02FB1014 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_018A1028 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_10511734 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_01021749 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_34A08086 = "ql2300"
> < PCI\VEN_1077&DEV_2312&SUBSYS_34BA8086 = "ql2300"
> < PCI\VEN_1077&DEV_6312&SUBSYS_01191077 = "ql2300"
> < PCI\VEN_1077&DEV_6312&SUBSYS_011C1077 = "ql2300"
> < PCI\VEN_1077&DEV_6312&SUBSYS_01301077 = "ql2300"
> < PCI\VEN_1077&DEV_2300&SUBSYS_00091077 = "ql2300"
> < PCI\VEN_1077&DEV_2300&SUBSYS_01061077 = "ql2300"
> < PCI\VEN_1000&DEV_0050 = "lsi_sas"
> < PCI\VEN_1000&DEV_0054 = "lsi_sas"
> < PCI\VEN_1000&DEV_0058 = "lsi_sas"
> < PCI\VEN_1000&DEV_005E = "lsi_sas"
> < PCI\VEN_1000&DEV_0056 = "lsi_sas"
> < PCI\VEN_1000&DEV_005A = "lsi_sas"
> < PCI\VEN_1000&DEV_0062 = "lsi_sas"
> 19688,19690d19609
> < lsi_sas = lsi_sas.sys,4
> <
> <
> 22077d21995
> < lsi_sas = "LSI Logic Fusion-MPT SAS Storport Driver"
>
>
>
> Sebastian Mellmann wrote:
>
> 1. You don't need those sections in the unattend.txt, because the driver
> will be integrated in the source (xp, 2003) itself.
> 2. You don't need that file, only the information contained in it. (for
> the txtsetup.sif file)
> 3. You just have to add the additional driver information to the
> txtsetup.sif file in the i386 directory.
>
> What message do you get after you've integrated the driver using my
> method?
>
>
> Sebastian
>
> ------------------------------
> *From:* [EMAIL PROTECTED] [
> mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]>]
> *On Behalf Of *Bryan Dunn
> *Sent:* Tuesday, October 16, 2007 2:03 PM
> *To:* Sebastian Mellmann
> *Cc:* unattended-info@lists.sourceforge.net
> *Subject:* Re: [Unattended] Mass Storage Drivers
>
> Thanks so much for the info Sebastian. I've tried the method with the
> first driver (ql2300) and get the same result. Looking at the procedure I
> have a few questions:
>
> 1. Must unattend.txt be modified to include the contents of the 'TEXTMODE'
> directory in [OemBootFiles] or the Drivers/SCSI directory in
> [OemPnPDriversPath]?
> 2. Must the txtsetup.oem that came with the driver be modified (commenting
> out .dll files or changing dll to inf)?
> 3. Must I combine txtsetup.oem files if I add multiple drivers?
>
> In a moment of weakness I did try using DriverPacks to do my
> slipstreaming, but I've since created a "clear" source.
>
> -Bryan
>
> Sebastian Mellmann wrote:
>
> Hello Bryan,
>
> do you have a "clear" windows2003 install source?
> Not altered with any drivers or patches?
>
> Normally you get this message, when you tried to integrate a textmode driver
> into an install source using e.g. nLite.
> That does NOT work.
>
> I've written an how-to to do that (e.g. Dell PERC SCSI Controller), because
> tools like nlite doesnt work for TEXTMODE drivers:
>
>
>
> You should have the following files:
>
> aac.inf
> aac.sys
> aaccin.dll
> aacevt.exe
> aacmgt.inf
> raiddisk1
> txtsetup.oem
>
>
>
> Copy the Files to the following Destination:
>
> * Copy the files .cat, .inf and .sys to $XP_SHARE\i386\$oem$\TEXTMODE
>
> * Copy the files .exe, .dll (and maybe others) to
> $XP_SHARE\i386\$oem$\$$\OemDir
>
> * Copy ALL files to $XP_SHARE\i386\$oem$\Drivers\SCSI
>
> * Compress ALL .sys files using 'makecab' (e.g. makecab aac.sys in the
> commandline under windows) and copy them to $XP_SHARE\i386
>
> Modification of the 'TXTSETUP.SIF' in $XP_SHARE\i386 (for XP64 this files
> can be found in AMD64!)
>
> Search for the section [SourceDisksFiles] and add the following:
>
> [SourceDisksFiles]
>
> aac.sys = 100,,,,,,3_,4,1,,,1,4
>
> This is necessary for ALL .sys files.
>
> In this case we only got on .sys file.
>
> For Windows2000 this entry looks like this:
>
> [SourceDisksFiles]
>
> aac.sys = 1,,,,,,3_,4,1
>
>
>
> Search for the section [HardwareIdsDatabase] and add the following:
>
> [HardwareIdsDatabase]
>
> PCI\VEN_9005&DEV_0285&SUBSYS_02871028 = "aac"
>
> These information can be found in the TXTSETUP.OEM shipped with driver.
>
> Just open it with a normal editor like notepad.
>
> Search for the section [SCSI.load] and add the following:
>
> [SCSI.Load]
>
> aac = aac.sys,4
>
> You also need to add EVERY single .sys file here!
>
> Last but not least add the following to the [SCSI] section:
>
> [SCSI]
>
> aac = "Dell PERC 320/DC SCSI RAID Controller"
>
> You can just choose anything you want here as the description.
>
> Save the file and give it a try.
>
>
>
> Before you start have a closer look to the TXTSETUP.OEM file shipped with
> the driver.
> You've to be 100% sure what you're doing to the TXTSETUP.SIF file as you can
> f*ck up your whole XP or 2003 source.
> So you'd better make a backup of that file before fooling around with it :-)
>
> I've added several drivers (Intel Matrix, Adaptec, Dell Perc, etc.) using
> this method.
> Hope it helps.
>
>
>
> Sebastian
>
>
>
> ________________________________
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>] On Behalf Of Bryan
> Dunn
> Sent: Monday, October 15, 2007 8:04 PM
> To: unattended-info@lists.sourceforge.net
> Subject: [Unattended] Mass Storage Drivers
>
>
> Hello All,
>
> I've been trying to make this work for the last two weeks and after
> countless hours googling I'm close to insanity. Here is my situation, I am
> attempting to install Windows 2003 on an IBM LS21 blade with:
>
>
> 73GB 10K SFF SAS HDD
>
> QLogic 4Gb Fibre Channel Expansion Card (CFFv)
>
> With no mass storage drivers added to i386/$oem$/textmode on the
> first boot from the hard disk (after pxe booting the linux boot disk) I get
> a black screen with a flashing cursor in the top left corner. Adding the
> driver for the qlogic card gets me to the text mode installation, which ends
> abruptly with a:
>
> File textsetup.oem caused an unexpected error (18) at line 1896 in
> d:\srvrtm\base\boot\setup\oemdisk.c
>
> The fact that I get further with the qlogic driver installed tells
> me that it is obviously needed. What I am unsure of is what mass storage
> driver I'm missing (which is what I believe is causing the txtsetup.oem
> error, though I'm willing to hear arguments to the contrary). I've tried
> combining the txtsetup.oem files from the SAS HDD and the qlogic card,
> adding the drivers from each into the textmode directory and updating
> unattend.txt with the entire list, which results in the blank screen with
> the blinking cursor.
>
> Can someone give me some direction about what to try to make this
> setup work? I've been through all of Microsoft's documentation (if you can
> call it that) and can't make it happen.
>
> Thanks,
> Bryan
>
>
>
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.488 / Virus Database: 269.14.10/1070 - Release Date:
> 14.10.2007 09:22
>
>
>
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.488 / Virus Database: 269.14.10/1070 - Release Date: 14.10.2007
> 09:22
>
>
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.488 / Virus Database: 269.14.12/1072 - Release Date:
> 15.10.2007 17:55
>
>
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.488 / Virus Database: 269.14.12/1072 - Release Date:
> 15.10.2007 17:55
>
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.488 / Virus Database: 269.14.12/1072 - Release Date:
> 15.10.2007 17:55
>
>
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.488 / Virus Database: 269.14.12/1072 - Release Date:
> 15.10.2007 17:55
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> unattended-info mailing list
> unattended-info@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unattended-info
>
>
--
Michael De Groote
ICT-coordinator Sancta Maria Basisschool Leuven
ICT-coordinator Sint-Pietersschool Korbeek-Lo
ICT-coordinator Scholengemeenschap Katholieke Basisscholen Leuven
ICT-coordinator Parkschool Leuven
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info
