Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site sphinx.UChicago.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!gargoyle!sphinx!god3
From: god3@sphinx.UChicago.UUCP (Peter Godwin)
Newsgroups: net.micro.apple
Subject: Re: Franklins and ProDos
Message-ID: <1573@sphinx.UChicago.UUCP>
Date: Sat, 1-Feb-86 13:50:21 EST
Article-I.D.: sphinx.1573
Posted: Sat Feb  1 13:50:21 1986
Date-Received: Sun, 2-Feb-86 01:19:14 EST
References: <2b9faf7f.46b9@apollo.uucp>, <2407@reed.UUCP>
Organization: U. Chicago - Computation Center
Lines: 25

The problem with most programs written under Pro-Dos (and with Pro-Dos
itself) is that they check for an Apple. - in other words if you dont
use an apple on the program it might not work.

Getting Pro-dos booted in no big deal BUT using Appleworks is
impossible as far as I know.  So if Appleworks is the program
you wish to use, even if you get prodos booted, you will still see
that it is impossible to run many applications.

I had a Franklin at one time but now I use an enhanced Apple //e.

I had, at one time, the locations in memory that needed adjustment
to have a Franklin run under Pro-dos but I must have dumped them.
The process simply involves changing the check that Pro-Dos does
for seeing if the host computer is an Apple to NOP's (EA's)
Look for a JSR to $FB60, or any reference to that memory location
or the locations which this location refers to.

This deals with calling the routine to print the words "Apple //e"
or in Franklins case "Franklin Ace 1000 v2.2" on the top of the
screen (as in when the computer is turned on.

If I do come up with something specifically I'll post it here.

--Pete Godwin