OS/2, eCS & ArcaOS - Technical > Applications

Firefox error message

(1/3) > >>

Joop:
Yesterday I downloaded the new JAlbum. Its grown from about 18.5Mb to about 169Mb. You get 30 days to play with it and after that you need a license. In the zip also chromium browsers and this will give an error if JAlbum wants to use it. But there is in the preferences a choice for internal or external browsers, so internal set to off. Now the external browser is used and for OS/2-eCS this is Firefox. Up to the test I had Firefox 6.02 as browser. But we have more up to date FF with at least FF 17.01.1. So set it up that JAlbum have to use this FF, but as soon as it needs the browser I get an error from Firefox with the message "Couldn't load xpcom.dll". Is this a missing item in Odin?,  is it just that simple to copy xpcom.dll from an Windows xp installation in the Odin\system32 directory?, or will it just not work because it has to be an xpcom.dll but rebuild for Odin? Can someone help me with this?

Joop:
Seems to be a bigger thing which also shows up in other OS. Tried clean up, didn't help. If you do this a map named "old firefox data" is created on your desktop. Its big. After done so started JAlbum, but as soon as it needed FF the same message appears. Will be continued as usual....

Joop:
Xpcom.dll is something from within the directory of FF, so no Windows shit. But in FF17 xpcom.dll is present, FF17 loads normally, matter of fact I'm working with it right now.
So I did a few tests. Does other FF have the same problem. Its not that easy. After installing FF10 latest as browser nothing happened, FF10 doesn't understand if a file is send to it. Okay, lets try FF24. Rebuild the command file for use with FF24. Started JAlbum and I get the message can't load xul.dll. That file is present, but about 10Mb more in size than found with FF17. So here we might have a problem of a memory issue, I only have 1G on board and Java has to see real memory.
In the mean time, real sick joke :-(. Lets see what I can find out more about xpcom.dll. Now I do understand why FF is so high in version number....

Joop:
Didn't find a real solution for xpcom.dll. FF is installed (if you can speak of installation) in a new created directory and through the program itself all plugins and add-ons installed. I'm working with it right now and don't have any or get any messages that something is not right. So its the combination of two programs and that's make things complicated.

I've tested latest JAlbum with FF 6.02 as an external browser and that works, ie the browser is started and the page is loaded, but if your happy with the contents is another question and is not the problem of the browser. So for now latest payed version of JAlbum seems to work without integrated browser and as external browser FF 6.02.

Dave Yeo:

--- Quote from: Joop on July 28, 2014, 06:29:26 pm ---Yesterday I downloaded the new JAlbum. Its grown from about 18.5Mb to about 169Mb. You get 30 days to play with it and after that you need a license. In the zip also chromium browsers and this will give an error if JAlbum wants to use it. But there is in the preferences a choice for internal or external browsers, so internal set to off. Now the external browser is used and for OS/2-eCS this is Firefox. Up to the test I had Firefox 6.02 as browser. But we have more up to date FF with at least FF 17.01.1. So set it up that JAlbum have to use this FF, but as soon as it needs the browser I get an error from Firefox with the message "Couldn't load xpcom.dll". Is this a missing item in Odin?,  is it just that simple to copy xpcom.dll from an Windows xp installation in the Odin\system32 directory?, or will it just not work because it has to be an xpcom.dll but rebuild for Odin? Can someone help me with this?

--- End quote ---

The xpcom missing thing is a general error which was fixed but seems to have somehow got reverted  :(
The real problem is that you are missing something else, pthreads (pthr01.dll) mmap.dll, gcc444.dll, stdcpp6.dll or another gcc dll that one of the above depends on as well as the mzfntcfgft package. Easiest is to download moz_required_dlls_v1 and the newest mzfntcfgft from Hobbes.

Navigation

[0] Message Index

[#] Next page

Go to full version