Re: [Freedos-user] Dial-up emulation?

[Frantisek Rysanek via Freedos-user]

Here is a neat summary of the DOS PPP drivers:
http://www.oldskool.org/guides/tvdog/internet.html#I

...but, someone has already raised this question:
Do you have a "counterpart"?
I mean - a dial-in service answering with a modem and a PPP stack.
Or at least a null-modem connection to a PPP "server", such as pppd 
running on Linux. Or possibly Windows running the "server side of 
RAS" would work too.

You have mentioned that one of the PC emulators contains a "Hayes 
modem emulation". What is the use for that, exactly? What does it do?
Suggestion: it answers to a few AT commands, including ATD, to which 
it responds with CONNECT, and puts you through onto a serial line - 
either a physical outside COM port, or e.g. an emulated virtual COM 
port in your host OS (where the emulator / VM is running).

This might be useful to bamboozle some old DOS software, that insists 
on dialing out a modem (when accessing a serial line for whatever 
final purpose) - while in reality all you have is a null-modem cable, 
or a virtual equivalent thereof.

The other option would be, that the "modem emulator" also provides 
the "server side PPP stack", effectively to set up a network 
connection, probably TCP/IP (although in principle, PPP can 
encapsulate other L3 protocols, such as Novell IPX/SPX or MS NetBEUI 
if I have all the ancient buzzwords right).

Note that theoretically, at some sub-layers, PPP is really 
symmetrical, a conversation between equal parties. The client/server 
distinction stems from one party asking the other to authenticate, 
again using a modular mechanism supporting several protocols. For 
your practical purposes, these details are somewhat esoteric...
Should you be interested, try reading RFC1661.

If you don't insist on PPP / dial-up, and you really mean "I want to 
open Google in Arachne", just go down the "packet driver" route. You 
will save yourself quite a bit of hassle (configuring PPP).
If OTOH it is the pain that you are after, go ahead with PPP client 
side and server side :-) and the follow-up networking stuff on the 
server part.

Frank

> 
> I'm not looking for anything out of Qmodem specifically. I'm 
> searching for a TSR that handles dial-up networking in the background 
> while I use TCP/IP utilities like PING, TRACERT and FTP; and/or a web 
> browser like Arachne.
> 
> Brandon Taylor
> 
> 
> From: Frantisek Rysanek 
> Sent: Wednesday, April 24, 2024 4:52 PM
> To: Brandon Taylor via Freedos-user 
> 
> Cc: Brandon Taylor 
> Subject: Re: [Freedos-user] Dial-up emulation? 
> 
> Hello there Brandon,
> 
> to me the key question is - what do you expect of Qmodem?
> What would you like to achieve in / by using that program?
> I've never used it, but I figure it would be a "terminal emulator"
> with some added candy. An analog (predecessor, really) of Putty or
> Hyperterminal in Windows.
> 
> A terminal was originally a hardware device, having a screen and a
> keyboard. I believe the rows of text on the screen were an evolution
> / innovation after line printers. The text no longer rolled on paper,
> now it rolled on a screen. The terminal needed to connect to
> something, typically a relatively large computer (like an early UNIX
> or mainframe machine), and the computer presented a command-line
> interface to the user using that terminal. A single server could
> cater for several terminals simultaneously, already back then.
> 
> Later, when PC's and other computers became common-place, the
> so-called "terminal emulator" programs allowed you to use your PC
> (which is a pretty versatile computer) as a dumb terminal = to
> display what arrived by an RS232 serial line, and to send your
> keystrokes to the opposite party. You can actually connect two
> terminals (or emulators) together over a cross-over RS232 line (also
> called a Null Modem) and chat with each other...
> 
> A modem is a device that originally allowed two parties to connect
> over a phonecall, via the POTS/PSTN (telephone network). You first
> needed to talk to your modem a little, to have it dial out the call.
> If the call got picked up by an opposite modem, the two modems would
> establish a "virtual serial line" spanning potentially hundreds of
> kilometers. You could then chat or transfer files with a friend
> (terminal emulators supported file transfer protocols such as X-modem
> and Z-modem), or there were machines called "bulettin board systems",
> nowadays I'd call them early servers, that you could dial into to
> download or upload files, maybe do a bit of messaging... I don't
> really have much of a clue what these could do, because this was
> before I got my hands on a PC with a modem :-) Obviously you could
> dial in remotely into a UNIX machine and work in its command line
> "shell" = work with files, read and send e-mail, use NNTP newsgroups
> and whatnot.
> All of the above was possible using a PC with a modem and a terminal
> emulator - I assume your Qmodem belongs to this category.
> I wouldn't call this 

