31
Setup & Installation / Re: CUPS tripped up SeaMonkey and Firefox
« on: February 09, 2024, 11:38:03 pm »...Pete, after reboot with the CUPS daemon removed from the Startup folder, trying to start SeaMonkey still gives the same error.
...Yes, the failures are indeed registered in popuplog.os2; here are the results of the latest attempts to start SeaMonkey and Firefox:
------------------------------------------------------------
02-09-2024 22:43:10 SYS3175 PID 0092 TID 0001 Slot 0086
F:\PROGRAMS\SEAMONKEY2\SEAMONKEY.EXE
c0000005
167507c7
P1=00000001 P2=00000001 P3=XXXXXXXX P4=XXXXXXXX
EAX=00000000 EBX=1731887c ECX=5ad1e9f0 EDX=00000000
ESI=173187e4 EDI=00000000
DS=0053 DSACC=d0f3 DSLIM=5fffffff
ES=0053 ESACC=d0f3 ESLIM=5fffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:5e117d4b CSACC=d0df CSLIM=5fffffff
SS:ESP=0053:0013ff64 SSACC=d0f3 SSLIM=5fffffff
EBP=0013ff70 FLG=00010293
PSPRINT.DRV 0002:000107c7
------------------------------------------------------------
Aha...I think I know the root cause here, or at least a worthy attempt to fix this.
I have encountered this before while attempting to remove a FXPrint printer setup.
It would seem the application stores the printer selection from the last time you used that printer. However, if that printer is now no longer defined/present, the application may not gracefully handle that and it may subsequently crash.
This was some time ago, but I think I ultimately editted either the app INI settings, or the OS2.INI file for this specific application. By "editted" I mean I removed the reference to that printer which no longer existed on my system.
So in your case, given that Seamonkey is the culprit, check the appropriate entries that might reference the printer.
...in the meantime I'll scratch my head a little more to remember the specific of what I had encountered...