Hello Deron,

I am using PS 4.1.5.6 and have been for a long time. Now I am
getting some strange behavior. I have an AmigaOne XE with 1 GB of
memory and Radeon 7000 graphics card.

If I print to a PostScript file, it creates a relatively large file.
It is a one page handout I have created that I am printing. The
PostScript file is over 500,000 in size. If the file is given a new
name the PostScript file is created with no problems. However, if I
try to overwrite an existing file, the program crashes. I get the Grim
Reaper.

I have attached both the PageStream4 file and the log from the GR. I
hope these are useful. Both are relatively small files.

Can't wait to get PS 5 Pro working.

Talk to you later.
--
Dr. Larry Keller
Levin College of Urban Affairs
Cleveland State University
lkeller@nacs.net

[Non-text portions of this message have been removed]

Deron,

My A1 is back and running now with the DMA and USB fixes. So I've
finally tried 5.0.3.3 pro. NO change in behavior.

If I boot from my update 4 CD, I Can run the program from my hard
drive, all seems OK.

If I boot from my normal system partition, or from an unchanged update
4 install on another partition, I get the "vertical tool bar, tiny
window" behavior.

WHile I had it running with the Update 4 CD, I cahnged the
preferences, and made the vertical toolbar into a palette, opened a
document, arranged the windows and ran the command to remember window
positions. The toolbar palette is not remembered, but the project
window and edit pallette are remembered.

Does this suggest some kind of problem with the toolbar?

Paul Zager

--- In PageStreamAmigaBeta@yahoogroups.com, "Paul R.
Zager" <paulrzager@...> wrote:
>
> Deron,
>
> My A1 is back and running now with the DMA and USB fixes. So I've
> finally tried 5.0.3.3 pro. NO change in behavior.
>
> If I boot from my update 4 CD, I Can run the program from my hard
> drive, all seems OK.
>
> If I boot from my normal system partition, or from an unchanged
update
> 4 install on another partition, I get the "vertical tool bar, tiny
> window" behavior.
>
> WHile I had it running with the Update 4 CD, I cahnged the
> preferences, and made the vertical toolbar into a palette, opened a
> document, arranged the windows and ran the command to remember window
> positions. The toolbar palette is not remembered, but the project
> window and edit pallette are remembered.
>
> Does this suggest some kind of problem with the toolbar?
>
> Paul Zager
>

After booting OS4.0 initially, change the Softlogik drawer name to
something else (e.g. Softlogic.old) and run Pagestream. Close
Pagestream, restore the drawer name and then run Pagestream again and
it should work. If you cannot open one of the example documents then
try the same process from another OS4.0 install.

In my case, the OS4.0 UD4 clean partition will not open an existing
document using this method. However, the normal install does not even
need the drawer renaming and works OKish except for the known problems.

The fact that it runs acceptably from your OS4.0 CD and my normal boot
partition suggests that it is not, specifically, a toolbar issue. I
had surmised it was a font problem and was just about to copy the font
folder across. Your experience with the CD shows that this is not the
problem. I have already made sure that the MUI classes are correct and
the missing PGS bitmap fonts are in Fonts: so it does not seem to be
that, either.

By the way, if you run Snoopdos for OS4.0 (from OS4Depot) you will
find that the 'two toolbars' effect is associated with a continual
attempt to produce a grim reaper and the memory indication will show
the free memory dropping until the system freezes from the lack of it.
I suspect that the only reason that the program does not run is that
the OS is too busy with the string of failed GRs to respond to
requests from the program. I have mailed the Snoopdos log to Deron.
There is, of course, no GR log as the GR fails to produce an interface
and is, anyway, unable to report what has caused the OS failure.

Regards
Roy Leith

Roy (& Deron)

> After booting OS4.0 initially, change the Softlogik drawer name to
> something else (e.g. Softlogic.old) and run Pagestream. Close
> Pagestream, restore the drawer name and then run Pagestream again
> and it should work. If you cannot open one of the example documents
> then try the same process from another OS4.0 install.

This is REALLY wierd! Following your drawer renaming scheme, I am able
to run the program after booting into my main OS4 partition as well as
if I booted from the update 4 CD. I can open an example document, but
can't open any of my own more recent documents (Amiga, I haven't tried
yet bringing in anything I've done on Windoze PgS.)

But if I boot into my "stock" OS4 partition, I can't open ANY
documents, either wtih the ".old" drawer naming or with the ".old"
remmoved. In fact, the program won't even run initially under the
"stock" OS on the second attempt, when I've renamed the Softlogik
drawer back to its original name.

The variety of behaviors here just between our two setups is
astounding. I sure hope Deron can track it down.

> In my case, the OS4.0 UD4 clean partition will not open an existing
> document using this method. However, the normal install does not
> even need the drawer renaming and works OKish except for the known
> problems.

> The fact that it runs acceptably from your OS4.0 CD and my normal
> boot partition suggests that it is not, specifically, a toolbar
> issue. I had surmised it was a font problem and was just about to
> copy the font folder across. Your experience with the CD shows that
> this is not the problem. I have already made sure that the MUI
> classes are correct and the missing PGS bitmap fonts are in Fonts:
> so it does not seem to be that, either.

Smae here with MUI classes. I'll have to check for the Softlogik
fonts.

> By the way, if you run Snoopdos for OS4.0 (from OS4Depot) you will
> find that the 'two toolbars' effect is associated with a continual
> attempt to produce a grim reaper and the memory indication will show
> the free memory dropping until the system freezes from the lack of
> it. I suspect that the only reason that the program does not run is
> that the OS is too busy with the string of failed GRs to respond to
> requests from the program. I have mailed the Snoopdos log to Deron.
> There is, of course, no GR log as the GR fails to produce an
> interface and is, anyway, unable to report what has caused the OS
> failure.

Same behavior here. I've sent several of my SnoopDOS logs to Deron
since the PPC PgS beta's started coming out.

Thanks for the help Roy!

Paul