PGS 5.0.4.17a and Windows XP SP3

Hi all,

Yesterday Deron asked me if could read a document I send to him.
Well, of course I can (and I did this in PGS 5.0.4.4).
But when I wanted to test this with PGS 5.0.4.17a I can open PGS but
could not open any document or open even an empty document.
PGS crashes and Windows wants to call home...

Normally I work as a user / guest on my system. So I logged in as an
administrator... and I can open any document in PGS.
Back to the user / guest privilege, and opened PGS as administrator and
PGS can open any document (also Deron's document).
So what's happened?

In the end I remembered what has changed since I 'played' with PGS
5.0.4.17a: that I installed XP Service Pack 3.
So Microsoft did change something in the (group policy?) or did
something wrong, but what?

Theo

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

.

On Thursday, June 12, 2008, at 12:02PM, "Theo Zweers&quot; < tjzwrs%40xs4all.nl">tjzwrsxs4all.nl> wrote:
&gt;Hi all,
>;
>Yesterday Deron asked me if could read a document I send to him.
>;Well, of course I can (and I did this in PGS 5.0.4.4).
>But when I wanted to test this with PGS 5.0.4.17a I can open PGS but
>could not open any document or open even an empty document.
>PGS crashes and Windows wants to call home...
>
>Normally I work as a user / guest on my system. So I logged in as an
>administrator... and I can open any document in PGS.
>;Back to the user / guest privilege, and opened PGS as administrator and
>PGS can open any document (also Deron's document).
>So what's happened?
>
&gt;In the end I remembered what has changed since I 'played' with PGS
>5.0.4.17a: that I installed XP Service Pack 3.
>So Microsoft did change something in the (group policy?) or did
>something wrong, but what?

SP3 is such a substantial roll up it is hard to say what has and has not been done. Permissions change of some sort are likely and based on your troubleshooting would seem to be at fault. I don't have WinXP (well, I do, but it is on a work-managed computer) so I can't test this directly myself, but I would try running FileMon to see what PgS is failing on. Specifically:

1. download FIleMon if you don't already have it. Perhaps from http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx though the page didn't load when I tried. Might also try http://www.microsoft.com/technet/sysinternals/processesandthreads/filemon.mspx

2. Run FileMon, make sure it is capturing data (it should by default from start)

3. Clean up the reporting. You are probably getting *lots* of data. Right click and select "Exclude". Repeat until nothing or very little is being logged

4. Start PageStream

5. Try to open a document

6. Stop FileMon capture

7. Review the results. It is unlikely to be obvious what is going wrong, but it might be visible.

8. If no luck feel free to save out the results and email them to me.

Note, for step three it would probably work cleaner to set an include filter to only capture events from PageStream but the outlined procedure is valid. It can also be dangerous (though probably accurate in this case) to assume that the failure is being generated directly by the application rather than through a proxy.

FYI: FileMon was a product of Sysinternals, a pair of esteemed Windows gurus who were absorbed by the borg -- there is no reason to try and download FileMon (or any other sysinternals tool) from a different location as it is now a Microsoft product.

Tim Doty

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

.

Theo Zweers wrote:
&gt; Hi all,
>;
> Yesterday Deron asked me if could read a document I send to him.
>; Well, of course I can (and I did this in PGS 5.0.4.4).
> But when I wanted to test this with PGS 5.0.4.17a I can open PGS but
> could not open any document or open even an empty document.
> PGS crashes and Windows wants to call home...
>
> Normally I work as a user / guest on my system. So I logged in as an
> administrator... and I can open any document in PGS.
>; Back to the user / guest privilege, and opened PGS as administrator and
> PGS can open any document (also Deron's document).
> So what's happened?
>
> In the end I remembered what has changed since I 'played' with PGS
> 5.0.4.17a: that I installed XP Service Pack 3.
> So Microsoft did change something in the (group policy?) or did
> something wrong, but what?

Some people are having `major issues` with SP3! My grandson in his last
month of his first year at uni totalled his system by
downloading/installing SP3 - nearly cost him his whole year`s work!

:-(

Apparently the SP2 `feature` that some users suffered (masses of
spurious additions to registry, causing drivers to fail) happens on some
systems.

Be vewy, vewy careful with SP3.

:-(

--
Tony Cooke
http://myweb.tiscali.co.uk/tonyandgillcooke/
Boycott meat - suck your thumb.

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

.

Tim Doty wrote:
&gt; On Thursday, June 12, 2008, at 12:02PM, "Theo Zweers&quot; < tjzwrs%40xs4all.nl">tjzwrsxs4all.nl> wrote:
&gt;
>>; Hi all,
>;>
>;> Yesterday Deron asked me if could read a document I send to him.
>;> Well, of course I can (and I did this in PGS 5.0.4.4).
>> But when I wanted to test this with PGS 5.0.4.17a I can open PGS but
>>; could not open any document or open even an empty document.
>> PGS crashes and Windows wants to call home...
>>
>> Normally I work as a user / guest on my system. So I logged in as an
>>; administrator... and I can open any document in PGS.
>;> Back to the user / guest privilege, and opened PGS as administrator and
>>; PGS can open any document (also Deron's document).
>> So what's happened?
>>
>> In the end I remembered what has changed since I 'played' with PGS
>>; 5.0.4.17a: that I installed XP Service Pack 3.
>&gt; So Microsoft did change something in the (group policy?) or did
>>; something wrong, but what?
&gt;>
>
> SP3 is such a substantial roll up it is hard to say what has and has not been done. Permissions change of some sort are likely and based on your troubleshooting would seem to be at fault. I don't have WinXP (well, I do, but it is on a work-managed computer) so I can't test this directly myself, but I would try running FileMon to see what PgS is failing on. Specifically:
>
> 1. download FIleMon if you don't already have it. Perhaps from http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx though the page didn't load when I tried. Might also try http://www.microsoft.com/technet/sysinternals/processesandthreads/filemon.mspx
>
Because the name changed to Process Monitor. I've downloaded it.

&gt; 2. Run FileMon, make sure it is capturing data (it should by default from start)
&gt;
> 3. Clean up the reporting. You are probably getting *lots* of data. Right click and select "Exclude". Repeat until nothing or very little is being logged
&gt;
> 4. Start PageStream
>
&gt; 5. Try to open a document
>
>; 6. Stop FileMon capture
>
> 7. Review the results. It is unlikely to be obvious what is going wrong, but it might be visible.
>
>; 8. If no luck feel free to save out the results and email them to me.
>

Hmm, I do this privately.
> Note, for step three it would probably work cleaner to set an include filter to only capture events from PageStream but the outlined procedure is valid. It can also be dangerous (though probably accurate in this case) to assume that the failure is being generated directly by the application rather than through a proxy.
&gt;
> FYI: FileMon was a product of Sysinternals, a pair of esteemed Windows gurus who were absorbed by the borg -- there is no reason to try and download FileMon (or any other sysinternals tool) from a different location as it is now a Microsoft product.
>
>; Tim Doty
>;

Thanks Tim.

Theo

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

.

Tony Cooke wrote:
&gt; Theo Zweers wrote:
&gt;
>>; Hi all,
>;>
>;> Yesterday Deron asked me if could read a document I send to him.
>;> Well, of course I can (and I did this in PGS 5.0.4.4).
>> But when I wanted to test this with PGS 5.0.4.17a I can open PGS but
>>; could not open any document or open even an empty document.
>> PGS crashes and Windows wants to call home...
>>
>> Normally I work as a user / guest on my system. So I logged in as an
>>; administrator... and I can open any document in PGS.
>;> Back to the user / guest privilege, and opened PGS as administrator and
>>; PGS can open any document (also Deron's document).
>> So what's happened?
>>
>> In the end I remembered what has changed since I 'played' with PGS
>>; 5.0.4.17a: that I installed XP Service Pack 3.
>&gt; So Microsoft did change something in the (group policy?) or did
>>; something wrong, but what?
&gt;>
>
> Some people are having `major issues` with SP3! My grandson in his last
> month of his first year at uni totalled his system by
> downloading/installing SP3 - nearly cost him his whole year`s work!
&gt;
> :-(
>
> Apparently the SP2 `feature` that some users suffered (masses of
> spurious additions to registry, causing drivers to fail) happens on some
> systems.
>
>; Be vewy, vewy careful with SP3.
>;
> :-(
>

This is the first problem with SP 3 since I have (a week) it. And the
problem could be PGS also.
Deron is trying to get things easier for any user on the same computer.
And this does not work in one go.

Yes I am vewy careful with new installations, even with PGS.

Thanks Tony.

Theo

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

.

On Friday, June 13, 2008, at 06:24AM, "Theo Zweers&quot; < tjzwrs%40xs4all.nl">tjzwrsxs4all.nl> wrote:
&gt;Tim Doty wrote:
&gt;> On Thursday, June 12, 2008, at 12:02PM, "Theo Zweers&quot; < tjzwrs%40xs4all.nl">tjzwrsxs4all.nl> wrote:
&gt;>
>>;> Hi all,
>;>>
>>&gt; Yesterday Deron asked me if could read a document I send to him.
>;>> Well, of course I can (and I did this in PGS 5.0.4.4).
>>&gt; But when I wanted to test this with PGS 5.0.4.17a I can open PGS but
>>;> could not open any document or open even an empty document.
>>&gt; PGS crashes and Windows wants to call home...
>>>;
>>;> Normally I work as a user / guest on my system. So I logged in as an
>>;> administrator... and I can open any document in PGS.
>;>> Back to the user / guest privilege, and opened PGS as administrator and
>>;> PGS can open any document (also Deron's document).
>>> So what's happened?
>>&gt;
>&gt;> In the end I remembered what has changed since I 'played' with PGS
>>;> 5.0.4.17a: that I installed XP Service Pack 3.
>&gt;> So Microsoft did change something in the (group policy?) or did
>>;> something wrong, but what?
&gt;>>
>>;
>>; SP3 is such a substantial roll up it is hard to say what has and has not been done. Permissions change of some sort are likely and based on your troubleshooting would seem to be at fault. I don't have WinXP (well, I do, but it is on a work-managed computer) so I can't test this directly myself, but I would try running FileMon to see what PgS is failing on. Specifically:
>&gt;
>&gt; 1. download FIleMon if you don't already have it. Perhaps from http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx though the page didn't load when I tried. Might also try http://www.microsoft.com/technet/sysinternals/processesandthreads/filemon.mspx
>>
>Because the name changed to Process Monitor. I've downloaded it.

No, process monitor is different. FileMon tracks access to the file system. Two entirely different programs.

Tim DOty

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

.

Hi Theo,

On Friday 13 June 2008, Theo Zweers wrote:
&gt; Tim Doty wrote:
&gt; > On Thursday, June 12, 2008, at 12:02PM, "Theo Zweers&quot; < tjzwrs%40xs4all.nl">tjzwrsxs4all.nl>
wrote:
> >> Hi all,
>; >>
> >> Yesterday Deron asked me if could read a document I send to him.
>; >> Well, of course I can (and I did this in PGS 5.0.4.4).
> >> But when I wanted to test this with PGS 5.0.4.17a I can open PGS but
> >> could not open any document or open even an empty document.
> >> PGS crashes and Windows wants to call home...
> >>
> >> Normally I work as a user / guest on my system. So I logged in as an
> >> administrator... and I can open any document in PGS.
>; >> Back to the user / guest privilege, and opened PGS as administrator and
> >> PGS can open any document (also Deron's document).
> >> So what's happened?
> >>
> >> In the end I remembered what has changed since I 'played' with PGS
> >> 5.0.4.17a: that I installed XP Service Pack 3.
> >> So Microsoft did change something in the (group policy?) or did
> >> something wrong, but what?

Comparing the log files I found that your user settings are different between
the two accounts (admin and normal user). For example, Application
DataPageStream5PageStream5 kleuren did not exist in the admin user settings
and PgS was unable to find it to load. This might have some bearing.

Also, are you running PgS in "compatability mode"? If so are you doing it both
times (admin and non-admin)?

I didn't see you trying to open a file. What was the file path? Though it
probably won't make any difference it will help me determine that.

My first recommendation to narrowing things down would be to rename C:
Documents and SettingsTheo ZweersApplication DataPageStream5 to something
else, perhaps PageStream5-old and then try running PgS again and opening the
document. If that "fixes" things we've got a much smaller set of things to
look at.

Tim

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

.

Tim Doty wrote:
&gt; Hi Theo,
&gt;
> On Friday 13 June 2008, Theo Zweers wrote:
&gt;
>>; Tim Doty wrote:
&gt;>
>>;> On Thursday, June 12, 2008, at 12:02PM, "Theo Zweers&quot; < tjzwrs%40xs4all.nl">tjzwrsxs4all.nl>
>>;>
> wrote:
&gt;
>>;>> Hi all,
>;>>&gt;
>&gt;>> Yesterday Deron asked me if could read a document I send to him.
>;>>&gt; Well, of course I can (and I did this in PGS 5.0.4.4).
>>&gt;> But when I wanted to test this with PGS 5.0.4.17a I can open PGS but
>>>>; could not open any document or open even an empty document.
>>&gt;> PGS crashes and Windows wants to call home...
>>>;>
>;>>&gt; Normally I work as a user / guest on my system. So I logged in as an
>&gt;>> administrator... and I can open any document in PGS.
>;>>&gt; Back to the user / guest privilege, and opened PGS as administrator and
>>>>; PGS can open any document (also Deron's document).
>>>> So what's happened?
>>&gt;>
&gt;>>> In the end I remembered what has changed since I 'played' with PGS
>>>>; 5.0.4.17a: that I installed XP Service Pack 3.
>&gt;>> So Microsoft did change something in the (group policy?) or did
>>>>; something wrong, but what?
&gt;>>&gt;
>
> Comparing the log files I found that your user settings are different between
> the two accounts (admin and normal user). For example, Application
> DataPageStream5PageStream5 kleuren did not exist in the admin user settings
> and PgS was unable to find it to load. This might have some bearing.
>
>; Also, are you running PgS in "compatability mode"? If so are you doing it both
> times (admin and non-admin)?
>
> I didn't see you trying to open a file. What was the file path? Though it
> probably won't make any difference it will help me determine that.
&gt;

!!!!

> My first recommendation to narrowing things down would be to rename C:
> Documents and SettingsTheo ZweersApplication DataPageStream5 to something
> else, perhaps PageStream5-old and then try running PgS again and opening the
> document. If that "fixes" things we've got a much smaller set of things to
> look at.
>
> Tim
>

This did the trick!
When I had a new Documents and Settings folder, PGS can open a new
document and opens other documents.
What is wrong with PageStream5.ini, I don't know at this moment.

Anyway:
Not Derons fault.
Not XP SP3 fault either.

Who or what did it?
Me?!
PGS?!
XP?!

Thanks (again) Tim!

The O

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

.

On Jun 14, 2008, at 10:12 AM, Theo Zweers wrote:
&gt; This did the trick!
&gt; When I had a new Documents and Settings folder, PGS can open a new
> document and opens other documents.
> What is wrong with PageStream5.ini, I don't know at this moment.
>
> Anyway:
> Not Derons fault.
&gt; Not XP SP3 fault either.
>
> Who or what did it?
>

My guess is the "PageStream5 kleuren&quot; file. Is that Dutch for
"colors"? Maybe a definition PgS doesn't like? When you create a new
document PgS inserts default colors so that might have some bearing.

Tim

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

.

Tim Doty wrote:
&gt; On Jun 14, 2008, at 10:12 AM, Theo Zweers wrote:
&gt;
>>; This did the trick!
&gt;> When I had a new Documents and Settings folder, PGS can open a new
>> document and opens other documents.
>> What is wrong with PageStream5.ini, I don't know at this moment.
>>
>> Anyway:
>> Not Derons fault.
&gt;> Not XP SP3 fault either.
>>
>> Who or what did it?
>>
>>
>
> My guess is the "PageStream5 kleuren&quot; file. Is that Dutch for
> "colors"? Maybe a definition PgS doesn't like? When you create a new
> document PgS inserts default colors so that might have some bearing.
>
>; Tim
>

Please wait a moment!!!
I'm still busy with the other e-mail for you privately (I hope).
And yes: kleuren is colors. Good guess!

The O

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

.