Hi Paul,

I know it can happen. As I said: I haven't seen this behavior for years now.
I hoping that someone could lay a hand on this: 'I did that and that is
what's happening. And I can do this over and over again.'

Just guessing from my experience: did this happen after a crash with
intensive drawing in PGS? Or was it a couple of redo's that did the trick?
I must say that I am careful with redo's.
My guess is that PGS rewrites the .ini file while it's crashing.

I think you could do this without the reboot of the computer! Only
replacing the .ini/.prefs file does the trick (that's the only place a
starting PGS is looking for. Also PGS writes to the .ini/.prefs file
while it's closing. The only times when those files are looked into, I
think).
In fact, you only have to replace the values of the document window with
the correct figures in the .ini/.prefs text (!) document:
SETWINDOWDEFAULTS AT (for me: SETWINDOWDEFAULTS AT 37 0 SIZE 1027 987,
where 37 and 0 tells PGS where to start the left-top position of the
document window, and 1027 987 the size (width en height) of that
document window).

Look at:http://www.pagestream.org/?action=Documents&id=610 or
http://www.pagestream.org/?action=Documents&id=611

Theo

Op 27-4-2013 23:38, Paul Zager schreef:
> Hi Theo,
>
>> And, what do you do to keep that problem. Meaning: I haven't seen this
>> in years. And I use PGS daily (almost) on Windows 7 (see below!).
>> Keeping my fingers crossed.
>>
>> Theo
> Coincidentally, this just happened to me (again) on one of my Windoze 7
> machines. It's happened so many times, that I now keep an extra copy of
> pagestream.ini on a separate partition on that computer.
>
> It also takes a full reboot of the computer after changing to a good copy of
> pagestream.ini.
>
> Paul
>
>

--
PageStream Pro 5.0.5.8 on Windows 7 Home Premium 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0 (all 32 bits, unless stated otherwise)
AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM

Hi Derron,

It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.

What would be wrong to affect both machines?\

Sorry about not starting another thread, could not find the forums

Barry

On 04272013--, at 11:45 PM, Theo Zweers <tjzwrs@gmail.com> wrote:

> Hi Paul,
>
> I know it can happen. As I said: I haven't seen this behavior for years now.
> I hoping that someone could lay a hand on this: 'I did that and that is
> what's happening. And I can do this over and over again.'
>
> Just guessing from my experience: did this happen after a crash with
> intensive drawing in PGS? Or was it a couple of redo's that did the trick?
> I must say that I am careful with redo's.
> My guess is that PGS rewrites the .ini file while it's crashing.
>
> I think you could do this without the reboot of the computer! Only
> replacing the .ini/.prefs file does the trick (that's the only place a
> starting PGS is looking for. Also PGS writes to the .ini/.prefs file
> while it's closing. The only times when those files are looked into, I
> think).
> In fact, you only have to replace the values of the document window with
> the correct figures in the .ini/.prefs text (!) document:
> SETWINDOWDEFAULTS AT (for me: SETWINDOWDEFAULTS AT 37 0 SIZE 1027 987,
> where 37 and 0 tells PGS where to start the left-top position of the
> document window, and 1027 987 the size (width en height) of that
> document window).
>
> Look at:http://www.pagestream.org/?action=Documents&id=610 or
>http://www.pagestream.org/?action=Documents&id=611
>
> Theo
>
> Op 27-4-2013 23:38, Paul Zager schreef:
> > Hi Theo,
> >
> >> And, what do you do to keep that problem. Meaning: I haven't seen this
> >> in years. And I use PGS daily (almost) on Windows 7 (see below!).
> >> Keeping my fingers crossed.
> >>
> >> Theo
> > Coincidentally, this just happened to me (again) on one of my Windoze 7
> > machines. It's happened so many times, that I now keep an extra copy of
> > pagestream.ini on a separate partition on that computer.
> >
> > It also takes a full reboot of the computer after changing to a good copy of
> > pagestream.ini.
> >
> > Paul
> >
> >
>
> --
> PageStream Pro 5.0.5.8 on Windows 7 Home Premium 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0 (all 32 bits, unless stated otherwise)
> AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM
>
>

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

