Public Discussions > General Discussion

PMfax

<< < (6/6)

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: ---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

--- End code ---

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.

Navigation

[0] Message Index

[*] Previous page