Conference hydra::amiga_v1

    I don't have PageStream so I don't know if this will work or not but it
    works with some other programs that don't give back memory. After I exit
    the program that won't give back memory, I run XOPER and use the flush
    command. Then I quit XOPER and I have my memory back.
    
    tom

    What is XOPER?

SoftLogic's PageStream has a similar history on the ST.  They shipped a
few early versions of PageStream to eagar customers, who were very
disappointed.  Version 5.1 for the Atari seems to be fairly stable, but
I'm not convinced that they test these programs very much before they
ship them.

The predecessor (Publishing Partner) has a habit of bombing when
writing the output file, so you have to take care not to write your
file to the same filename, but to alternate between two names, in case
it does this. (I've had newsletters eaten by this.)

I tend to think of Publishing Partner like "this program is junk but for
the price, it can't be beat".   I've heard PageStream is much better, so
long as you avoid the bugs.

Also, since it's a port from the ST, and the ST's memory management
doesn't require that you free everything before you exit, it's no
surprise that there are memory leaks in it.  My guess is that these guys
are moving to the Amiga because of the growing imbalance between the ST
market and the Amiga market.  I'm gald they didn't go for the clones...

Re: .1

I don't have XOPER, but I suspect that its flush command isn't as useful
as you think.

The Amiga operating system intentionally doesn't free certain resources
as soon as it could.  If a program uses shareable libraries or fonts (most
do) then the operating system doesn't reclaim the memory for the libraries
or fonts as soon as they are closed by their last user.  Instead, the system
allows the libraries and fonts to continue to reside in memory so that
they will not have to be reloaded into memory when the next program opens
them.

If any memory allocation can not be fulfilled, the system will purge all
unused libraries and fonts from memory.  The system then retries the memory
allocation that failed.

This "lazy memory flush" means that the Amiga does less disk I/O at the
possible expense of additional memory fragmentation.

XOPER "flush" command is probably like many other utilities' flush command:
it simply causes the system to flush currently unused resources to reclaim
the memory now, as opposed to when you need it.  As such, XOPER only
reclaims resources that were properly released by completely correct
programs.  The command is useful only if you are worried about memory
fragmentation, or you wish to check that the extra memory allocation left
over from running a program is the result of the system cache, or due
to the program not releasing system resources.  (If after the flush, all
memory is returned, then the program was correct.  If after the flush,
additional memory is still allocated, then the program didn't release
some resource.)

If you load use a magic flag on the LoadWB command, Workbench will have
an extra menu that allows you to do a flush (and enter the ROM debugger,
and other mostly useless things).

    XOPER is a system monitor sort of like sysdpy on tops10. After reading
    .-1 I suspect Randy is correct and XOPER will only flush properly released
    memory.
    
    sorry,
    
    tom
    
    ps - I thought I got XOPER from the net somewhere but I don't see it on
    NORSE or TAPE. I don't have it here at work anymore. I'll try and upload it
    and send it over to NORSE::[upload].

    This seems as good a place as any to ask my questions about PageStream
    1.6.  Just got my copy on Friday and have already produced a prototype
    newsletter (a one pager) and printed it on my Epson 9 pin with
    astonishing results.  Which brings me to my first question: I got
    my best results with the good old AmigaDOS 1.3 EpsonX printer driver.  
    I tried the Pagestream EpsonX driver but got a dreadful mess.  Has
    anyone gotten anything useful from the PS EpsonX driver (or any
    of the PS dot matrix drivers, for that matter)?
    
    Also.  In one of the tutorials (which are poorly written, by the
    way) they ask you to import a graphic from the PSGraphics directory.
    Mine was empty.  Anybody have a PageStreamFonts: disk that actually
    has something in that directory?
    
    It may have been my imagination, but I could swear that I
    saw someone in this conference make mention of a release 1.61. 
    Is that right?   What are the chances that if I send my registration
    card in, I'll get the latest release?  (If it's other than 1.6, that
    is.)
    
    After 8 or 10 hours worth of using PageStream, I have mixed emotions.
    The program has a pretty professional look to it.  (I've been using
    it in the 640x400x2 mode and with the right colors it looks good.)
    It's reasonably fast, though I admit that I have little to compare
    it to.  My biggest criticisms are with the documents and the fact
    that it has an annoying habit of locking up *just* before I attempt
    to save.  The documents are iffy because the tutorial sections are
    inconsistent.  I've seen two differing explanations of one feature.
    (It must've changed from one release to the next.)  They also tend
    to assume that you know more than you should.  That is, they ask
    one to use features that have yet to be discussed.
    
    But, as I said, the dot matrix output impressed me and I'm looking
    forward to seeing what can be done with a PostScript laser printer.
    I just hope a few bug fixes are forthcoming.
    
    Gary

    I got a package in the mail today from SoftLogik containing a 50 or 60
    page, PageSteam formatted, newsletter.  Very nicely done.  It contains
    information about the supposedly upcoming release 1.8, a few hints and
    tips, and a beginner's tutorial.  According to the "What's Happening at
    SoftLogik" column:  (Comments in []'s are mine.)
    
    "SoftLogik is proud to announce that PageStream is about to turn 1.8. 
    This rendition adds many newer and faster features to the previous
    versions of the program, as well as eliminationg bugs.  [It's about
    time. :-)]"
    
    "If you have recieved this newsletter, it is probably because you are a
    registered owner of PageStream, and as such, are entitled to obtain an
    upgrade to version 1.8."
    
    "Version 1.8 is on its way.  It will be sent to you *automatically*
    ...."
    
    New "features" include:
    
    o Faster startup
    o Faster graphic manipulation
    o Import ASDG 24-bit color pictures
    o Improved postscript
    o Numerous bugs fixed [That should never have been present in the first
    place.]
    
    So if you've sent in your registration card, you should be getting this
    newsletter, and ultimately, (we hope) a copy of 1.8.
    
    
    As an aside, I thought I might say that I've used PageStream quite a
    bit now and am for the most part pleased with its performance.  There
    are times when I tire of working around the bugs, but it does a good
    job with my fellowship's newsletter.  I'm sure that PPage is more of a
    pleasure to work with, but I get good postscript output with PageStream
    and I only spent $130.  I'm looking forward with relish towards 1.8 since 
    it seems that most of my "favorite" bugs have been fixed.
    
    
    Gary

    I got a package from Soft-Logik today, containing 20 pages of document
    updates and a diskette containing version 1.8 of the program and
    drivers.  I haven't had time to give it a workout, but I loaded up one
    of my old newsletters and played a little.  It's a little cleaner all
    around.  The file requester is much better thought out this time.  I
    hope that is true of the rest of the package.
    
    Oddly enough it *was* a free update.  They didn't lie about that.
    
    -Gary