[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

3713.0. "Professional page V1.31 Problem" by DICKNS::MACDONALD (VAXELN - Realtime Software Pubs) Tue Apr 24 1990 14:17

I am having difficulty printing Professional Page documents on my dot
matrix printer. I am using Professional Page V1.31 and the CGFonts only.

The problem is observed as freezing of the program in the middle of
printing a page, as the program is reading strips. The entire system
locks up requiring a reboot. Other symptoms include 0 file sizes for any
created 180x180 CGcache files. I did experience the freezing a couple
times before while displaying a screen, but that problem appears to have
gone away. PostScript files are created without incident. My best guess
is that there is a problem with the routine that creates the cache files
for the CGfonts. 

Anyone out there with a similar problem who has a solution?

Thanks.

Paul MacDonald 
T.RTitleUserPersonal
Name
DateLines
3713.1Out of Memory?ULTRA::KINDELBill Kindel @ BXB1Tue Apr 24 1990 15:0312
    Re .0:
    
>   The problem is observed as freezing of the program in the middle of
>   printing a page, as the program is reading strips. The entire system
>   locks up requiring a reboot.
    
    Perhaps you've been had by the dreaded memory drought.  Try opening a
    Shell/CLI window before starting PPage and when the problem occurs flip
    to it and do an avail.  (Better yet, run ClockDJ with both Chip & Fast
    RAM displayed and pull the PPage screen down to see it.)  I've got to
    believe PPage is memory-intensive during printing and it may well be
    only half-graceful about memory shortfalls.
3713.2NAVIER::MELLITZTue Apr 24 1990 15:2718
    
    Re: .0;
    
    How much memory do you have and what printer are you using?
    
    How complicated is the document being printed?
    
    I'm thinking of buying ProPage and was wondering problems
    I would encounter.  
    
    I've heard that you need 3MByte to run effectively. I have only
    2 MBytes. Wonder if this will be a problem.
    
    
    ...r 
    
    ... Rich
    
3713.3DICKNS::MACDONALDVAXELN - Realtime Software PubsTue Apr 24 1990 16:2410
    RE: .1
    
    Bill, memory is not a problem. I never drop below 398K chip mem
    or 1700K fast mem. Running a 5 Mbyte system with an A2620.
    
    RE: .2
    
    Not complicated enough for successful screen or PostScript output.
    As I mentioned the problem seems to be related to the use of CGFonts
    and the CacheEditor.
3713.4Back to the drawing board...ULTRA::KINDELBill Kindel @ BXB1Tue Apr 24 1990 17:1910
    Re .3:
    
>   ... memory is not a problem. I never drop below 398K chip mem
>   or 1700K fast mem. Running a 5 Mbyte system with an A2620.
    
    You're right, memory shouldn't be a problem.  (I had visions of a 1MB
    A500 rather than the monster system you're running.)  How about
    downloading ARTM (Amiga Run Time Monitor) and firing it up to find out
    what the PPage task is up to?  It sounds like it's in a wait state of
    some sort.
3713.5Gold Disk HelpDICKNS::MACDONALDVAXELN - Realtime Software PubsTue Apr 24 1990 18:2413
    
    A lengthy and expensive call to Gold Disk has produced some insight
    into possible causes of the problem. it seems that there are two
    important files in the CGCache directory supplied with the disks.
    One is called Timesxxx and the other Triumviratexxx. I don't recall
    the characters (xxx). Gold disk claims they must be present for
    the caching to work properly. They suggested that I delete all the
    files in the CGCache directory, copy those two files from the V1.31
    floppy's CGCache directory (the only two files present) and go from
    there.
    
    They also strongly urged using the hard drive for all caching rather
    than RAM.