1426
Applications / Re: Whatever happened to...
« on: February 20, 2013, 08:25:10 pm »
Hi
Thanks for your sympathies Melf.
What makes my (and others) problems with OO3 so frustrating is simply that so many other people have no problems with OO3 reliability/crashing. Even more annoying is that at the moment the Mrs is sitting at her pc - next to me - and running OO3 with no problems. She is actually designing some business cards which is 1 of those things that causes OO3 to simply disappear (as in exit) without any warning, error message or error log when I try it on my system!
Rodericks post leaves me wondering if loading DLLs into high memory will overcome those problems. I can only hope it does and offer my services as a tester - if a build of OO3 works properly on my system it will probably work on anything ;-)
However, I seem to recall that I supplied details of memory use (obtained using Thesus) which showed plenty of free shared memory space so I'm not over hopeful this will cure the problems. OTOH: I'm not that familiar with Thesus so may have misunderstood the ouput.
I do agree that Wordpro was a good package and have no doubt that it can still work well - Ben seems to have the answer to making current format docs available for use in Wordpro. It would certainly be a lot more convenient if Wordpro had the necessary filters though.
As regards font antialias: I suspect the Innotek Font Engine may have a use there. You would need to add Wordpro to the applications supported by the Font Engine in the Registry - see the Font Engine readme file for details.
Regards
Pete
Too bad to hear Pete. I have followed your long term problems with OO on news.ecomstation.com, but have never experienced them myself. On the contrary OO has proven to be quite reliable here at my end.
Thanks for your sympathies Melf.
What makes my (and others) problems with OO3 so frustrating is simply that so many other people have no problems with OO3 reliability/crashing. Even more annoying is that at the moment the Mrs is sitting at her pc - next to me - and running OO3 with no problems. She is actually designing some business cards which is 1 of those things that causes OO3 to simply disappear (as in exit) without any warning, error message or error log when I try it on my system!
Rodericks post leaves me wondering if loading DLLs into high memory will overcome those problems. I can only hope it does and offer my services as a tester - if a build of OO3 works properly on my system it will probably work on anything ;-)
However, I seem to recall that I supplied details of memory use (obtained using Thesus) which showed plenty of free shared memory space so I'm not over hopeful this will cure the problems. OTOH: I'm not that familiar with Thesus so may have misunderstood the ouput.
I do agree that Wordpro was a good package and have no doubt that it can still work well - Ben seems to have the answer to making current format docs available for use in Wordpro. It would certainly be a lot more convenient if Wordpro had the necessary filters though.
As regards font antialias: I suspect the Innotek Font Engine may have a use there. You would need to add Wordpro to the applications supported by the Font Engine in the Registry - see the Font Engine readme file for details.
Regards
Pete