Re: [Freedos-user] Dial-up emulation?

[tsiegel--- via Freedos-user]

On 4/24/2024 11:33 PM, Brandon Taylor via Freedos-user wrote:
I'm not looking for anything out of Qmodem specifically. I'm searching 
for a TSR that handles dial-up networking in the background while I 
use TCP/IP utilities like PING, TRACERT and FTP; and/or a web browser 
like Arachne.



In that case, what you need is one of two things.

either the crin packet drivers (already mentioned by Frank), which is 
probably the most useful option here,


or

something like rlfossil which pretends to be a fossil driver, that 
allows your programs to pretend to dial out to the internet even though 
none of that is necessary.  Both have their advantages, depending on 
what you're doing, but it sounds like for you, the packet drivers are 
what you want/need.  With those loaded, and configured properly, you 
should be able to run your other software as desired without worrying 
about the connection at all.


The key words here are configured properly, because there are separate 
configuration items for software that uses a config file to read it's 
options (like some dos software does), and those that expect the 
connection to already be live when you open them.


For what it's worth, there is actually a third option, you can run a 
program that contains multiple protocols built in already. there are 
programs that do this, but they were pretty nitch programs.  There's 
also something like KA9Q which was a piece of software that could turn 
your dos box into an internet server, providing things like email, ftp, 
early web access (I believe they only support version 1.0 of the http 
protocol).   but it doesn't sound like a server is what you're after.


