Messages

1

General Discussion / Re: PMfax

« on: April 28, 2024, 02:05:59 am »

OK, Neil, I've made those changes but haven't tested PMFax yet.

The one curious think I note is that these DEVICE lines separate the initial BASEDEV lines and the
BASEDEV=USBD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBHID.SYS
BASEDEV=USBKBD.SYS
BASEDEV=USBCDROM.ADD /CDS:1
BASEDEV=USBMSD.ADD /REMOVABLES:3 /FLOPPIES:1
lines. 

Is this a problem?  It would seem the the above lines ought to precede
DEVICE=C:\OS2\BOOT\USBCOM.SYS /M:3
DEVICE=C:\OS2\BOOT\USBRESMG.SYS
DEVICE=C:\OS2\BOOT\USBPRT.SYS

2

General Discussion / Re: PMfax

« on: April 27, 2024, 09:02:20 pm »

OK, Neil I'll give it a try.

> On my system, I made sure that USBCOM.SYS was the first device= statement. That ensures that the USB com port comes before all the other com ports.


I'll Un-REM <USBCOM.SYS> and move it up to the top of the Device lines.  I'll also REM the <USB.COM> line.  And, of course, I'll reconnect the USB cable to the modem.


> IBM File and Print services also shares COM ports, so if you install that, it will grab a com port.


Here I'll have to dredge up my recollection of how IBM File and Print services differs from CUPS.  I have an HP DeskJet 3052a connected via a USB cable.  Opening the Properties for it shows that it utilizes a CUPS Port and, of course, is identified by a network IP Address.  The Output Port window also shows COM ports 1 through 4, and as they are not "shadowed" they don't seem to be utilized by any printer.

And RM View doesn't show that either IRQ 4 or 3 are utilized by any device.  Maybe then there ought not be any conflict?


> I didn't bother installing COM.SYS, apparently.


As said, I'll REM out <COM.SYS> and see how this goes.

3

General Discussion / Re: PMfax

« on: April 26, 2024, 02:21:01 am »

It seems a new thread was created.  I tried to insert my last reply into the old one, but it was inserted here.  Hence the reason for the non-chronological order.

4

General Discussion / Re: PMfax

« on: April 26, 2024, 02:16:38 am »

OK, Dave.

The output is:
[C:\]mode com1
baud     = 9600                   parity   = NONE
databits = 8                      stopbits = 1
TO       = OFF                    XON      = OFF
IDSR     = OFF                    ODSR     = OFF
OCTS     = OFF                    DTR      = ON
RTS      = ON                     BUFFER   = N/A

[C:\]mode com2
baud     = 9600                   parity   = NONE
databits = 8                      stopbits = 1
TO       = OFF                    XON      = OFF
IDSR     = OFF                    ODSR     = OFF
OCTS     = OFF                    DTR      = ON
RTS      = ON                     BUFFER   = N/A

[C:\]mode com3
SYS0021: The drive is not ready.

This is consistent w/ the <COM.SYS> parameters.  Strange that PMFax reports COM3 UNLESS it is accessing the <USBCOM.SYS> setting rather than the <COM.SYS> setting.

5

General Discussion / Re: PMfax

« on: April 26, 2024, 02:14:03 am »

I REMd out the USBCOM line and Mode returned the same information.  Therefore it is the Serial ports that ArcaOS recognizes. 

Opening PMFax now only displays for Ports:  FMD!; COM1; and COM2.  Since then the USBCOM line might have been confusing it, I unplugged the USB cable from the modem.  However, since I still can't receive any calls, more investigation is required.

