🚀 go-pugleaf

Richard Ashton <{R}@sunshine.tm> wrote in message
<895623190snz129.os2.7@sunshine.tm>...
>In article <895620760.23504.0.nnrp-05.c1eddda8@news.demon.co.uk>
>           Pete@bownsite.demon.co.uk "Pete Bown" writes:
>
>} My modem works fine with Windows 3.11 and Windows 95 but OS/2 Warp 3.0
can't
>} see it.
>} Trouble is, it's plug and play and needs to be configured to run on COM
3.
>
>Go to hobbes.nmsu.edu search for sio155 that's SIO155 and download it.


Downloaded sio155 but couldn't get it to work - it can't see the modem
either. Not sure if it needs a specific I/O address.  If I go into Windows
3.11 first then OS/2, sio155 can then see the modem, but that's pointless as
OS/2 could see the modem that way without sio155.
The modem in question is a Harmony 33.6k internal plug & play
voice/fax/modem


>They will solve every OS/2 comms driver problem instanto.
>


>
>Ok so to an OS/2 command window and type [x:\]ver /r and post or mail the
>answer and we will tell you which fixpack to get.
>
>I get
>
>[F:\]ver /r
>
>The Operating System/2 Version is 4.00
>Revision 9.029


If I type ver /r,  I get:
The Operating System/2 Version 3.00
Revision 8.200

>
>{R}
>

Pete Bown

Pete Bown wrote:
> 
> Downloaded sio155 but couldn't get it to work - it can't see the modem
> either. Not sure if it needs a specific I/O address.  If I go into Windows
> 3.11 first then OS/2, sio155 can then see the modem, but that's pointless as
> OS/2 could see the modem that way without sio155.
> The modem in question is a Harmony 33.6k internal plug & play
> voice/fax/modem
> 

Sounds like the factory defaults in your modem are wrongly set and it
needs an init string to configure it properly. It would be nice if the
documentation spelled the requirements out to you. Can't you dig them
out of Windows?

Regards,
Tim

Tim Timmins wrote in message <35647F95.287E@bcs.org.uk>...
>
>Sounds like the factory defaults in your modem are wrongly set and it
>needs an init string to configure it properly. It would be nice if the
>documentation spelled the requirements out to you. Can't you dig them
>out of Windows?
>
>Regards,
>Tim
>

Tried that. The Windows 95 settings didn't work.

Pete

Pete Bown wrote:
> 
> Tim Timmins wrote in message <35647F95.287E@bcs.org.uk>...
> >
> >Sounds like the factory defaults in your modem are wrongly set and it
> >needs an init string to configure it properly. It would be nice if the
> >documentation spelled the requirements out to you. Can't you dig them
> >out of Windows?
> >
> >Regards,
> >Tim
> >
> 
> Tried that. The Windows 95 settings didn't work.
> 
> Pete

What settings did you try?

For example, I use

AT&F&D2&C1X1V1Q0S7=70

Regards,
Tim

Richard Ashton <{R}@sunshine.tm> wrote in message
<895743507snz129.os2.7@sunshine.tm>...
>In article <895723087.25266.0.nnrp-08.c1eddda8@news.demon.co.uk>
>           Pete@bownsite.demon.co.uk "Pete Bown" writes:

>DEVICE=D:\SIO\SIO.SYS (COM1,3F8,IRQ4) (COM2,Internet,None) (COM3,3E8,IRQ7)
>                       standard COM1   My mouse is on COM2  COM3 chose
>                                       (COM2,2F8,IRQ3)      your own
interrupt
>                                        would work here
>(COM4,2E8,IRQ15)
>Choose your own
>interrupt
>
>DEVICE=D:\SIO\VSIO.SYS


No,  that didn't work either.  I'll e-mail the sio155 developers to see if
they
have heard of the modem and I'll try e-mailing the modem manufacturers again
-they're not replying.
In Windows 3.11 and 95,  I've configured the modem to work on COM3 IRQ5,
COM1 is the mouse and COM2 is another comms device.


>There are easier ways but I doubt you have access to the CDROMS, you
>need the "kicker disks" may be one or two and LOADDSKF to turn the
>downloaded .dsk files into floppy disks. I expect fixpack 32 is quite
>a lot of disks

Mmm,  18 files of 1.4Mb.  I'll wait until I've got some spare time before I
download that lot!

>
>That is a lot of downloading. You may prefer aquiring WARP 4 which is
>only at fixpack 6.


I won't even consider Warp 4 until I'm 100% sure that the modem will work.

Pete

Pete Bown wrote:
> 
> In Windows 3.11 and 95,  I've configured the modem to work on COM3 IRQ5,
> COM1 is the mouse and COM2 is another comms device.
> 

