Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!mcvax!kth!draken!tut!santra!saha!s29749s From: s29749s@saha.hut.fi (Olli Johannes Arnberg) Newsgroups: comp.sys.mac Subject: Re: A free HP DeskJet driver Summary: Bug reports welcomed. Keywords: HP DeskJet HPDJ Bug Message-ID: <21529@santra.UUCP> Date: 25 Apr 89 17:06:23 GMT References: <3829@utastro.UUCP> <10308@netnews.upenn.edu> Sender: news@santra.UUCP Reply-To: s29749s@saha.hut.fi (Olli Johannes Arnberg) Distribution: comp Organization: Helsinki University of Technology, Finland Lines: 80 In article <10308@netnews.upenn.edu> hodas@eniac.seas.upenn.edu (Josh Hodas) writes: >I spent 1/2 an hour downloading it (locally, not the ftp) and 4 hours printing >the 70 page manual on my deskjet (using my existing grappler driver). >I should have waited. It seems to be extremely buggy, Would we dare to suggest: not notably more buggy than many other free software packages, some of which do not come with source code to allow you to verify and fix the bug in case you would be willing to do so. > at least on my >Mac II (the manual mentions it was tested on a plus, a 512 i think, >and a macified atari, but nothing with 128k ROMS). Actually, both the Plus and the 512KE we used have (of course) 128K ROMs. Mr. Jari Asikainen (who owns the 512KE with Dove 2MB+SCSI) has been testing the HPDJ driver since December 1988. A local Mac & HP DeskJet dealer has been using HPDJ with a Mac II since 4th of April 1989 for demonstration purposes. Neither of them have reported any problems appearing to be this serious. >It bombed as soon as I tried to print a catalog from the finder. With which id did it bomb? Were you using AppleTalk? AppleShare? Did you reboot after removing Grappler from your system folder and changing the HPDJ Chooser settings not to conflict with possible AppleTalk (as instructed in the manual, in section 3.4, Settings) before trying to print the first time? A more detailed bug report would be much appreciated. With your minimal description, we were unable to reproduce the bug. (Please see section 5.2 of the manual, Reporting Bugs for detailed instructions for as how to report a problem with HPDJ.) We have certainly printed literally hundreds of pages from the Finder (versions 4.1, 6.0, and 6.1) using both 64K and 128K ROMs. >I was able to get it printing from other apps, From applications not mentioned in our list of (apparently) working applications? We would be interested to hear. It would be nice if you could mail this information together a more detailed bug report to the mail alias "hpdj-bugs@hut.fi". > but suddenly after a >few printouts, it kept printing in 75 dpi (or 100 i forget) no matter >what I selected in the print dialog. Which application were you using? Which version? Most notably, MS Word 3.0x and Pagemaker 2.x are known to use print records in bizarre ways, forcing themselves to 100 dpi printout with HPDJ. Perhaps this is a bug peculiar to the Mac II only. On the other hand, this behavior has never appeared with Atari+Aladin, Mac 512KE, Mac Plus, or Mac SE. Please report the situation more carefully so we can try to reproduce the bug. > Basically, I applaud the >concept, and I hope Olli et al can get it working, but for now its >back in my inactive file. > >Josh Thank you for encouragement. >PS: I forgot to mention, the application that prints the spooled documents > (such as the manual) seems unable to deal with page subranges that > do not begin with 1. It crunches for a while and then returns without > doing anything. Again, a great idea, but to many problems. This is an actual bug; thank you for reporting it. In the process of adding printing a specified number of pages as described in Inside Macintosh II-156, we added the code found there scrupulously without realizing that it must be done before the call "PrOpenDoc". We hope that this bug won't prevent you from using the program the current version 0.0 of the BatchPrint application was mainly intended to allow printing the manuals. The bug will be corrected in the next release of BatchPrint. Those who want to fix it by themselves: in function "fOurPrintWindow", move the lines between a call to "PrOpenDoc" and a "FOR" statement before the "PROPenDoc" call. Olli Arnberg (s29749s@saha.hut.fi), Ari Mujunen (s29851c@taltta.hut.fi)