That I am not sure of. My only experience with OS/2 is with a 386 or better. Seems to me that some sysops were using VMODEM long before OS/2 Warp was released, though.
You couldn't as you needed the "conenct" package from OS/2 Warp v3
Connect to
use it via telnet. As a virtual com port, I'm not sure if Ray had any
use for
Hopefully someone else here will have a better answer. That said, it sounds like you found a version of Procomm that runs well with Windows. Procomm (for DOS) was another program I used a lot early in my days of bbsing.
kirkspragg wrote to MIKE POWELL <=-
I briefly tired procomm for dos but like most terminal clients it does
not do telnet, com port/modem only as far as I could tell from my brief experiments.
³ Regarding you suggetsion to use OS/2 & VMODEM, is this likely goingÀÄ[K=>> MP]
to work
³ with early verions of OS/2 (i.e. the ones that will run on a 286) or
am I
³ would I need to use 386+ class machine & a later version of OS/2.
That I am not sure of. My only experience with OS/2 is with a 386 or better. Seems to me that some sysops were using VMODEM long before
OS/2 Warp was released, though.
Hopefully someone else here will have a better answer.
telnet://bbs.roonsbbs.hu:1212 <<=-
I thought there was a DOS FOSSIL that talked TCP/IP? Procomm Plus does support FOSSIL and int14, two means of redirecting modem ports.
I thought there was a DOS FOSSIL that talked TCP/IP? Procomm Plus does support FOSSIL and int14, two means of redirecting modem ports.
If you find one that uses ethernet instead of WiFi, let us know.
I remember getting my first 16550 and being so happy that I could finally use my new 14.4k modem properly. ;)
I do wonder now what UART these USB-to-Serial cables are using (or emulating). It must be something smaller than the original chipsets. Based on experience, I strongly suspect they are in the OK to bad category, unfortunately.
I've wondered the same thing. But I've had the thought
that technology has advanced a bit since then, and
hopefully they'd be able to fit a good enough UART into
the space available for USB-to-serial cables. Unless
the manufacturer is being really cheap, I'd see no
reason not to use a 16550 (or equivalent/better) in
those USB-to-serial cables.
I've wondered the same thing. But I've had the thought
that technology has advanced a bit since then, and
hopefully they'd be able to fit a good enough UART into
the space available for USB-to-serial cables. Unless
the manufacturer is being really cheap, I'd see no
reason not to use a 16550 (or equivalent/better) in
those USB-to-serial cables.
The 16550 has a 16 byte buffer. An FTDI FT232R USB-to-serial IC has a
128 byte receive buffer. So in some ways, the USB-to-serial cables
are more capable than 16550 UARTs. There are other USB-to-serial ICs,
but FTDI is kind of the 'gold standard' and others I've looked at at similar specs.
A downside to USB-to-serial cables is that they use USB instead of
being connected directly to the bus like a 16550 is. So there is some latency between the data being received by the USB-to-serial cable and
it being received by the software on the PC itself due to the USB
protocol. The throughput is great, but in some cases the latency can
be a problem. Usually for modem use it's fine, but some other serial devices can be thrown off by the added latency of USB.
telnet://bbs.roonsbbs.hu:1212 <<=-
A downside to USB-to-serial cables is that they use USB instead of
being connected directly to the bus like a 16550 is. So there is some latency between the data being received by the USB-to-serial cable and
it being received by the software on the PC itself due to the USB
protocol. The throughput is great, but in some cases the latency can
be a problem. Usually for modem use it's fine, but some other serial devices can be thrown off by the added latency of USB.
and one more downside is that they need usb2, they don't
work in usb3 ports :(
/i've learned it in the hard way :)/
I do wonder now what UART these USB-to-Serial cables are using (or emulating). It must be something smaller than the original chipsets. Based on experience, I strongly suspect they are in the OK to bad category, unfortunately.
A downside to USB-to-serial cables is that they use USB instead of
being connected directly to the bus like a 16550 is. So there is
some latency between the data being received by the USB-to-serial
cable and it being received by the software on the PC itself due
to the USB protocol. The throughput is great, but in some cases
the latency can be a problem. Usually for modem use it's fine,
but some other serial devices can be thrown off by the added
latency of USB.
and one more downside is that they need usb2, they don't
work in usb3 ports :(
/i've learned it in the hard way :)/
I thought USB3 was supposed to be backward compatible, I would say I
am surprised it's a problem but then again USB can throw some weird
shit at you sometimes.
Speaking of weird USB stuff - I have a USB to ISA interface from ARS Technologies, it's an interesting device but definitely not plug n play.http://arstech.com/install/ecom-prodshow/usb2isax3.html
telnet://bbs.roonsbbs.hu:1212 <<=-
A downside to USB-to-serial cables is that they use USB instead of being connected directly to the bus like a 16550 is. So there is some latency between the data being received by the USB-to-serial cable and it being received by the software on the PC itself due to the USB protocol. The throughput is great, but in some cases the latency can be a problem. Usually for modem use it's fine, but some other serial devices can be thrown off by the added latency of USB.
A downside to USB-to-serial cables is that they use USB instead of being
connected directly to the bus like a 16550 is. So there is some latency
and one more downside is that they need usb2, they don't work in usb3 ports :( /i've learned it in the hard way :)/
I've wondered about latency sometimes and have wondered why there often isn't something directly connected to the bus for things like serial
ports & such these days. I often see things like USB MIDI adapters, USB headsets & microphones, and latency probably does play a role in those, but it seems those are good enough for many situations..
can't really speak for every manufacturer but my ASUS X570 motherboard still has a serial port on it. just need a breakout cable and a slot cover with the serial plug itself to get out to the outside of the case.. my ham radio is connected to mine. there are probably others brands that have this. and if you really need it there are 2 port pci express serial cards (or more!) on amazon.
Usually for modem use it's fine, but some other serial devices can be thrown off by the added latency of USB.
I've wondered about latency sometimes and have wondered
why there often isn't something directly connected to
the bus for things like serial ports & such these days.
I often see things like USB MIDI adapters, USB headsets
& microphones, and latency probably does play a role in
those, but it seems those are good enough for many situations..
A downside to USB-to-serial cables is that they use USB instead
of being connected directly to the bus like a 16550 is. So there
is some latency
and one more downside is that they need usb2, they don't work in
usb3 ports :( /i've learned it in the hard way :)/
Really? I thought USB3 was supposed to be backwards-compatible. I'm pretty sure I've plugged USB2 devices into USB3 ports and I thought
they worked.
telnet://bbs.roonsbbs.hu:1212 <<=-
can't really speak for every manufacturer but my ASUS X570 motherboar still has a serial port on it. just need a breakout cable and a slot
port on the back of the PC. I'm not using it now, but I remember it looked like that serial port on the motherboard is connected to the USB bus..
It is still possible - you can get PCIe serial (and parallel) interfaces (if you have an available PCIe slot). It does seem fairly niche these days though.
I've got a PCIe parallel port card in my main Win 10 PC.
With a bit of fiddling it was possible to configure
Dosbox-X to use the parallel port directly & map it to
dos LPT1.
Has been very useful that. Can run fastlynx/Laplink on
my main PC & have my main PCs large hard drive mounted
in & then use fastlynx to copy stuff from it to my retro
PCs via a parallel port laplink cable.
That's a great way to transfer files to retro PCs! What kind of speed
do you get using fastlynx? I used Laplink but only a little bit and
it's been decades, so I don't really recall the speed of it either.
Your setup sounds great for pulling the files you want from your collection to your retro PC, when you want the files.
Nightfox wrote to Roon <=-
Really? I thought USB3 was supposed to be backwards-compatible. I'm pretty sure I've plugged USB2 devices into USB3 ports and I thought
they worked.
fusion wrote to Nightfox <=-
yeah, mine is specifically a real serial port, not a USB one bodged
onto the motherboard.
AKAcastor wrote to Kirkspragg <=-
That's a great way to transfer files to retro PCs! What kind of speed
do you get using fastlynx? I used Laplink but only a little bit and
it's been decades, so I don't really recall the speed of it either.
Your setup sounds great for pulling the files you want from your collection to your retro PC, when you want the files.
I get 40-50 kB/s (kilobytes per sec) with fastlynx. I no
longer use laplink due to consistent issues I've had
with stability. For short transfers its fine, but
anything that needs more that 20-30 minutes is almost
guaranteed to either stall or crash outright - sometimes
requiring a full power off and on cycle (at both ends)
to get everything up and running again, somehow when it
breaks it can really mess with your parallel/com ports.
If you interested I can give you more detailed info on
how to set this up with dosbox-x on windows. Main things
to do are to ensure you get your PCI-E parallel port's
IO addresses from the device manager (these are unlikely
to be the standard DOS LPT1/2 IO addresses) and use
those when configuring the the LTP pass-through with Dosbox-x.
Computer hobbyists are notorious for hoarding cables. I know I've gone through my phases.
When I moved the last time, I did a reckoning of my cable stash, and tossed parallel cables, old SCSI-1 cables and terminators, IDE cables, weird PS/2 to serial dongles, and even an old joystick with that weird connector.
The one cable I would NOT part with? A Laplink DB9 to DB9 null modem cable. I'm sure someday I'll need it. :)
I used Laplink with an HP Omnibook 300, a weird little laptop with a reflective screen, Windows 3.1 in ROM, and insane battery life. It could run on AA batteries in a pinch.
I am not ready at the moment to test the setup, I am familiar enough with dosbox to get the gist of it, but I think it would be great to have detailed information about this as it's such a good way to pull the
files you want to use onto your retro PC and your experience here would
be valuable.
AKAcastor wrote to Poindexter Fortran <=-
When I moved the last time, I did a reckoning of my cable stash, and tossed parallel cables, old SCSI-1 cables and terminators, IDE cables, weird PS/2 to serial dongles, and even an old joystick with that weird connector.
But what if you need another SCSI-1 cable? What then??
That Omnibook 300 sounds like a very neat machine, I have never seen
one, it sounds pretty cool. Based on the laplink cable I guess it had
a proper serial port, would be a great little portable terminal.
I can't given details for how to get this working on
linux as I have only tried this on windows.
1 - Download and install the latest Dosbox-x (dosbox-
x.com), use the installer not the potable version as it
may be missing an the dlls required to access a physical
printer port.
This might work with other software, however I am pretty sure that dosbox-x doesn't pass through hardware interrupt requests thus
anything relying on this won't work or may be very slow -
I believe this is an issue for PLIP.
But what if you need another SCSI-1 cable? What then??
I'd buy a new one.
I have the duality of hoarding cable and not being
able to find them. I'd find myself spending hours looking for a cable
that I could buy a replacement online in 5 minutes. Buying the
replacement then has the benefit of meaning I'd find the original as
soon as I hit "buy".
50 quatloos for using "bodged" in context.
I actually bought some nullmodem adapters within the past few months, to be sure I always have an extra on hand. They're obsolete right up until you need one!
I'd buy a new one. I have the duality of hoarding cable and not being able to find them. I'd find myself spending hours looking for a cable that I could buy a replacement online in 5 minutes.
| Sysop: | Gary Ailes |
|---|---|
| Location: | Pittsburgh, PA |
| Users: | 132 |
| Nodes: | 5 (0 / 5) |
| Uptime: | 66:17:40 |
| Calls: | 733 |
| Files: | 2,171 |
| Messages: | 81,302 |
