OS2 World Community Forum

Public Discussions => General Discussion => Topic started by: Derrick Price on March 22, 2023, 11:52:01 am

Title: PMfax
Post by: Derrick Price on March 22, 2023, 11:52:01 am
Help :'(. I have lost module imgfx6mn.dll required by PMfax. Is there anybody who has a copy and could send it to me?
Title: Re: PMfax
Post by: Remy on March 22, 2023, 04:09:40 pm
May be it is installed by pmfax !
Did you try to install again pmfax ?
https://hobbes.nmsu.edu/?detail=%2Fpub%2Fos2%2Fapps%2Fcomm%2Ffax%2FPMFaxPro_upd_3-2.zip
Title: Re: PMfax
Post by: Derrick Price on March 28, 2023, 11:09:58 am
The problem is that the *exe does not contain the module but expects it to be somewhere in the system  >:(
Title: Re: PMfax
Post by: Remy on March 28, 2023, 04:00:00 pm
Help :'(. I have lost module imgfx6mn.dll required by PMfax. Is there anybody who has a copy and could send it to me?

I just started my older PMFax to review logs and it start without the need of the dll !

I suppose imgfx6mn is from ImageMAKER provided by your fax device drivers.
Check if you have your fax card drivers. 
Title: Re: PMfax
Post by: Martin Iturbide on March 28, 2023, 04:50:11 pm
Hi.

I'm sorry I don't know about PMFax, I tried to find the imgfx6mn.dll file on my collection but I was not able to find it.

Searching on the Internet I found this information "imgfx6mn.dll is a module belonging to ImageMAKER Development Fax Printer Driver from ImageMAKER Development Inc.". But that site reference it as a Windows DLL.

Derrick, which version of PMFax are you using? version? Lite, Pro?. Which OS/2, ArcaOS version are you running?
Do you have some special hardware, or it is just a modem to get fax?

Regards
Title: Re: PMfax
Post by: mauro on March 28, 2023, 08:27:26 pm
I'm curious about PMFax. First connection functionality I've been able to run at first OS2 usage in 1995 was a fax client in WINOS2 even before I could connect to Internet. Unfortunately cannot remember the software name.
Was by a 14.4 kbps modem through the serial port.
I'd like to try again, what I have is a Webrunner Atlantis Land 56.6 kbps USB faxmodem working in Windows 10, Conexant chipset, and OS2 Warp 4.52 on a Virtualbox guest machine.
Do you think I can afford the challenge?
Of course assuming that PMFax accepts USB connection or an alternative configuration setup for connection, and also can be used with the so said "winmodem" as that model should be.
Thank you
Title: Re: PMfax
Post by: Dave Yeo on March 28, 2023, 08:34:20 pm
Looks like a winmodem, so no, it won't work under OS/2. Something like a USB USR robotics modem will work as the USB interface is presented as a com port.
Title: Re: PMfax
Post by: mauro on March 28, 2023, 08:56:49 pm
Looks like a winmodem, so no, it won't work under OS/2. Something like a USB USR robotics modem will work as the USB interface is presented as a com port.

understand, I'had suspected that.
Thank you
Title: Re: PMfax
Post by: Martin Iturbide on March 29, 2023, 12:57:51 am
Hi

I just found the waybackmachine archived site with some dead liks:
- https://web.archive.org/web/20000815221748/http://www.kellergroup.com/ (https://web.archive.org/web/20000815221748/http://www.kellergroup.com/)

But no hints of the Windows version nor "imgfx6mn.dll ".

Regards
Title: Re: PMfax
Post by: Neil Waldhauer on March 29, 2023, 03:46:59 pm
I can confirm that the US Robotics USB modem works great with ArcaOS. I'm using the latest Arca Noae USB drivers.

I will also note that land lines, FAX and dial-up are now much less commonly available. I found challenges using a modem that were just me trying to remember how we used to do communications.
Title: Re: PMfax
Post by: Wayne A. Smith 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?
Title: Re: PMfax
Post by: Neil Waldhauer on April 22, 2024, 05:09:53 am
The system installs COM ports at boot time while parsing the Config.Sys. The COM port number depends on the ordering of the statements in Config.Sys, and which of them claims a serial port. (Some might not be obvious)

I'm not sure how many COM ports OS/2 supports. Some say 99, some say 255.

In the time since I last posted, both ends of the POTS line have ended service. AT&T has applied for a permit to stop providing POTS to anyone.
Title: Re: PMfax
Post by: nyao on April 22, 2024, 05:02:25 pm
Hi.
A precautionary note from when I installed it a long time ago.
It is unknown whether it is related to imgfx6mn.dll.

"Please note that if you do not enter the registration key from Add.exe after installation (maybe the procedure is incorrect?), the program will not start and will only display a message recommending that you contact the company."
http://hp.vector.co.jp/authors/VA028575/faq.htm#32
Title: Re: PMfax
Post by: Wayne A. Smith 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.)
Title: Re: PMfax
Post by: Dave Yeo on April 25, 2024, 09:25:51 pm
Try mode com1, mode com2 etc to see which com ports are installed. Seems I remember someone having problems as the com port was a higher then expected number.
Title: Re: PMfax
Post by: Wayne A. Smith 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.
Title: Re: PMfax
Post by: Wayne A. Smith 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.
Title: Re: PMfax
Post by: Wayne A. Smith 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.
Title: Re: PMfax
Post by: Dave Yeo on April 25, 2024, 10:36:04 pm
You could try reming the com.sys lines in config.sys and removing the /m:3 from usbcom.sys for testing purposes.
I used to run a USR robotics USB modem, model #5637, worked fine until there was a thunderstorm. It was fragile and  storms killed 2 of them.
Title: Re: PMfax
Post by: Wayne A. Smith 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.)
Title: Re: PMfax
Post by: Wayne A. Smith 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.)
Title: Re: PMfax
Post by: Wayne A. Smith 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.