(The modem manual cautions not to have any line splitter or other devices between the wall jack and the modem.  However, I'm aware of a situation - parallel to your experience - where a hospital didn't have any protection between its telephone line and its computer and a lightning strike fried the latter.  Therefore, I'm still going to keep the line going into and out of my Tripp Lite UPS.)

6

General Discussion / Re: PMfax

« on: April 26, 2024, 02:12:20 am »

I REMd out the USBCOM line and Mode returned the same information.  Therefore it is the Serial ports that ArcaOS recognizes. 

Opening PMFax now only displays for Ports:  FMD!; COM1; and COM2.  Since then the USBCOM line might have been confusing it, I unplugged the USB cable from the modem.  However, since I still can't receive any calls, more investigation is required.

(The modem manual cautions not to have any line splitter or other devices between the wall jack and the modem.  However, I'm aware of a situation - parallel to your experience - where a hospital didn't have any protection between its telephone line and its computer and a lightning strike fried the latter.  Therefore, I'm still going to keep the line going into and out of my Tripp Lite UPS.)

7

General Discussion / Re: PMfax

« on: April 25, 2024, 10:16:27 pm »

Sorry for the second, semi-duplicate, message.  I didn't notice the posting of the initial one.

8

General Discussion / Re: PMfax

« on: April 25, 2024, 10:11:40 pm »

OK, Dave.

The output is:
[C:\]mode com1
baud     = 9600                   parity   = NONE
databits = 8                      stopbits = 1
TO       = OFF                    XON      = OFF
IDSR     = OFF                    ODSR     = OFF
OCTS     = OFF                    DTR      = ON
RTS      = ON                     BUFFER   = N/A

[C:\]mode com2
baud     = 9600                   parity   = NONE
databits = 8                      stopbits = 1
TO       = OFF                    XON      = OFF
IDSR     = OFF                    ODSR     = OFF
OCTS     = OFF                    DTR      = ON
RTS      = ON                     BUFFER   = N/A

[C:\]mode com3
SYS0021: The drive is not ready.

Strange that PMFax reports COM3 unless it is recognizing the <USBCOM.SYS> setting rather than the <USB.COM> setting.

9

General Discussion / Re: PMfax

« on: April 25, 2024, 10:06:43 pm »

OK, Dave.

The output is:
[C:\]mode com1
baud     = 9600                   parity   = NONE
databits = 8                      stopbits = 1
TO       = OFF                    XON      = OFF
IDSR     = OFF                    ODSR     = OFF
OCTS     = OFF                    DTR      = ON
RTS      = ON                     BUFFER   = N/A

[C:\]mode com2
baud     = 9600                   parity   = NONE
databits = 8                      stopbits = 1
TO       = OFF                    XON      = OFF
IDSR     = OFF                    ODSR     = OFF
OCTS     = OFF                    DTR      = ON
RTS      = ON                     BUFFER   = N/A

[C:\]mode com3
SYS0021: The drive is not ready.

This is consistent w/ the <COM.SYS> parameters.  Strange that PMFax reports COM3 UNLESS it is accessing the <USBCOM.SYS> setting rather than the <COM.SYS> setting.

10

General Discussion / Re: PMfax

« on: April 25, 2024, 08:29:18 pm »

I'm pretty sure my problem is in the PMFax Pro Settings.  I'll probably have to search through Keller's various user guide PDFs to see if I can figure out what parameters are wrong.

I have both the Serial Cable and the USB cable attached.  I also have
     DEVICE=C:\OS2\BOOT\COM.SYS (1,3f8,4) (2,2f8,3)
     DEVICE=C:\OS2\BOOT\USBCOM.SYS /M:3
in <config.sys>.  The OS is ArcaOS 5.0.8.
The Ports displayed under PMFAx Pro's settings are:  FMD1; COM1; COM2; and COM3.

The only non-Internet communications program I have on this computer is HyperHost, and it seems it recognizes the modem - though I don't know how to externally connect to test it.

As far as the Add program, I don't think this is an issue.  Though I copied the PMFax Pro directory from an installation on another computer, IIRC it was just an upgrade from a license I had from Keller for an earlier version.  It opens fine and allows updating of <fx.ini>.  It's just that I can' send faxes or receive voice calls w/ it - something that was no problem when I was able to use an ISA card.

Like I said, I'll just have to drill down into the guide files, though I did just buy an unopened 3COM US ROBOTICS Model 5605 56K Voice Faxmodem Pro V.90 X 2 to see if this works better.  (It's still an old model but newer than my Model No. 0525, and it seems Model 5605 is reported to work well under OS/2.)

11

General Discussion / Re: PMfax

« on: April 21, 2024, 11:18:23 pm »

Neil,
How right you are ...  It's bit a long time since i had to configure this kind of connection, though I'm trying again after a long hiatus in trying PMFax Pro again.

I also have a US Robotics External 54K Voice FaxModem Pro, connected by the USB cable and to a landline.  While PMFax is (I believe) installed properly, I can't get a dial-in recognized by it.  (I first used Suntan Special for installation but got an Error that "Product not enabled."  I then copied an old directory, and used the Registry Editor to change the directory reference.)

USBCOM.SYS is referenced in <config.sys>.  Since FMD1 as the Port didn't work, I tried COM1 but No Joy there either.

Looking in <system.ini> for COM1, the PORTDRIVER key is "Serial".  Since the modem now has a USB connection, is this the problem?  (I also have a Serial cable for it and might be able to use an adapter to connect it to my ThinkCentre M93p, but would prefer to avoid this if this extra work would be in vain.)

Any ideas?

12

Applications / Re: Firefox 45.9 XUL.DLL error

« on: February 13, 2023, 05:37:43 pm »

As an addendum to yesterday's message, I know that my solution was not particularly elegant.  But it accomplished what I immediately required.

When I have more time I plan to use the Registry Editor and UniMaint to locate the PSPRINT.DRV references and explore how any anomalies might be corrected.  The USB connected printer might require CUPS and thus might need the driver; right now, though, I'm not using it on the desktop computer and can defer resolution.

At least I can save the current partition and files, to revert to them, if the efforts and movement back of PSPRINT.DRV again causes problems.

13

Applications / Re: Firefox 45.9 XUL.DLL error

« on: February 13, 2023, 12:06:51 am »

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.

14

Applications / Re: Firefox 45.9 XUL.DLL error

« on: February 11, 2023, 06:39:04 pm »

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.

15

Applications / Re: Firefox 45.9 XUL.DLL error

« on: February 11, 2023, 01:00:48 am »

Inserting
-ProfileManager
in the Parameters still causes a crash and throws out the same "Couldn't load XUL.DLL (OS2 error 87)" error.

I may have installed some printers in FF 38.8.0 but not 45.9.0 or Seamonkey since I could never get them to run.  In fact I don't recall any menu for printer installation under any of them.

I see no reference to <psprint.drv> in the <config.sys>.  I did try to rename it, to see if this helped, but failed since it said it was being used by another application.  Accordingly I deleted the printer object for the PS Printer I had created - since I probably had created it erroneously thinking PMPDF may have required it, or for creating files for Distiller - and rebooted.  Still the same problem.

As far as my INI files I have only relied on IFX examining and cleaning them.  I did, long, long ago, purchase a license for UniTools and have it installed on the desktop.  Do you think I should give this a whirl?