Re: TCP/IP for CP/M 2.2
- From: Allison@xxxxxxxxxxxxx
- Date: Sat, 21 Mar 2009 22:21:46 GMT
On Sat, 21 Mar 2009 11:10:44 -0700 (PDT), susowa <susowa.kc85@xxxxxx>
wrote:
Seems trivial enough do you plan to use FTP, SCP, Thppd or if winders
is involved SMB?
FTP - Yes
SCP -No
Thppd - ???
Simple server good for files, outgoing.
SMB - I think this makes no sense (over 100 message-types!), too much
for me :-)
Winders uses that for file transfers via IP.
FYI browsing and seriving files is relly no different to the IP stack
and it's only different to the application layered on it.
I know, technically it isn't a problem but my time is limited. First
the protocols I want use.
as a user there is no $59.99 solution for CP/M, never was. The bit of
networking seen back when (outside of packet radio) was typically
1000-2000 dollare per node and required serious effort to get going.
Far from PC stle plug and play.
Our KC85 Modul for networking and usb (vinculum VDIP2) costs about 130
EUR. So far we have about 30 advance orders.
Yes, that is the most economical solution and does a large portion of
the protocal work. But the solution while solving some of the
problems does not solve all.
However on this side of the pond the KC85 is rarely seen.
no not true. 4mhz is plenty fast if the physical layer is either slow
(SLIP or PPP on serial line)
And the usability for the user isn't one.
Not sure what you mean there. For CP/M like work 4mhz is fast
enough but it depends on what you want to do.
or some external device handles the fast
work like the ethernet to serial device I highlighted earlier.
Not freely programmable - a 'must have' for me.
hence the Vinculum VDIP2.
True, but that also violates the idea of portability. Go look at
modem programs, each one had to be tweaked for every differnt system
as the modem port was at different address, differnt device type or
worse had no support at all and a third party board was needed.
Thats true, but this is the problem of CP/M. It has no driver concept
for hardware drivers or a HAL like windows. Every hardware expansion
Actually the idea of loadable hardware drivers in CP/M is one of
implementation and it was done. For example the Konan and Teletek
hard disk boards for S100 installed by trapping the bios calls and
vectoring to high memory (you did have to resize to leave space)
and all the ZCPR add ons had RSXs.
makes it more incompatible than before. I can't solve CP/M problems
with new hardware, thats why I selected the PIO - Z80 standard in
every Z80 system but the I/O-address has to be chosen from the user
system needs.
The HAL is the BIOS. From the bios level the hardware is abstracted
to match the BDOS logical interface. the problem is once you start
talking to deviced directly the OS is not helping you. For modem like
work (FTP) thats reasonable. If the hardware expansion is a serial
port that is by far the most common and most likely to be already
available. Even serial has you dealing with the "modem serial port"
problem already mentioned.
Also PIO is not standard. I have at least 5 differnt and common
(amproLB+, DEC VT180, NS* Horizon, Compupro, CCS, Altair)
systems where PIO is unidirectional. The solution is an adaptor
in each case. Serial is universal, very few Z80 systems only have
one serial so you can take advanatage of the second part that was
formerly used for a modem.
Allison
.
- Follow-Ups:
- Re: TCP/IP for CP/M 2.2
- From: susowa
- Re: TCP/IP for CP/M 2.2
- References:
- TCP/IP for CP/M 2.2
- From: Roger Schmidt
- Re: TCP/IP for CP/M 2.2
- From: Allison
- Re: TCP/IP for CP/M 2.2
- From: susowa
- Re: TCP/IP for CP/M 2.2
- From: Allison
- Re: TCP/IP for CP/M 2.2
- From: susowa
- TCP/IP for CP/M 2.2
- Prev by Date: Re: Z80 emulator for Amiga O/S
- Next by Date: Re: TCP/IP for CP/M 2.2
- Previous by thread: Re: TCP/IP for CP/M 2.2
- Next by thread: Re: TCP/IP for CP/M 2.2
- Index(es):
Relevant Pages
|