PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Spencer <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Tue, 13 Oct 1998 18:36:25 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (80 lines)
When I tried the advice below, the system still booted up and said that all
but mscd000 were not found. The correct number of drive letters were
assigned however, they were all assigned to mscd000. This made the system
extremely unreliable when reading from any of the cdrom drives. After a
while, I'd get a "Not ready reading drive d" error.

I would also like to re-iterate that the only reason I am trying to get
these older drives working is for the benefit of my school.

Thanks in advance for any help offered.

-----Original Message-----
From: David Spencer <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Tuesday, October 13, 1998 1:19 AM
Subject: Re: [PCBUILD] Daisychaining SoundBlaster CDROM Drives


>Thanks, I'll give it a try. To be clear however, the problem wasn't the
>drive letters, it was the fact that all of the drives were being associated
>with mscd000 by the sbcd.sys line in config.sys. I will give your
suggestion
>a try though.
>Thanks again!
>
>
>-----Original Message-----
>From: Earl Truss <[log in to unmask]>
>To: [log in to unmask] <[log in to unmask]>
>Date: Sunday, October 11, 1998 10:39 PM
>Subject: Re: [PCBUILD] Daisychaining SoundBlaster CDROM Drives
>
>
>>At 08:30 PM 10/10/98 -0400, you wrote:
>>>syntax I'm using has included:
>>>
>>>device=c:\sb16\drv\sbcd.sys /d:mscd000 /p:220 /n:4    {on one attempt}
>>>
>>>device=c:\sb16\drv\sbcd.sys /d1:mscd000 /d2:mscd001 /d3:mscd003
>/d4:mscd004
>>>/p:220 /n:4
>>>
>>>The mscdex.exe line in autoexec.bat looks like:
>>>
>>>mscdex.exe /d:mscd000 /d:mscd001 /d:mscd002 /d:mscd003
>>>
>>I don't know much about this, but I'll bet that you have to have four
>>separate lines in CONFIG.SYS and AUTOEXEC.BAT as shown below, unless the
>>"N" parameter tells the system how many drives are to be serviced by that
>>driver.
>>
>>device=c:\sb16\drv\sbcd.sys /d:mscd000 /p:220 /n:4
>>device=c:\sb16\drv\sbcd.sys /d:mscd001 /p:220 /n:4
>>device=c:\sb16\drv\sbcd.sys /d:mscd002 /p:220 /n:4
>>device=c:\sb16\drv\sbcd.sys /d:mscd003 /p:220 /n:4
>>
>>mscdex.exe /d:mscd000 /L:W
>>mscdex.exe /d:mscd001 /L:X
>>mscdex.exe /d:mscd002 /L:Y
>>mscdex.exe /d:mscd003 /L:Z
>>
>>The lines in the CONFIG.SYS each load and identify a driver for a CD
drive.
>> The MSCDEX lines associate the drive letter given by the "L" parameter
>>with the driver identified by the "D" parameter.
>>
>>                                  -----
>>                PCBUILD mailing list -  http://nospin.com
>>         Bob Wright:[log in to unmask] - Drew Dunn:[log in to unmask]
>>
>
>                                  -----
>                PCBUILD mailing list -  http://nospin.com
>         Bob Wright:[log in to unmask] - Drew Dunn:[log in to unmask]
>

                                  -----
                PCBUILD mailing list -  http://nospin.com
         Bob Wright:[log in to unmask] - Drew Dunn:[log in to unmask]

ATOM RSS1 RSS2