[Blindapple] Making silent Disks Talk?

[Teresa Cochran]

Hey, I actually understood that. :) I'll give this a try. It's easy to replace the disk. Based on my limited knowledge of Basic, I do understand the number sequence in the programs.

Thanks,
Teresa
On Oct 1, 2013, at 9:50 AM, Kyle <kyle at gmx.ca> wrote:

> Yeah, you did run textalker on the disk, but you completely replaced the
> HELLO program, which was probably not what you wanted to do. Do you have
> a backup copy of the disk you changed? Try the following:
> 
> First, make a copy of the disk, as you don't want to modify the original
> disk; you want it as a backup in case you mess things up. Now put
> DOSTALK.DSK, BEXBOOT.DSK or one of a couple of other disks you have with
> both FID and Textalker into drive 1 (-flop1). Put your non-talking disk
> in drive 2 (-flop2). If you are using bex, you can type
> 
> MESS
> 
> when it asks for a configuration, and type F at the main menu to run
> FID. If you are using DOSTALK or another disk that had FID, just type
> 
> BRUN FID
> 
> at the "ready" prompt.
> 
> Once FID is running, Follow the prompts to select the source and
> destination slot and drive. Your disk drives are in slot 6, and are
> numbered 1 and 2. You will be copying from slot 6 drive 1 to slot 6
> drive 2. When asked for a filename, enter TEXTALKER.RAM. Also copy
> TEXTALKER.OBJ. If you get an error when trying to copy TEXTALKER.OBJ,
> copy TEXTALKER.RAM.OBJ instead. Now quit out of FID. If you are running
> from Bex, you will also need to quit out of Bex by typing Q at the menu.
> Otherwise, quitting out of FID will return you to the "ready" BASIC
> prompt. Now type the following commands as shown.
> 
> NEW
> LOAD HELLO,D2
> LIST
> 
> Make note of the number of the first line of the program. Hopefully it
> is higher than 1. You can press control+c at this point. You will hear a
> beep followed by the word BREAK.
> 
> So I told you to make a note of the line number of the first line of the
> program. This number is important because you are going to enter a new
> line into the program that starts with a lower number. For example, if
> the first line is 10, you can use any line number lower than 10. As long
> as the first line is higher than 1, you can safely use line 1 without
> damaging the program. Again, list the program to be sure that the first
> line number is higher than 1 and enter
> 
> 1 PRINT CHR$(4) "BRUN TEXTALKER.RAM"
> 
> Now save the program
> 
> SAVE HELLO
> 
> The next time you reboot your silent disk, assuming of course that the
> program you want is either written in BASIC or doesn't overwrite
> Textalker in memory, you will have a newly talking disk with access to
> the programs that you wanted. Hope all this old Apple2e technobabble
> helps just a little. And people think Linux is an OS for geeks lol. Just
> drop them into a "ready" ] prompt on an Apple2e and see how far they
> get. It would be quite daunting even for some people who consider
> themselves geeks in 2013 <smiles>.
> ~Kyle
> http://kyle.tk/
> -- 
> "Kyle? ... She calls her cake, Kyle?"
> Out of This World, season 2 episode 21 - "The Amazing Evie"
> _______________________________________________
> BlindApple mailing list
> BlindApple at bluegrasspals.com
> http://jaybird.no-ip.info/mailman/listinfo/blindapple