Hi,

PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
problem but obviously doesn't know how to solve it. You have to stick
with the old buggy 5.0.5.8 version.

Ingo

Am 14.05.13 01:29, schrieb Barry Moore:
>
> Hi Derron,
>
> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
>
> What would be wrong to affect both machines?\
>
> Sorry about not starting another thread, could not find the forums
>
> Barry
>
>
> On 04272013--, at 11:45 PM, Theo Zweers <tjzwrs@gmail.com> wrote:
>
>> Hi Paul,
>>
>> I know it can happen. As I said: I haven't seen this behavior for years now.
>> I hoping that someone could lay a hand on this: 'I did that and that is
>> what's happening. And I can do this over and over again.'
>>
>> Just guessing from my experience: did this happen after a crash with
>> intensive drawing in PGS? Or was it a couple of redo's that did the trick?
>> I must say that I am careful with redo's.
>> My guess is that PGS rewrites the .ini file while it's crashing.
>>
>> I think you could do this without the reboot of the computer! Only
>> replacing the .ini/.prefs file does the trick (that's the only place a
>> starting PGS is looking for. Also PGS writes to the .ini/.prefs file
>> while it's closing. The only times when those files are looked into, I
>> think).
>> In fact, you only have to replace the values of the document window with
>> the correct figures in the .ini/.prefs text (!) document:
>> SETWINDOWDEFAULTS AT (for me: SETWINDOWDEFAULTS AT 37 0 SIZE 1027 987,
>> where 37 and 0 tells PGS where to start the left-top position of the
>> document window, and 1027 987 the size (width en height) of that
>> document window).
>>
>> Look at:http://www.pagestream.org/?action=Documents&id=610 or
>>http://www.pagestream.org/?action=Documents&id=611
>>
>> Theo
>>
>> Op 27-4-2013 23:38, Paul Zager schreef:
>>> Hi Theo,
>>>
>>>> And, what do you do to keep that problem. Meaning: I haven't seen this
>>>> in years. And I use PGS daily (almost) on Windows 7 (see below!).
>>>> Keeping my fingers crossed.
>>>>
>>>> Theo
>>> Coincidentally, this just happened to me (again) on one of my Windoze 7
>>> machines. It's happened so many times, that I now keep an extra copy of
>>> pagestream.ini on a separate partition on that computer.
>>>
>>> It also takes a full reboot of the computer after changing to a good copy of
>>> pagestream.ini.
>>>
>>> Paul
>>>
>>>
>>
>> --
>> PageStream Pro 5.0.5.8 on Windows 7 Home Premium 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0 (all 32 bits, unless stated otherwise)
>> AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM
>>
>>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

--
________________________________________________________________________

skyynet i.heinicke@skyynet.de
simple solutions for a complicated world www.skyynet.de
________________________________________________________________________

Please note: PgS 5.0.5.9 *does* work at least for some, including myself. Saying that it "just doesn't work" is not accurate. It working for some and not others it what makes it difficult -- it can be difficult to figure out why something doesn't work for someone else when you can't reproduce the problem.

Tim Doty

On May 15, 2013, at 6:49 PM, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:

> Hi,
>
> PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
> problem but obviously doesn't know how to solve it. You have to stick
> with the old buggy 5.0.5.8 version.
>
> Ingo
>
> Am 14.05.13 01:29, schrieb Barry Moore:
>>
>> Hi Derron,
>>
>> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
>>
>> What would be wrong to affect both machines?\
>>
>> Sorry about not starting another thread, could not find the forums
>>
>> Barry
>>
>>
>> On 04272013--, at 11:45 PM, Theo Zweers <tjzwrs@gmail.com> wrote:
>>
>>> Hi Paul,
>>>
>>> I know it can happen. As I said: I haven't seen this behavior for years now.
>>> I hoping that someone could lay a hand on this: 'I did that and that is
>>> what's happening. And I can do this over and over again.'
>>>
>>> Just guessing from my experience: did this happen after a crash with
>>> intensive drawing in PGS? Or was it a couple of redo's that did the trick?
>>> I must say that I am careful with redo's.
>>> My guess is that PGS rewrites the .ini file while it's crashing.
>>>
>>> I think you could do this without the reboot of the computer! Only
>>> replacing the .ini/.prefs file does the trick (that's the only place a
>>> starting PGS is looking for. Also PGS writes to the .ini/.prefs file
>>> while it's closing. The only times when those files are looked into, I
>>> think).
>>> In fact, you only have to replace the values of the document window with
>>> the correct figures in the .ini/.prefs text (!) document:
>>> SETWINDOWDEFAULTS AT (for me: SETWINDOWDEFAULTS AT 37 0 SIZE 1027 987,
>>> where 37 and 0 tells PGS where to start the left-top position of the
>>> document window, and 1027 987 the size (width en height) of that
>>> document window).
>>>
>>> Look at:http://www.pagestream.org/?action=Documents&id=610 or
>>>http://www.pagestream.org/?action=Documents&id=611
>>>
>>> Theo
>>>
>>> Op 27-4-2013 23:38, Paul Zager schreef:
>>>> Hi Theo,
>>>>
>>>>> And, what do you do to keep that problem. Meaning: I haven't seen this
>>>>> in years. And I use PGS daily (almost) on Windows 7 (see below!).
>>>>> Keeping my fingers crossed.
>>>>>
>>>>> Theo
>>>> Coincidentally, this just happened to me (again) on one of my Windoze 7
>>>> machines. It's happened so many times, that I now keep an extra copy of
>>>> pagestream.ini on a separate partition on that computer.
>>>>
>>>> It also takes a full reboot of the computer after changing to a good copy of
>>>> pagestream.ini.
>>>>
>>>> Paul
>>>>
>>>>
>>>
>>> --
>>> PageStream Pro 5.0.5.8 on Windows 7 Home Premium 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0 (all 32 bits, unless stated otherwise)
>>> AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM
>>>
>>>
>>
>>
>>
>> [Non-text portions of this message have been removed]
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>
>
> --
> ________________________________________________________________________
>
> skyynet i.heinicke@skyynet.de
> simple solutions for a complicated world www.skyynet.de
> ________________________________________________________________________
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Hi Tim,

Well, that makes a difference. Nice to know that pgs works for some folks. Since months. While the predecessor can't even copy&paste. I think pgs no longer works productively since the release of Mac OS X 10.8. this is not beta shareware but a commercial program. I'm happy I don't have to rely on it as then I would be lost.

I offered to help tracking down the problem e.g. with debug versions. Got one from Deron which gave no helpfull output. From my point of view it seems that nothing happens to fix a blocker in an official productivity release.

Regards,

Ingo

Am 16.05.2013 um 03:47 schrieb Tim Doty <thoromyr@mac.com>:

> Please note: PgS 5.0.5.9 *does* work at least for some, including myself. Saying that it "just doesn't work" is not accurate. It working for some and not others it what makes it difficult -- it can be difficult to figure out why something doesn't work for someone else when you can't reproduce the problem.
>
> Tim Doty
>
> On May 15, 2013, at 6:49 PM, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:
>
>> Hi,
>>
>> PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
>> problem but obviously doesn't know how to solve it. You have to stick
>> with the old buggy 5.0.5.8 version.
>>
>> Ingo
>>
>> Am 14.05.13 01:29, schrieb Barry Moore:
>>>
>>> Hi Derron,
>>>
>>> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
>>>
>>> What would be wrong to affect both machines?\
>>>
>>> Sorry about not starting another thread, could not find the forums
>>>
>>> Barry
>>>
>>>
>>> On 04272013--, at 11:45 PM, Theo Zweers <tjzwrs@gmail.com> wrote:
>>>
>>>> Hi Paul,
>>>>
>>>> I know it can happen. As I said: I haven't seen this behavior for years now.
>>>> I hoping that someone could lay a hand on this: 'I did that and that is
>>>> what's happening. And I can do this over and over again.'
>>>>
>>>> Just guessing from my experience: did this happen after a crash with
>>>> intensive drawing in PGS? Or was it a couple of redo's that did the trick?
>>>> I must say that I am careful with redo's.
>>>> My guess is that PGS rewrites the .ini file while it's crashing.
>>>>
>>>> I think you could do this without the reboot of the computer! Only
>>>> replacing the .ini/.prefs file does the trick (that's the only place a
>>>> starting PGS is looking for. Also PGS writes to the .ini/.prefs file
>>>> while it's closing. The only times when those files are looked into, I
>>>> think).
>>>> In fact, you only have to replace the values of the document window with
>>>> the correct figures in the .ini/.prefs text (!) document:
>>>> SETWINDOWDEFAULTS AT (for me: SETWINDOWDEFAULTS AT 37 0 SIZE 1027 987,
>>>> where 37 and 0 tells PGS where to start the left-top position of the
>>>> document window, and 1027 987 the size (width en height) of that
>>>> document window).
>>>>
>>>> Look at:http://www.pagestream.org/?action=Documents&id=610 or
>>>>http://www.pagestream.org/?action=Documents&id=611
>>>>
>>>> Theo
>>>>
>>>> Op 27-4-2013 23:38, Paul Zager schreef:
>>>>> Hi Theo,
>>>>>
>>>>>> And, what do you do to keep that problem. Meaning: I haven't seen this
>>>>>> in years. And I use PGS daily (almost) on Windows 7 (see below!).
>>>>>> Keeping my fingers crossed.
>>>>>>
>>>>>> Theo
>>>>> Coincidentally, this just happened to me (again) on one of my Windoze 7
>>>>> machines. It's happened so many times, that I now keep an extra copy of
>>>>> pagestream.ini on a separate partition on that computer.
>>>>>
>>>>> It also takes a full reboot of the computer after changing to a good copy of
>>>>> pagestream.ini.
>>>>>
>>>>> Paul
>>>>
>>>> --
>>>> PageStream Pro 5.0.5.8 on Windows 7 Home Premium 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0 (all 32 bits, unless stated otherwise)
>>>> AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM
>>>
>>>
>>>
>>> [Non-text portions of this message have been removed]
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Yahoo! Groups Links
>>
>>
>> --
>> ________________________________________________________________________
>>
>> skyynet i.heinicke@skyynet.de
>> simple solutions for a complicated world www.skyynet.de
>> ________________________________________________________________________
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

hhmmm i wonder if this is a simple permissions problem...deron, i take it on a mac that pgs installs like it does on any other os, no real install just kinda drop into userspace...
on a mac do you need to set permissions for something to be executable? i'm wondering if this is a possible cause..

On Wed, 15 May 2013 19:49:28 -0400, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:

> Hi,
>
> PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
> problem but obviously doesn't know how to solve it. You have to stick
> with the old buggy 5.0.5.8 version.
>
> Ingo
>
> Am 14.05.13 01:29, schrieb Barry Moore:
>>
>> Hi Derron,
>>
>> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
>>
>> What would be wrong to affect both machines?\
>>
>> Sorry about not starting another thread, could not find the forums
>>
>> Barry
>>
>>

Nope. I can install 5.0.5.9 and swap on library to the one that came with 5.0.5.8 and pgs works. The problem is not the permissions of a pgs file.

Ingo

Am 16.05.2013 um 16:31 schrieb admfubar@gmail.com:

> hhmmm i wonder if this is a simple permissions problem...deron, i take it on a mac that pgs installs like it does on any other os, no real install just kinda drop into userspace...
> on a mac do you need to set permissions for something to be executable? i'm wondering if this is a possible cause..
>
>
>
> On Wed, 15 May 2013 19:49:28 -0400, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:
>
>> Hi,
>>
>> PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
>> problem but obviously doesn't know how to solve it. You have to stick
>> with the old buggy 5.0.5.8 version.
>>
>> Ingo
>>
>> Am 14.05.13 01:29, schrieb Barry Moore:
>>>
>>> Hi Derron,
>>>
>>> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
>>>
>>> What would be wrong to affect both machines?\
>>>
>>> Sorry about not starting another thread, could not find the forums
>>>
>>> Barry
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

On May 16, 2013, at 9:31 AM, admfubar@gmail.com wrote:

> hhmmm i wonder if this is a simple permissions problem...deron, i take it on a mac that pgs installs like it does on any other os, no real install just kinda drop into userspace...
> on a mac do you need to set permissions for something to be executable? i'm wondering if this is a possible cause..

In this case it isn't the cause, but PgS is just drop where ever you want it.

FYI, the way apps work on OS X is they have a directory structure with the exe, libraries and other resources all in a directory ending with extension .app -- these are referred to as application bundles. The OS X file browser shows the application bundle as a file, not a directory, and clicking on it launches the executable. Because of the launch mechanism I don't think the permissions even matter.

One of the things Deron considered, and apparently discarded, is the idea that there's somehow a dependency that is satisfied on his system (and mine, and others for whom it works) such as developer tools. Initially it seemed plausible as I have Xcode installed, but IIRC it didn't pan out. Doesn't really make any sense, either, as the dependencies can be queried.

As far as I know the debug build run on a working vs non-working system gave no information. Nothing fails. There are no errors. The PgS process simply ends. So without an error or some sort of failure its kinda hard to figure out what to do to make it work for those where it isn't. Very strange.

When the first post in this thread showed up I'd forgotten about all of these issues or I'd have responded differently :/ Oh well.

>
> On Wed, 15 May 2013 19:49:28 -0400, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:
>
> > Hi,
> >
> > PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
> > problem but obviously doesn't know how to solve it. You have to stick
> > with the old buggy 5.0.5.8 version.
> >
> > Ingo
> >
> > Am 14.05.13 01:29, schrieb Barry Moore:
> >>
> >> Hi Derron,
> >>
> >> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
> >>
> >> What would be wrong to affect both machines?\
> >>
> >> Sorry about not starting another thread, could not find the forums
> >>
> >> Barry
> >>
> >>
>

Hi Tim,

We tracked down the problem to one library. It can't be too hard to take the working 5.0.5.8 version and replace its functions one by one from the 5.0.5.9 release and see where it stops working. Kind of brute force debugging but quite effective from my experience.

Ingo

Am 16.05.2013 um 19:17 schrieb Tim Doty <thoromyr@mac.com>:

