home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.pc-clone.32bit:1000 comp.unix.sysv386:17713
- Newsgroups: comp.unix.pc-clone.32bit,comp.unix.sysv386
- Path: sparky!uunet!cs.utexas.edu!usc!wupost!spool.mu.edu!umn.edu!csus.edu!netcom.com!jdpierc
- From: jdpierc@netcom.com (Jerry D. Pierce)
- Subject: CDROM & VP/ix headache
- Message-ID: <1993Jan9.062210.18668@netcom.com>
- Followup-To: poster
- Organization: Netcom - Online Communication Services (408 241-9760 guest)
- Date: Sat, 9 Jan 1993 06:22:10 GMT
- Lines: 44
-
-
- Must be my week for weird hardware problems.
-
- I just installed a Toshiba CDROM drive on a 486 at
- work which we're running Interactive UNIX 3.0 on.
-
- I used the Future Domain controller which came with
- the CDROM drive, and it was surprisingly easy to get
- it working with unix.
-
- After going through and configuring the hpdd, I rebooted
- the box and there it was. Mounted up a cd and was able
- to peruse files no problem.
-
- Since I need to be able to run some dos software (under
- vpix) on the CDROM drive, I fire up vpix. OK so far, but
- in order to run the demo software that came with the
- CDROM drive, I need to add a line to the config.sys
- that points it towards a device driver, and then another
- line to the autoexec.bat which runs a general setup
- of some sort based on finding the previously loaded
- driver.
-
- Still no problem, I edit the config.sys and autoexec.bat
- and put the driver (something.sys) into the /usr/vpix/dosbin
- along with the program which'll be called from the autoexec.bat
- file. Fire up vpix again, and get: "BAD OR MISSING XXXXX.SYS
- DRIVER".
-
- Now UNIX appears happy with the device/controller, and to a
- point, vpix appears happy. (I can access files on the cdrom
- from within vpix, just not run the included software...)
-
- Suggestions?
-
- Oh, and I discovered initially that going into vpix and doing
- a "dir" on the mounted CDROM showed no files - it was a bug in
- the "high sierra" drivers shipped with Interactive 3.0 and
- needed to get a fixdisk to correct that problem. (This,
- at least, works now)
-
- Jerry D. Pierce
- jdpierc@netcom.com
-
-