Hi all:

I've been upgrading my workstn. from Win 98 to 98SE. I installed SE on a
new hard drive so that I could switch back and forth as I migrate. I'm
now permanently on the SE hard drive. The other drive in now D & E. In
PgS I do most of my work on my laptop running Win ME. I brought one of
my files from the laptop to the desktop to do some printing testing. I
discovered that I was short of fonts on the new SE installation so I
copied my fonts over but I still have troubles.

All the fonts located in the 'C:\Windows\fonts' are visible in PgS. I
now have all the same fonts in the same place as on the Laptop. The
problem is with 'C:\psfonts'. I ran AFM and it's happy with all these
fonts. PgS 5..37 doesn't see any of these postscript fonts on the
desktop, no problem on the laptop. WordPerfect sees all the fonts just
fine and identifies the problem fonts as 'T1' type.

I can't figure out what I've missed?

Peter Martin pjmartin@magma.ca

Hi,

If you still can't see these fonts on your laptop in PageStream, please do
the following:

First, put the word DEBUG in your .ini file (the one stored in UserPrefs).
When you run and then quit PageStream (you don't need to do anything but
load/quit), and it should create a file called "DisplayDebug.txt" in your
pagestream directory. Please compress that (unless it is small) and send it
to me at support@grasshopperllc.com.

