Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 (Tek) 9/28/84 based on 9/17/84; site tektools.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!daemon!tektools!tomm
From: tomm@tektools.UUCP (Tom Milligan)
Newsgroups: net.micro.mac
Subject: Manx C Printing Mangler -er I mean Manager- support
Message-ID: <238@tektools.UUCP>
Date: Thu, 16-May-85 11:55:16 EDT
Article-I.D.: tektools.238
Posted: Thu May 16 11:55:16 1985
Date-Received: Sat, 18-May-85 02:05:55 EDT
Distribution: net
Organization: Tektronix, Beaverton OR
Lines: 28

I have the  Manx professional C compiler, and have been writing some programs
that use the Printing Manager toolbox.  I have found that in order for the
programs to work (ie. to get something to actually print on the printer), I 
must have Manx' console driver installed as a resource in my program.  My
understanding of the printing manager stuff is that I should only need to have
the driver (called ".Print") for the currently installed printer installed in 
the System resource file.  Of course I would prefer not to have to install
Manx' console driver in my programs because 

	1)  It takes up 3K of disk space that shouldn't be necessary to
		take up.

	2)  I don't know whether the printing manager routines are truly
		"printer independant" as they should be if they relied
		soley upon the current printer driver.

I have repeatedly talked to someone at Manx several times 
about this problem, and he can't seem to remember any of my previous calls 
about the problem, and claims that he doesn't know much about the Print 
Manager stuff as it relates to the console driver.  I am tired of getting no 
response from Manx, and am wondering if anyone else out there has any 
experience and/or workarounds for this problem.

Other than this however, I like the Manx system quite a bit.

				Thanks,

				Tom Milligan