Re: Zlink Block Error Problems.

[Rubywand <rubywand@swbell.net>]

Ernest writes ...
> 
> Rubywand wrote in message <3931D2BF.35675F8C@swbell.net>...
> >Ernest writes ...
> >>
 ....
> I know that when I use 8n1, and type PR#2 from the DOS prompt, I only get
> gibberish on the PC side

     That is normal. When you set up a simple direct connection using PR#2, the Apple II outputs normal Text with the eighth bit (bit 7) set to "1".

     A telecom program will usually set the high bit (7) to "0" when sending in ASCII or "Text" mode. Try the typing experiment while connected via ZLink using this ZLink setup:

BAUD    19200
LENGTH  8 BITS
PARITY  NONE
STOP    1
SLOT    2


> but with 7n1, I get normal letters. That's why I
> used it with Zlink. I tried it with no emulation on the Zlink side, with the
> same results -Block Number Errors. I'm not sure what it means by Block
> Number
> 
> I do use Xmodem on the PC side to transfer, and I start the Zlink side
> first.

     And, ZLink needs to be receiving/sending via Xmodem.


> It's frustrating to be so close, and still it doesn't work. This
> whole set up has been one big pain. Asimov and Tarnover are gone, and along
> with them went the only real source of .dsk files (en masse.) Grr.

     Having those sites down is definitely inconvenient. For now, you can find quite a few disk images for vintage 8-bit games on The Vault.


> It
> shouldn't be this stinkin' hard to do. I've set this same kind of transfer
> up on other types of systems with no problem but everything seems to be much
> more difficult with an Apple IIe. ADT was almost as much of a pain but
> fortunately, I only needed to send one way.
 ....

     Being able to do PC-->A2 disk image transfers with ADT validates a lot of things about your hardware setup.

     Try the ZLink setup mentioned earlier using Xmodem and a Hyperterm setup for 19200 baud, 8-N-1, Terminal= Auto-detect, ASCII Setup= nothing checked except "Wrap lines that exceed terminal width".



Rubywand