OS/2, eCS & ArcaOS - Technical > Applications
Firefox 45.9 XUL.DLL error
Wayne A. Smith:
OK, will give these a try today, or at east some of them between other commitments. I'll try your recommendation of using WPTools before UniMaint; I suffered a Senior Moment yesterday when I dubbed UniMaint as UniTools.
I did last night before retiring to bed boot the desktop into Linux and used DFSee to create an image backup of 5.0.7. Possible messing up these INI efforts then won't be dangerous.
The residing of PMPRINT.DRV in the INI files may well be the problem; the old creation of the PS Printer Object likely inserted it. I do not presently perceive any danger in removing it as I don't conceive any need for it; the only potentially-associated application would seem to be PMPDF and it doesn't seem to use or need it.
I'll report later. Thanks for all your effort.
Dave Yeo:
If those don't help, I guess we'll have to try to check for broken DLL's in the dependencies.
Another test would be to try the screensavers Cairo clock, with the date turned on, as that would test the fontconfig and such and whether they're broken. Desktop properties is where you find the screensaver settings.
Alex Taylor:
Since the exception is happening in the PSPRINT driver, I suggest you delete all PM printers (or at least all of those using PSPRINT). If that fixes it, you can then reinstall printer(s) one by one and make sure Firefox still runs.
(By delete, I mean fully delete the printer queue and the driver instance, which you can do using PM Printer Manager, or the old FaxWorks PRNDRV.EXE.)
Dave Yeo:
I found an issue where Lewis mentioned the same problem, https://github.com/bitwiseworks/mozilla-os2/issues/255 which was from importing a PPD into psprint.drv, which as he put it, wrecked havoc with the native print system. Also confirms that F 45.9 tries to initialize the printing system upon program load
So follow Alex's advice to remove all printers
Wayne A. Smith:
SUCCESS!!! I now have FF 45.9.0 and SM 2.42.9 opeating on the Desktop.
I ran <check.ini> yesterday and, while it seemed to report FF w/out an ID - though this could have referred to 38.8.0 installed w/ ArcaOS 5.0.0 - the log didn't show anything. (It seemed it was doing something w/ the INI files since the Archive operation was activated during the process - I having it set to automatically archive for any change greater than 2.5% and every 15 days - but neither FF or SM still functioned afterward. (However since I was interrupted in following the whole process by attending to a church member who was here fixing a faulty circuit breaker, I may have missed something.)
Before trying a clean w/ UniMaint, I today moved PSPRINT.DRV to another partition, and then rebooted. On running both FF and SM the Profile Manager window for each opened and I created them. I then instructed them to open and they did what they were supposed to do.
I've noted the intervening three messages and will print them for future reference and possible future use. I had last week deleted the PS Printer Object I had created but this didn't help. Since FF and SM now are operating I haven't endeavored to pursue the printer delete suggestion; I'm not sure it would have had any effect since the printers consist of: a dot matrix connected to LPT1; an HP DeskJet w/ a USB connection; and the PMPDF generator. (I also do have the PMFax driver installed but this doesn't seem to cause a problem. (It's a shame configuration of PMFax w/ new hardware is so difficult since it was a fine answering machine, I now having to use an application under XP on a different computer for this purpose.))
The situation was definitely strange since on this ThinkPad T-540p PSPRINT.DRV continues to reside in <os2\dill\psprint\> and it never stopped FF or SM from opening. I suppose it must have been that PS Printer Object I created long ago that inserted something weird in the INI files.
Thanks Much to all for their help.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version