How did you configure the modem?
What's the model number anyway?
Does it work in Win-OS2 ? (with Com Direct Access set to ON)

At an OS2 command prompt, type HELP COM.SYS 

Regards,
Tim

In article <895794411.6884.0.nnrp-07.c1eddda8@news.demon.co.uk>
           Pete@bownsite.demon.co.uk "Pete Bown" writes:

> No,  that didn't work either.  I'll e-mail the sio155 developers to see if
> they
> have heard of the modem and I'll try e-mailing the modem manufacturers again
> -they're not replying.
> In Windows 3.11 and 95,  I've configured the modem to work on COM3 IRQ5,
> COM1 is the mouse and COM2 is another comms device.

Unless I've missed it, I haven't noticed anyone suggest that this modem
might be a dreaded WinModem type of device: if so, it certainly won't
work (until it's been "spoken to" by Windoze [in your case WinOS/2]
first).  Is this a possibility?

-- 
Brian {Hamilton Kelly}                                         bhk@dsl.co.uk
        "The fundamental design flaws [of the products of the Micros^WSirius
        Cybernetics Corporation]  are completely hidden by their superficial
        design flaws."  SLATFATF 1983 --- wasn't Douglas Adams prescient?:-)

Brian {Hamilton Kelly} wrote in message <895935979snz@dsl.co.uk>...
>In article <895794411.6884.0.nnrp-07.c1eddda8@news.demon.co.uk>
>
>Unless I've missed it, I haven't noticed anyone suggest that this modem
>might be a dreaded WinModem type of device: if so, it certainly won't
>work (until it's been "spoken to" by Windoze [in your case WinOS/2]
>first).  Is this a possibility?
>
>--
>Brian {Hamilton Kelly}
bhk@dsl.co.uk
>        "The fundamental design flaws [of the products of the
Micros^WSirius
>        Cybernetics Corporation]  are completely hidden by their
superficial
>        design flaws."  SLATFATF 1983 --- wasn't Douglas Adams
prescient?:-)
>

Brian,

It looks as if this is the case, although Windows 95 and 3.11 seem to
configure the modem in a different way to each other.  If I reboot after
configuring the modem in Windows 3.11, the BIOS and OS/2 can see
COM port 3 on IRQ 5. Windows 95 doesn't do that.

Maybe that's the only way it will work - I'll have to boot up into Windows
3.11 then reboot into OS/2.  I don't use Win/OS2 although I might have to!
It annoying because I would like to delete the partition containing Windows
3.11 to make room for OS/2 Warp 4 (I'm currently running version 3).

I'm not going to get Warp 4 until I can get the modem to work.
I suppose the other alternative is to change the modem, but it's only six
months old!

Pete

Pete Bown wrote:
> 
> Brian,
> 
> It looks as if this is the case, although Windows 95 and 3.11 seem to
> configure the modem in a different way to each other.  If I reboot after
> configuring the modem in Windows 3.11, the BIOS and OS/2 can see
> COM port 3 on IRQ 5. Windows 95 doesn't do that.

Ah, the BIOS - The default for COM3 is at 3E8 and IRQ 4, isn't it? Maybe
you need to change your BIOS settings, you seem to be implying that the
modem is only recognised by the BIOS after some utility has been run
(which only runs under Windows 3.11).

> 
> Maybe that's the only way it will work - I'll have to boot up into Windows
> 3.11 then reboot into OS/2.  I don't use Win/OS2 although I might have to!
> It annoying because I would like to delete the partition containing Windows
> 3.11 to make room for OS/2 Warp 4 (I'm currently running version 3).

Pity the DOS SETMODEM.EXE utility from their web site checks to see if
'Win95' is running, or else you may have been able to run that in a Dos
box in OS2.

What is the reason you don't run WinOS2, out of interest?  

> 
> I'm not going to get Warp 4 until I can get the modem to work.
> I suppose the other alternative is to change the modem, but it's only six
> months old!
> 

Warp 4 has support for plug and pray.

> Pete

There is no mention of the modem on the device driver web site though...
http://service.software.ibm.com/os2ddpak/html/index.htm

Regards,
Tim

Brian {Hamilton Kelly} wrote:
> 
> Unless I've missed it, I haven't noticed anyone suggest that this modem
> might be a dreaded WinModem type of device: if so, it certainly won't
> work (until it's been "spoken to" by Windoze [in your case WinOS/2]
> first).  Is this a possibility?
> 

If this was a winmodem, it would only work in Win95, not 3.1, NT, OS2,
BE, Linux, .. .. ..

Regards,
Tim.