For your case, (as mentioned above), you'll most likely want to load the 
packet driver associated with your network card (most can pretend to be 
a ne2000 card, so just try that driver first, if it works, then you 
won't need to play around with anything else. Many 3com cards are also 
emulated these days, so if the ne2000 driver doesn't work, try the 
various 3com ones, one of those may do the trick for you.


I can't recall the name of it now, but there was a package someone put 
together to allow you to use your packet driver to make the connection, 
then drop back to dos, with batch files to run the various programs, 
including ftp, email, and web browsing (using archne browser (apologies 
if I get any of the names wrong, it's been a while).


If you want to go the fossil driver route, then you can use qmodem, but 
unless you're connecting to another machine (such as a shell account), 
this will be of extreme limited use/capabily.  To use the rlfossil 
driver, you just type atdt  and it will make a telnet 
connection to the hostname of choice (you can provide a port number as 
well).  This was handy for playing muds back then, or for logging into a 
unix shell, but beyond that, it's use was pretty much useless, but it's 
there if you want to mess around with it.


This is likely more information than you needed, but maybe something in 
here will trigger some wish to experiment or something.


Basically, the packet drivers are what you want unless you want to do 
something specific that isn't covered by their use.


I.E. running nettamer for irc chatting.

Hope this helps, and good luck making it all work. I wish I still had a 
real dos machine operational, but I lost my last one in a forced move a 
bit over 2 years ago, so I can't actually try any of this stuff anymore 
sadly.



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-up emulation?

[Brandon Taylor via Freedos-user]

I'm not looking for anything out of Qmodem specifically. I'm searching for a 
TSR that handles dial-up networking in the background while I use TCP/IP 
utilities like PING, TRACERT and FTP; and/or a web browser like Arachne.

Brandon Taylor

From: Frantisek Rysanek 
Sent: Wednesday, April 24, 2024 4:52 PM
To: Brandon Taylor via Freedos-user 
Cc: Brandon Taylor 
Subject: Re: [Freedos-user] Dial-up emulation?

Hello there Brandon,

to me the key question is - what do you expect of Qmodem?
What would you like to achieve in / by using that program?
I've never used it, but I figure it would be a "terminal emulator"
with some added candy. An analog (predecessor, really) of Putty or
Hyperterminal in Windows.

A terminal was originally a hardware device, having a screen and a
keyboard. I believe the rows of text on the screen were an evolution
/ innovation after line printers. The text no longer rolled on paper,
now it rolled on a screen. The terminal needed to connect to
something, typically a relatively large computer (like an early UNIX
or mainframe machine), and the computer presented a command-line
interface to the user using that terminal. A single server could
cater for several terminals simultaneously, already back then.

Later, when PC's and other computers became common-place, the
so-called "terminal emulator" programs allowed you to use your PC
(which is a pretty versatile computer) as a dumb terminal = to
display what arrived by an RS232 serial line, and to send your
keystrokes to the opposite party. You can actually connect two
terminals (or emulators) together over a cross-over RS232 line (also
called a Null Modem) and chat with each other...

A modem is a device that originally allowed two parties to connect
over a phonecall, via the POTS/PSTN (telephone network). You first
needed to talk to your modem a little, to have it dial out the call.
If the call got picked up by an opposite modem, the two modems would
establish a "virtual serial line" spanning potentially hundreds of
kilometers. You could then chat or transfer files with a friend
(terminal emulators supported file transfer protocols such as X-modem
and Z-modem), or there were machines called "bulettin board systems",
nowadays I'd call them early servers, that you could dial into to
download or upload files, maybe do a bit of messaging... I don't
really have much of a clue what these could do, because this was
before I got my hands on a PC with a modem :-) Obviously you could
dial in remotely into a UNIX machine and work in its command line
"shell" = work with files, read and send e-mail, use NNTP newsgroups
and whatnot.
All of the above was possible using a PC with a modem and a terminal
emulator - I assume your Qmodem belongs to this category.
I wouldn't call this usage style "the internet", except maybe in a
very broad sense :-)

RS232-style async serial lines, and their modem-based long-distance
extensions, were also useful for other styles of traffic.

As a side note, I'd mention UUCP, as a distributed worldwide e-mail
system, predating TCP/IP-based SMTP (in practical popularity, if not
by actual age). There were in fact several e-mail standards before
SMTP, and UUCP was one of them. UUCP was an "open standard" - unlike
other e-mail protocols/systems that were proprietary.

RS232-style direct lines and modem connections can also be used to
transport TCP/IP - in case this is what you mean by "internet".
To "encapsulate" IP packets over an async serial line, you need an
intermediate layer, called a "layer 2 protocol" (IP is layer 3).
See also the layered ISO/OSI networking model (of which the Internet
is not a verbatim implementation).
So for serial links, there were two popular L2 protocols: SLIP and
PPP. During that era, PPP pretty much took over - being generally
more advanced / flexible / extensible... more suitable to the age of
mammoth modem pools and dial-up internet access.

To start PPP, you generally need two things:

1) a piece of software that talks to the modem, to make it dial a
number, and wait for the modem to establish connection (the modem
reports CONNECT  and maybe some further info).
You can do this by hand in a terminal emulator, or by a script, or by
a dedicated unattended piece of software called a "dialer".

2) an implementation of PPP. After you dial the modem connection, you
need a way to hand over the established modem session to a PPP
"driver" (protocol talker).

On top of PPP, you can then run a TCP/IP stack, which in turn gets
used by "internet" applications such as e-mail clients, web browsers,
FTP clients and whatnot (you can also run a server with a PPP
connection to the internet).

