Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!enea!jan From: jan@enea.se (Jan Wester) Newsgroups: comp.sys.ibm.pc.misc Subject: GOSCRIPT VERSION 2 - 3 PROBLEMS Keywords: LaserGo Goscript Message-ID: <2001@enea.se> Date: 15 Aug 90 10:21:15 GMT Organization: Enea Data AB, Sweden Lines: 42 There seems to be a serious bug in GoScript version 2.2 and 3.0. They are the ones I have tested. The problem seems to come only if you have several megabytes of internal memory and uses it as EMS-memory. I myself have 8 Megabytes. And everything is specified as EMS-memory using 386max. Back to the problem : When I print out a document containing several pages and every page contains rather few fonts and needs rather little formatting it seems like GoScript starts to send the next page when the printer not yet has finished the current page printing. This means that you will get some shit up in the left corner of the document. This must be a bug. I tried to print my document to a file not using GoScript as the print task. I then printed the file with PRINT and I was able to look at the sending of data to the port. PRINT did not send ANY data until the printer had finished printing the current page and been silent. This meant that the document that came was perfect !. It seems like GoScript is not handling the parallell port correctly as I recall it. The printer driver I am talking about ( and the only one I have tested ) is the one for HP LaserJet II. Anyone else that have had this problem ???? I did not have this problem with 2 Megabytes of memory ! Another problem is that GoFonts from version 2.2 does not seem to be compatible with Goscript version 3.0. But I do not care about that. I have only made some brief tests on version 3. #################################################################### Jan Wester ENEA DATA Stockholm Sweden E-mail : jan@enea.se ####################################################################