Greetings Deron et al,

Just as I finished a long and tiring Email to Deron---he will probably agree with this opinion when he gets that Email ---I got the message about the 'new' guy 5.0.5.6. What timing!

Here's what happened:

(1) Download was fine but when Unarc swung into action the complaint;

WorkageStream5056/Help/PGUser/Screenshots/ParagrapFormat.KeepTogether.lines.mui.png
already exists, overwrite?

appeared. «WorkageStream5056» had just been created and was empty, so the message above is in error. I chose the option "Skip" and Unarc continued and completed the unpacking and declared no errors.

(2) Registration
Clicking the executable icon brought up the Registration window. I had to do the procedure twice but only because I erased my "Product Key" after the first registration.

(3) Copying PageStream5.prefs
I used the old guy that I had for version 5055, although after the registration process PageStream had created a tiny version which I erased and copied over.

(4) Opening from the executable icon
It did not work and after several tries, and doing a warm reboot prior to each trial. Then I added the lines

DEBUG
DEGUBFILE

to the «PageStream5.prefs» file but the only 'appdebug' files I could produce contained 0 bytes. So I gave up and moved to

(5) Open from a shell
This finally worked (stack at 300000 bytes) and 5056 opened nicely on a MUI screen. Everything looked well and I was able to use NEW from the navigator, but as soon as I tried to specify some font families with

File -> System Preferences -> Fonts

the GR immediately appeared. The GR claimed DSI problems; the option «Ignore DSI errors» returned me to PageStream, but it was essentially dead, although the mouse remained active and OS4.0 did not fail, but slowed to less than a walk.

Eventually, I did the Sashimi thing as follows:

Open a shell and gave:
1> cd «directory where the sashimi executable dwells»
directory where the sashimi executable dwells> run >nil: sashimi bufk=128

then opend another shell and gave

2> cd WorkageStream5056/
WorkageStream5056> stack 300000
WorkageStream5056> pagestream5

When PageStream opened I tried to do the «File -> System Preferences -> Fonts» thing again, got the GR to appear, so returned to the shell and did:

directory where the sashimi executable dwells> sashimi save
«sashimi said the saved file was in T:sashimi.out»
directory where the sashimi executable dwells> sashimi off

and then found that sashimi.out consisted of 345 rows and 17,000+ bytes.

So I've attached the sashimi.out file with this message. It will be stripped on the way to PageStreamAmigaBeta but Deron should receive it at <support@pagestream.org>.

Thanks to whoever gave the details about using Sashimi.

Great work Deron! Hope the sashimi.out sheds some light. Tomorrow, actually today but later, I'll try some other things, but if I cannot load in any font families ....... Hmmmmm!

My MAIL.OUT server has been down for several hours, so I'll be sending this off in a moment.

Cheers Don (Green Dragon)
--

My experience was similar to Don's:

On 03/23/2010, Ferguson, Don wrote:

> [...]
> (1) Download was fine but when Unarc swung into action the complaint;
>
>
WorkageStream5056/Help/PGUser/Screenshots/ParagrapFormat.KeepTogether.lines.mui.png
> already exists, overwrite?
>
> appeared.

One difference. No problems unarc'ing.

> (2) Registration
> Clicking the executable icon brought up the Registration window. I had
> to do the procedure twice but only because I erased my "Product Key"
> after the first registration.

Another difference. I "follow orders" better than Don and used the shell.

> (3) Copying PageStream5.prefs
> I used the old guy that I had for version 5055, although after the
> registration process PageStream had created a tiny version which I
> erased and copied over.

I did this for my second or third launch, and added my old PageStream5
Fonts. But now I'm wondering whether the old prefs are entirely compatible
with 5056. I'm going to erase all but what I got with the first launch, and
try setting things up with the program's Prefs setting devices, starting
with the one in the Navigator window. By the way, I'm delighted to see Tips
in that window. They hadn't been automatic in any PageStream5s so far.

> [...]
> DEBUG
> DEGUBFILE
> to the «PageStream5.prefs» file but the only 'appdebug' files I could
> produce contained 0 bytes.

I used DEBUGFILE instead of DEGUBFILE, and regularly get AppDebug.txt. I
have four in my UserPrefs drawer. Those files become real only after
stopping PageStream--needing a reboot if it crashed and can't be Quitted,
but his problem obviously wasn't a typo.

> So I ...moved to
>
> (5) Open from a shell
> This finally worked (stack at 300000 bytes) and 5056 opened nicely on a
> MUI screen. Everything looked well and I was able to use NEW from the
> navigator, but as soon as I tried to specify some font families with
>
> File -> System Preferences -> Fonts
>
> the GR immediately appeared. The GR claimed DSI problems; the option
> «Ignore DSI errors» returned me to PageStream, but it was essentially
> dead, although the mouse remained active and OS4.0 did not fail, but
> slowed to less than a walk.

Don may be ahead of me here. I clicked "A" for text before I would try to
set fonts, and clicking "A" always brought up the DSI Guru with "ignore"
not working, whether I was working on a New file or and old one I had
Opened. My first attempts to Open old files (I used some I had made with
5055) came up without any text at all, although the graphics were OK.

> Eventually, I did the Sashimi thing as follows:
> [...]

I haven't tried Sashimi again yet, but I have some DebugBufferDump.txts. I
get 11441 rows in 1048576 bytes, but almost all of them are variants on

Task 0x6B261370 (Background CLI) bad access @ 0x1C91D1C0, pc = 0x014508A4,
lr = 0x014509D8,

> [...]
> and then found that sashimi.out consisted of 345 rows and 17,000+
> bytes.
>
> [...]
--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Greetings "Bart Mathias" <mathias@hawaii.edu>
On 23/03/2010 at 21:49 you wrote concerning
Re: [PageStreamAmigaBeta] First encounter with PageStream 5056

Hi Bart,

<<snip>>
BM> One difference. No problems unarc'ing.

Good.

BM>> (2) Registration
BM>> Clicking the executable icon brought up the Registration window. I had
BM>> to do the procedure twice but only because I erased my "Product Key"
BM>> after the first registration.

BM> Another difference. I "follow orders" better than Don and used the shell.

OOoooohhhHH! Some guys really like to rub it in!

BM>> (3) Copying PageStream5.prefs
BM>> I used the old guy that I had for version 5055, although after the
BM>> registration process PageStream had created a tiny version which I
BM>> erased and copied over.

BM> I did this for my second or third launch, and added my old PageStream5
BM> Fonts. But now I'm wondering whether the old prefs are entirely compatible
BM> with 5056. I'm going to erase all but what I got with the first launch, and
BM> try setting things up with the program's Prefs setting devices, starting
BM> with the one in the Navigator window. By the way, I'm delighted to see Tips
BM> in that window. They hadn't been automatic in any PageStream5s so far.

On Tips! You're right. Had not even noticed that.

BM>> [...]
BM>> DEBUG
BM>> DEGUBFILE
BM>> to the «PageStream5.prefs» file but the only 'appdebug' files I could
BM>> produce contained 0 bytes.

BM> I used DEBUGFILE instead of DEGUBFILE, and regularly get AppDebug.txt. I
BM> have four in my UserPrefs drawer. Those files become real only after
BM> stopping PageStream--needing a reboot if it crashed and can't be Quitted,
BM> but his problem obviously wasn't a typo.

What a low DEGUB BLOW! Once again, the Bart One leaves me behind. Must be all that running that he still does.

I tried again tonight, but I could not get 5056 to open from the executable.

Hah! Confirming that the three example docs in the /Documents directory---5.0Flyer.pgs and the other two---loaded and displayed the graphic components properly. Did not fool with font substitution, just accepted whatever PageStream came out with---no fonts installed. No fonts, so no text. I'll see if I can move from page to page in the 'Examples' guy.

Hah! Was able to walk through the five pages in the Examples doc without a GR visit or freeze.

Also, change the magnification works.

Let's see if we can load some font families! Managed to get two font families installed and SAVEd (I think) before 5056 refused to function further. We'll see what happens after a reboot.

Damn! Got careless and lost brilliant reportage due to a hard freeze from 5056. By 'hard' I mean the OS froze and a cold reboot was required.

Anyway...

Loading old PageStream files
============================
Was successful with two out of two trials. Since text appeared---though strictly the Artistic font---I know now that my attempts to load font families worked. However, on the second try I tried to use font substitution. But the font substitution window would not allow me to choose one of the fonts that appeared on clicking the >> gadget. After a couple of attempts the 'hard' freeze above set in. Also noticed that some of the font names that appeared were incorrect.

However, the kiss of death arrived when I tried to access the text cursor which consistently (well .... often then!) brings a hard freeze. By 'hard' I mean the OS locks up, and a COLD reboot necessary. That's not good. In 5055 I could use the text cursor, though with trepidation.

<<snip>>
BM> Don may be ahead of me here.

Oh Joy!

BM> I clicked "A" for text before I would try to
BM> set fonts, and clicking "A" always brought up the DSI Guru with "ignore"
BM> not working, whether I was working on a New file or and old one I had
BM> Opened. My first attempts to Open old files (I used some I had made with
BM> 5055) came up without any text at all, although the graphics were OK.

Well, that's useful to know that the files will open without the text, and, as noted above it is possible, though dicey, to load in font families.

SCRIPT PALETTE
==============
I fiddled with the line

SCRIPTPALETTE HIDE AT -2 -2 SIZE -1 -1 COLLAPSED OFF

in PageStream5.pregs by removing «HIDE AT -2 -2» since in 5055 the script palette was a miserable, unexpandable (horizontally» gadget. The deletion brought out the script palette alright, after a GR visit, but then I noted that it could be expanded horizontally. That's a splendid improvement, as the usual options become visible. In 5055 I could not access APPEND, LOAD and so forth.

I was able to open the Style, Document and Pages palette as well, and my styles appeared on loading an old document. Was able to load in my scripts as well, but as soon as I reached to the text cursor, PageStream died, though allowed the OS to continue this time.

Well .... that's enough for today. How's the text cursor behaving elsewhere?

<<snip>>

Cheers Don (Green Dragon)
--