For instance, Windows since 95 have an ex-works "connection software"
called "Microsoft Dial-Up Networking" (if memory serves) or RAS in
the NT-based Windows - which combines an unattended dialer + PPP
stack, and can transport TCP/IP (or other protocols) over that.

You can also run PPP over a 

Re: [Freedos-user] Dial-up emulation?

[Frantisek Rysanek via Freedos-user]

Hello there Brandon,

to me the key question is - what do you expect of Qmodem?
What would you like to achieve in / by using that program?
I've never used it, but I figure it would be a "terminal emulator" 
with some added candy. An analog (predecessor, really) of Putty or 
Hyperterminal in Windows.

A terminal was originally a hardware device, having a screen and a 
keyboard. I believe the rows of text on the screen were an evolution 
/ innovation after line printers. The text no longer rolled on paper, 
now it rolled on a screen. The terminal needed to connect to 
something, typically a relatively large computer (like an early UNIX 
or mainframe machine), and the computer presented a command-line 
interface to the user using that terminal. A single server could 
cater for several terminals simultaneously, already back then.

Later, when PC's and other computers became common-place, the 
so-called "terminal emulator" programs allowed you to use your PC 
(which is a pretty versatile computer) as a dumb terminal = to 
display what arrived by an RS232 serial line, and to send your 
keystrokes to the opposite party. You can actually connect two 
terminals (or emulators) together over a cross-over RS232 line (also 
called a Null Modem) and chat with each other...

A modem is a device that originally allowed two parties to connect 
over a phonecall, via the POTS/PSTN (telephone network). You first 
needed to talk to your modem a little, to have it dial out the call. 
If the call got picked up by an opposite modem, the two modems would 
establish a "virtual serial line" spanning potentially hundreds of 
kilometers. You could then chat or transfer files with a friend 
(terminal emulators supported file transfer protocols such as X-modem 
and Z-modem), or there were machines called "bulettin board systems", 
nowadays I'd call them early servers, that you could dial into to 
download or upload files, maybe do a bit of messaging... I don't 
really have much of a clue what these could do, because this was 
before I got my hands on a PC with a modem :-) Obviously you could 
dial in remotely into a UNIX machine and work in its command line 
"shell" = work with files, read and send e-mail, use NNTP newsgroups 
and whatnot.
All of the above was possible using a PC with a modem and a terminal 
emulator - I assume your Qmodem belongs to this category.
I wouldn't call this usage style "the internet", except maybe in a 
very broad sense :-)

RS232-style async serial lines, and their modem-based long-distance 
extensions, were also useful for other styles of traffic.

As a side note, I'd mention UUCP, as a distributed worldwide e-mail 
system, predating TCP/IP-based SMTP (in practical popularity, if not 
by actual age). There were in fact several e-mail standards before 
SMTP, and UUCP was one of them. UUCP was an "open standard" - unlike 
other e-mail protocols/systems that were proprietary.

RS232-style direct lines and modem connections can also be used to 
transport TCP/IP - in case this is what you mean by "internet".
To "encapsulate" IP packets over an async serial line, you need an 
intermediate layer, called a "layer 2 protocol" (IP is layer 3).
See also the layered ISO/OSI networking model (of which the Internet 
is not a verbatim implementation).
So for serial links, there were two popular L2 protocols: SLIP and 
PPP. During that era, PPP pretty much took over - being generally 
more advanced / flexible / extensible... more suitable to the age of 
mammoth modem pools and dial-up internet access.

To start PPP, you generally need two things:

1) a piece of software that talks to the modem, to make it dial a 
number, and wait for the modem to establish connection (the modem 
reports CONNECT  and maybe some further info).
You can do this by hand in a terminal emulator, or by a script, or by 
a dedicated unattended piece of software called a "dialer".

2) an implementation of PPP. After you dial the modem connection, you 
need a way to hand over the established modem session to a PPP 
"driver" (protocol talker).

