#MS Extensions-help
8 messages in this thread
Hi,
I'm new to working with CD ROMs. I have a stand-alone external caddy that
holds two drives that we've had for a number of years at work. It was
working fine until we loaded DOS 5.0 and files must have gotten corrupted.
Since that time I have not been able to successfully load a new copy of the
Microsoft Extensions because I can't find the original documentation. I
keep getting "invalid drive specification" when I type in drive d:. I'm
sure it is something simple but I need some direction. I have my
autoexec.bat and config.sys files ready if these are needed for further
help.
Thank you.
Kay Wagner
Send up the files.
Clarke,
The machine I'm trying to configure is on a Novell Network.
Autoexec.bat:
echo off
cls
prompt $p$g
path c:\dos;\c:\dev
c:\da51
set temp=c:\dos
set pmdir=c:\dos
ipx
netx ps=library
f:
login guest
\bin\mscdex.exe /d:mscd006 /d:mscd001 /d: /l:d /m:16
rem \bin\mscdex.exe /d:mscd007 /d:mscd006 /d:mscd001 /d: /l:e /M:20
Config.sys to follow
(con't)
Kay, if I can make a suggestion, load the drivers BEFORE starting the
network. Novell is going to try and grab all the drive letters that DOS is'nt
using.
Plus clean up the config.sys so it looks somthing like:
Device=c:\dos\setver.exe
Shell=c:\command.com /e:1024 /p
Device=c:\dos\himem.sys
device=c:\dos\ansi.sys <— Note that devicehigh will not work without
EMM386.EXE being installed with the RAM parm
device=c:\dev\cd1100s.sys /d:mscd001 /n:2 <– (/n:2 # of drives use /P is
you need to add port info for the card)
device=c:\da51\dndevice.sys /b <—- what is this?
files=40
buffers=20
Chop your autoexec.bat to contain only the one MSCDEX driver (before the
network drivers):
\bin\mscdex /d:mscd001 /m:16 /l:e <— this should work fine with the CD-ROM
#1 being E and #2 being F. If you
don't have a 'D' drive use /l:d
That will leave F: for the network.
-Clarke
P.S.
If this does'nt work, let me know. Also can you tell me what error messages
you get (if any), plus what messages come up when attempting to load both the
hardware driver and the MSCDEX. Who makes the unit and card?
Clarke,
Thanks so much for your quick reply. I will try your suggestions on Monday
as I have a meeting out of house tomorrow. The device=da51 is a driver for
the Direct Access menuing system. In order for the software to keep a log,
the driver must be loaded.
Can I use d & e as drives for the CD? F is being used by the network. I'm
assuming from your first message that I can.
I will watch for error messages and report them to you.
As far as the unit and the card, it is an Online Systems product- does that
sound right? I received the unit when we were using another CD product and
didn't have the CDs networked. If you need further clarification on the
card and unit I will get it for you on Monday.
Again, I appreciate your help. Information Systems here is backed up and
can't get down here to help me and I need to preview some CDs.
Kay Wagner
Kay, you can use any drive letter not in use at the time you load the MSCDEX
driver. You may have to extend the LASTDRIVE= statment in your config.sys if
you have more than 3 local hard drives.
If you have a C drive, you can set the MSCDEX to be drive d—>z depending on
how many drive letters you reserved in your config.sys.
The network is adding additional complexity, the Novell shell likes to grab
any unused drive letter for it's self.
On Monday, try to run without your network drivers after cleaning up your
config.sys. If that works, try the network drivers last (after the CD-ROM is
assigned drive letters).
-Clarke
Let me know how it goes.
Clarke,
Config.sys
device=c:\dos\setver.exe
lastdrive=e
shell=command.com /e:1024/p
device=c:\dos\himem.sys
dos=high,umb
devicehigh=c:\dos\ansi.sys
rem device=\dev\cd1100s.sys /d:mscd001 /n:2
device=c:\da51\dndevice.sys /b
device=\dev\cd1100s.sys /d:mscd006 /n:2 p:2a0
rem device=\dev\cd1100s.sys /d:mscd007
files=40
buffers=20
There are alot of "rems" because I was fiddling around with what was already
in the config.sys file trying to find the correct driver to run with the
extensions. Obviously I haven't succeeded as I'm getting "invalid drive
specification."
Thank you very much.
Kay Wager
Kay, also try removing the network drivers and removing all other device
drivers from the config.sys:
Files=20
Buffers=20
device=c:\dev\cd1100s.sys /d:mscd001 /n:2
Autoexec.bat:
prompt $p$G
path=c:\dos;c:\dev
c:\bin\mscdex /d:mscd001 /l:d /m:4
-Clarke