Title: Re: PMfax
Post by: Wayne A. Smith 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.
Title: Re: PMfax
Post by: Neil Waldhauer on April 26, 2024, 03:24:06 pm
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.

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

I didn't bother installing COM.SYS, apparently.
Title: Re: PMfax
Post by: Wayne A. Smith 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.
Title: Re: PMfax
Post by: Wayne A. Smith 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
Title: Re: PMfax
Post by: Dave Yeo on April 28, 2024, 04:05:28 am
Ideally those basedev lines should precede the regular dev lines but the config.sys is parsed multiple times with the basedev lines parsed early, by  the mini-file system, so the result is a slightly slower boot.
I always had usbcom.sys towards the end of config.sys and it worked. Remming out the com.sys lines (and vcom.sys) for testing purposes seems the important step.
Title: Re: PMfax
Post by: Andi B. on April 28, 2024, 10:40:55 am
I've it in that order and it works. I've used serial devices on this system since ages. Both the original ones (COM1: COM2: on the standard addresses with PSCOM) and USB converter devices. Mind the PL2303 device lines which are now remed out. I needed to load it 4 times to use the up to 4 attached USB converters. Since about a year the usbcom.sys (v12.13?) from Davids package work with my devices. And usbcom.sys is now loaded only once in contrast to the PL2303 driver.

Code: [Select]
DEVICE=M:\OS2\BOOT\PSCOM.SYS /F

.....
BASEDEV=USBD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBXHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBOHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBEHCD.SYS

BASEDEV=USBHID.SYS
BASEDEV=USBKBD.SYS
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM5 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM6 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM7 /Z
REM ! DEVICE=P:\util\USBCOM_PL2303\usbcom.sys /V /M:1 /N:COM8 /Z
REM ! DEVICE=M:\OS2\BOOT\USBCOM.SYS
DEVICE=M:\OS2\BOOT\USBCOM.SYS /M:4 /N:COM6 /Z

When I attach one or more usb converters 'mode com6:' 'mode com7:' shows me the attached working devices. I need the /Z option cause I don't use CTS/RTS/DTR/DSR (?) handshake I guess. But with a real modem attached I think you should enable hardware handshake. Anyway as long as 'mode comx:' does not show the device working you don't need to play with any higher level program. Maybe it's necessary to attach a working modem to recognize the handshake lines for that. So maybe testing with /Z first.

Btw. when I played the last time with modems probably more then a decade ago I can't get my US Robotics 56k to work again after it was laying around for 10 years or so. The even older ELSA 33k on the other hand did work with PMFAX.
Title: Re: PMfax
Post by: Neil Waldhauer on April 28, 2024, 03:21:41 pm
The serial device drivers, USB, IBMCOM and COM all work fine in any position. All the position in Config.Sys does is determine which com port COM1, COM2, etc. is assigned to which device.

RMVIEW is voluntary, so if a device driver doesn't participate, RMVIEW will not show it.

BASEDEV statements are processed in an earlier pass. We've presented the process at Warpstock several times. They have to be correct, but their order compared to DEVICE= statements is not relevant.