On top of PPP, you can then run a TCP/IP stack, which in turn gets 
used by "internet" applications such as e-mail clients, web browsers, 
FTP clients and whatnot (you can also run a server with a PPP 
connection to the internet).

For instance, Windows since 95 have an ex-works "connection software" 
called "Microsoft Dial-Up Networking" (if memory serves) or RAS in 
the NT-based Windows - which combines an unattended dialer + PPP 
stack, and can transport TCP/IP (or other protocols) over that.

You can also run PPP over a direct RS232 connection (null modem) or 
over a pair of leased-line modems. Async serial modems in leased line 
mode create a permanent connection, and do not respond to Hayes AT 
commands. In these cases, you do not need a dialer (item 1 above).

As for Internet in DOS:

Both MS-DOS and FreeDOS can connect to the internet.
But, the first question is, what sort of "experience" you expect 

Re: [Freedos-user] Dial-up emulation

[Jose Senna via Freedos-user]

 Tomas said:
 > network card =/= modem

 I never said nor implied they are the same.
 I said that, if an user has a machine with a network card,
 and a suitable DOS driver for the card is available, he/she
 may use it, instead of setting a dial-up connection.



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-uo emulation ?

[Tomas By via Freedos-user]

On Wed, 24 Apr 2024 21:59:00 +0200, Jose Senna via Freedos-user wrote:
> Anyway, you will still need a modem driver for DOS. There used to be
> many of them in old software repositories as the Crynwr collection.


Network card =/= modem.

/Tomas


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-up emulation?

[Brandon Taylor via Freedos-user]

My apologies for the confusion. I know FreeDOS has internet capability, but not 
on 86Box, since FreeDOS for some reason treats 86Box as if it were a real 
computer.

Get Outlook for Android

From: Robert Riebisch via Freedos-user 
Sent: Wednesday, April 24, 2024 2:04:17 PM
To: freedos-user@lists.sourceforge.net 
Cc: Robert Riebisch 
Subject: Re: [Freedos-user] Dial-up emulation?

Hi Brandon,

> Since FreeDOS doesn't support physical network hardware (even if it's
> emulated in a program like PCem or 86Box), I figure there's no way
> FreeDOS is gonna be able to connect to the Internet, right? Well...

Says who?

Cheers,
Robert
--
BTTR Software   https://www.bttr-software.de/
DOS ain't dead  https://www.bttr-software.de/forum/


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-uo emulation ?

[Brandon Taylor via Freedos-user]

I didn't grow up on that part of DOS. I know basic commands like DIR, COPY, 
TYPE etc., but all this talk about DOS drivers bamboozles me.

Get Outlook for Android

From: Jose Senna via Freedos-user 
Sent: Wednesday, April 24, 2024 2:59:00 PM
To: FreeDOS users 
Cc: Jose Senna 
Subject: Re: [Freedos-user] Dial-uo emulation ?

Brandon Taylor said:

 > Well, I did find a nice package in the
 > FreeDOS repository called LSPPP. Would that work better?

  It shall work if you have an internet service
 provider that supports a PPP connection.
  Anyway, you will still need a modem driver for
 DOS. There used to be many of them in old
 software repositories as the Crynwr collection.
  It seems that you already have internet access.
 If it is by an Ethernet LAN through a gateway,
 you may use it under DOS too. You will need
 a DOS device driver for your Ethernet card.
 A difference between DOS and Windows or Linux
is that DOS does not autodetects nor autoinstalls
hardware drivers. Nor are DOS hardware drivers
the same used by other O/Ss; you have to find
and install them yourself.
 Excuse me if I am attempting to explain the obvious,
but it also seems that you are a newbie to DOS.



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-uo emulation ?

[Jose Senna via Freedos-user]

