[Coco] VCC Experience

[Bill Pierce]

Bill, are you trying to do this at system level, or software level?
At software level you just:
open(path,"/n",mode)
then just read and write on that path until you're done. There's already 2 hi-level cmd protocols that will use the ports like this. "dw" & "ui". Dw is geared more to user calls, where ui is geared more to machine calls.
 
But if you're going for system level, the underlying lo-level protocol is what you're after which is what the above is based on.

To see the dw protocol in action,on the Coco in NOS9 at the cmd prompt just type:
dw server dir ftp://os9archive.rtsi.com/RSDOS/   (be prepared to wait a bit)

The "dw" util is in your cmds already. I have a uitlity that does the same for the "ui" protocol.
 

Bill Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com


 
 
-----Original Message-----
From: Bill Nobel <b_nobel at hotmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Thu, May 22, 2014 10:11 pm
Subject: Re: [Coco] VCC Experience


Ok I found it,  I do assume link to dwio subroutine module would open all 
functions? or would I be better off direct embedding code?.

Bill Nobel

On May 22, 2014, at 2:47 PM, Tormod Volden <lists.tormod at gmail.com> wrote:

> On Thu, May 22, 2014 at 10:32 PM, Bill Pierce wrote:
>> 
>> Bill, some of the "telnet" code you're seeking is either in
>> "nitros9/defs/drivewire.d"
>> or
>> "nitros9/lib/net.as"
> 
> And "hg grep TCPOpen" will reveal that this function is in the latter.
> 
>> 
>> The reason you're not seeing reference to these files us those references are 
in the makefiles.
>> 
>> In "nitros9/level1/modules" you'll find:
>> boot_dw.asm (dw boot module)
>> clock_dw.asm dw clock sub-module
>> dw4read.asm (incomplete turbo mode subs, do not use)
>> dw4write.asm (same as above)
>> dwcheck.asm (dw crc check)
>> dwdesc.asm (v-drive "/Xx" descriptors)
>> dwinit.asm
>> dwio.asm (general dw io subroutine)
>> dwread.asm (main dw read)
>> dwwrite.asm (main dw write)
>> p_scdwp.asm (virtual printer descriptor)
>> rbdw.asm (dw rbf device driver)
>> scdwp.asm (virtual printer driver)
>> scdwv.asm (v-port driver)
>> scdwvdesc.asm (v-port descriptors for "/Nx" and "/Zx")
>> term_scdwt.asm (remote terminal device)
>> 
>> and I think that about covers it. The sources are mixed and combined by the 
makefiles to make up the various module that make dw.
>> Now in most of these there a "conditional" to set for the "becker port" which 
is the form Vcc uses for TCP else it is in serial mode for the real Coco.
> 
> Great list. We could need more of such documentation to encourage
> people to look at the code. Feel free to submit such things as Readme
> files or to the wiki.
> 
> Tormod
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


-- 
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco