Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!cbmehq!cbmger!peterk
From: peterk@cbmger.UUCP (Peter Kittel GERMANY)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Wb2 questions, ECS Denise
Message-ID: <674@cbmger.UUCP>
Date: 28 Dec 90 17:01:23 GMT
References: <632@cbmger.UUCP> <1145@cnw01.storesys.coles.oz.au> <650@cbmger.UUCP> <1990Dec20.131346.23479@marlin.jcu.edu.au> <663@cbmger.UUCP> <1990Dec21.182047.12630@msuinfo.cl.msu.edu>
Reply-To: peterk@cbmger.UUCP (Peter Kittel GERMANY)
Organization: Commodore Bueromaschinen GmbH, West Germany
Lines: 22

In article <1990Dec21.182047.12630@msuinfo.cl.msu.edu> jap@convex.cl.msu.edu (Joe Porkka) writes:
>peterk@cbmger.UUCP (Peter Kittel GERMANY) writes:
>
>>The timeout value is placed among the very first bytes in a
>>printer driver. If you take out the RKMs, it shouldn't be too
>>difficult to patch your driver for more convenient values.
>
>Perhaps you couldclarify this point.

Oh, I hoped nobody would ask :-). You see, I did this ONE time
in my life (with not SO much success) and still under 1.2, that
I tried to write a printer driver. There was that little part
that had to be in Assembler, named printertag.asm that had to
be linked as the very first part of the final driver code.
It has the entry "DC.L 30 ;Timeout" at offset about 60 from
the beginning (add some bytes for hunk header in the file).
Details are found in the RKM Libraries & Devices (1.3, blue),
p. 764.

-- 
Best regards, Dr. Peter Kittel  // E-Mail to  \\  Only my personal opinions... 
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk