I'm wondering if the people who find the most recent beta for Amiga
(5.0.3.3) almost unusable are perhaps trying the Pro version instead of the
plain one?

I have started playing with the Pro version, and finding it almost unusable
so far. With the plain version I was able to use the menus, and quit the
program when I wanted to. Not so with Pro.

Bart Mathias

Bart Mathias <mathias@hawaii.edu>:
> I'm wondering if the people who find the most recent beta for Amiga
> (5.0.3.3) almost unusable are perhaps trying the Pro version instead of the
> plain one?

No, it's non-pro here.

--
Philippe Elwood Ferrucci
AmigaOS 4.x betatester
Amiga Translator Organisation
http://elwoodb.free.fr

Hi Bart,

On 01/06/2009, you wrote:
> I'm wondering if the people who find the most recent beta for Amiga
> (5.0.3.3) almost unusable are perhaps trying the Pro version instead of the
> plain one?

> I have started playing with the Pro version, and finding it almost unusable
> so far. With the plain version I was able to use the menus, and quit the
> program when I wanted to. Not so with Pro.

Huh, good point.

I have only tried the Pro version so far - will try the plain pne later.

But, isn't the only difference between the 2, the add-ons? Like pdf, Borders
included & so on?

Will habve to check, later.

Bye for now,
--

A conservative is a man with two perfectly good legs who has never learned to
walk.
-- Franklin D. Roosevelt

wurzel
Russell

weather: Clear Skies : 20.00 C, 68.00 F
Winds : Variable 16.11 MPH, 25.93 KPH, 14.00 Knots
Jersey Airport (EGJJ), United Kingdom

> Hi Bart,
>
> On 01/06/2009, you wrote:
>
>> I'm wondering if the people who find the most recent beta for Amiga
>> (5.0.3.3) almost unusable are perhaps trying the Pro version instead of the
>> plain one?
>>
>
>
>> I have started playing with the Pro version, and finding it almost unusable
>> so far. With the plain version I was able to use the menus, and quit the
>> program when I wanted to. Not so with Pro.
>>
>
> Huh, good point.
>
> I have only tried the Pro version so far - will try the plain pne later.
>
> But, isn't the only difference between the 2, the add-ons? Like pdf, Borders
> included & so on?
>
> Will habve to check, later.
>
>
> Bye for now,
>

No, the Pro version has additional code. However, they are both compiled
from the same sources and no one is certainly getting to the point of
using one of those Pro features. _IF_ there is a difference, then most
likely it is simply because code/data falls at different locations and
something that is trashing memory is trashing different memory so
causing a different problem.

The Pro version lets you do things like gradient blend picture/drawing
masks; path math where you can select two overlapping paths and generate
a path which is the sum of those paths or the difference between those
paths, etc; export selected objects to a bitmap (including now with
alpha mask) or EPS.

Deron

--
Deron Kazmaier - support@pagestream.org
Grasshopper LLC Publishing -http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

Greetings "Bart Mathias" <mathias@hawaii.edu>
On 02/06/2009 at 03:51 you wrote concerning
[PageStreamAmigaBeta] PageStream5.0.3.3 beta vs. 5.0.3.3 Pro

Hi Bart,

BM> I'm wondering if the people who find the most recent beta for Amiga
BM> (5.0.3.3) almost unusable are perhaps trying the Pro version instead of the
BM> plain one?

I occasionally use the Pro version of 5.0.3.3 here. No longer would I describe
it as "almost unusable", rather I would assess it as "almost usable". I do not
use it for 'serious' work that would involve a large time involvement since
there has been more than one disaster following that avenue. It can be great
for printing to my fancy HP 2605 printer since it will handle duplexing.
However, main problem is getting past the font conversion problems. Font
conversion works nicely, but some of the TrueType fonts that are available for
Pro 5 are inadequate here.

BM> I have started playing with the Pro version, and finding it almost unusable
BM> so far. With the plain version I was able to use the menus, and quit the
BM> program when I wanted to. Not so with Pro.

Have not attempted to compare the 'plain' versus the 'pro' version. The menus in
Pro 5 seem to work well, although I cannot say that I've tried all of them.
Quitting Pro 5 has the undesireable effect -- as noted many times by Michael
Merkel -- that the next time you open Pro 5, it opens on the Workbench screen
and not on the MUI guy that I much prefer. If I want to use Pro 5 a 'second'
time, then I just reboot the AmigaOne, unless there is some critical reason
for not so doing.

I've not caught up in reading all the reports about that 'alpha' version that
has been released recently, but it sounds like you've gotten farther than
anyone. For a change, luck is with thee. )

Cheers Don (Green Dragon)
--

Hello Don

On 06.06.2009, you wrote:
> [...]
> Have not attempted to compare the 'plain' versus the 'pro' version. The menus in
> Pro 5 seem to work well, although I cannot say that I've tried all of them.
> Quitting Pro 5 has the undesireable effect -- as noted many times by Michael
> Merkel -- that the next time you open Pro 5, it opens on the Workbench screen
> and not on the MUI guy that I much prefer. If I want to use Pro 5 a 'second'
> time, then I just reboot the AmigaOne, unless there is some critical reason
> for not so doing.
> [...]
> Cheers Don (Green Dragon)

I solved this by protecting the PageStreamMUI.prefs.

open a shell and type:

protect ENVARC:MUI/PAGESTREAM#? -WD <press enter or return>

and

Protect [putpagestream5.033-directory-here]/UserPrefs/pageStream#? -wd <press enter or return>

this simply protects the pagestream preferences fom being changed. Bare in
mind, that if you proposedly want to change PageStream's prefs, you first
should undo this command by typing the following:

protect ENVARC:MUI/PAGESTREAM#? +WD <enter or return>

and

Protect [putpagestream5.033-directory-here]/UserPrefs/pageStream#? +WD <enter or return>

( see the the Writeable and Deleteable protection bits are ADDed againg by the "+" )

this may set the files to writeable and deleteable again.

hope this saves you some reboots.

Regards

--
I know not with what weapons World War III will be fought, but World
War IV will be fought with sticks and stones.
-- Albert Einstein

I'm using the best Operating System ever:
****************************************************
* www.AmigaOS4.com *
****************************************************
-------------------- AmigaONE XE-G4: --------------------
----------------------------- visit ------------------------------
www.AmigaWorld.net www.amiga-news.de
www.alinea-computer.de
www.hyperion-entertainment.biz
www.grasshopperllc.com
www.vesalia.de

Greetings "Remo" <rcostantin@yahoo.de>
On 07/06/2009 at 08:36 you wrote concerning
Re: [PageStreamAmigaBeta] PageStream5.0.3.3 beta vs. 5.0.3.3 Pro

Hello Remo,

<<snip>>
R>> Workbench screen and not on the MUI guy that I much prefer. If I want to use
R>> Pro 5 a 'second' time, then I just reboot the AmigaOne, unless there is some
R>> critical reason for not so doing.

R> I solved this by protecting the PageStreamMUI.prefs.

R> open a shell and type:

R> protect ENVARC:MUI/PAGESTREAM#? -WD <press enter or return>

R> and

R> Protect [putpagestream5.033-directory-here]/UserPrefs/pageStream#? -wd <press
R>>

R> this simply protects the pagestream preferences fom being changed. Bare in
R> mind, that if you proposedly want to change PageStream's prefs, you first
R> should undo this command by typing the following:

R> protect ENVARC:MUI/PAGESTREAM#? +WD <enter or return>

R> and

R> Protect [putpagestream5.033-directory-here]/UserPrefs/pageStream#? +WD <enter
R>>

R> ( see the the Writeable and Deleteable protection bits are ADDed againg by
R> the "+" )

R> this may set the files to writeable and deleteable again.

R> hope this saves you some reboots.

OK, that's neat and I even follow what's happening. However, I have a
couple of questions:

In Envarc:Mui I find the relevant files:

PAGESTREAM.1.prefs PAGESTREAM.2.prefs PAGESTREAM.3.prefs

and since the last version of PageStream used in this session was 5.0.3.3, I
assume that the three files above were created by PageStream 5.0.3.3. So I
understand the relevance of changing the protection bits relative those files,
but ....

In WorkageStream5/UserPrefs there are the four files:

FontSubstitutionData
PageStream5 Fonts
PageStream5.prefs
PageStream5 Styles

Your PROTECT command would apply to the last three files listed above. Would it
not be preferable to use but

Protect WorkageStream5/UserPrefs/pageStream5.prefs -wd

since I don't necessarily want to 'protect' the 'Fonts' and 'Styles' files?

Neat idea, thanks for suggesting it. Too bad it did not work for Bart!

Cheers Don (Green Dragon)
--

Hello Don

On 08.06.2009, you wrote:

>
> OK, that's neat and I even follow what's happening. However, I have a
> couple of questions:
>
> In Envarc:Mui I find the relevant files:
>
> PAGESTREAM.1.prefs PAGESTREAM.2.prefs PAGESTREAM.3.prefs
>
> and since the last version of PageStream used in this session was 5.0.3.3, I
> assume that the three files above were created by PageStream 5.0.3.3. So I

I suppose so. But I can't tell you anything about. Deron should know.

> understand the relevance of changing the protection bits relative those files,
> but ....
>

> In WorkageStream5/UserPrefs there are the four files:
>
> FontSubstitutionData
> PageStream5 Fonts
> PageStream5.prefs
> PageStream5 Styles
>
> Your PROTECT command would apply to the last three files listed above. Would it
> not be preferable to use but
>
> Protect WorkageStream5/UserPrefs/pageStream5.prefs -wd
>
> since I don't necessarily want to 'protect' the 'Fonts' and 'Styles' files?
>
> Neat idea, thanks for suggesting it. Too bad it did not work for Bart!
>
>
> Cheers Don (Green Dragon)

Yes, that should do it. I just was overcautious and thought that if the prefs files
get corrupted, it could happen to the other prefs files too.

Mmmh.. about Bart, maybe for some odd reason his beta is not reading the prefs
file when he launces pagestream.

sorry for that, I thought my suggestion it would help him too.

Regards
--
Everybody is talking about the weather but nobody does anything about it.
-- Mark Twain

I'm using the best Operating System ever:
****************************************************
* www.AmigaOS4.com *
****************************************************
-------------------- AmigaONE XE-G4: --------------------
----------------------------- visit ------------------------------
www.AmigaWorld.net www.amiga-news.de
www.alinea-computer.de
www.hyperion-entertainment.biz
www.grasshopperllc.com
www.vesalia.de

Remo wrote:
> Hello Don
>
> On 08.06.2009, you wrote:
>
>
>> OK, that's neat and I even follow what's happening. However, I have a
>> couple of questions:
>>
>> In Envarc:Mui I find the relevant files:
>>
>> PAGESTREAM.1.prefs PAGESTREAM.2.prefs PAGESTREAM.3.prefs
>>
>> and since the last version of PageStream used in this session was 5.0.3.3, I
>> assume that the three files above were created by PageStream 5.0.3.3. So I
>>
>
> I suppose so. But I can't tell you anything about. Deron should know.
>

Actually, I can't. I presume that these are some kind of MUI pref file
being created. Nothing that PageStream is writing directly. The fact
that you get multiple copies is probably a symptom of the problem where
PageStream is not freeing up the MUI screen properly and if you relaunch
it generates a new screen?

Deron

--
Deron Kazmaier - support@pagestream.org
Grasshopper LLC Publishing -http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

PageStream Support wrote on 09.06.2009
about <Re: [PageStreamAmigaBeta] PageStream5.0.3.3 beta vs. 5.0.3.3 Pro> the
following:

> Remo wrote:
>> Hello Don
>>
>> On 08.06.2009, you wrote:
>>
>>
>>> OK, that's neat and I even follow what's happening. However, I
>>> have a couple of questions:
>>>
>>> In Envarc:Mui I find the relevant files:
>>>
>>> PAGESTREAM.1.prefs PAGESTREAM.2.prefs PAGESTREAM.3.prefs
>>>
>>> and since the last version of PageStream used in this session was
>>> 5.0.3.3, I assume that the three files above were created by
>>> PageStream 5.0.3.3. So I
>
>>
>> I suppose so. But I can't tell you anything about. Deron should know.
>>
>
> Actually, I can't. I presume that these are some kind of MUI pref file
> being created. Nothing that PageStream is writing directly. The fact
> that you get multiple copies is probably a symptom of the problem where
> PageStream is not freeing up the MUI screen properly and if you
> relaunch it generates a new screen?

exactly!
this is since the first alphas.

byebye...
--
Michael Merkel (MiMe@IRC)
Michael.Merkel@gmx.net
http://www.mirime.de/Michael
Member ofhttp://www.amiga-freunde.de

Greetings "Remo" <rcostantin@yahoo.de>
On 09/06/2009 at 03:43 you wrote concerning
Re: [PageStreamAmigaBeta] PageStream5.0.3.3 beta vs. 5.0.3.3 Pro

Hi Remo,

Thanks for replying. I messed around a bit and found:

R>> OK, that's neat and I even follow what's happening. However, I have a
R>> couple of questions:

R>> In Envarc:Mui I find the relevant files:

R>> PAGESTREAM.1.prefs PAGESTREAM.2.prefs PAGESTREAM.3.prefs

R>> and since the last version of PageStream used in this session was 5.0.3.3,
R>> I
R>> assume that the three files above were created by PageStream 5.0.3.3. So I

R> I suppose so. But I can't tell you anything about. Deron should know.

After shifting back and forth between PageStream4 (i.e., 4.1.5.6) and
PageStream5 (i.e., 5.0.3.3) I found that those «PAGESTREAM.n.prefs» files in
Envarc.Mui did NOT change. After a soft reboot and much shifting back and
forth, the LIST command continued to insist that

PAGESTREAM.1.prefs 162 ----rw-d 19-Jan-09 21:37:02
PAGESTREAM.3.prefs 572 ----rw-d 30-Mar-09 14:40:21
PAGESTREAM.2.prefs 506 ----rw-d 16-Dec-08 22:04:05
3 files - 1K byte - 9 blocks used

and I have no idea why the dates given are relevant!!! The above was performed
before any fooling around with the PROTECT command. For example, I haven't any
idea what I did on 30 March 2009 which caused the creation or modification of
the file P

Then I read Deron's comment about the above probably being related to the
activities of MUI, so that might account for the dates involved.

R>> In WorkageStream5/UserPrefs there are the four files:
R>>
R>> FontSubstitutionData
R>> PageStream5 Fonts
R>> PageStream5.prefs
R>> PageStream5 Styles

R>> Your PROTECT command would apply to the last three files listed above.
R>> Would it
R>> not be preferable to use but

R>> Protect WorkageStream5/UserPrefs/pageStream5.prefs -wd

R>> since I don't necessarily want to 'protect' the 'Fonts' and 'Styles' files?

R>> Neat idea, thanks for suggesting it. Too bad it did not work for Bart!

R>> Cheers Don (Green Dragon)

R> Yes, that should do it. I just was overcautious and thought that if the
R> prefs files get corrupted, it could happen to the other prefs files too.

R> Mmmh.. about Bart, maybe for some odd reason his beta is not reading the
R> prefs file when he launces pagestream.

R> sorry for that, I thought my suggestion it would help him too.

Bart assumed that I had tried out your suggestions. That was false until an hour
or so ago. The short story is that the changes did not work and PageStream
5.0.3.3 continues to open (on the second and following openings) on the
Workbench screen after the PROTECT command(s) were given. In each trial, I did

** soft reboot
** apply a PROTECT command
** try opening 5.0.3.3 several times in succession.

I started out with just changing the protect bits in
WorkageStream5/UserPrefs/pageStream5.prefs
and that made no difference. Then I additionally applied the PROTECT command to
the files:

PAGESTREAM.1.prefs
PAGESTREAM.3.prefs
PAGESTREAM.2.prefs

in Envarc:MUI and that made no difference. So, after several trials, it appears
that your splendid suggestion does not work here.

Cheers Don (Green Dragon)
--

Greetings "Remo" <rcostantin@yahoo.de>
On 09/06/2009 at 03:43 you wrote concerning
Re: [PageStreamAmigaBeta] PageStream5.0.3.3 beta vs. 5.0.3.3 Pro

OH... OH! I hit a wrong prematurely and most of the missive below was sent off
in error. Below there is a small addition that was cut off. Sorry!

Hi Remo,

Thanks for replying. I messed around a bit and found:

R>> OK, that's neat and I even follow what's happening. However, I have a
R>> couple of questions:

R>> In Envarc:Mui I find the relevant files:

R>> PAGESTREAM.1.prefs PAGESTREAM.2.prefs PAGESTREAM.3.prefs

R>> and since the last version of PageStream used in this session was 5.0.3.3,
R>> I
R>> assume that the three files above were created by PageStream 5.0.3.3. So I

R> I suppose so. But I can't tell you anything about. Deron should know.

After shifting back and forth between PageStream4 (i.e., 4.1.5.6) and
PageStream5 (i.e., 5.0.3.3) I found that those «PAGESTREAM.n.prefs» files in
Envarc.Mui did NOT change. After a soft reboot and much shifting back and
forth, the LIST command continued to insist that

PAGESTREAM.1.prefs 162 ----rw-d 19-Jan-09 21:37:02
PAGESTREAM.3.prefs 572 ----rw-d 30-Mar-09 14:40:21
PAGESTREAM.2.prefs 506 ----rw-d 16-Dec-08 22:04:05
3 files - 1K byte - 9 blocks used

and I have no idea why the dates given are relevant!!! The above was performed
before any fooling around with the PROTECT command. For example, I haven't any
idea what I did on 30 March 2009 which caused the creation or modification of
the file P

---------------
I meant to add:
---------------

PAGESTREAM.3.prefs to be created or modified.

-------------------------------
The rest is as in the original.
-------------------------------

Then I read Deron's comment about the above probably being related to the
activities of MUI, so that might account for the dates involved.

R>> In WorkageStream5/UserPrefs there are the four files:
R>>
R>> FontSubstitutionData
R>> PageStream5 Fonts
R>> PageStream5.prefs
R>> PageStream5 Styles

R>> Your PROTECT command would apply to the last three files listed above.
R>> Would it
R>> not be preferable to use but

R>> Protect WorkageStream5/UserPrefs/pageStream5.prefs -wd

R>> since I don't necessarily want to 'protect' the 'Fonts' and 'Styles' files?

R>> Neat idea, thanks for suggesting it. Too bad it did not work for Bart!

R>> Cheers Don (Green Dragon)

R> Yes, that should do it. I just was overcautious and thought that if the
R> prefs files get corrupted, it could happen to the other prefs files too.

R> Mmmh.. about Bart, maybe for some odd reason his beta is not reading the
R> prefs file when he launces pagestream.

R> sorry for that, I thought my suggestion it would help him too.

Bart assumed that I had tried out your suggestions. That was false until an hour
or so ago. The short story is that the changes did not work and PageStream
5.0.3.3 continues to open (on the second and following openings) on the
Workbench screen after the PROTECT command(s) were given. In each trial, I did

** soft reboot
** apply a PROTECT command
** try opening 5.0.3.3 several times in succession.

I started out with just changing the protect bits in
WorkageStream5/UserPrefs/pageStream5.prefs
and that made no difference. Then I additionally applied the PROTECT command to
the files:

PAGESTREAM.1.prefs
PAGESTREAM.3.prefs
PAGESTREAM.2.prefs

in Envarc:MUI and that made no difference. So, after several trials, it appears
that your splendid suggestion does not work here.

Cheers Don (Green Dragon)
--