Brandon Taylor said:

 > Well, I did find a nice package in the
 > FreeDOS repository called LSPPP. Would that work better?

  It shall work if you have an internet service
 provider that supports a PPP connection.
  Anyway, you will still need a modem driver for
 DOS. There used to be many of them in old
 software repositories as the Crynwr collection.
  It seems that you already have internet access.
 If it is by an Ethernet LAN through a gateway,
 you may use it under DOS too. You will need
 a DOS device driver for your Ethernet card.
 A difference between DOS and Windows or Linux
is that DOS does not autodetects nor autoinstalls
hardware drivers. Nor are DOS hardware drivers
the same used by other O/Ss; you have to find
and install them yourself.
 Excuse me if I am attempting to explain the obvious,
but it also seems that you are a newbie to DOS.



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-up emulation?

[Tomas By via Freedos-user]

On Wed, 24 Apr 2024 21:08:49 +0200, Michał Dec via Freedos-user wrote:
> So I would try to get regular DOS drivers for that modem if I were you.


There were no DOS drivers for modems? There were "winmodems" that
needed drivers, maybe that is what you are thinking of.

/Tomas


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-up emulation?

[Michał Dec via Freedos-user]

> Since FreeDOS doesn't support physical network hardware (even if it's 
emulated in a program like PCem or 86Box), I figure there's no way 
FreeDOS is gonna be able to connect to the Internet, right? Well...


Lol. Lmao, even. I did manage to connect my FreeDOS to the Internet at 
some point but it's not as glamorous as one would think.


> The developers of the 86Box project have recently implemented 
emulation of a Hayes-compatible dial-up modem. So my question is... will 
FreeDOS support the emulated modem?


This isn't FreeDOS' scope. If that modem has DOS drivers, then since it 
falls into FD's scope to be ABI-compatible with Microsoft DOS up to and 
including 6.22, supporting that modem and therefore its drivers is a 
welcome and in fact intended consequence of this rigid scope. So I would 
try to get regular DOS drivers for that modem if I were you. Best of luck.


Best regards,

Michał Dec



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-up emulation?

[Robert Riebisch via Freedos-user]

Hi Brandon,

> Since FreeDOS doesn't support physical network hardware (even if it's
> emulated in a program like PCem or 86Box), I figure there's no way
> FreeDOS is gonna be able to connect to the Internet, right? Well...

Says who?

Cheers,
Robert
-- 
BTTR Software   https://www.bttr-software.de/
DOS ain't dead  https://www.bttr-software.de/forum/


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-up emulation?

[Brandon Taylor via Freedos-user]

Well, I did find a nice package in the FreeDOS repository called LSPPP. Would 
that work better?

Get Outlook for Android

From: tom ehlert via Freedos-user 
Sent: Wednesday, April 24, 2024 11:48:03 AM
To: Discussion and general questions about FreeDOS. 

Cc: tom ehlert 
Subject: Re: [Freedos-user] Dial-up emulation?


> Indeed, I'm using an old-school program called Qmodem.

>  My question now is – would I be able to use the Internet using the emulated 
> modem?
yes (if you had any idea what you are doing). But definitively not with QMODEM.

Tom


> Brandon Taylor
> 
> From: Jim Hall via Freedos-user 
> Sent: Tuesday, April 23, 2024 10:12 PM
> To: Discussion and general questions about FreeDOS. 
> 
> Cc: Jim Hall 
> Subject: Re: [Freedos-user] Dial-up emulation?



> On Tue, Apr 23, 2024, 9:38 PM Brandon Taylor via Freedos-user 
> mailto:freedos-user@lists.sourceforge.net>>
>  wrote:
> Since FreeDOS doesn't support physical network hardware (even if it's 
> emulated in a program like PCem or 86Box), I figure there's no way FreeDOS is 
> gonna be able to connect to the Internet, right? Well...

> The developers of the 86Box project have recently implemented emulation of a 
> Hayes-compatible dial-up modem. So my question is... will FreeDOS support the 
> emulated modem?


