#mscdex 2.22
8 messages in this thread
Kevin, I downloaded and read your super LASER.TXT document. However, I still
don't know what I should specify for the MSCDEX /D: parameter for my specific
setup. Here are the details.
I have an internal Toshiba 3401 installed in a PS/2 Model 77, which is a
40486DX machine with SCSI on the motherboard (so, I don't need an adapter
card). It took me less than 45 seconds to install this drive under OS/2 2.1,
using OS/2's selective install (all I had to do was pick the drive and the SCSI
adapter (IBM internal) from two list boxes in a dialog and click on install).
With NOTHING more, I can use the drive with OS/2, and with DOS and Windows
applications running under OS/2. No futzing with drivers and their parameters,
memory managers, UMBs, exclude regions, config.sys and autoexec.bat files, etc.
Neat!
However, I'd also like to be able to use the drive with native DOS and native
DOS/Windows 3.1 (which are installed on another primary partition on my hard
file). For that, I know that I need MSCDEX and I have a copy of version 2.22.
However, as you know, MSCDEX's /D: parameter is used to specify "a name for the
device driver." But, I don't have a device driver for my built-in SCSI, which
BTW supports my hard drive under DOS and Windows 3.1 just fine with no driver.
So, do I need some other DOS driver for the Toshiba 3401? If so, what is it
and where do I find one? If not, what do I specify for the /D: parameter? I
realize you have Sony gear. So, maybe, if you don't know, someone else will
chime in here with some help. TIA.
Bill
Bill, I'd expect you'll need a Toshiba driver that is compatible with
your drive. Contact Toshiba first; they'll have it, and maybe they
have a BBS from which to download?? I don't think I have their
number around; I do remember they have a major PC service center in
the Los Angeles area somewhere, but that's a lotta real estate and
area codes I'm afraid. (800) directory might have something. Also
ask them for the driver name, not the filename, they use in case you
don't get an install routine with the driver. I've heard anecdotally
that you can use any name, e.g. "Bill" for the driver name as long as
you keep the name identical in both the driver and mscdex switches,
but that seems a bit counterintuitive. A lot of driver names look
like SONY001, MV001, etc., usually in the form of mfgr's name and a
number to differentiate it from other drives you may have connected.
It's also possible that a vendor such as Trantor — I think they're
on the new CD vendor forum (CDVEN) — may have a driver that'll work
too, but that'll cost you something.
Thanks Kevin.
If no one chimes in here with any info on the 3401 DOS driver, I'll call
Toshiba next week. I have the number somewhere, but the last time I called I
listened to music for 20 minutes before I got to talk to someone — and, then
he couldn't answer my question. But, he did send me a manual, so all wasn't
lost. <g>
Bill
Your drive will work with the IBM driver for their cd-rom, it should be
compatible, so you might be able to use it for all the same operations
supported by the 3301. Funny but the VCDROM virtual cdrom driver which
simulates mscdex under dos emulation has a name which it reports to apps. Why
would anyone want to use DOS? <g>
Thanks Bill. I suspected that the IBM CD-ROM II DOS SCSI driver would work and
am now trying to find one. I have a post on the IBM NSC BBS. It's probably
there, but I don't know it's name and that BBS only allows searches by file
names. If I don't get an answer today, I reckon I'll do a listing of all the
*.sys files there.
> Why would anyone want to use DOS? <g> <
I agree, and am finding myself booting to DOS and DOS/Windows much less
frequently (and I haven't installed OS/2 2.1 GA yet). However, I want to
maintain a vanilla DOS/Windows boot drive for three of reasons.
First, if I have a DOS or Window's app with a problem, I want to be able to say
to the developer's tech support folks that its failing when running under the
vanilla DOS or DOS/Windows setup.
Second, some Windows apps (eg. those that use Windows virtual device drivers)
aren't supported by OS/2.
Last, I want to be able to compare DOS and DOS/Windows apps' performance under
OS/2 to that under the vanilla setup.
As I said, I do have DOS/Windows installed in a primary partition which isn't
even visible when I boot OS/2 from its primary partition.
Sometimes, I even forget that c: drive is even there! <g>
Bill
Good reasons all. I suppose that with the regular windows hidden that the win
application setup programs will work. When I was set for dual boot, they used
the normal windows and I had to migrate them to win/os2.
Yes Bill, the few Windows apps that I've installed setup just fine under
WIN-OS2. However, I do have to boot under DOS and install them again so that I
can run them under vanilla Windows. I reckon I could copy the DLLs and INI
entries, etc., but that sounds like a potentially error-prone process. I do
install the apps themselves on a common logical drive, so I don't have two
copies of the apps on my hard file.
BTW, a couple of folks on the IBM NSC forum told me that the IBM CDROM II has
some additional firmware that the Toshiba 3401 doesn't, and that the IBM driver
won't work with the Toshiba drives.
So, unless I can find a Toshiba 3401 DOS driver for the IBM internal SCSI, I
reckon I won't be able to use it under DOS/Windows.
If anyone here knows where I might find one, please let me know.
Bill