[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DiversiDial working in Jace, almost 100%

On Thursday, August 9, 2012 8:06:35 PM UTC+1, BLuRry wrote:
> A little while ago I received an email asking for help with getting Jace to work with DiversiDial.  Because Jace only has SSC (well, HAD) emulation it was a non-starter.  DiversiDial only supports the Hayes Micromodem and Novation Cat cards.  I looked at the spec for the Hayes card and found it was extremely similar to SSC, largely due to the fact it uses the same ACIA chip.  The I/O ports work a little differently but after a lot of twiddling I finally have it working.  A side effect of this is that the serial handling (inclusive of the SSC emulation as well) is WAY improved and you no longer have to press CTRL+RESET to force it to reset its connection after closing a telnet client.
> 
> 
> 
> I have one open issue, which prevents it from being 100%: The first connection to DiversiDial is answered by the program but there is no response.  It just sits there, and no messages from the host are sent over the wire (the program does not send any output even though it knows it connected.)  If I disconnect and wait a few minutes for the connection to time-out in ddial, then it starts working 100%.  I noticed that when it is working correctly, the time is counting minutes/seconds but when it is not working, the time is stopped.
> 
> 
> 
> Does DiversiDial need a clock card to work properly?  Are there any other known issues similar to this on the real hardware?
> 
> 
> 
> -Brendan

Impressive stuff, Brendan!

I took a look at ddial a few years ago.

AppleWin had a bug(?) where TAPEIN.b7 was floating. I pulled it high, which fixed the fast running timer. This doesn't sound like your problem, but my notes might be of interest:
https://developer.berlios.de/bugs/?func=detailbug&bug_id=17055&group_id=6117

There's also a frozen clock bug too (probably the IO isn't working correctly when in debugger trace mode):
https://developer.berlios.de/bugs/?func=detailbug&bug_id=17758&group_id=6117

Tom