OS/2, eCS & ArcaOS - Technical > Applications

Whatever happened to...

<< < (2/3) > >>

Ben:

--- Quote from: melf on February 20, 2013, 02:57:47 pm ---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. However, one of the bad things with OO is that i sometimes feels a lilttle clumsy and slow and I wish it could be as light and fast as Lotus Smart Suite.
--- End quote ---

Well stated, Melf, for that has been my experience as well. However, unlike you I continue to use Lotus Smartsuite, (Word Pro), the speed and lightness of it working well with 600+ page projects... and I have a means to get around the export/import filters that LSS lacks... read on!


--- Quote from: melf on February 20, 2013, 02:57:47 pm --- If Smartsuite had updated import/export modules for the current document formats I would doubtless use it, in spite of the absent antialias.

--- End quote ---

I simply export my Word Pro document into the last form of MS Word that Word Pro supports. Then I import it into Open Office 3.* and presto! Magicko! I can then use whatever filters that OO has... of course to import into Word Pro... just reverse the procedure. :o

I hope that helps you.

Pete:
Hi


--- Quote from: melf on February 20, 2013, 02:57:47 pm ---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.

--- End quote ---


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

melf:
Hi Ben, unfortunately this doesn't work very well for me. 1) Can't always open documents from OO even if I save them as rtf. Yesterday I could open a document I had currently used "trackhanges" on and proceeded in WordPro. This worked great, but then when importing to OO again, the document was quite corrupted (from an OO-perspective ...) 2) Pictures are dealt with in another way and tables use to be strange also. I also often exchange documents with people using some of the later MSOffice and then it just become too much! So, that's why I stick to OO anyway - it complies well with MS - which most other people seem to use.

Pete: You ought to be the given test person for that new build of OO ..!  And I have tried to use Innotek Font engine on WordPro before, it hangs the application quite hard.

Sigurd Fastenrath:

--- Quote from: Roderick Klein on February 20, 2013, 03:01:01 pm ---We have an internal release ready.

We are working on trying to load the DLL's from Open office into the high memory area of OS/2. We are already having some success with Firefox.
By doing this the lower shared memory issue's with OS/2 and the associates hangs of the desktop should going away.

This is a a feature we have been trying to get in previous open office versions as the loading of these large DLL's into lower shared memory reduces the uptime of an OS/2 system.

Roderick Klein
Mensys B.V.

--- End quote ---

What should I expect with this answer?

- is there an already running Open Office 3.4 or not?
- when will it be public? (next month/year...?)
- loading the dlls in high memory - has open office to be changed for this or eCS?

That is what it makes hard to understand and follow or stay tuned: the (allways) avesive answers and non concrete informations and timetables - why can't there be an answer that is not a mystery/riddle or that is just simple?

 :-\

Roderick Klein:

--- Quote from: Sigurd Fastenrath on February 21, 2013, 10:23:54 am ---
--- Quote from: Roderick Klein on February 20, 2013, 03:01:01 pm ---We have an internal release ready.

We are working on trying to load the DLL's from Open office into the high memory area of OS/2. We are already having some success with Firefox.
By doing this the lower shared memory issue's with OS/2 and the associates hangs of the desktop should going away.

This is a a feature we have been trying to get in previous open office versions as the loading of these large DLL's into lower shared memory reduces the uptime of an OS/2 system.

Roderick Klein
Mensys B.V.

--- End quote ---

What should I expect with this answer?

- is there an already running Open Office 3.4 or not?
- when will it be public? (next month/year...?)
- loading the dlls in high memory - has open office to be changed for this or eCS?

That is what it makes hard to understand and follow or stay tuned: the (allways) avesive answers and non concrete informations and timetables - why can't there be an answer that is not a mystery/riddle or that is just simple?

 :-\

--- End quote ---

There is a 3.4 version that is receiving final internal testing. It does not yet work with loading DLL into high memory.


The source code for open office does not have be modified for this feature. When you open a word document it already uses API calls to store the dats of that document into high kernel memory (effected by the virtualaddresslimit).  However with several different tools  you can modify the DLL headers to tell the kernel what portion to also load high of the DLL's into high memory itself.
Scott Garfunkel from IBM (before he stopped working on the OS/2 kernel) put that feature in very far.

Now you can use a tool such as highmem.exe and do *.dll. Once you do that on firefox/thunderbird/openoffice DLL. It works fine, until you exit the application. Then some memory clean up code in the kernel blows up and you get a system TRAP.
(As a warning don't start experimenting these on your system unless you know what your doing and keep track of which DLL's you modify!)

We are looking at the applications to find out if we can only use a subset of DLL's to load high memory. This is already working with Firefox partly. Instead of having 150 of lower shared memory we now end up in the lab with 260 MB or more. (These figures can change). This research is being done with memory dumps, theseus and the kernel debugger. This takes time and is not realy something you can translate into a time frame.

Can this highmem stuff be fixed in the long term, yes it can and we might get a sollution for eCS 2.2. We fixed plenty of other stuff in eCS without kernel sources. Sometimes a fix is easy sometimes its down right hard. For example look at the TCPIP32DLL.DLL that would crash on SMP systems. That new DLL version (gets installed with eCS 2.2 by default and all latest ACPI versions) reduces Firefox crashes on SMP systems. But it did take time to get it done.

If we don't make it then Open Office 3.4 will  be released with eCS 2.2 without the high load option with eCS 2.2 in the second week of april.
Thats also why you don't hear much about Open Office because more focus has been on eCS with all the new drivers. Currently I'm also working with David and Lars on the USB drivers.

Roderick Klein
Mensys B.V.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version