Re: modem communication


<manusha@xxxxxxxxxxxxxxxx> wrote in message
news:1133955294.977637.64960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> hi, thank for the reply.
> i always wanted to use sockets for the communications, but there are
> some requrements that makes using sockets difficult ( this is what i
> think).

Like, What?

> the scenario is =>
>
> there will be several PC's with each having a modem and a telephone
> connection. No PC has the internet access. All PC's should have the
> ability to connect to any other PC by just dialing the corresponding
> telephone number. After connected, they need to communicate
> using the TCP/IP protocol. ( i.e i need to use Sockets in the
> communication.). PC's will have Windows Me/98 as the O/s.


Even that sorry pile of duff code wrapped in a GUI could do Sockets, PPP and
at least MSCHAP - a broken-by-microsoft-design version of the chap
protocol - for the dialup/connect part.

I will bet that your main problem will be how to configure the dial-in;
Windows 98 was never much of a Server OS.

Another problem will be how to manage the configuration of the machines;

Static IP adresses of each host that must be entered in one dialog box for
PPP to work (with a reboot at the end), fixed telephone numbers and an
"hosts" file with all the other PC's since you do not have DNS. Default
Gateway should be 0.0.0.0 - that should cause PPP to negotiate an adress
with the other end.


>
>
> (this is similar to what happens with hyperterminal, but i think the
> difference is the protocol used in the communication.)
>
> i guess i can use PPP for this, but this will require atleast windows
> 2000.
>
> please advice me on the path i should choose.
>
> thank you
> CMOS

"FidoNet" actually worked like what you describe. Maybe there is an
implementation?

>


.

Relevant Pages

  • About Process Communication Implementation in Windows.
    ... In the book< Programming Application for miscrosoft windows>: ... These mechanisms[note:Process communication] include RPC, COM, OLE, ... mailslots, pipes, sockets, and so on. ... So the author means that RPC, OLE, OLE DDE, socket etc, they are all ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Why no socket package in the standard ?
    ... If the endpoints of communication are Ada partitions. ... distribution and that is the annex E. ... Because sockets is the most widely used transport. ...
    (comp.lang.ada)
  • Hardware Server
    ... Back in old days before evolution of BSD sockets, ... Communication between tow machines was in fact ... develop an operating system + platform dependent piece of code. ... kernel and an entity (Hardware Server). ...
    (microsoft.public.development.device.drivers)
  • Hardware Server
    ... Back in old days before evolution of BSD sockets, ... Communication between tow machines was in fact ... develop an operating system + platform dependent piece of code. ... kernel and an entity (Hardware Server). ...
    (comp.os.research)
  • Hardware Server
    ... Back in old days before evolution of BSD sockets, ... Communication between tow machines was in fact ... develop an operating system + platform dependent piece of code. ... kernel and an entity (Hardware Server). ...
    (comp.arch.embedded)