Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!cass.ma02.bull.com!mips2!bull.bull.fr!corton!mcsun!ukc!harrier.ukc.ac.uk!zodiac.ukc.ac.uk!cur022
From: cur022%cluster@ukc.ac.uk (Bob Eager)
Newsgroups: comp.os.os2.programmer
Subject: Re: 16-Bit Device Driver + OS/2 V2.0
Message-ID: <22458.2838e31f@cluster@ukc.ac.uk>
Date: 21 May 91 09:06:39 GMT
References: <9105191848.AA16778@grape.ecs.clarkson.edu>
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 23

In article <9105191848.AA16778@grape.ecs.clarkson.edu>, kenkahn@pksmrvm.vnet.ibm.com (Kenneth A. Kahn) writes:
> It is my understanding and experience that if you have a 16-bit device driver
> that uses 'documented interfaces', e.g. DevHelp calls, it should work on
> V2.0 without modification.  I can't speak for the EZtape driver never having
> used it, but perhaps it does something 'funny';  there's some device drivers
> I know of that work for 1.2 and 1.3 that do some funny things with GDTs and
> such that won't work with V2.0 because the 'undocumented assumptions' they made
> are no longer true for V2.
> 
> To turn this around a little, if you know of a device driver that does not
> work with V2 and it uses strictly documented interfaces, please let your
> IBM rep know about it; we consider it a HIGH priority for these types of
> things to work in V2.  If you can isolate what the problem is report it here
> and I'll make sure it gets to the right people.

I believe the EZtape driver (or a variant) is the one used by the IBM OS/2
Internal Tape Backup Program. Anyone know if that works? I have one, so I'm
interested and possibly a bit concerned if it doesn't!
----------------------------+----------------------------------------------
Bob Eager                   | University of Kent at Canterbury
rde@ukc.ac.uk               | +44 227 764000 ext 7589
100016.2770@compuserve.com  |
----------------------------+----------------------------------------------