PMfax

[Wayne A. Smith]

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.

[Wayne A. Smith]

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.

[Wayne A. Smith]

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

[Dave Yeo]

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.

[Wayne A. Smith]

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.)

[Wayne A. Smith]

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.)

[Wayne A. Smith]

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.

[Wayne A. Smith]

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.

[Neil Waldhauer]

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.

[Wayne A. Smith]

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.

[Wayne A. Smith]

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

[Dave Yeo]

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.

[Andi B.]

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.

[Neil Waldhauer]

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.