5.0.4.3 Windows beta crashes upon open

Hello PageStreamSupport,

Both of the beta versions, pro and regular, crash as soon as they try to
open. I did get past the registration screens and that was it.

The only thing I get is "Windows has encountered an error and needs to
close" or whatever that error is.

--
Regards,
Billy
Video Image Productions http://www.vipvideo.com
Hattiesburg, MS
(601) 544-TAPE (8273)

Messages in this topic (1) Reply (via web post) | Start a new topic

.

I had the same issue. I discovered that Pagestream does not like the
desktop. When I moved the file to my c drive, the crash issue with
opening went away.

I tried to make a PDF file and the program crashed. Also, I briefly
played with tables and it seems more stable in that regard.

Peter

Billy Horton wrote:
>
> Hello PageStreamSupport,
>
> Both of the beta versions, pro and regular, crash as soon as they try to
> open. I did get past the registration screens and that was it.
>
> The only thing I get is "Windows has encountered an error and needs to
> close"; or whatever that error is.
>
> --
> Regards,
> Billy
&gt; Video Image Productions http://www.vipvideo.com <http://www.vipvideo.com>
> Hattiesburg, MS
> (601) 544-TAPE (8273)
&gt;
>

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

Messages in this topic (0) Reply (via web post) | Start a new topic

.

Hi,
...When I moved the file...
which file (or folder???) do you mean?
Frank Baudermann

Peter Bullock schrieb:
>
>; I had the same issue. I discovered that Pagestream does not like the
> desktop. When I moved the file to my c drive, the crash issue with
>; opening went away.
&gt;
> I tried to make a PDF file and the program crashed. Also, I briefly
> played with tables and it seems more stable in that regard.
>
> Peter
&gt;
> Billy Horton wrote:
&gt; >
>; > Hello PageStreamSupport,
> >
>; > Both of the beta versions, pro and regular, crash as soon as they try to
> > open. I did get past the registration screens and that was it.
> >
>; > The only thing I get is "Windows has encountered an error and needs to
> > close"; or whatever that error is.
> >
>; > --
> > Regards,
> > Billy
&gt; > Video Image Productions http://www.vipvideo.com
> <http://www.vipvideo.com> <http://www.vipvideo.com
> <http://www.vipvideo.com>>;
> > Hattiesburg, MS
> > (601) 544-TAPE (8273)
&gt; >
>; >
>;
> [Non-text portions of this message have been removed]
>
>;

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

Messages in this topic (0) Reply (via web post) | Start a new topic

.

On Friday 07 September 2007, Billy Horton wrote:
&gt; Hello PageStreamSupport,
>
> Both of the beta versions, pro and regular, crash as soon as they try to
> open. I did get past the registration screens and that was it.
>
> The only thing I get is "Windows has encountered an error and needs to
> close"; or whatever that error is.

And that is what I get trying to print. Not that I have ever had luck printing
from PgS windows to my networked printer -- at least some part of which is my
fault (insistence on using Win2k which doesn't have proper support for IPP,
and refusing to setup samba print sharing).

Anyway, looking through the readme I noticed a problem:

one of the new mnemonics is:

ctrl-d |= for the lira (substitute to pound if not present). This may be a
typo in the readme (it is followed by another mnemonic for lira), but that
mnemonic historically and currently produces a double dagger.

On the other hand I'm please for all the new short cuts (arrows, double
arrows, equality aw well as the autoligatures for !!, ??, ?! and !?. However
the mnemonics for ?! and !? are broken? They refer to 2048 and 2048
respectively, but this does not produce the characters in question (though
the auto-ligature does).

The PDF export does have the new font embedding options. Unfortunately if
there is any text in the document PgS crashes when saving the PDF.

Regrettably I lack time at the moment to continue checking but at present it
looks like the mixed bag you'd expect from a beta.

Tim Doty

Messages in this topic (0) Reply (via web post) | Start a new topic

.

Hello Tim,

