Re: Virtual serial drive

[David Schmenk <dschmenk@gmail.com>]

On Wednesday, September 5, 2012 8:00:20 AM UTC-7, schmidtd wrote:
> On 9/4/2012 9:57 PM, Kevin wrote:
> 
> > question though, since your using the serial magic of ADT, would that imply that one could use faster port speeds? ADT has no issue transferring disk images to my machine at 115Kbaud, but from basic 600 baud is kind of pushing it without the magic.
> 
> 
> 
> Quite so.  Once everything gets ironed out, it will (he boldly predicts) 
> 
> run at 115.2kbps as everything else in the family does.
> 
> 
> 
> > I thank you very much for your modifications to this driver, ASM is just something I get totally lost in, and really do appreciate your efforts.
> 
> 
> 
> No problem, it was just too cool to leave alone.
> 
> 
> 
> After neglecting some Real World things that require my attention, I'm 
> 
> going to have to put this down for a little bit.  Everyone is invited to 
> 
> look at the code in is current form here, assuming this link works:
> 
> adtpro.cvs.sourceforge.net/viewvc/adtpro/adtpro/client/src/prodos/serial/drive/drivemain.asm?view=markup
> 
> 
> 
> Current state of affairs: the block read requests are making it up to 
> 
> the host, and the checksum of the command envelope is calculated 
> 
> correctly.  They disagree on the checksum of the block coming back, so 
> 
> that's still to be worked out.  I also get inconsistent results from the 
> 
> one machine/USB serial adapter I was working with, so there are either 
> 
> more code or hardware problems lurking (or both).  But it's probably 
> 
> just my bugs.  I've got some indicators that flash on the screen to give 
> 
> some "I am here" hints that need to expand to help debugging, and then 
> 
> disappear once it works.  Though a little flashing dohicky in the corner 
> 
> might be cool.
> 
> 
> 
> The ADTPro server in CVS along with this code has the ability to serve 
> 
> block read requests, calculate checksums, and the build process creates 
> 
> a disk for the server to serve in the default location.  So it's pretty 
> 
> much point and shoot for debugging purposes.

So what are the chances of making this work with Uthernet too?