> On May 16, 2013, at 9:31 AM, admfubar@gmail.com wrote:
>
>> hhmmm i wonder if this is a simple permissions problem...deron, i take it on a mac that pgs installs like it does on any other os, no real install just kinda drop into userspace...
>> on a mac do you need to set permissions for something to be executable? i'm wondering if this is a possible cause..
>
> In this case it isn't the cause, but PgS is just drop where ever you want it.
>
> FYI, the way apps work on OS X is they have a directory structure with the exe, libraries and other resources all in a directory ending with extension .app -- these are referred to as application bundles. The OS X file browser shows the application bundle as a file, not a directory, and clicking on it launches the executable. Because of the launch mechanism I don't think the permissions even matter.
>
> One of the things Deron considered, and apparently discarded, is the idea that there's somehow a dependency that is satisfied on his system (and mine, and others for whom it works) such as developer tools. Initially it seemed plausible as I have Xcode installed, but IIRC it didn't pan out. Doesn't really make any sense, either, as the dependencies can be queried.
>
> As far as I know the debug build run on a working vs non-working system gave no information. Nothing fails. There are no errors. The PgS process simply ends. So without an error or some sort of failure its kinda hard to figure out what to do to make it work for those where it isn't. Very strange.
>
> When the first post in this thread showed up I'd forgotten about all of these issues or I'd have responded differently :/ Oh well.
>
>
>>
>> On Wed, 15 May 2013 19:49:28 -0400, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:
>>
>>> Hi,
>>>
>>> PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
>>> problem but obviously doesn't know how to solve it. You have to stick
>>> with the old buggy 5.0.5.8 version.
>>>
>>> Ingo
>>>
>>> Am 14.05.13 01:29, schrieb Barry Moore:
>>>>
>>>> Hi Derron,
>>>>
>>>> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
>>>>
>>>> What would be wrong to affect both machines?\
>>>>
>>>> Sorry about not starting another thread, could not find the forums
>>>>
>>>> Barry
>>>>
>>>>
>>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

And?
Which library?

Theo - not that I am that curious. I have a working PGS

Op 17-5-2013 9:14, Ingo Heinicke schreef:
> Hi Tim,
>
> We tracked down the problem to one library. It can't be too hard to take the working 5.0.5.8 version and replace its functions one by one from the 5.0.5.9 release and see where it stops working. Kind of brute force debugging but quite effective from my experience.
>
> Ingo
>
> Am 16.05.2013 um 19:17 schrieb Tim Doty <thoromyr@mac.com>:
>
>> On May 16, 2013, at 9:31 AM, admfubar@gmail.com wrote:
>>
>>> hhmmm i wonder if this is a simple permissions problem...deron, i take it on a mac that pgs installs like it does on any other os, no real install just kinda drop into userspace...
>>> on a mac do you need to set permissions for something to be executable? i'm wondering if this is a possible cause..
>> In this case it isn't the cause, but PgS is just drop where ever you want it.
>>
>> FYI, the way apps work on OS X is they have a directory structure with the exe, libraries and other resources all in a directory ending with extension .app -- these are referred to as application bundles. The OS X file browser shows the application bundle as a file, not a directory, and clicking on it launches the executable. Because of the launch mechanism I don't think the permissions even matter.
>>
>> One of the things Deron considered, and apparently discarded, is the idea that there's somehow a dependency that is satisfied on his system (and mine, and others for whom it works) such as developer tools. Initially it seemed plausible as I have Xcode installed, but IIRC it didn't pan out. Doesn't really make any sense, either, as the dependencies can be queried.
>>
>> As far as I know the debug build run on a working vs non-working system gave no information. Nothing fails. There are no errors. The PgS process simply ends. So without an error or some sort of failure its kinda hard to figure out what to do to make it work for those where it isn't. Very strange.
>>
>> When the first post in this thread showed up I'd forgotten about all of these issues or I'd have responded differently :/ Oh well.
>>
>>
>>> On Wed, 15 May 2013 19:49:28 -0400, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:
>>>
>>>> Hi,
>>>>
>>>> PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
>>>> problem but obviously doesn't know how to solve it. You have to stick
>>>> with the old buggy 5.0.5.8 version.
>>>>
>>>> Ingo
>>>>
>>>> Am 14.05.13 01:29, schrieb Barry Moore:
>>>>> Hi Derron,
>>>>>
>>>>> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
>>>>>
>>>>> What would be wrong to affect both machines?\
>>>>>
>>>>> Sorry about not starting another thread, could not find the forums
>>>>>
>>>>> Barry
>>>>>
>>>>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

--
PageStream Pro 5.0.5.8 on Windows 7 Home Premium 64 bits (Dutch), Python 2.7.3 and PySide 1.1.0 (all 32 bits, unless stated otherwise)
AMD Athlon(tm) II X2 215 Processor at 2.70 GHz and 4 GB RAM

