Well, the good news is that today, after the computer had been on for most of the morning with various programs running (e.g. Firefox, Thunderbird, Skype, Chrome, though no "Office 2013" or "LibreOffice 5.0" programs which I frequently use) I started up PageSTream and it happily opened two recently opened files, one after another.  I tend to write it "PageSTream" in memory of the Atari, but I know that the official name is "PageStream".

Googling "IFF CTXT filter" comes up with several PageStream documentation items dated 2006.  So, it looks as if this "intermittent problem" has been around for 10 years.

Why powering down and then up should make any difference is, for me, rather hard to imagine.  It looks as if PageStream is expecting something to be running and, if it is not, it just throws in the towel.  What I would expect is PageStream to see if something is running and , if not, to tell it to start running, wait till it is running and then continue as if nothing had happened.  Why whatever it is should be running after powering down and then up again is completely unclear to me.

I can only suppose that life is not as simple as that or Deron would have fixed it years ago.

As far as the printing is concerned I have not even looked at it since being in Toronto.  We are leaving for the UK again next Wednesday.

Another question is where is PageStream best installed ?  I do not remember choosing where to install it under Windows 7 Ultimate.  It was installed in "C:\Users\T M N Irish\Documents\PageSTream5.0.5.8\PageStream5.exe" and put its various folders in "C:\Users\T M N Irish\".  It is conceivable that it might be better for it to be installed in "C:\Program Files (x86)\" if only because, at present, Windows 10 Pro does not consider it worthy to be included in "Programs and Features".

I have just tried to print an existing document.  Nothing.  But worse than that, I fear there are problems with the keyboard and display under Windows 10.

I have just set PageStream5.exe Properties, Compatibility, Run this program in compatibility mode for Windows 7, Disable display scaling on high DPI settings, Run this program as an administrator.  This lot seems to be better as far as the keyboard and display are concerned.

-- 
Michael  Irish  ن
ن
The digital certificate signing this email is attached to
my Sent-From ISP email address:- irish274@btinternet.com
and NOT to any one of
my permanent Reply-To email address:- T.M.N.Irish@bcs.org.uk
my Google email address:- t.m.n.irish@gmail.com
or my CAB email address:- michaeli@whcab.org.uk

> Googling "IFF CTXT filter" comes up with several PageStream
> documentation items dated 2006. So, it looks as if this "intermittent
> problem" has been around for 10 years.
>

Those documents contain the description of IFF CTXT, which is the file
format used by PageStream to store formatted text.

The first report is from Theo back in 2011, and is documented here in
the bug tracker:http://www.pagestream.org/?action=Bug Tracker&id=317

Still, as he reports then and still true now " a problem which I can't
put a finger on"

>
> Why powering down and then up should make any difference is, for me,
> rather hard to imagine.
>

Why?

Near as I can tell, something (previous run of PageStream?) has left the
IFFCTXT.tfilter (and possibly others) locked and the OS does not release
that lock until the system is rebooted.

Deron

> --
> Michael Irish ن
> ن

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

[..]
Why powering down and then up should make any difference is, for me, 
rather hard to imagine.

Why?




Near as I can tell, something (previous run of PageStream?) has left the 
IFFCTXT.tfilter (and possibly others) locked and the OS does not release 
that lock until the system is rebooted.




Deron

-- 
Redacteur, illustrator bij Ligfiets.net

On 4/29/16 1:22 AM, Theo Zweers tjzwrs@gmail.com [PageStreamSupport] wrote:
>
> Op 29-4-2016 om 03:11 schreef PageStream Support deron@pagestream.org
> [PageStreamSupport]:
>> Why?
>>
>> Near as I can tell, something (previous run of PageStream?) has left the
>> IFFCTXT.tfilter (and possibly others) locked and the OS does not release
>> that lock until the system is rebooted.
>>
>> Deron
>
> Yes, this is likely.
> But, there is always a but, why can I, when I close 5.0.5.8, start
> 5.0.5.7... and PGS is working.

Well, a file lock is on a specific file. Not all similar named files!
5.0.5.8 would have a copy in its SoftLogik/Filters folder, and 5.0.5.7
has a different copy in its own SoftLogik/Filters folder.

Assuming that something is causing the file to not be unlocked, then if
you had previously made two copies of 5.0.5.8, when one refused to load
then the second one would still load.

This is all conjecture, but a fairly educated one.

Microsoft has a command line tool that will list locked files. Here is a
discussion on it:
http://stackoverflow.com/questions/241178/command-line-tool-for-finding-out-who-is-locking-a-file

Might help narrow down if that is really what is going on.

Deron

> What is the main difference between version .7 and .8? Does .7 ignores
> the former IFF filters (from ., or does it start its own filters?
> I can, on Windows, close PGS if it stays in memory after I closed it,
> or PGS crashed (with Task Manager). But can I find those filters in
> memory if PGS fails to load something (must be easy because otherwise
> I loose interest soon Lots of other things to do)?
>
> Theo - not suggesting that this is THE answer

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