> Well, it's not that "FreeDOS" would support the Hayes modern, but that 
> terminal/dialer software would then be able to. FreeDOS is not like Linux, 
> which uses a Hardware Abstraction Layer (HAL) to support the hardware 
> directly. FreeDOS, like any DOS, does normal DOS things and leaves certain 
> hardware access (like playing sounds through a sound card, or accessing a 
> network to browse the web or check email, or dialing out through a modem) to 
> other software.

> So if you had a terminal/dialer program like Procomm or Telix, then yes, I 
> expect you'd be able to dial out through this emulated Hayes modem from 
> FreeDOS.





___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-up emulation?

[tom ehlert via Freedos-user]

> Indeed, I'm using an old-school program called Qmodem.

>  My question now is – would I be able to use the Internet using the emulated 
> modem?
yes (if you had any idea what you are doing). But definitively not with QMODEM.

Tom


> Brandon Taylor
> 
> From: Jim Hall via Freedos-user 
> Sent: Tuesday, April 23, 2024 10:12 PM
> To: Discussion and general questions about FreeDOS. 
> 
> Cc: Jim Hall 
> Subject: Re: [Freedos-user] Dial-up emulation?



> On Tue, Apr 23, 2024, 9:38 PM Brandon Taylor via Freedos-user 
> mailto:freedos-user@lists.sourceforge.net>>
>  wrote:
> Since FreeDOS doesn't support physical network hardware (even if it's 
> emulated in a program like PCem or 86Box), I figure there's no way FreeDOS is 
> gonna be able to connect to the Internet, right? Well...

> The developers of the 86Box project have recently implemented emulation of a 
> Hayes-compatible dial-up modem. So my question is... will FreeDOS support the 
> emulated modem?


> Well, it's not that "FreeDOS" would support the Hayes modern, but that 
> terminal/dialer software would then be able to. FreeDOS is not like Linux, 
> which uses a Hardware Abstraction Layer (HAL) to support the hardware 
> directly. FreeDOS, like any DOS, does normal DOS things and leaves certain 
> hardware access (like playing sounds through a sound card, or accessing a 
> network to browse the web or check email, or dialing out through a modem) to 
> other software.

> So if you had a terminal/dialer program like Procomm or Telix, then yes, I 
> expect you'd be able to dial out through this emulated Hayes modem from 
> FreeDOS.





___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Dial-up emulation?

[Brandon Taylor via Freedos-user]

Indeed, I'm using an old-school program called Qmodem. My question now is – 
would I be able to use the Internet using the emulated modem?

Brandon Taylor

From: Jim Hall via Freedos-user 
Sent: Tuesday, April 23, 2024 10:12 PM
To: Discussion and general questions about FreeDOS. 

Cc: Jim Hall 
Subject: Re: [Freedos-user] Dial-up emulation?



On Tue, Apr 23, 2024, 9:38 PM Brandon Taylor via Freedos-user 
mailto:freedos-user@lists.sourceforge.net>> 
wrote:
Since FreeDOS doesn't support physical network hardware (even if it's emulated 
in a program like PCem or 86Box), I figure there's no way FreeDOS is gonna be 
able to connect to the Internet, right? Well...

The developers of the 86Box project have recently implemented emulation of a 
Hayes-compatible dial-up modem. So my question is... will FreeDOS support the 
emulated modem?


Well, it's not that "FreeDOS" would support the Hayes modern, but that 
terminal/dialer software would then be able to. FreeDOS is not like Linux, 
which uses a Hardware Abstraction Layer (HAL) to support the hardware directly. 
FreeDOS, like any DOS, does normal DOS things and leaves certain hardware 
access (like playing sounds through a sound card, or accessing a network to 
browse the web or check email, or dialing out through a modem) to other 
software.

So if you had a terminal/dialer program like Procomm or Telix, then yes, I 
expect you'd be able to dial out through this emulated Hayes modem from FreeDOS.
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user