Greetings,

I had vmodem working version sio160d (using Sean Dennis's faq) suddenly tho typing vmodem at the prompt no longer starts it. I tried reinstalling, checking all the paths etc, but no dice.. Wondering if some update in arca may have broke it?
--
Regards,


Nitro


... Behind every successful man is an astonished mother-in-law.

NITRO wrote to ALL <=-

I had vmodem working version sio160d (using Sean Dennis's faq) suddenly tho typing vmodem at the prompt no longer starts it. I tried reinstalling, checking all the paths etc, but no dice.. Wondering if
some update in arca may have broke it? --

What is happening when you try to start it up?

I have 1.60d running here as well, never had an issue with vmodem that
I can remember (besides it not being able to handle spam connects).

Kev

--- Telegard/2/QWK v3.09.g2-sp4/mL
* Origin: Razor's Domain/2 BBS (618:200/1)

Hello Kevin!

Monday February 27 2023 08:05, you wrote to Nitro:

* Forwarded from area 'MIN_OS2'

NITRO wrote to ALL <=-

I had vmodem working version sio160d (using Sean Dennis's faq)
suddenly tho typing vmodem at the prompt no longer starts it. I
tried reinstalling, checking all the paths etc, but no dice..
Wondering if some update in arca may have broke it? --

What is happening when you try to start it up?

I have 1.60d running here as well, never had an issue with vmodem that
I can remember (besides it not being able to handle spam connects).

nothing no error, just doesnt start.. Returns to prompt.

Regards,

Rick

... BBSing is like sex, except for not wanting to get off.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (618:300/1)

Hello Rick!

Monday February 27 2023 05:06, Rick Smith wrote to Kevin Nunn:

I have 1.60d running here as well, never had an issue with vmodem
that I can remember (besides it not being able to handle spam
connects).

nothing no error, just doesnt start.. Returns to prompt.

Check POPUPLOG.OS2 on your boot drive; most likely you'll see it crashed in TCP32DLL. If so, it's a conflict between the version of TCP/IP for OS/2 on your system and SIO. The only fix I've found is to use SIO2K instead of SIO.

The technical reason for it is changes that IBM made to TCP/IP, dropping some rather arcane functions that weren't used often, although Ray Gwinn did use them in VMODEM versions for SIO v1.xx. I never did figure out exactly what version of TCP/IP for OS/2 the problem first appeared in. Installing SIO2K in place of SIO has fixed it on every system I've had that problem on.

Andrew

---
* Origin: Bits & Bytes BBS * bnbbbs.net (618:100/1)