Path: utzoo!utgpu!watmath!clyde!att!westmark!dave
From: dave@westmark.UUCP (Dave Levenson)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DOS device driver problem
Summary: stty raw
Message-ID: <556@westmark.UUCP>
Date: 11 Nov 88 05:22:33 GMT
References: <712@inuxh.UUCP> <395@megatek.UUCP>
Organization: Westmark, Inc., Warren, NJ, USA
Lines: 27

In article <395@megatek.UUCP>, hollen@spot.megatek.uucp (Dion Hollenbeck) writes:
> From article <712@inuxh.UUCP>, by blp@inuxh.UUCP (Bruce Paramore):
> > I am having a problem with a DOS device driver I have written.  All it has
> > to do for my present application is to write a byte to a register on a custom
> > board.  This seems to work fine for all values except 0x1a (^Z).
...
> DOS is looking at ^Z and saying "Oh, he means end of file, don't send
> this".  You might be able to get around this by picking any other control
> character (or maybe a sequence) and having your device driver translate
> it into the register as ^Z, otherwise, DOS will continue to eat it for


MS-DOS allows an application to place a device in RAW mode.  The
ioctl function call supports this if your driver does.  The trouble
is that there is no way to use it from the command line (no stty
command) and no ioctl() library function provided in MS C.  But you
can do it yourself (in assembly language, or by using intdos() in C)
in your application, after you've opened your custom device.

Have a look at dos function 0x44:  Bit 5 of the value passed in
register DX is the RAW/COOKED flag for the device.

-- 
Dave Levenson
Westmark, Inc.		The Man in the Mooney
Warren, NJ USA
{rutgers | att}!westmark!dave