Friday, September 7, 2007, 12:10:34 PM, you wrote:

> And that is what I get trying to print. Not that I have ever had luck printing
> from PgS windows to my networked printer -- at least some part of which is my
> fault (insistence on using Win2k which doesn't have proper support for IPP,
>; and refusing to setup samba print sharing).

That's the main reason I wanted to try the beta, and I get the same
results as you. I can't even use PgS like I want because it won't print to
our laser printer, which is on a network. I've had to replace PgS with
other programs that will print normally.

So sad to see it get such little use around here.

--
Regards,
Billy
Video Image Productions http://www.vipvideo.com
Hattiesburg, MS
(601) 544-TAPE (8273)

Messages in this topic (0) Reply (via web post) | Start a new topic

.

> Anyway, looking through the readme I noticed a problem:
>
>; one of the new mnemonics is:
>
> ctrl-d |= for the lira (substitute to pound if not present). This may be a
> typo in the readme (it is followed by another mnemonic for lira), but that
> mnemonic historically and currently produces a double dagger.
>
Actually, the readme (and the source, i checked), is using lowercase-L
and uppercase-L = for lira. That is small-l not a vertical bar-|. No
conflict!

>; On the other hand I'm please for all the new short cuts (arrows, double
> arrows, equality aw well as the autoligatures for !!, ??, ?! and !?. However
> the mnemonics for ?! and !? are broken? They refer to 2048 and 2048
> respectively, but this does not produce the characters in question (though
> the auto-ligature does).
&gt;
Well, it worked for me using DejaVu Sans Book. At no time did ligatures
work and mnemonics didn't. Are you sure you had the ligature? It
_should_, but doesn't always, sense that the ligature doesn't exist and
simply display the two (or three) characters.
> The PDF export does have the new font embedding options. Unfortunately if
> there is any text in the document PgS crashes when saving the PDF.
>;
Hmm. I know it worked when I wrote the code. I'll play with it.
> Regrettably I lack time at the moment to continue checking but at present it
> looks like the mixed bag you'd expect from a beta.
&gt;
No problem. A appreciate all the feedback. I just need to find my
printers and cables so I can work on Windows printing...
> Tim Doty
>;
Deron

--
Deron Kazmaier - support%40pagestream.org">supportpagestream.org
Grasshopper LLC Publishing - http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

Messages in this topic (0) Reply (via web post) | Start a new topic

.

On Friday 07 September 2007, PageStream Support wrote:
&gt; > Anyway, looking through the readme I noticed a problem:
> >
>; > one of the new mnemonics is:
> >
>; > ctrl-d |= for the lira (substitute to pound if not present). This may be
> > a typo in the readme (it is followed by another mnemonic for lira), but
> > that mnemonic historically and currently produces a double dagger.
>
> Actually, the readme (and the source, i checked), is using lowercase-L
> and uppercase-L = for lira. That is small-l not a vertical bar-|. No
> conflict!

Good! That's what I get for not copying and pasting!

> > On the other hand I'm please for all the new short cuts (arrows, double
&gt; > arrows, equality aw well as the autoligatures for !!, ??, ?! and !?.
> > However the mnemonics for ?! and !? are broken? They refer to 2048 and
> > 2048 respectively, but this does not produce the characters in question
> > (though the auto-ligature does).
&gt;
> Well, it worked for me using DejaVu Sans Book. At no time did ligatures
> work and mnemonics didn't. Are you sure you had the ligature? It
> _should_, but doesn't always, sense that the ligature doesn't exist and
> simply display the two (or three) characters.

Well, with PgS seamless handling of ligatures that is always an issue. What I
did was magnify the view so that I could clearly distinguish spacing and it
was definitely grouping the pairs closer. I haven't turned autoligatures off
yet to compare but I didn't see the need to as the difference was distinct.

> > The PDF export does have the new font embedding options. Unfortunately if
> > there is any text in the document PgS crashes when saving the PDF.
>;
> Hmm. I know it worked when I wrote the code. I'll play with it.

