Re: help running prodos on a // clone <please!>

[Rubywand <rubywand@swbell.net>]

Keven Fedirko writes ...
> 
> Okay.  A buddy got this clone from his parents (un-used for 10
> years), and it "works", but he didn't have any db s/w for it,
> so over christmas I looked through my stash, and found
> my copy of appleworks.  "Great".  But this system doesn't
> seem to want to LOAD it off the disk, or even the 3.3 system
> disk I've made.  All the stuff worked fine on my //e, but not
> his system which seems to be a APCO 64k system, and Tiger
> on the back (not sure which is the brand and which the name).
> 
> It would load some of the other bootable disks (binarys with
> an interactive catalog, and full-disk applications).
> 
> Is it even possible to run prodos on such an old machine, or was the
> //e + //c series the minimum configuration?  Or perhaps his
> system doesn't have a 80 column card or something.  Is there
> s/w versions of these things?  The prodos was only v1.0.1
> or some-such-thing circa 1984 and 1986.
>
 ....



     As Harald Mommer mentions, standard ProDOS does a ROM check which
many clones fail. In an old Apple Clinic note, Stephen Craft listed
specific locations to change after one popular clone (a Franklin)
freezes. You could then restart via a 2000G from the monitor.

     It turns out that the bytes Stephen was diddling are D0 03 in the
sequence 69 0B D0 03 A5 0C 60.  The sequence is found in all versions of
ProDOS I've checked so far.


     To fix the booting problem, try this:

 Start Copy II+ and select "Sector Editor"

 Swap-in the ProDOS diskette

 READ Track 0, Sector 0

 Search for (Hex bytes): 69 0B D0 03 A5 0C 60

 When you find the above, change the D0 03 to EA EA
   and write the changed sector back to diskette.

 
     This patch has no effect on ProDOS functioning on regular Apple
II's. In fact, most users probably have diskettes on which the patch is
already present. 



Rubywand