IIe Cassette In problems?

plug in headphones?

It would be really, really unusual for the cassette ports not to be working. Mostly because they never get used. It's not like they'd wear out or anything.

The audio really does need to be SCREAMING at the Apple. Try at volume close to 100% (not all the way, though, as you might get distortion).

Also, it is important to get the timing down correctly. Start the Apple listening (the 2000.xxxxR command) _before_ you hit go on the server end. The server emits a ~10 second "leader" tone, and the Apple needs to hear at least 3 seconds of it in order to sync up. You don't need to have fantastic twitch reflexes or anything, but you should be prepared to say "go" on both ends at approximately the same time.

You could test cassette out on the Apple by hooking your headphones to the port (don't put them on!) and asking the Apple to send some data (0000.01FFW).

Finally... I find the icons on the back of the IIe to be counter-intuitive. I always get them backwards. "Cassette In" to me suggests the arrow pointing towards the cassette; but that's wrong. You want the white wire on the http://adtpro.sourceforge.net/connectionsaudio.html page. I have to refer to that page whenever I'm hooking up to an IIe.

Good news/bad news. Glad to hear it's working now. I'll see what kind of caveat I can put on the page to make that more explicit. I guess Apple was still experimenting with user friendliness when they made those icons.

The cassette out on the IIe plugs into my Line in, on my Mac Pro it has an image of >0< two triangles pointing into a circle, i hope thats the right input...
but i don't get any response when i do receive and input a file name that is inside the "disks" directory, it is set as the working directory, is ADTPro set to listen to the right input?

Probably. You may need to tell your Mac Pro to "listen" to the line in (vs. the microphone) in a control panel somewhere. Sorry for not having more specific instructions, but every OS (and even different sound cards on Windows - not your problem, I know) have different means of doing this.

Also when i formatted and wrote the "ADTPro Audio Client" to a 5.25 floppy, and tried to boot,

Ooops, stop right there. I know it's long and it's boring, but you have to read the whole bootstrapping process. Step 17(!) says: "Put (or leave) your freshly formatted floppy in the drive. The disk formatted with this utility isn't bootable yet, so don't reboot now - or you'll have to re-send the two ProDOS stages again."

This is different from DOS 3.3, where formatting means to also lay down the DOS image. It's a separate process in ProDOS.

What you need to do now is re-boot ProDOS by sending the two parts over the audio line again. Stick in your ADTPro floppy and you can start up ADTPro from floppy. Once we get your audio working in the host-to-//e direction, you will use ADTPro to send the entire disk image of itself to the drive - which will leave you with a formatted, bootable diskette of all versions of ADTPro plus the formatting utility.

I think i did it right the first time i just didn't explain it fully in my post

No, you wrote it all down in perfect detail.

once i had ADTPro audio on 803G memory location, and ran it, i pressed "G" and saved it to the diskette, after that i rebooted and it didnt work.

So now you have a ProDOS-formatted diskette with the ADTPro program on it; but no ProDOS boot image. That's what I was saying before... the act of formatting doesn't lay down a bootable image of ProDOS.

in the tutorial, it says the first thing i should send over, after i get the audio client saved, is the entire ADTPro program called "(ADTPro-v.r.m.dsk)" i assume this was from an earlier distribution, because it isn't included in the Disks directory, should i send over ADTPro-0.2.6.dsk instead?

Yes indeed. The letters v, r, and m are variables. (v=version, r=release, m=modification.) In release 0.2.6,
v=0; r=2; m=6.
So, ADTPro-v.r.m.dsk means ADTPro-0.2.6 in today's case. It changes a lot.

To test the back-and-forth of the Audio cables, can you try do do a directory listing? Get everybody restarted (click Disconnect, then Audio on the server; hit escape on the Apple //e) and hit the 'D' key on the Apple //e. Does it give you a directory listing? Does the ADTPro server notice that the client sent the directory command?

how do i launch the program off the floppy?

Either:
-ADTPROAUD
or:
BRUN ADTPROAUD
will start it up.

the server says "request: image from host to Apple"
adn the IIe starts receiving blocks ( well it receives one)

Ok, so there is definitely some give-and-take going on. I wonder why it's not behaving well. One thing to try... sometimes, there is feedback when the volume is way, way up. Try turning the volume down at the host somewhat - back to 50%.

PS- after launching the audio client with 803G, going to the settings, and saving it the Disk, what else do i have to do to make this disk bootable, its ProDos formatted, with the application on it,

or does this only save the ADTPROAUD program to the disk and i have to launch it some other way?

To make a ProDOS disk bootable, you need to copy the PRODOS and, optionally, BASIC.SYSTEM files to the disk. The formatter can't do that for you. But when you successfully transfer the ADTPro-0.2.6.dsk image to your drive, those files will already be there and thus will be a bootable disk.

The command is BRUN. The ADTPro client programs are in assembler.

AMAZING!
the transfer is 9/280 so far, its working
the volume feedback seemed to do the trick!

Great. Glad to hear it. Audio transfers are an exercise in patience once they get going, that's for sure. Imagine how much time I spent testing these fool things... only to have it fail on block 265. (By then, most of the data is already transferred... so even if you don't get to 100%, your disk will likely work anyway.)

I tweaked all my references to volume to say 50%; I think anything above that is in danger of causing feedback.

hope this works out, your program is great, much thanks to you and whoever contributed.

I miss the minute-by-minute updates already.
As for contributors - lots of folks did in lots of different ways. See:
http://adtpro.sourceforge.net/credits.html

does a failed transfer usually happen because of feedback?

Feedback, your computer beeping because mail came in (it's sending ALL audio to the Apple, remember), sunspots, you name it.

is the audio transfer more prone to failing, i guess i will have to find a SSC card if i want to the this reliably and faster...

Audio is waaaaaaay more prone to failure. It does have retry logic, so unless it gets hopelessly lost, it ought to be able to recover from problems. I tested by unplugging various wires from time to time and watching it get back in sync. Sometimes it just can't. But it's painful to do more than one - this audio business is for desperate people. You really want to get an SSC card.

Digital Dinos (http://www.digitaldinos.com/DigitalDinos/Pages/ForSale/AppleII/docAppleII.htm) has one for cheap. Or just wait for your IIgs to arrive.

Ok, I got the proverbial oscilloscope out and figured out what went wrong. I was able to reproduce the failure reliably (!) and found a fix. Would you like to try an early version to see if it works better for you?