From: Digest To: "OS/2GenAu Digest" Date: Sat, 6 Sep 2008 00:01:36 EST-10EDT,10,1,0,7200,4,1,0,7200,3600 Subject: [os2genau_digest] No. 1702 Reply-To: X-List-Unsubscribe: www.os2site.com/list/ ************************************************** Friday 05 September 2008 Number 1702 ************************************************** Subjects for today 1 Re: USB Modems and eCS : Mike O'Connor 2 Re: USB Modems and eCS : Ed Durrant 3 Re: USB Modems and eCS : Ed Durrant 4 Re: USB Modems and eCS : Voytek Eymont" 5 Re: USB Modems and eCS : Ed Durrant 6 Re: USB Modems and eCS : Ed Durrant 7 Re: USB Modems and eCS : Ed Durrant 8 Re: USB Modems and eCS : Mike O'Connor 9 Re: USB Modems and eCS : John Angelico" 10 Re: USB Modems and eCS : Mike O'Connor 11 Re: USB Modems and eCS : Mike O'Connor 12 Re: USB Modems and eCS : Ed Durrant 13 Re: USB Modems and eCS : Wayne 14 Re: USB Modems and eCS : John Angelico" 15 Re: USB Modems and eCS : John Angelico" **= Email 1 ==========================** Date: Fri, 05 Sep 2008 03:47:12 +1000 From: Mike O'Connor Subject: Re: USB Modems and eCS John Angelico wrote: > On Thu, 04 Sep 2008 19:25:48 +1000, Ed Durrant wrote: >> What parameters do you have on your com.sys device driver line in >> config.sys ?? >> > DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) > DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v Hi John, I think you now have your config.sys entries at cross purposes. You are showing both the RS232C port and the USB-COM port assigned to COM8! COM.SYS line should not require anything other than "DEVICE=C:\OS2\BOOT\COM.SYS", which will cover your RS232C modem on COM1. When I was running my Telstra ISDN modem connected via USB cable to PC, I used "/N:COM5" as the parameters for USBCOM.SYS. AFAIK the USBCOM.SYS driver is completely independent of COM.SYS. I could use it flawlessly with either IJ Dialler 2.30 or 3.0x or with eCSCoNet application (ISDNPM for eCS) N.B. ",S" is not a valid parameter - "S" is either "D" or "I" in the config.sys entry: Should have come up as a boot error when in config.sys (from COMMAND.REF - COM.SYS parameters) S = Unexpected interrupt handling value. D is to deinstall the COM.SYS device driver if more than 1000 unexpected interrupts occur consecutively. I is to ignore unexpected interrupts. (The default is D.) This value is optional. Think in most cases the above would now be deprecated, you definitely shouldn't have to use it, in your case. Regards, Mike ---------------------------------------------------------------------------------- **= Email 2 ==========================** Date: Fri, 05 Sep 2008 06:30:05 +1000 From: Ed Durrant Subject: Re: USB Modems and eCS John Angelico wrote: > On Thu, 04 Sep 2008 19:25:48 +1000, Ed Durrant wrote: > > >> What parameters do you have on your com.sys device driver line in >> config.sys ?? >> > DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) > DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v > > OK. > > Have Injoy, got it configured as you said in the article. > > Now I don't have the modem to test it live, so I tested Injoy dialing; but > all I got was: > [opening port] > [Port open fail, retrying in 5 secs...] > [Port open fail, retrying in 5 secs...] > [Port open fail, retrying in 5 secs...] > [Port open fail, retrying in 5 secs...] > > until I interrupted it. > > > > Best regards > John Angelico > OS/2 SIG > os2 at melbpc dot org dot au or > talldad at kepl dot com dot au > ___________________ > Well that looks good ! How about mode com8 after running Injoy does it show the configuration as you set in Injoy ? Cheers/2 Ed. ---------------------------------------------------------------------------------- **= Email 3 ==========================** Date: Fri, 05 Sep 2008 06:35:57 +1000 From: Ed Durrant Subject: Re: USB Modems and eCS John Angelico wrote: > On Thu, 4 Sep 2008 22:35:47 +0930, Wayne wrote: > > Hi and thanks for jumping in Wayne. > > >> ** Reply to note from "John Angelico" Thu, 04 Sep 2008 22:45:02 +1000 >> (AEST) >> >>> >>> On Thu, 04 Sep 2008 19:25:48 +1000, Ed Durrant wrote: >>> >>> >>>> What parameters do you have on your com.sys device driver line in >>>> config.sys ?? >>>> >>> DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v >>> >>> OK. >>> >>> Have Injoy, got it configured as you said in the article. >>> >>> Now I don't have the modem to test it live, so I tested Injoy dialing; but all I got was: [opening port] >>> [Port open fail, retrying in 5 secs...] [Port open fail, retrying in 5 secs...] [Port open fail, retrying in >>> 5 secs...] [Port open fail, retrying in 5 secs...] >>> >>> until I interrupted it. >>> >>> >>> >>> Best regards John Angelico OS/2 SIG os2 at melbpc dot org dot au or talldad at kepl dot com dot au >>> >> That happens here when I forget to plug in the phone. >> > > Hmm, no change here when I plug in the phone. > > But I see an extra CD-ROM in my Drives folder, assigned Drive T: after my > regular Drive S: which is the real DVD-Burner. > > The modem starts with its little indicator light flashing green then turns > to flashing blue. > > Waited for Blue - no difference. > > Oh, well, Ed did say it was going to be a trial and error, iterative > process. ;-) > > > Best regards > John Angelico > OS/2 SIG > os2 at melbpc dot org dot au or > talldad at kepl dot com dot au > ___________________ > > > > Yes I have read that the Hauwei USB modems have memory formatted in CDFS - the reason being under Windoze when you plug it in the autostart function then starts whatever software the supplier wants, from the modem. You should be able to see something on the new CD-Rom object. I think we are now at the point that we need to know the correct initiation code, if it is *99# that you are sending and getting an error. Another question - can you disable any other com ports in the bios for now to make sure we don't have an IRQ or IO address clash between the virtual port com8 and the physical ports ? Cheers/2 Ed. ---------------------------------------------------------------------------------- **= Email 4 ==========================** Date: Fri, 5 Sep 2008 06:38:50 +1000 (EST) From: "Voytek Eymont" Subject: Re: USB Modems and eCS > John Angelico wrote: > Yes I have read that the Hauwei USB modems have memory formatted in CDFS > - the reason being under Windoze when you plug it in the autostart > function then starts whatever software the supplier wants, from the modem. > You should be able to see something on the new CD-Rom object. I recently had to install one of these things (on xp): you plug it in, it mounts as a drive, installs required drivers/software off the 'usb flash drive/modem', then 'changes over' to a modem or brodband router or whatever it's meant to be it was quite nifty, and, child's play -- Voytek ---------------------------------------------------------------------------------- **= Email 5 ==========================** Date: Fri, 05 Sep 2008 07:09:08 +1000 From: Ed Durrant Subject: Re: USB Modems and eCS Mike O'Connor wrote: > John Angelico wrote: >> On Thu, 04 Sep 2008 19:25:48 +1000, Ed Durrant wrote: >>> What parameters do you have on your com.sys device driver line in >>> config.sys ?? >>> >> DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) >> DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v > Hi John, > > I think you now have your config.sys entries at cross purposes. > You are showing both the RS232C port and the USB-COM port assigned to > COM8! > > COM.SYS line should not require anything other than > "DEVICE=C:\OS2\BOOT\COM.SYS", which will cover your RS232C modem on > COM1. When I was running my Telstra ISDN modem connected via USB cable > to PC, I used "/N:COM5" as the parameters for USBCOM.SYS. AFAIK the > USBCOM.SYS driver is completely independent of COM.SYS. I could use it > flawlessly with either IJ Dialler 2.30 or 3.0x or with eCSCoNet > application (ISDNPM for eCS) > > N.B. ",S" is not a valid parameter - "S" is either "D" or "I" in the > config.sys entry: > Should have come up as a boot error when in config.sys > > (from COMMAND.REF - COM.SYS parameters) > S = Unexpected interrupt handling value. D is to deinstall the COM.SYS > device driver if more than 1000 unexpected interrupts occur > consecutively. I is to ignore unexpected interrupts. (The default is > D.) This value is optional. > > Think in most cases the above would now be deprecated, you definitely > shouldn't have to use it, in your case. > > Regards, > Mike Hi Mike, COM.SYS without any parameters only allows com ports up to 4 to exist, to use a com port above that whether physical or virtual (as with the USB com port), we do need to add the parameters. It is key however that the same IO address and/or IRQ are not allocated to multiple device ports (again physical or virtual). Hence I have asked John to disable all physical RS232 COM ports for the time being. Once we have the communications working to the USB 3G modem, we can then look at finding an IRQ and IO address that don't clash with COM1: or COM2: Or if John doesn't use Com1/2 he can simply leave them disabled. In that case we could even use com1 or com2 to the usb modem but for now it's safer to work with a higher number and hence the reason it does have to be defined on com.sys. Cheers/2 Ed. ---------------------------------------------------------------------------------- **= Email 6 ==========================** Date: Fri, 05 Sep 2008 07:11:03 +1000 From: Ed Durrant Subject: Re: USB Modems and eCS Mike O'Connor wrote: > John Angelico wrote: >> On Thu, 04 Sep 2008 19:25:48 +1000, Ed Durrant wrote: >>> What parameters do you have on your com.sys device driver line in >>> config.sys ?? >>> >> DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) >> DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v > Hi John, > > I think you now have your config.sys entries at cross purposes. > You are showing both the RS232C port and the USB-COM port assigned to > COM8! > > COM.SYS line should not require anything other than > "DEVICE=C:\OS2\BOOT\COM.SYS", which will cover your RS232C modem on > COM1. When I was running my Telstra ISDN modem connected via USB cable > to PC, I used "/N:COM5" as the parameters for USBCOM.SYS. AFAIK the > USBCOM.SYS driver is completely independent of COM.SYS. I could use it > flawlessly with either IJ Dialler 2.30 or 3.0x or with eCSCoNet > application (ISDNPM for eCS) > > N.B. ",S" is not a valid parameter - "S" is either "D" or "I" in the > config.sys entry: > Should have come up as a boot error when in config.sys > > (from COMMAND.REF - COM.SYS parameters) > S = Unexpected interrupt handling value. D is to deinstall the COM.SYS > device driver if more than 1000 unexpected interrupts occur > consecutively. I is to ignore unexpected interrupts. (The default is > D.) This value is optional. > > Think in most cases the above would now be deprecated, you definitely > shouldn't have to use it, in your case. > > Regards, > Mike > > > Forgot to say - I agree that "S" should not be there DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3) (or different IRQ/IO addresses) is all that is required. ---------------------------------------------------------------------------------- **= Email 7 ==========================** Date: Fri, 05 Sep 2008 07:27:35 +1000 From: Ed Durrant Subject: Re: USB Modems and eCS Ed Durrant wrote: > Mike O'Connor wrote: >> John Angelico wrote: >>> On Thu, 04 Sep 2008 19:25:48 +1000, Ed Durrant wrote: >>>> What parameters do you have on your com.sys device driver line in >>>> config.sys ?? >>>> >>> DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) >>> DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v >> Hi John, >> >> I think you now have your config.sys entries at cross purposes. >> You are showing both the RS232C port and the USB-COM port assigned to >> COM8! >> >> COM.SYS line should not require anything other than >> "DEVICE=C:\OS2\BOOT\COM.SYS", which will cover your RS232C modem on >> COM1. When I was running my Telstra ISDN modem connected via USB >> cable to PC, I used "/N:COM5" as the parameters for USBCOM.SYS. AFAIK >> the USBCOM.SYS driver is completely independent of COM.SYS. I could >> use it flawlessly with either IJ Dialler 2.30 or 3.0x or with >> eCSCoNet application (ISDNPM for eCS) >> >> N.B. ",S" is not a valid parameter - "S" is either "D" or "I" in the >> config.sys entry: >> Should have come up as a boot error when in config.sys >> >> (from COMMAND.REF - COM.SYS parameters) >> S = Unexpected interrupt handling value. D is to deinstall the >> COM.SYS device driver if more than 1000 unexpected interrupts occur >> consecutively. I is to ignore unexpected interrupts. (The default is >> D.) This value is optional. >> >> Think in most cases the above would now be deprecated, you definitely >> shouldn't have to use it, in your case. >> >> Regards, >> Mike > > Hi Mike, > > COM.SYS without any parameters only allows com ports up to 4 to > exist, to use a com port above that whether physical or virtual (as > with the USB com port), we do need to add the parameters. It is key > however that the same IO address and/or IRQ are not allocated to > multiple device ports (again physical or virtual). Hence I have asked > John to disable all physical RS232 COM ports for the time being. Once > we have the communications working to the USB 3G modem, we can then > look at finding an IRQ and IO address that don't clash with COM1: or > COM2: Or if John doesn't use Com1/2 he can simply leave them disabled. > In that case we could even use com1 or com2 to the usb modem but for > now it's safer to work with a higher number and hence the reason it > does have to be defined on com.sys. > > Cheers/2 > > Ed. > > > Hi Mike, Perhaps I should have phrased my reply a little different and started It is my understanding that .... As you are saying that (at least with eCScoNET and Injoy) you don't need to tell com.sys to support com8: In any case, let try this as described (but without IRQ/IO address clash with the hardware ports) as this is what I had working, and then see if we can remove the parameters and see if it still works. Cheers/2 Ed. ---------------------------------------------------------------------------------- **= Email 8 ==========================** Date: Fri, 05 Sep 2008 07:53:29 +1000 From: Mike O'Connor Subject: Re: USB Modems and eCS Ed Durrant wrote: > Mike O'Connor wrote: >> John Angelico wrote: >>> On Thu, 04 Sep 2008 19:25:48 +1000, Ed Durrant wrote: >>>> What parameters do you have on your com.sys device driver line in >>>> config.sys ?? >>>> >>> DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) >>> DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v >> Hi John, >> >> I think you now have your config.sys entries at cross purposes. >> You are showing both the RS232C port and the USB-COM port assigned to >> COM8! >> >> COM.SYS line should not require anything other than >> "DEVICE=C:\OS2\BOOT\COM.SYS", which will cover your RS232C modem on >> COM1. When I was running my Telstra ISDN modem connected via USB >> cable to PC, I used "/N:COM5" as the parameters for USBCOM.SYS. AFAIK >> the USBCOM.SYS driver is completely independent of COM.SYS. I could >> use it flawlessly with either IJ Dialler 2.30 or 3.0x or with >> eCSCoNet application (ISDNPM for eCS) >> >> N.B. ",S" is not a valid parameter - "S" is either "D" or "I" in the >> config.sys entry: >> Should have come up as a boot error when in config.sys >> >> (from COMMAND.REF - COM.SYS parameters) >> S = Unexpected interrupt handling value. D is to deinstall the >> COM.SYS device driver if more than 1000 unexpected interrupts occur >> consecutively. I is to ignore unexpected interrupts. (The default is >> D.) This value is optional. >> >> Think in most cases the above would now be deprecated, you definitely >> shouldn't have to use it, in your case. >> >> Regards, >> Mike > > Hi Mike, > > COM.SYS without any parameters only allows com ports up to 4 to > exist, to use a com port above that whether physical or virtual (as > with the USB com port), we do need to add the parameters. It is key > however that the same IO address and/or IRQ are not allocated to > multiple device ports (again physical or virtual). Hence I have asked > John to disable all physical RS232 COM ports for the time being. Once > we have the communications working to the USB 3G modem, we can then > look at finding an IRQ and IO address that don't clash with COM1: or > COM2: Or if John doesn't use Com1/2 he can simply leave them disabled. > In that case we could even use com1 or com2 to the usb modem but for > now it's safer to work with a higher number and hence the reason it > does have to be defined on com.sys. > > Cheers/2 > > Ed. Hi Ed, John, "COM.SYS without any parameters only allows com ports up to 4 to exist, to use a com port above that whether physical or virtual (as with the USB com port), we do need to add the parameters" Although I concur with the first phrase, I have to disagree about the balance of above quote, as I never once had any parameters to COM.SYS in config.sys the entire time (close to a year**) I was running COM5 over direct USB cable between respective USB (1.1) ports on PC and ISDN modem (no converters involved). Only time I ever had any parameters on the RS232C driver was when I used Ray Gwinn's VMODEM.exe for toll-free BBS downloads over the web. I had COM1 and COM2 (RS232C) enabled the whole time, sometimes using SIO2K, depending upon boot partition. COM5 over USB worked irrespective of whether using IBM's COM.SYS, SIO2K, or previous SIO (1.60d IIRC) for the RS232C ports ** : previously I had just used the RS232C ports on PC and Modem as I erroneously assumed the USB connection wouldn't work under eCS-OS/2 Regards, Mike ---------------------------------------------------------------------------------- **= Email 9 ==========================** Date: Fri, 05 Sep 2008 07:55:25 +1000 (AEST) From: "John Angelico" Subject: Re: USB Modems and eCS On Fri, 05 Sep 2008 07:27:35 +1000, Ed Durrant wrote: >Ed Durrant wrote: >> Mike O'Connor wrote: Thanks to everyone who has responded so far. I am (re)learning a lot about comms (and about reading help files). Gotta rush off to work now but will test and reply fully tonight Melb time. Best regards John Angelico OS/2 SIG os2 at melbpc dot org dot au or talldad at kepl dot com dot au ___________________ ---------------------------------------------------------------------------------- **= Email 10 ==========================** Date: Fri, 05 Sep 2008 08:08:14 +1000 From: Mike O'Connor Subject: Re: USB Modems and eCS Ed Durrant wrote: > Hi Mike, > > Perhaps I should have phrased my reply a little different and started > It is my understanding that .... As you are saying that (at least > with eCScoNET and Injoy) you don't need to tell com.sys to support > com8: In any case, let try this as described (but without IRQ/IO > address clash with the hardware ports) as this is what I had working, > and then see if we can remove the parameters and see if it still works. > > Cheers/2 > > Ed. Hi Ed, If RS232C ports are disabled in BIOS it should be sufficient to just REM out the COM.SYS/VCOM.SYS entries in config.sys - as long as " /n:com8" is appended to USBCOM.SYS. If I still had the ISDN line I could have verified that. Regards, Mike ---------------------------------------------------------------------------------- **= Email 11 ==========================** Date: Fri, 05 Sep 2008 08:24:03 +1000 From: Mike O'Connor Subject: Re: USB Modems and eCS Mike O'Connor wrote: > Ed Durrant wrote: >> Hi Mike, >> >> Perhaps I should have phrased my reply a little different and started >> It is my understanding that .... As you are saying that (at least >> with eCScoNET and Injoy) you don't need to tell com.sys to support >> com8: In any case, let try this as described (but without IRQ/IO >> address clash with the hardware ports) as this is what I had working, >> and then see if we can remove the parameters and see if it still works. >> >> Cheers/2 >> >> Ed. > Hi Ed, > > If RS232C ports are disabled in BIOS it should be sufficient to just > REM out the COM.SYS/VCOM.SYS entries in config.sys - as long as " > /n:com8" is appended to USBCOM.SYS. > > If I still had the ISDN line I could have verified that. > > Regards, > Mike USBCOMM.TXT dependencies/requirements seems to confirm that : 2.5 Requirements ================ 2.5.1 Hardware USBCOM.SYS driver is designed to serve any modem device following USB Communication Device specifications with AT command support (Abstract Control Model). 2.5.2 Software (a.) USB Basic support 2.6 Dependencies ================ This package contains only USB-Communication driver, in order USB-Modem USB base stack driver package (USBBASIC.EXE) must also be installed. Regards, Mike ---------------------------------------------------------------------------------- **= Email 12 ==========================** Date: Fri, 05 Sep 2008 08:27:51 +1000 From: Ed Durrant Subject: Re: USB Modems and eCS Mike O'Connor wrote: > Ed Durrant wrote: >> Hi Mike, >> >> Perhaps I should have phrased my reply a little different and started >> It is my understanding that .... As you are saying that (at least >> with eCScoNET and Injoy) you don't need to tell com.sys to support >> com8: In any case, let try this as described (but without IRQ/IO >> address clash with the hardware ports) as this is what I had working, >> and then see if we can remove the parameters and see if it still works. >> >> Cheers/2 >> >> Ed. > Hi Ed, > > If RS232C ports are disabled in BIOS it should be sufficient to just > REM out the COM.SYS/VCOM.SYS entries in config.sys - as long as " > /n:com8" is appended to USBCOM.SYS. > > If I still had the ISDN line I could have verified that. > > Regards, > Mike > > > I would not rem out anything until we have the solution working. The old rule of changing one thing at a time is very relevant when trying new hardware. By the way John - the windoze support "driver" file should contain what you need as an initiation string for the modem. Cheers/2 Ed. ---------------------------------------------------------------------------------- **= Email 13 ==========================** Date: Fri, 5 Sep 2008 20:13:17 +0930 From: Wayne Subject: Re: USB Modems and eCS > > On Thu, 4 Sep 2008 22:35:47 +0930, Wayne wrote: > > >> > > >> >What parameters do you have on your com.sys device driver line in > >> >config.sys ?? > >> DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v > >> > Best regards John Angelico OS/2 SIG os2 at melbpc dot org dot au or talldad at kepl dot com dot au As Mike suggested, I would lose the reference to com8 in the COM.SYS line. Cheers Wayne ---------------------------------------------------------------------------------- **= Email 14 ==========================** Date: Fri, 05 Sep 2008 23:22:08 +1000 (AEST) From: "John Angelico" Subject: Re: USB Modems and eCS On Fri, 5 Sep 2008 20:13:17 +0930, Wayne wrote: >> >> On Thu, 4 Sep 2008 22:35:47 +0930, Wayne wrote: >> > >> >> > >> >> >What parameters do you have on your com.sys device driver line in >> >> >config.sys ?? >> >> DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 >/v >> >> >> Best regards John Angelico OS/2 SIG os2 at melbpc dot org dot au or talldad at kepl dot com dot au > >As Mike suggested, I would lose the reference to com8 in the COM.SYS line. > >Cheers >Wayne Thanks Wayne, Mike and Ed. Status report: Machine has 1 only hardware serial connection with external fax/modem connected Bios enables ONLY COM1: Config.sys now shows: DEVICE=C:\OS2\BOOT\COM.SYS rem DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) DEVICE=C:\OS2\BOOT\USBPRT.SYS rem DEVICE=C:\OS2\BOOT\USBMOUSE.SYS rem DEVICE=C:\AMouse\USBMOUSE.SYS rem DEVICE=C:\OS2\BOOT\USBKBD.SYS DEVICE=C:\OS2\BOOT\USBCOM.SYS /n:com8 /v Boot up with Alt-F2 showed no errors Injoy reports: Ä[ Terminal Mode ]ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ [opening port] [Port open fail, retrying in 5 secs...] [Port open fail - Interrupted] (after I hit Hang Up) Result was the same whether we had the modem connected to the USB cable or not. I suspect we haven't reached the stage of talking to the device as yet... So still no Joy with InJoy... Best regards John Angelico OS/2 SIG os2 at melbpc dot org dot au or talldad at kepl dot com dot au ___________________ ---------------------------------------------------------------------------------- **= Email 15 ==========================** Date: Fri, 05 Sep 2008 23:51:59 +1000 (AEST) From: "John Angelico" Subject: Re: USB Modems and eCS On Fri, 05 Sep 2008 08:27:51 +1000, Ed Durrant wrote: > >By the way John - the windoze support "driver" file should contain what >you need as an initiation string for the modem. Thanks Ed. We have those strings now in InJoy, but we haven't got that far yet. Found USBRESCFG the gui configuration tool. Used it to check the USB stuff, and changed one item: Modem = 1 Now the CONFIG.SYS looks like this DEVICE=C:\OS2\BOOT\COM.SYS rem DEVICE=C:\OS2\BOOT\COM.SYS (8,2f8,3,S) DEVICE=C:\OS2\BOOT\USBCOM.SYS /N:COM8 /M:1 /I: /O: /V and BASEDEV=USBEHCD.SYS BASEDEV=USBUHCD.SYS BASEDEV=USBUHCD.SYS BASEDEV=USBUHCD.SYS BASEDEV=USBUHCD.SYS BASEDEV=USBD.SYS BASEDEV=USBHID.SYS BASEDEV=USBMSD.ADD /FLOPPIES:0 /REMOVABLES:1 BASEDEV=USBCDROM.ADD /CDS:1 DEVICE=C:\OS2\BOOT\USBPRT.SYS DEVICE=D:\TAME\USBRESMG.SYS InJoy status line shows: [Mobile] [COM8:345600:DOWN] [LEARN:OFF] [IPSEC:OFF] [FW:OFF] [FLT:OFF] but still: [Port open fail, retrying in 5 secs...] [Port open fail, retrying in 5 secs...] [Port open fail - Interrupted] It's late again. Have more work to do tomorrow. Must stop ... Thanks for the patient help so far, fellas! Best regards John Angelico OS/2 SIG os2 at melbpc dot org dot au or talldad at kepl dot com dot au ___________________ ----------------------------------------------------------------------------------