home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!darwin.sura.net!wupost!waikato.ac.nz!comp.vuw.ac.nz!actrix!conrad
- Newsgroups: comp.os.os2.misc
- Subject: Re: Use your "unsupported" CD-ROM drive natively with OS/2!
- Message-ID: <1992Aug17.221800.7327@actrix.gen.nz>
- From: conrad@actrix.gen.nz (Conrad Bullock)
- Date: Mon, 17 Aug 1992 22:18:00 GMT
- References: <1992Aug17.194511.27929@inmet.camb.inmet.com>
- Organization: Actrix Information Exchange
- Lines: 45
-
- In article <1992Aug17.194511.27929@inmet.camb.inmet.com> newbie@dylan.camb.inmet.com (Chris Newbold) writes:
- > This probably rates as a mild hack, but if you want CD-ROM support without
- > waiting or spending money...
- >
- > After installing my Sony CDU-541 CD-ROM drive and having a ball under DOS,
- > Linux and Windows NT, I tried OS/2. No dice. The driver spat out the
- > id string for my drive and pompusly declared "Unsupported vendor." What a
- > load of horsepucky. It's a SCSI CD-ROM drive, just like the Toshiba and
- > IBM drives which are supported. *SCSI* That means there is some semblance
- > of standardization. The driver shouldn't give a damn what's on the other
- > end, as long as it will talk SCSI with a supported host.
- >
- > But, I though, par for the course, looking at the crappy video driver
- > support in OS/2.
- >
- > So, I copied the CD-ROM driver CDROM.SYS off my HPFS partition into a FAT
- > parition; load it up under debug. Low and behold. There are a couple of
- > vendor id strings... So, I just replaced the word "TOSHIBA" with "SONY"
- > (filling the three remaining letters with spaces) and wrote it out.
- >
- > Load up OS/2, copy it back into the HPFS partition, reboot and.. Voila!
- > The happy-little-camper driver installed itself running my Sony drive.
-
- The easiest way is to add the /I parameter (I *think* it's /I), which tells
- the driver to ignore the manufacturer info.
-
- > I seriously wonder if this whole "unsupported vendor" thing isn't a
- > marketing sham to get people to buy hardware from certain vendors or
- > get vendors to dump a load of money on IBM for some "driver development kit."
- >
- > When will they learn that for an OS to be successful it must support a very
- > broad range of hardware? Passing the buck to a third party because you
- > are afraid of detracting from your own hardware sales because you write
- > a driver for someone else's product just isn't going to wash with me...
-
- I believe the manufacturer-specific code is for 'non-data' extensions (ie
- audio). These will probably not work if you use the /I flag (or hack the
- ID string).
-
- I can't remember which bit of documentation I read about the CDROM.SYS
- flags though - probably one of the (many) INF files available through IBM.
-
-
-
-
-