DriverPacks.net Forum - Problem with LSL_SAS.sys

Re: Problem with LSL_SAS.sys

null@example.com (OverFlow) — Thu, 17 Jan 2008 01:31:38 +0000

that may just do the trick...

hi jaak!

Re: Problem with LSL_SAS.sys

null@example.com (Logos302) — Wed, 16 Jan 2008 21:00:54 +0000

The driver posted in this forum http://forum.driverpacks.net/viewtopic.php?id=2306 seems to have fixed the problem (updated Driver for support of the Perc 6 cards)..

Re: Problem with LSL_SAS.sys

null@example.com (Jaak) — Wed, 16 Jan 2008 20:25:35 +0000

old mass 7092 had
ms_1_tag="lsi_sas"
ms_1_sysFile="lsi_sas.sys"
filename itself had all uppercase LSI_SAS.SYS

current lines say
ms_1_tag="LSI_SAS"
ms_1_sysFile="LSI_SAS.SYS"

ms_1_exc_disableIfOS="w2k" was added to the INIand
The filename's extention became lower case.

I hear this (upper/lower) should not make a difference, but while I worked on a Compac/HP SAS driver in late december I could not make it load in TXTmode, and it defied everything I tried with upper/lower case..

This LSI SAS driver most probably acts the same..
However, this one must have worked for server.
(I think we had trouble hgetting it to work, tho)
I suggest you rename the file to all upper case, and again use lower case in the INI for this one.

If that works for server, then the ms_1_exc_disableIfOS="w2k" is not causing this.
(ms_1_exc_disableIfOS="w2k" could be causing this, tho.. I think we want to find out, because most requests are for server stuff nowadays, and we are only two drivers away from the win2000 memory limit.)

Re: Problem with LSL_SAS.sys

null@example.com (Logos302) — Wed, 16 Jan 2008 20:05:54 +0000

I have no problem with it except with this driver. if I don't incorperate the Mass storage drivers, I don't get the error, but of course it then can not find the HardDrives. I have contacted them and they suggested I ask the question here. I suspect that most of the testing is done on Workstation hardware and this is a SErver a Dell 2900 with a LSI Sata Attached Scsi controler.

Sorry for the long post could not see an attach button.

DP_BASE_Version : 7.05.2
Mass Storage Version : 7.12.1
AutoImage Verison : 0.1.9.6 Beta

But this I belive is modified by AutoImage on the fly.
DPs_Base.ini
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"