I may not need it, but it wouldn't hurt, if you also ran regedit and
exported a copy of your registry. That will certainly need to be compressed
and can be mailed to me at the above address as well. If it is really big,
you can also upload it to the public ftp site (I gave directions to that
awhile ago on the main support list. I can dig it up from the archives if
you don't have it).

Deron

>Hi all:
>
>I've been upgrading my workstn. from Win 98 to 98SE. I installed SE on a
>new hard drive so that I could switch back and forth as I migrate. I'm
>now permanently on the SE hard drive. The other drive in now D & E. In
>PgS I do most of my work on my laptop running Win ME. I brought one of
>my files from the laptop to the desktop to do some printing testing. I
>discovered that I was short of fonts on the new SE installation so I
>copied my fonts over but I still have troubles.
>
>All the fonts located in the 'C:\Windows\fonts' are visible in PgS. I
>now have all the same fonts in the same place as on the Laptop. The
>problem is with 'C:\psfonts'. I ran AFM and it's happy with all these
>fonts. PgS 5..37 doesn't see any of these postscript fonts on the
>desktop, no problem on the laptop. WordPerfect sees all the fonts just
>fine and identifies the problem fonts as 'T1' type.
>
>I can't figure out what I've missed?
>
>Peter Martin pjmartin@magma.ca

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

Hello PageStream

If you recall I sent you a flie that crashrd my system and you reported that
you could not duplicate the problem. Well <Sigh> it happened again and this
time it rendered the file useless. PageStream won't even open it. I double
click on it and PgS kinda says "and your point was???" But here's what I
have observed to be a common thread. I was entering text into a, cunningly
enough, a text box and I exceeded the size of the box. I had also hit
"enter" a couple times too. I expected a problem so before trying to resize
the box, I saved the file. As soon as I tired to drag the resizing handle
the screen went blank and that as they say was that! Dead in the water. As
I said before, trying to reopen the file was futile and BTW I had to wait a
good long time for W2K to revalidate my drive. Which leads me to the really
boring points, I am using PageStream 4.1.3.7 on a 512mg, Athalon 2100+,
Windows 2000 Pro system. If you want I can send you the unopenable file,
maybe you can do something with it, but I can't. As always I apprecate your
responses and attempts to resolve these problems. Again my problem always
seems to revolve around moving oversized graphic boxes or resizing
overfilled text boxes. the results are the same, an unceremonious crash and
too often an invalidated drive and a useless file. Any help would be
appreciated. OK enough for now, I have to start scratch... again 8-/.

PS is it possible we have a memory leak here?

Regards
--
Cruising on AutoPilot |
With an Amiga ---o-o-O-o-o--- and a CoCo

Hello PageStream

I misquoted the version level I'm using, it's 4.1.6.37.

Regards
--
Cruising on AutoPilot |
With an Amiga ---o-o-O-o-o--- and a CoCo

on 9/7/2005 7:46 PM, Richard E. Crislip at rcrislip@neo.rr.com wrote:

> Hello PageStream
>
> If you recall I sent you a flie that crashrd my system and you reported that
> you could not duplicate the problem. Well <Sigh> it happened again and this
> time it rendered the file useless. PageStream won't even open it. I double
> click on it and PgS kinda says "and your point was???" But here's what I
> have observed to be a common thread. I was entering text into a, cunningly
> enough, a text box and I exceeded the size of the box. I had also hit
> "enter" a couple times too. I expected a problem so before trying to resize
> the box, I saved the file. As soon as I tired to drag the resizing handle
> the screen went blank and that as they say was that! Dead in the water. As
> I said before, trying to reopen the file was futile and BTW I had to wait a
> good long time for W2K to revalidate my drive. Which leads me to the really
> boring points, I am using PageStream 4.1.3.7 on a 512mg, Athalon 2100+,
> Windows 2000 Pro system. If you want I can send you the unopenable file,
> maybe you can do something with it, but I can't. As always I apprecate your
> responses and attempts to resolve these problems. Again my problem always
> seems to revolve around moving oversized graphic boxes or resizing
> overfilled text boxes. the results are the same, an unceremonious crash and
> too often an invalidated drive and a useless file. Any help would be
> appreciated. OK enough for now, I have to start scratch... again 8-/.
>
> PS is it possible we have a memory leak here?
>
> Regards

Hello PageStream Users,

I have occasionally had similar problems (system crashing and file becoming
unopenable) although not in precisely similar circumstances. But I am using
PGS 4.1.3.4 on a Mac G4 running Mac OS 9.2.2.

By painful trial and error I have discovered that the problem occurs only if
memory is getting tight. So now, when using PGS on a big document I make
sure to close down most other applications and since then I have not had a
problem. By the way I have 512Mb of RAM.

Many thanks,

Cheerio,

Terence Casey

Just a point of interest though OT.
I have an HTML editor that often tells me that I do not have enough memory to load a page.

I have 4 Gigabytes of RAM

Frank Taylor
Dell Dimension 8400
Pentium 4 - 3.2 GHz
Windows XP Professional - SR2
=====================================
4 GigByte RAM
=====================================
150 GByte HD in PC
120 GByte HD external on USB
HP Business inkjet 1100D printer

*********** REPLY SEPARATOR ***********

On 10/07/2005 at 07:46 Terence Casey wrote:

>> PS is it possible we have a memory leak here?
>>
>> Regards
>
>Hello PageStream Users,
>
>I have occasionally had similar problems (system crashing and file becoming
>unopenable) although not in precisely similar circumstances. But I am using
>PGS 4.1.3.4 on a Mac G4 running Mac OS 9.2.2.
>
>By painful trial and error I have discovered that the problem occurs only
>if
>memory is getting tight. So now, when using PGS on a big document I make
>sure to close down most other applications and since then I have not had a
>problem. By the way I have 512Mb of RAM.
>
>Many thanks,
>
>Cheerio,
>
>Terence Casey
>
>
>
>
>Yahoo! Groups Links
>
>
>

look in your Backups folder, in documents you may have a working version in
there

-------Original Message-------

From: Richard E. Crislip
Date: 07/09/05 22:39:19
To: PageStreamWindowsBeta@yahoogroups.com
Subject: [PageStreamWindowsBeta] Still Crashing my System After all These
years 8-/

Hello PageStream

If you recall I sent you a flie that crashrd my system and you reported that
you could not duplicate the problem. Well <Sigh> it happened again and this
time it rendered the file useless. PageStream won't even open it. I double
click on it and PgS kinda says "and your point was???" But here's what I
have observed to be a common thread. I was entering text into a, cunningly
enough, a text box and I exceeded the size of the box. I had also hit
"enter" a couple times too. I expected a problem so before trying to resize
the box, I saved the file. As soon as I tired to drag the resizing handle
the screen went blank and that as they say was that! Dead in the water. As
I said before, trying to reopen the file was futile and BTW I had to wait a
good long time for W2K to revalidate my drive. Which leads me to the really
boring points, I am using PageStream 4.1.3.7 on a 512mg, Athalon 2100+,
Windows 2000 Pro system. If you want I can send you the unopenable file,
maybe you can do something with it, but I can't. As always I apprecate your
responses and attempts to resolve these problems. Again my problem always
seems to revolve around moving oversized graphic boxes or resizing
overfilled text boxes. the results are the same, an unceremonious crash and
too often an invalidated drive and a useless file. Any help would be
appreciated. OK enough for now, I have to start scratch... again 8-/.

PS is it possible we have a memory leak here?

Regards
--
Cruising on AutoPilot |
With an Amiga ---o-o-O-o-o--- and a CoCo



Yahoo! Groups Links

Hello Frank

Thanks for the hint concerning tight memory.

On 07/10/2005, Frank Taylor wrote:
> Just a point of interest though OT.
> I have an HTML editor that often tells me that I do not have enough
> memory to load a page.
>
> I have 4 Gigabytes of RAM
>
> Frank Taylor
> Dell Dimension 8400
> Pentium 4 - 3.2 GHz
> Windows XP Professional - SR2
> =====================================
> 4 GigByte RAM
> =====================================
> 150 GByte HD in PC
> 120 GByte HD external on USB
> HP Business inkjet 1100D printer
>
> *********** REPLY SEPARATOR ***********
>
> On 10/07/2005 at 07:46 Terence Casey wrote:
>
>>> PS is it possible we have a memory leak here?
>>>
>>> Regards
>>
>>Hello PageStream Users,
>>
>>I have occasionally had similar problems (system crashing and file
>>becoming unopenable) although not in precisely similar circumstances.
>>But I am using PGS 4.1.3.4 on a Mac G4 running Mac OS 9.2.2.
>>
>>By painful trial and error I have discovered that the problem occurs
>>only if
>>memory is getting tight. So now, when using PGS on a big document I
>>make sure to close down most other applications and since then I have
>>not had a problem. By the way I have 512Mb of RAM.
>>
>>Many thanks,
>>
>>Cheerio,
>>
>>Terence Casey
>>
>>
>>
>>
>>Yahoo! Groups Links
>>
>>
>>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>> To visit your group on the web, go to:
> http://groups.yahoo.com/group/PageStreamWindowsBeta/
>
>> To unsubscribe from this group, send an email to:
> PageStreamWindowsBeta-unsubscribe@yahoogroups.com
>
>> Your use of Yahoo! Groups is subject to:
> http://docs.yahoo.com/info/terms/
>
>
>
Regards
--
Cruising on AutoPilot |
With an Amiga ---o-o-O-o-o--- and a CoCo

Hello Terence

On 07/10/2005, Terence Casey wrote:
> on 9/7/2005 7:46 PM, Richard E. Crislip at rcrislip@neo.rr.com wrote:
>
>> Hello PageStream
>>
>> If you recall I sent you a flie that crashrd my system and you
>> reported that you could not duplicate the problem. Well <Sigh> it
>> happened again and this time it rendered the file useless. PageStream
>> won't even open it. I double click on it and PgS kinda says "and your
>> point was???" But here's what I have observed to be a common thread. I
>> was entering text into a, cunningly enough, a text box and I exceeded
>> the size of the box. I had also hit "enter" a couple times too. I
>> expected a problem so before trying to resize the box, I saved the
>> file. As soon as I tired to drag the resizing handle the screen went
>> blank and that as they say was that! Dead in the water. As I said
>> before, trying to reopen the file was futile and BTW I had to wait a good
>> long time for W2K to revalidate my drive. Which leads me to the really
boring
>> points, I am using PageStream 4.1.3.7 on a 512mg, Athalon 2100+, Windows
>> 2000 Pro system. If you want I can send you the unopenable file, maybe
>> you can do something with it, but I can't. As always I apprecate your
responses
>> and attempts to resolve these problems. Again my problem always seems
>> to revolve around moving oversized graphic boxes or resizing overfilled
>> text boxes. the results are the same, an unceremonious crash and too
>> often an invalidated drive and a useless file. Any help would be
appreciated.
>> OK enough for now, I have to start scratch... again 8-/.
>
>> PS is it possible we have a memory leak here?
>>
>> Regards
>
> Hello PageStream Users,
>
> I have occasionally had similar problems (system crashing and file
> becoming unopenable) although not in precisely similar circumstances.
> But I am using PGS 4.1.3.4 on a Mac G4 running Mac OS 9.2.2.
>
> By painful trial and error I have discovered that the problem occurs
> only if memory is getting tight. So now, when using PGS on a big
> document I make sure to close down most other applications and since
> then I have not had a problem. By the way I have 512Mb of RAM.

Thanks for the tight memory idea, I'll kepp an eyeon that.

Regards
--
Cruising on AutoPilot |
With an Amiga ---o-o-O-o-o--- and a CoCo

Hello Rodney

On 07/10/2005, Rodney Lee Volkmar wrote:
> look in your Backups folder, in documents you may have a working
> version in there

Yeah... I looked in there an dit was empty. I must do something about that.

Regards
--
Cruising on AutoPilot |
With an Amiga ---o-o-O-o-o--- and a CoCo

>Hello PageStream
>
>If you recall I sent you a flie that crashrd my system and you reported that
>you could not duplicate the problem. Well <Sigh> it happened again and this
>time it rendered the file useless. PageStream won't even open it. I double
>click on it and PgS kinda says "and your point was???" But here's what I
>have observed to be a common thread. I was entering text into a, cunningly
>enough, a text box and I exceeded the size of the box. I had also hit
>"enter" a couple times too. I expected a problem so before trying to resize
>the box, I saved the file. As soon as I tired to drag the resizing handle
>the screen went blank and that as they say was that!

Have you re-tried these steps in PageStream in a new document to see if the
problem is reproducible? That would be best if you had a series of steps
that would reproduce the problem!!

>If you want I can send you the unopenable file, maybe you can do something
>with it, but I can't.

You are welcome to send the file to support@grasshopperllc.com.

>PS is it possible we have a memory leak here?

Well, that was certainly true in the versions prior to 4.1.6. I found a
system resource leak (related to opening and closing lots of requesters),
but that is fixed in the latest versions of PageStream. I'm not aware of
any other issue. I see someone else mentioned a possible problem with out
of memory, and that is always possible. Memory is allocated in thousands of
places in PageStream and it is always possible that it one of them doesn't
handle low memory properly, but resizing objects takes so very little
memory that seems odd. You might keep a system resource monitor open
while running PageStream to see if you are running out of memory? It is how
ever very unusual.

Deron

>Regards
>--
>Cruising on AutoPilot |
> With an Amiga ---o-o-O-o-o--- and a CoCo

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

on 10/7/2005 11:36 AM, Richard E. Crislip at rcrislip@neo.rr.com wrote:

> Hello Rodney
>
> On 07/10/2005, Rodney Lee Volkmar wrote:
>> look in your Backups folder, in documents you may have a working
>> version in there
>
> Yeah... I looked in there an dit was empty. I must do something about that.

-------------

Hello PGS Users,

Yes I too also have this problem.

In 'Preferences I have always ticked the following:

1. Autosave every 5 minutes

2. Keep 3 Revisions

3. Path: Documents: Backups

But nevertheless whether or not PGS makes and keeps backups seems to be a
lottery.

Sometimes when I am working I regularly see the heading 'Auto saving' at the
top of the page and I have to wait until it has finished.

At other times I can go on for hours, or even days, without ever seeing it.

I have never been able to find out what causes this change in behaviour.

If I happen to notice that PGS is not backing up I make backups myself. But
on occasions have forgotten to do this and so after a crash resulting in an
'unopenable' file I have been left with nothing which is quite a pain.

I am using PGS 4.1.3.4 on a G4 Mac running Mac OS 0.2.2.

cheerio,

Terence Casey

>Hello PGS Users,
>
>Yes I too also have this problem.
>
>In 'Preferences I have always ticked the following:
>
>1. Autosave every 5 minutes
>
>2. Keep 3 Revisions
>
>3. Path: Documents: Backups
>
>But nevertheless whether or not PGS makes and keeps backups seems to be a
>lottery.
>
>Sometimes when I am working I regularly see the heading 'Auto saving' at the
>top of the page and I have to wait until it has finished.
>
>At other times I can go on for hours, or even days, without ever seeing it.

The only thing I can think of is that it will not auto save if you are
actively working (which as I recall the threshold is any change in the last
15 seconds, but it will wait no more than 2 minutes). This was done because
of the speed of saving on older computers. I wonder now if that can not be
decreased in light of faster computers and hard drives, but still 2 extra
minutes won't make much difference.

>I have never been able to find out what causes this change in behaviour.
>
>If I happen to notice that PGS is not backing up I make backups myself. But
>on occasions have forgotten to do this and so after a crash resulting in an
>'unopenable' file I have been left with nothing which is quite a pain.

The backups occur every time a save occurs. If you don't save (or the auto
save doesn't kick in), no backups. No other reason other than a bad or full
backup path.

>I am using PGS 4.1.3.4 on a G4 Mac running Mac OS 0.2.2.
>
>cheerio,
>
>Terence Casey

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

Hello PageStream

> Have you re-tried these steps in PageStream in a new document to see if
> the problem is reproducible? That would be best if you had a series of
> steps that would reproduce the problem!!

>
> Well, that was certainly true in the versions prior to 4.1.6. I found a
> system resource leak (related to opening and closing lots of
> requesters), but that is fixed in the latest versions of PageStream.
> I'm not aware of any other issue. I see someone else mentioned a
> possible problem with out of memory, and that is always possible.
> Memory is allocated in thousands of places in PageStream and it is
> always possible that it one of them doesn't handle low memory
> properly, but resizing objects takes so very little memory that seems
> odd. You might keep a system resource monitor open while running
> PageStream to see if you are running out of memory? It is how ever
> very unusual.

I watched my memory usage via the System Task (is that what you meant by
System Resource Monitor) tool and My usage never exceeded 198mg out of the
512mg i have installed. I suggested a memory leak because I can see PgS
crashing, but it should not take the Windows OS with it. So it seems to me
that something important got stumped on. Is there a debugging version or
someway I can log this problem? I can reproduce this far too often on this
system. The frustrating part of it is that it doesn't happen EVERY time.
Just often enough to make me grit my teeth .

Regards
--
Cruising on AutoPilot |
With an Amiga ---o-o-O-o-o--- and a CoCo

Hello Deron,

I have only been using PGS since January 1993 (on an Atari) so I'm a
relative new boy. But I congratulate Deron on persistently keeping up the
technical development of this wonderful programme over so many changes in
platforms and operating systems.

It is quite the best I have seen!

Keep it up Deron!

We may whinge from time to time but we still love you!

Many thanks,

Cheerio,

Terence Casey