You are making an assumption that there is an errant function, and that a change in a function is responsible. Regrettably, it isn't that simple. And keep in mind that when Deron can't reproduce the problem you are experiencing the approach you suggest -- even if it were effective -- could not be done in-house.

Tim Doty

On May 17, 2013, at 2:14 AM, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:

> Hi Tim,
>
> We tracked down the problem to one library. It can't be too hard to take the working 5.0.5.8 version and replace its functions one by one from the 5.0.5.9 release and see where it stops working. Kind of brute force debugging but quite effective from my experience.
>
> Ingo
>
> Am 16.05.2013 um 19:17 schrieb Tim Doty <thoromyr@mac.com>:
>
> > On May 16, 2013, at 9:31 AM, admfubar@gmail.com wrote:
> >
> >> hhmmm i wonder if this is a simple permissions problem...deron, i take it on a mac that pgs installs like it does on any other os, no real install just kinda drop into userspace...
> >> on a mac do you need to set permissions for something to be executable? i'm wondering if this is a possible cause..
> >
> > In this case it isn't the cause, but PgS is just drop where ever you want it.
> >
> > FYI, the way apps work on OS X is they have a directory structure with the exe, libraries and other resources all in a directory ending with extension .app -- these are referred to as application bundles. The OS X file browser shows the application bundle as a file, not a directory, and clicking on it launches the executable. Because of the launch mechanism I don't think the permissions even matter.
> >
> > One of the things Deron considered, and apparently discarded, is the idea that there's somehow a dependency that is satisfied on his system (and mine, and others for whom it works) such as developer tools. Initially it seemed plausible as I have Xcode installed, but IIRC it didn't pan out. Doesn't really make any sense, either, as the dependencies can be queried.
> >
> > As far as I know the debug build run on a working vs non-working system gave no information. Nothing fails. There are no errors. The PgS process simply ends. So without an error or some sort of failure its kinda hard to figure out what to do to make it work for those where it isn't. Very strange.
> >
> > When the first post in this thread showed up I'd forgotten about all of these issues or I'd have responded differently :/ Oh well.
> >
> >
> >>
> >> On Wed, 15 May 2013 19:49:28 -0400, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:
> >>
> >>> Hi,
> >>>
> >>> PageStream 5.0.5.9 for Mac just doesn't work. Derron is aware of the
> >>> problem but obviously doesn't know how to solve it. You have to stick
> >>> with the old buggy 5.0.5.8 version.
> >>>
> >>> Ingo
> >>>
> >>> Am 14.05.13 01:29, schrieb Barry Moore:
> >>>>
> >>>> Hi Derron,
> >>>>
> >>>> It's been awhile since I've done anything DTP but when I do it's Pagestgream I use. Only the latest version I just downloaded does not launch on my iMac or MacBook Pro running 10.8.3.
> >>>>
> >>>> What would be wrong to affect both machines?\
> >>>>
> >>>> Sorry about not starting another thread, could not find the forums
> >>>>
> >>>> Barry
> >>>>
> >>>>
> >>
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
>

Hi Tim,

I just offered again my assistance. I know, that it's hard to remotely
track down a problem but what's the alternative?

Ingo

> You are making an assumption that there is an errant function, and that a change in a function is responsible. Regrettably, it isn't that simple. And keep in mind that when Deron can't reproduce the problem you are experiencing the approach you suggest -- even if it were effective -- could not be done in-house.
>
> Tim Doty
>
> On May 17, 2013, at 2:14 AM, Ingo Heinicke <I.Heinicke@skyynet.de> wrote:
>
>> Hi Tim,
>>
>> We tracked down the problem to one library. It can't be too hard to take the working 5.0.5.8 version and replace its functions one by one from the 5.0.5.9 release and see where it stops working. Kind of brute force debugging but quite effective from my experience.
>>
>> Ingo