[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "D:\RemoteInstall\Setup\English\Images\WINDOWSXP\i386"

DPs_Base.log
2008-01-11 14:10:28 : DriverPacks BASE 7.05.2 initialized in API mode by AutoRIS v0.1.9.5.
2008-01-11 14:10:28 : Host environment: WIN_2003 Service Pack 2 on X86 CPU.
2008-01-11 14:10:28 : Created temporary working directory.
2008-01-11 14:10:28 : Imported proxy settings from Internet Explorer.
2008-01-11 14:10:36 : Start scanning for DriverPacks for the wnt5_x86-32 platform.
2008-01-11 14:10:36 : Detected DriverPack Chipset 7.10.1!
2008-01-11 14:10:36 : Detected DriverPack CPU 7.04.1!
2008-01-11 14:10:36 : Detected DriverPack Graphics A 7.10!
2008-01-11 14:10:36 : Detected DriverPack Graphics B 7.12.1!
2008-01-11 14:10:36 : Detected DriverPack Graphics C 7.12!
2008-01-11 14:10:36 : Detected DriverPack LAN 7.12.1!
2008-01-11 14:10:36 : Detected DriverPack MassStorage 7.12.1!
2008-01-11 14:10:36 : Detected DriverPack Sound A 7.12!
2008-01-11 14:10:36 : Detected DriverPack Sound B 7.12!
2008-01-11 14:10:36 : Detected DriverPack WLAN 7.12!
2008-01-11 14:10:36 : Could not detect any 3rd party DriverPacks.
2008-01-11 14:10:36 : Finished scanning.
2008-01-11 14:10:36 : Using settings file in custom location: D:\DriverPack\AutoImage-Bâshrat the Sneaky.ini.
2008-01-11 14:10:36 : Detected settings file "D:\DriverPack\AutoImage-Bâshrat the Sneaky.ini".
2008-01-11 14:10:37 : Windows Server 2003, Standard - Corporate SP2 detected.
2008-01-11 14:10:37 : The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2008-01-11 14:10:37 : Imported settings from settings file.
2008-01-11 14:10:37 : [OptionalSettingsOther]\ATI_cpl not specified: default (CCC) was set.
2008-01-11 14:10:37 : Selected module: mod_slip_w2k3_x86-32_disc_m2.
2008-01-11 14:10:37 : QuickStream Cache available for DriverPack MassStorage text mode drivers!
2008-01-11 14:10:44 : Removed all attributes from \I386.
2008-01-11 14:10:44 : Restored original mass storage text mode driver DPTI2O.sys.
2008-01-11 14:10:44 : Restored original mass storage text mode driver ADPU160M.sys.
2008-01-11 14:10:44 : Restored original mass storage text mode driver ALIIDE.sys.
2008-01-11 14:10:44 : Restored original mass storage text mode driver MRAID35X.sys.
2008-01-11 14:10:44 : Restored original mass storage text mode driver DAC2W2K.sys.
2008-01-11 14:10:44 : Restored original mass storage text mode driver DAC960NT.sys.
2008-01-11 14:10:44 : Restored original mass storage text mode driver ULTRA.sys.
2008-01-11 14:10:44 : Restored original mass storage text mode driver QL12160.sys.
2008-01-11 14:10:44 : Deleted old DriverPack MassStorage text mode drivers.
2008-01-11 14:10:44 : Created a backup of \I386\winnt.sif.
2008-01-11 14:10:45 : Restored \I386\txtsetup.sif.
2008-01-11 14:10:45 : Restored \I386\dosnet.inf.
2008-01-11 14:10:45 : Restored original setup: method 2 was used previously.
2008-01-11 14:10:45 : Created necessary directory structure for method 2.
2008-01-11 14:10:51 : Copied files necessary for method 2.
2008-01-11 14:10:53 : Extracted files necessary for method 2.
2008-01-11 14:10:54 : Deleted old presetup.cmd file from \I386.
2008-01-11 14:10:54 : Created \I386\presetup.cmd file.
2008-01-11 14:10:54 : Updated \I386\txtsetup.sif to support method 2.
2008-01-11 14:10:55 : Updated \I386\dosnet.inf to support method 2.
2008-01-11 14:11:06 : Copied DriverPacks to \OEM.
2008-01-11 14:11:06 : Could not slipstream KB888111 because Service Pack 1 isn't slipstreamed!
2008-01-11 14:11:10 : Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2008-01-11 14:11:22 : Removed entries from \I386\txtsetup.sif that will be updated.
2008-01-11 14:11:23 : Removed entries from \I386\dosnet.inf that will be updated.
2008-01-11 14:13:19 : Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2008-01-11 14:13:19 : Updated \I386\winnt.sif to support method 2.
2008-01-11 14:13:19 : Updated DPsFnshr.ini to enable KTD for all DriverPacks.
2008-01-11 14:13:19 : Created \$OEM$ directory.
2008-01-11 14:13:22 : Updated \$OEM$\cmdlines.txt to execute ROE.exe.
2008-01-11 14:13:22 : Temporary working directory successfully deleted.
2008-01-11 14:13:22 : Program terminated.

Controler that I belive is the problem or aleast cause the lsi_sas.sys to fail.

PCI\VEN_1028&DEV_0015&SUBSYS_1F031028&REV_00\5&22FD9970&0&700028: DELL PERC 5/i Integrated RAID Controller

Re: Problem with LSL_SAS.sys

null@example.com (RogueSpear) — Wed, 16 Jan 2008 16:54:32 +0000

I'm taking a peek at the driver to if there's anything unusual about it. I've tested integrating mass storage text mode in RIS images by way of AutoImage quite a few times with no problems. As far as the installation of a system via RIS goes, the only experience I really have is with Dell OptiPlex 755 desktops (and it works fine).

Re: Problem with LSL_SAS.sys

null@example.com (OverFlow) — Wed, 16 Jan 2008 01:32:30 +0000

hello Logos302
Welcome to DriverPacks.net and we're all glad your here.

Sorry i didnt see your post right away...

First line of attack on this problem should be with RogueSpear author of AutoImage (and one of my Unattended Windows heros).
as far as what info we need there is a link in my sig for that
but please check at RogueSpears forum first, as i think your issue lies with AutoImage and not with DriverPacks

http://www.doitrightconsulting.net/foru … ic.php?t=3

be sure to tell them which versions of software you are useing
autoimage version
DriverPacks BASE version
DriverPack MassStorage version
include your autoimage log
and also let them know it's for 2003 R2 SP2 as you posted for us.

if you need additional help or info we are glad to be of service any time.

have a great day and hope to see you here often

Problem with LSL_SAS.sys

null@example.com (Logos302) — Fri, 11 Jan 2008 23:26:21 +0000

I have used AutoImage to incorperate Mass Storage Drivers into my RIS images, and have had great success, until today. I tryed to install Windows 2003 R2 SP2 and found that during the Text Mode setup I get Error in LSL_sys.sys (21) line something don't remember, with a path to D:\nt\base\etc...... If more information is need please ask .. Oh and I was not sure if this was a bug