situation:
I bought a Raspberry 3 mod. B to connect it with my Apple IIe (enhanced).
I made the installation as discriped on Ivan's Website ( http://appleii.ivanx.com/prnumber6/category/a2cloud/ ).
I installed the latest Raspbian System on the SD Card and booted the Raspberry - everything worked well.
Then I installed Raspple II with the order "wget ivanx.com/a2cloud/setup; source setup" - that worked well without errors. (I also tried to install Raspple II directly on a SD card - but then the System does not boot up ... ?)
.
.
.
material:
I tried 3 different usb/serial adapter ((chipset: FTDI; TRENDnet TU-S9 USB to Serial Converter (the adapter Ivan suggests on his A2Cloud Website) and a third one - I don't know the chipset)) - with all of them I do have the same results.
I tried 3 different SSC - I tried jumper on modem and terminal - switches as disriped for the ADTPRO setting (SW1: 1001111 SW2: 1101100), switches as discriped in the ProTerm manual on page 281 (SW1: 0111111 SW2: 1111110) and switches as discriped in different version in the Super Serial Card operating manual on page 21 ff..
I use this serial cable ( http://www.produktinfo.conrad.com/datenblaetter/1400000-1499999/001404053-da-01-en-RENKFORCE_RS232_KABEL_25P_ZU_9P_1_5M.pdf )
.
.
.
THE PROBLEM: I get no terminal communication between the Apple IIe and the Raspberry (tried ProTerm and Kermit)and no correct vsdrive work:
1.)
If I start on the Raspberry PI ADTPRO with the order "adtpro.sh serial" and start then on the Apple IIe the "A2CLOUD.DSK" BootFloppy"; then press "V" and then type "Cat,S2,D2" I get the catalog from vsdrive - I can also start some programms from there (Proterm and Zlink not; sysutil, filer and AdtPro work)
BUT
If I "just connect" the Apple IIe (tried slot 1 and 2) and the Raspberry PI (lower usb port near to ethernet port) and start on the Apple IIe the "A2CLOUD.DSK" Floppy without starting ADTPRO on the Raspberry PI - the Apple IIe says after typing "Cat,S2,D2" : I/O Error ...
2.)
Trying Bootstrapping is this result:
chaos on the Apple IIe monitor:
http://s32.postimg.org/h0i7v6079/IMG_2276.jpg
3.)
Trying to connect ProTerm (start of ProTerm from the Apple IIe from my CFFA (slot 7); SSC in slot 2 a.s.o.; using the upper usb port near to the ethernet on the Raspberry PI) - no result - just a blinking ProTerm cursor.
.
.
.
What can I do?
Could it be that the A2CLOUD software for the Raspberry PI is not compatible with the Raspberry PI 3 Mod. B that I do have?
Thanks in advance for any help!
o.k. - I have a result:
- I took a Raspberry 2 mod. B and installed Raspple II directly on the sd card - everything works perfect!
- Then (on the Raspbian 2 mod. I tried to install Rasbian v. 1.9 on the sd; and then from the terminal installing the A2CLOUD system - the same bad results as on the Raspian 3 mod. B
Therefore it is not possible to install Raspple II on a sd card directly for the Raspbian 3 mod. B - A2Cloud is not compatible with the Raspbian 3 mod. B.
It seems that is also not compatible with the later Rasbian os (I tested 1.9 and 2014-12-24 wheezy-rasbian) on a Raspbian 2 mod. B.
(during installation there are some errors while the pi is installing a2pi - maybe here is the problem ...)
So I use now the Raspbian 2 mod. B with Raspple II on the sd card and be happy with it on my Apple IIe (I ordered a Videx Videoterm card for my Apple II plus - hope it will also work here with Kermit)
Yeah, im not entirely sold on this. Its really nothing more than telnet access to a linux box with text (vt100) based applications to use chat email and other various stuff with the Apple acting as a dumb terminal. The appearance of pulling files is nothing more than rzsz from the linux box to proterm. I understand the need at times to offload network related tasks to an external device, but this essentially offloads everything.
Ive accidentally replicated this effort with BPQ32, a packet radio application for linux that allows for terminal access via telnet. and that was at least impressive that it was 1200 baud over VHF
Glad you got it working, 6502. I seem to have serial communication errors all the time for no good reason. As robust as the protocol is, it is nowhere near as forgiving as plug-and-play devices today.
But that just makes it all the more fun...
Hi Wil, yea I'm happy that everthing it's working fine!
What cable and usb/seriel adapter are you using?
I have to say now I like the Apple II - Raspberry common work very much.
Under the aspect of using the Apple II for daily tasks it is very good to have now a real fine working email program.
I use "Alpine" for this and it is working very good.
My aim is always to work with my Apple II's modern time work.
So I use VisiCalc a lot for caculation for my company - it is a still extraordinary good programm for this task!
I use AppleWorks to write texts where I have to think a lot about - so where the task is quality and not speed.
And now I'm really very satisfied to use the Apple II for Emails - receiving and sending from any account I do have - very, very good!
Yes, I also would be happy to have an email program directly on the Apple II - but it seems that this is with modern email (ssl ...) not possible) - so the raspberry pi - Apple II work is a fine solution - thanks to Ivan!
And ... this post was written on my Apple II
Raspberry PI - just another very nice peripheral card for the Apple II
I'm late to the game for this, but reading this thread saved me a lot of time trying to make a2cloud work with an RPI3 or with a more recent version of raspian. I have my IIC connected to a pi 2B using rasapple as you do/did with my main goal being able to use Alpine for email. Problem I have is the repositories for that version of raspian are no longer active.
I'm hoping you are still using your setup and if so, still have the alpine package files on your pi 2. I can tell you exactly which packages those are if you need.
It's been three years since this thread was created, but I see you were on a late as last week....so crossing my fingers you can help me out!