Although my first test was with a real document all it took to reproduce was:

new document, draw line, save as pdf -> this works
add an empty frameless text object, save as pdf -> this works
add one character to the frameless text object, save as pdf -> crash

text was set in arial. same results wrt crash no matter which of the three
font options was chosen (none/all/all-but-14)

> > Regrettably I lack time at the moment to continue checking but at present
> > it looks like the mixed bag you'd expect from a beta.
&gt;
> No problem. A appreciate all the feedback. I just need to find my
> printers and cables so I can work on Windows printing...

And one of these days maybe I'll bend and configure a remote lpr queue or
samba and setup Win2K accordingly. I strongly suspect that my problem is
caused by PgS being more sensitive than other applications. Win2K only has
broken/incomplete IPP support. Getting it to work for *any* application is a
lot of trouble and the steps are not always reproducible...

Tim Doty

Messages in this topic (0) Reply (via web post) | Start a new topic

.

On Friday 07 September 2007, PageStream Support wrote:
[snip]
>; > On the other hand I'm please for all the new short cuts (arrows, double
&gt; > arrows, equality aw well as the autoligatures for !!, ??, ?! and !?.
> > However the mnemonics for ?! and !? are broken? They refer to 2048 and
> > 2048 respectively, but this does not produce the characters in question
> > (though the auto-ligature does).
&gt;
> Well, it worked for me using DejaVu Sans Book. At no time did ligatures
> work and mnemonics didn't. Are you sure you had the ligature? It
> _should_, but doesn't always, sense that the ligature doesn't exist and
> simply display the two (or three) characters.

I just double checked with Arial, Times New Roman, and Junicode.

In a text frame I typed one line with ligatures on and beneath it, in the same
font, the same text with ligatures off.

Although Times New Roman does not have pronounced ligatures there is a
distinct difference between the two. With Junicode the difference is *very*
apparent. (Including the 'st' ligature! I'd forgotten about that one!)

So, yes, I am getting the ligatures. Next step was to have ligatures turned
off but force the ligatures by using the character mnemonics. Yep, this works
just perfectly.

Finally, I tried the 2048 and confirmed that I do not get the desired
character, but instead a y diersis. Going into the character insertion
requester this character (y diersis) starts at some point and just runs on.
As the fonts in question do not use y diersis as .notdef this must be another
bug introduced -- that does not affect ligatures only the unicode selection.

To avoid focusing on bugs I would like to say thanks for the fixed bugs and
new features added in this version.

Tim Doty

Messages in this topic (0) Reply (via web post) | Start a new topic

.

Tim Doty wrote:
&gt; On Friday 07 September 2007, PageStream Support wrote:
&gt; [snip]
&gt;
>>;> On the other hand I'm please for all the new short cuts (arrows, double
&gt;>> arrows, equality aw well as the autoligatures for !!, ??, ?! and !?.
>>> However the mnemonics for ?! and !? are broken? They refer to 2048 and
>>> 2048 respectively, but this does not produce the characters in question
>>&gt; (though the auto-ligature does).
&gt;>>
>>; Well, it worked for me using DejaVu Sans Book. At no time did ligatures
>> work and mnemonics didn't. Are you sure you had the ligature? It
>&gt; _should_, but doesn't always, sense that the ligature doesn't exist and
>> simply display the two (or three) characters.
>>;
>
> I just double checked with Arial, Times New Roman, and Junicode.
>
&gt; In a text frame I typed one line with ligatures on and beneath it, in the same
> font, the same text with ligatures off.
>;
> Although Times New Roman does not have pronounced ligatures there is a
> distinct difference between the two. With Junicode the difference is *very*
> apparent. (Including the 'st' ligature! I'd forgotten about that one!)
&gt;
> So, yes, I am getting the ligatures. Next step was to have ligatures turned
> off but force the ligatures by using the character mnemonics. Yep, this works
> just perfectly.
>
&gt; Finally, I tried the 2048 and confirmed that I do not get the desired
> character, but instead a y diersis. Going into the character insertion
> requester this character (y diersis) starts at some point and just runs on.
> As the fonts in question do not use y diersis as .notdef this must be another
> bug introduced -- that does not affect ligatures only the unicode selection.
>
&gt; To avoid focusing on bugs I would like to say thanks for the fixed bugs and
> new features added in this version.
>
>; Tim Doty
>;
>
Using Junicode, I had no problem inserting the control-d ?! and
control-d !? producing the same ligature. Same for st, fi, ffi, fl ffl.
Also tested the lyra as well with this font. All was well.

I don't know what is up with the y diersis. Could be half a dozen
things. Character encoding gets more complicated with each release in
PageStream I did see a page or so of them in the Junicode font.
Range was 768-879. Does that range mean anything to you? Does this
happen to you in the older release? (I guess it is time I got that
installed on the computer...)

Deron

--
Deron Kazmaier - support%40pagestream.org">supportpagestream.org
Grasshopper LLC Publishing - http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

Messages in this topic (0) Reply (via web post) | Start a new topic

.

On Friday 07 September 2007, PageStream Support wrote:
&gt; Tim Doty wrote:
&gt; > On Friday 07 September 2007, PageStream Support wrote:
&gt; > [snip]
&gt; >
>; >>&gt; On the other hand I'm please for all the new short cuts (arrows, double
&gt; >>&gt; arrows, equality aw well as the autoligatures for !!, ??, ?! and !?.
> >>&gt; However the mnemonics for ?! and !? are broken? They refer to 2048 and
> >>&gt; 2048 respectively, but this does not produce the characters in question
> >>&gt; (though the auto-ligature does).
&gt; >>
> >> Well, it worked for me using DejaVu Sans Book. At no time did ligatures
> >> work and mnemonics didn't. Are you sure you had the ligature? It
> >> _should_, but doesn't always, sense that the ligature doesn't exist and
> >> simply display the two (or three) characters.
> >
>; > I just double checked with Arial, Times New Roman, and Junicode.
> >
>; > In a text frame I typed one line with ligatures on and beneath it, in the
> > same font, the same text with ligatures off.
>; >
>; > Although Times New Roman does not have pronounced ligatures there is a
> > distinct difference between the two. With Junicode the difference is
> > *very* apparent. (Including the 'st' ligature! I'd forgotten about that
>; > one!)
&gt; >
>; > So, yes, I am getting the ligatures. Next step was to have ligatures
> > turned off but force the ligatures by using the character mnemonics. Yep,
>; > this works just perfectly.
> >
>; > Finally, I tried the 2048 and confirmed that I do not get the desired
> > character, but instead a y diersis. Going into the character insertion
> > requester this character (y diersis) starts at some point and just runs
>; > on. As the fonts in question do not use y diersis as .notdef this must be
> > another bug introduced -- that does not affect ligatures only the unicode
> > selection.
> >
>; > To avoid focusing on bugs I would like to say thanks for the fixed bugs
>; > and new features added in this version.
> >
>; > Tim Doty
>;
> Using Junicode, I had no problem inserting the control-d ?! and
> control-d !? producing the same ligature. Same for st, fi, ffi, fl ffl.
>; Also tested the lyra as well with this font. All was well.

Maybe I'm confused. What is the meaning of the 2048 and 2049? I assumed that
it was the unicode reference, e.g., ctrl-d 02048 and 02049?

But using ctrl-d ?! works just fine.

> I don't know what is up with the y diersis. Could be half a dozen
&gt; things. Character encoding gets more complicated with each release in
> PageStream I did see a page or so of them in the Junicode font.
&gt; Range was 768-879. Does that range mean anything to you? Does this
>; happen to you in the older release? (I guess it is time I got that
>; installed on the computer...)

With a previous version (5.0.3.4) I got the rectangle for .notdef.

Tim Doty

Messages in this topic (0) Reply (via web post) | Start a new topic

.