Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Appleworks or Appleworks GS
427 views
Skip to first unread message
RJ
Jan 28, 2014, 7:58:25 AM1/28/14
to
Hi,
i am interested in installing this software on my unit. Which is the better
all round software (ie: upgradeablity, hard drive capable, functionality and
speed). I know the GS version is graphical but would think it may be slow
even with 4mb ram and running on a rom 03 unit. Anyways I would like to
install this on a 32mb cffa file image but would like some opinions and
suggested add-ons for this application.
Thanks in advance.
Rj
i am interested in installing this software on my unit. Which is the better
all round software (ie: upgradeablity, hard drive capable, functionality and
speed). I know the GS version is graphical but would think it may be slow
even with 4mb ram and running on a rom 03 unit. Anyways I would like to
install this on a 32mb cffa file image but would like some opinions and
suggested add-ons for this application.
Thanks in advance.
Rj
Steve Nickolas
Jan 28, 2014, 9:12:18 AM1/28/14
to
haven't even gotten the thing to work.
The 8-bit version is rock-solid.
-uso.
Hugh Hood
Jan 29, 2014, 10:04:51 PM1/29/14
to
RJ:
Provided your machine has at least 256K (as all IIGS's do, and as some IIc's
and IIe's do), I think you'll be hard pressed to find better 8-bit
text-based Apple II software than AppleWorks 5.1 is.
You may never need 16,000 line word processor/spreadsheet/database documents
or the ability to have 36 files open and on the Desktop at one time, but
AppleWorks 5.1 offers that capability. If you're an assembly language
programmer, its ability to both load and to save Merlin files (high-bit
weirdness included) is such a welcome reprieve from using the editor which
actually comes with Merlin.
But, even when used in the most mundane manner to do the most routine of
tasks, it is very quick, easy to master, useful and powerful. Tom Weishaar
thought so much of it he suggested in Open-Apple that Apple include it
(somehow) in the ROM of every Apple II sold.
And, when shifted into 'high gear' using either the 'TimeOut' series add-ons
(PowerPack, DeskTools IV and FileTools especially) or by using its built-in
programming language (UltraMacros) to construct your own 'application within
an application', it is in a class of its own.
I use it daily in a modern office environment to accomplish _real_ work
quickly and efficiently, in spite of having access to a Mac with Microsoft
Office on it. I never tire of finding new ways to program it, including
adding machine language routines within my macros, or communicating with a
Unix machine via the serial ports to do all sorts of cool tasks.
AppleWorks GS, on the other hand, and as Steve mentioned, has its problems
with some pretty serious bugs. Since it uses the GS/OS GUI, it does some
things that the 8-bit, text-based AppleWorks 5.1 cannot do, and never will.
I am biased, of course, but I can't imagine using AppleWorks GS today to do
any real work. But, if you just have the desire to experience vintage
productivity software, it might meet your needs, at the expense of power and
speed and stability.
I suggest you install and use both of them and report back your impressions.
The AppleWorks 5.1 docs (AppleWorks 4 Reference + 5 Delta) are here:
<ftp://ftp.apple.asimov.net/pub/apple_II/documentation/applications/applewor
ks/>
Hugh Hood
in article rj-139...@macgui.com, RJ at mod...@gmail.com wrote on
1/28/14 6:58 AM:
Provided your machine has at least 256K (as all IIGS's do, and as some IIc's
and IIe's do), I think you'll be hard pressed to find better 8-bit
text-based Apple II software than AppleWorks 5.1 is.
You may never need 16,000 line word processor/spreadsheet/database documents
or the ability to have 36 files open and on the Desktop at one time, but
AppleWorks 5.1 offers that capability. If you're an assembly language
programmer, its ability to both load and to save Merlin files (high-bit
weirdness included) is such a welcome reprieve from using the editor which
actually comes with Merlin.
But, even when used in the most mundane manner to do the most routine of
tasks, it is very quick, easy to master, useful and powerful. Tom Weishaar
thought so much of it he suggested in Open-Apple that Apple include it
(somehow) in the ROM of every Apple II sold.
And, when shifted into 'high gear' using either the 'TimeOut' series add-ons
(PowerPack, DeskTools IV and FileTools especially) or by using its built-in
programming language (UltraMacros) to construct your own 'application within
an application', it is in a class of its own.
I use it daily in a modern office environment to accomplish _real_ work
quickly and efficiently, in spite of having access to a Mac with Microsoft
Office on it. I never tire of finding new ways to program it, including
adding machine language routines within my macros, or communicating with a
Unix machine via the serial ports to do all sorts of cool tasks.
AppleWorks GS, on the other hand, and as Steve mentioned, has its problems
with some pretty serious bugs. Since it uses the GS/OS GUI, it does some
things that the 8-bit, text-based AppleWorks 5.1 cannot do, and never will.
I am biased, of course, but I can't imagine using AppleWorks GS today to do
any real work. But, if you just have the desire to experience vintage
productivity software, it might meet your needs, at the expense of power and
speed and stability.
I suggest you install and use both of them and report back your impressions.
The AppleWorks 5.1 docs (AppleWorks 4 Reference + 5 Delta) are here:
<ftp://ftp.apple.asimov.net/pub/apple_II/documentation/applications/applewor
ks/>
Hugh Hood
in article rj-139...@macgui.com, RJ at mod...@gmail.com wrote on
1/28/14 6:58 AM:
bpi...@gmail.com
Jan 29, 2014, 10:10:49 PM1/29/14
to
RJ
Jan 30, 2014, 6:00:11 AM1/30/14
to
Thanks for all your input on this. After reading Hugh Hoods response I
think I will go ahead and install and use 5.1 on the gs.
Rj
think I will go ahead and install and use 5.1 on the gs.
Rj
Sean Fahey
Jan 30, 2014, 10:28:55 AM1/30/14
to
On Wednesday, January 29, 2014 9:04:51 PM UTC-6, Hugh Hood wrote:
> And, when shifted into 'high gear' using either the 'TimeOut' series add-ons
> (PowerPack, DeskTools IV and FileTools especially) or by using its built-in
> programming language (UltraMacros) to construct your own 'application within
> an application', it is in a class of its own.
Hugh, do you know of a matrix or db showing what TO module functionality is built-in to AW 5.1 and/or what the latest version #s of the various compatible add-ons are to work with it?
> And, when shifted into 'high gear' using either the 'TimeOut' series add-ons
> (PowerPack, DeskTools IV and FileTools especially) or by using its built-in
> programming language (UltraMacros) to construct your own 'application within
> an application', it is in a class of its own.
Thanks in advance. Our community could surely use a definitive AppleWorksWiki.
Hugh Hood
Jan 30, 2014, 11:24:43 AM1/30/14
to
in article d1f08cb0-e269-48e4...@googlegroups.com, Sean Fahey
at a2...@hotmail.com wrote on 1/30/14 9:28 AM:
>
> Hugh, do you know of a matrix or db showing what TO module functionality is
> built-in to AW 5.1 and/or what the latest version #s of the various compatible
> add-ons are to work with it?
>
> Thanks in advance. Our community could surely use a definitive AppleWorksWiki.
Sean:
I agree that a definitive AppleWorksWiki needs to be built. I've got quite a
few things I could contribute, provided the rights holders of the materials
are agreeable.
One of the 'gems' which I prize the most is a copy of the 3.5" disk "TimeOut
Info" that Beagle distributed at the '89 Kansas developer conference (after
making folks sign a non-disclosure) that pretty much describes 'How to Write
an AppleWorks TimeOut Application", complete with Merlin source code. I
wasn't in attendance then, and don't know if there were any printed
materials that come with it, but I got the disk from 'a friend of a friend',
and would happy to share it provided I wouldn't offend somebody. I've been
working (for too long, it seems) on writing a _real_ TimeOut application and
I've found it most helpful.
My thought is that some of the currently written Apple II software could
benefit from being run from within AppleWorks, and use many of its
pre-written machine language routines and familiar, consistent interface to
handle the mundane, but necessary programming tasks.
Anyway, concerning your specific question, I suppose the best matrix
currently available for showing the TimeOut Module / AppleWorks status is
here:
<http://web.archive.org/web/19991011205317/http://members.aol.com/A2MG/TOVer
sions.html>
This table is not completely comprehensive, but it is pretty good. I'm glad
the Wayback Machine from the Internet Archive keeps it around. FWIW, there
are a few other things of interest to hardcore AppleWorks users in that same
archive collection.
Regards,
Hugh Hood
at a2...@hotmail.com wrote on 1/30/14 9:28 AM:
>
> Hugh, do you know of a matrix or db showing what TO module functionality is
> built-in to AW 5.1 and/or what the latest version #s of the various compatible
> add-ons are to work with it?
>
> Thanks in advance. Our community could surely use a definitive AppleWorksWiki.
I agree that a definitive AppleWorksWiki needs to be built. I've got quite a
few things I could contribute, provided the rights holders of the materials
are agreeable.
One of the 'gems' which I prize the most is a copy of the 3.5" disk "TimeOut
Info" that Beagle distributed at the '89 Kansas developer conference (after
making folks sign a non-disclosure) that pretty much describes 'How to Write
an AppleWorks TimeOut Application", complete with Merlin source code. I
wasn't in attendance then, and don't know if there were any printed
materials that come with it, but I got the disk from 'a friend of a friend',
and would happy to share it provided I wouldn't offend somebody. I've been
working (for too long, it seems) on writing a _real_ TimeOut application and
I've found it most helpful.
My thought is that some of the currently written Apple II software could
benefit from being run from within AppleWorks, and use many of its
pre-written machine language routines and familiar, consistent interface to
handle the mundane, but necessary programming tasks.
Anyway, concerning your specific question, I suppose the best matrix
currently available for showing the TimeOut Module / AppleWorks status is
here:
<http://web.archive.org/web/19991011205317/http://members.aol.com/A2MG/TOVer
sions.html>
This table is not completely comprehensive, but it is pretty good. I'm glad
the Wayback Machine from the Internet Archive keeps it around. FWIW, there
are a few other things of interest to hardcore AppleWorks users in that same
archive collection.
Regards,
Hugh Hood
Sean Fahey
Jan 30, 2014, 12:27:58 PM1/30/14
to
On Thursday, January 30, 2014 10:24:43 AM UTC-6, Hugh Hood wrote:
> <http://web.archive.org/web/19991011205317/http://members.aol.com/A2MG/TOVer
> sions.html>
Oh, that's very helpful. Thanks!
Maybe Bill M. would be open to creating an aw.applearchives.com site.
> <http://web.archive.org/web/19991011205317/http://members.aol.com/A2MG/TOVer
> sions.html>
Oh, that's very helpful. Thanks!
Maybe Bill M. would be open to creating an aw.applearchives.com site.
Antoine Vignau
Jan 30, 2014, 1:37:24 PM1/30/14
to
There were articles on the French magazine Pom's dedicated to the writing of TO applications.
Antoine
Antoine
Hugh Hood
Jan 31, 2014, 9:02:10 AM1/31/14
to
in article 426df07c-65e9-4219...@googlegroups.com, Antoine
Vignau at antoine...@laposte.net wrote on 1/30/14 12:37 PM:
> There were articles on the French magazine Pom's dedicated to the writing of
> TO applications.
>
> Antoine
Antoine:
Thanks for the information.
I noticed Pom's #38 and #42 had some TimeOut and UltraMacros articles, and I
noticed some macro listings in the pages of the printed magazines.
As my French skills are about as good as my Java skills (less than poor, at
best), other than #38 and #42 can you recommend a specific issue(s) that I
may have missed discussing some TimeOut programming? I do have a
French-English dictionary around here somewhere (or is that Google?) and I'd
like to put it to good use, I think.
Besides, 65C02 assembler source coding is still fairly easy to decipher,
regardless of the language of the comments.
Thanks.
Regards,
Hugh Hood
Vignau at antoine...@laposte.net wrote on 1/30/14 12:37 PM:
> There were articles on the French magazine Pom's dedicated to the writing of
> TO applications.
>
> Antoine
Thanks for the information.
I noticed Pom's #38 and #42 had some TimeOut and UltraMacros articles, and I
noticed some macro listings in the pages of the printed magazines.
As my French skills are about as good as my Java skills (less than poor, at
best), other than #38 and #42 can you recommend a specific issue(s) that I
may have missed discussing some TimeOut programming? I do have a
French-English dictionary around here somewhere (or is that Google?) and I'd
like to put it to good use, I think.
Besides, 65C02 assembler source coding is still fairly easy to decipher,
regardless of the language of the comments.
Thanks.
Regards,
Hugh Hood
Alistair Ross
Feb 6, 2014, 4:21:30 AM2/6/14
to
Hi Hugh,
I've been using AppleWorks version 2.0 under my //e for a while now and
it works great, but I like the sound of these extra features.
I downloaded 5.1 from asimov today and it crashes on the title screen
(hard lock). Do you have a recommended link for this which I can
install onto my CFFA3000?
Thanks in advance,
Alistair
I've been using AppleWorks version 2.0 under my //e for a while now and
it works great, but I like the sound of these extra features.
I downloaded 5.1 from asimov today and it crashes on the title screen
(hard lock). Do you have a recommended link for this which I can
install onto my CFFA3000?
Thanks in advance,
Alistair
Hugh Hood
Feb 6, 2014, 8:40:12 AM2/6/14
to
Alistair:
There are quite a few images of AppleWorks out there, as you have probably
discovered. Here are links (thanks David Finngan) to the (2) 'best' that I
would recommend downloading:
1. AppleWorks 5 'Install' Disk (called 'EXTRAS')
<http://www.macgui.com/downloads/?file_id=1969>
2. AppleWorks 5 'Program' Disk (called 'APPLEWORKS')
<http://www.macgui.com/downloads/?file_id=1970>
These are pretty much images of the disks as they come from Quality (on (2)
800kb floppies), with the exception being that someone has already applied
the Version 5.1 updater to them, which is actually a good modification, I
think.
Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
get it going.
Docs --
The AppleWorks 4 Reference Manual and the AppleWorks 5 'Delta' manual are
here:
<ftp://ftp.apple.asimov.net/pub/apple_II/documentation/applications/applewor
ks/>
Let me know if you have problems. I've got to go out of town today but I'll
be back next week.
Regards,
Hugh Hood
in article 2014020622213081585-ajrossnz@gmailcom, Alistair Ross at
ajro...@gmail.com wrote on 2/6/14 3:21 AM:
There are quite a few images of AppleWorks out there, as you have probably
discovered. Here are links (thanks David Finngan) to the (2) 'best' that I
would recommend downloading:
1. AppleWorks 5 'Install' Disk (called 'EXTRAS')
<http://www.macgui.com/downloads/?file_id=1969>
2. AppleWorks 5 'Program' Disk (called 'APPLEWORKS')
<http://www.macgui.com/downloads/?file_id=1970>
These are pretty much images of the disks as they come from Quality (on (2)
800kb floppies), with the exception being that someone has already applied
the Version 5.1 updater to them, which is actually a good modification, I
think.
Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
get it going.
Docs --
The AppleWorks 4 Reference Manual and the AppleWorks 5 'Delta' manual are
here:
<ftp://ftp.apple.asimov.net/pub/apple_II/documentation/applications/applewor
ks/>
Let me know if you have problems. I've got to go out of town today but I'll
be back next week.
Regards,
Hugh Hood
in article 2014020622213081585-ajrossnz@gmailcom, Alistair Ross at
ajro...@gmail.com wrote on 2/6/14 3:21 AM:
Alistair Ross
Feb 7, 2014, 12:41:34 AM2/7/14
to
> Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
> either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
> get it going.
Ah. That'll be it then. I have a 128K platinum :(
> either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
> get it going.
What's the best version that doesn't require so much RAM?
Michael J. Mahon
Feb 7, 2014, 3:08:39 AM2/7/14
to
Alistair Ross <ajro...@gmail.com> wrote:
>> Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
>> either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
>> get it going.
>
> Ah. That'll be it then. I have a 128K platinum :(
>
> What's the best version that doesn't require so much RAM?
Appleworks 3.
>> Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
>> either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
>> get it going.
>
> Ah. That'll be it then. I have a 128K platinum :(
>
> What's the best version that doesn't require so much RAM?
But I'd really recommend getting an expansion RAM card, if just for the
larger desktop.
-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon
Alistair Ross
Feb 7, 2014, 4:08:57 PM2/7/14
to
On 2014-02-07 08:08:39 +0000, Michael J. Mahon said:
> Alistair Ross <ajro...@gmail.com> wrote:
>>> Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
>>> either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
>>> get it going.
>>
>> Ah. That'll be it then. I have a 128K platinum :(
>>
>> What's the best version that doesn't require so much RAM?
>
> Appleworks 3.
>
> But I'd really recommend getting an expansion RAM card, if just for the
> larger desktop.
Thanks Michael.
> Alistair Ross <ajro...@gmail.com> wrote:
>>> Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
>>> either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
>>> get it going.
>>
>> Ah. That'll be it then. I have a 128K platinum :(
>>
>> What's the best version that doesn't require so much RAM?
>
> Appleworks 3.
>
> But I'd really recommend getting an expansion RAM card, if just for the
> larger desktop.
I ordered a Sirius RAM IIGS with 8MB on it from 16sector.com back in
January. Still waiting on it shipping so when I get all things on my
IIGS back in a working fashion I'll try 5.1 out there.
In the mean time, finding an expansion RAM card in the USA on Ebay is
probably quite easy. Not so much in New Zealand, so I don't think my
//e will see an upgrade in the RAM area any time soon.
Do you know if there is there any way to force AppleWorks to use the
CFFA/ProDOS volumes as the working Desktop, rather than RAM. I know it
would be slower, but it would be neat.
Cheers,
Alistair
Michael J. Mahon
Feb 8, 2014, 1:21:12 AM2/8/14
to
Alistair Ross <ajro...@gmail.com> wrote:
> On 2014-02-07 08:08:39 +0000, Michael J. Mahon said:
>
>> Alistair Ross <ajro...@gmail.com> wrote:
>>>> Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
>>>> either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
>>>> get it going.
>>>>> Ah. That'll be it then. I have a 128K platinum :(
>>>>> What's the best version that doesn't require so much RAM?
>>> Appleworks 3.
>>> But I'd really recommend getting an expansion RAM card, if just for the
>> larger desktop.
>
>
> Thanks Michael.
>
> I ordered a Sirius RAM IIGS with 8MB on it from 16sector.com back in
> January. Still waiting on it shipping so when I get all things on my IIGS
> back in a working fashion I'll try 5.1 out there.
>
> In the mean time, finding an expansion RAM card in the USA on Ebay is
> probably quite easy. Not so much in New Zealand, so I don't think my //e
> will see an upgrade in the RAM area any time soon.
>
> Do you know if there is there any way to force AppleWorks to use the
> CFFA/ProDOS volumes as the working Desktop, rather than RAM. I know it
> would be slower, but it would be neat.
>
> Cheers,
>
> Alistair
Unfortunately, I'm not aware of any "virtual memory" add-on for Appleworks.
> On 2014-02-07 08:08:39 +0000, Michael J. Mahon said:
>
>> Alistair Ross <ajro...@gmail.com> wrote:
>>>> Remember, AppleWorks 5 requires 256K. If your //e is stock, you'll need
>>>> either an aux slot card (e.g. RamWorks) or a slinky card (e.g. RamFactor) to
>>>> get it going.
>>>>> Ah. That'll be it then. I have a 128K platinum :(
>>>>> What's the best version that doesn't require so much RAM?
>>> Appleworks 3.
>>> But I'd really recommend getting an expansion RAM card, if just for the
>> larger desktop.
>
>
> Thanks Michael.
>
> I ordered a Sirius RAM IIGS with 8MB on it from 16sector.com back in
> January. Still waiting on it shipping so when I get all things on my IIGS
> back in a working fashion I'll try 5.1 out there.
>
> In the mean time, finding an expansion RAM card in the USA on Ebay is
> probably quite easy. Not so much in New Zealand, so I don't think my //e
> will see an upgrade in the RAM area any time soon.
>
> Do you know if there is there any way to force AppleWorks to use the
> CFFA/ProDOS volumes as the working Desktop, rather than RAM. I know it
> would be slower, but it would be neat.
>
> Cheers,
>
> Alistair
And I'm not sure you'd be willing to wait for a spreadsheet recalculate if
there were!
Interestingly, the Appleworks segment manager (developed for the Apple ///
when Appleworks began as Three Easy Pieces) actually *is* a virtual memory
manager. ;-)
mdj
Feb 10, 2014, 7:15:26 PM2/10/14
to
On Saturday, 8 February 2014 16:21:12 UTC+10, Michael J. Mahon wrote:
> Unfortunately, I'm not aware of any "virtual memory" add-on for Appleworks.
>
> And I'm not sure you'd be willing to wait for a spreadsheet recalculate if
>
> there were!
>
>
>
> Interestingly, the Appleworks segment manager (developed for the Apple ///
>
> when Appleworks began as Three Easy Pieces) actually *is* a virtual memory
>
> manager. ;-)
I would've thought that the modern flash based storage cards would be able to give a slinky card at least a run for its money ...
> Unfortunately, I'm not aware of any "virtual memory" add-on for Appleworks.
>
> And I'm not sure you'd be willing to wait for a spreadsheet recalculate if
>
> there were!
>
>
>
> Interestingly, the Appleworks segment manager (developed for the Apple ///
>
> when Appleworks began as Three Easy Pieces) actually *is* a virtual memory
>
> manager. ;-)
I've often heard tales of the Appleworks Segment Manager, but I'm not aware of any documentation of its technical details. Could somebody supply a description ?
Hugh Hood
Feb 15, 2014, 1:22:21 PM2/15/14
to
in article 5504a2c3-64f6-4841...@googlegroups.com, mdj at
mdj...@gmail.com wrote on 2/10/14 6:15 PM:
>
> I've often heard tales of the Appleworks Segment Manager, but I'm not aware of
> any documentation of its technical details. Could somebody supply a
> description ?
Matt:
A masterfully detailed description of the AppleWorks 5.1 Segment Manager was
written by Christian Serreau in Issue #2 of Howard Katz's "The AppleWorks
Gazette" (TAG) in 1996.
He detailed virtually _everything_, and even included old school flowcharts
explaining the logic involved (used mousetext).
Several years ago I approached Howard about releasing the (4) issues of TAG,
but never really got a 'yes' answer from him, so the status is ??.
Fortunately, an abbreviated version of Serreau's article 'Inside AppleWorks:
AppleWorks Segments' is available for download in the 'sample issue' of TAG
that Howard did release. It is here:
<http://www.wbwip.com/tag/tagsamp.hqx>
I believe it to be 'fair use' to include Chris' intro here:
BEGIN QUOTE
' From the start, AppleWorks has been too large a program for the Apple //
"main" memory. The author had to cut it into "segments", that are called to
main memory only when needed. Of course, the subprogram that calls segments
must always be in main memory.
Early versions of AppleWorks had 40 segments (with room for 43), stored in
files "M0" and "M1". The most recent version, AppleWorks 5.1, has as many as
46 segments (and room for only one more). These are stored in files SEG.AW,
SEG.DB, SEG.DR, SEG.SN, SEG.SS, and SEG.WP.
When AppleWorks 3.0 was designed, the principle of two program files (SEG.M0
and SEG.M1), which had been used since the very first version of the
program, was changed; subprograms for desktop tasks, the data base, the
spreadsheet, and the word processor were stored in separate files, named
SEG.AW, SEG.DB, SEG.SS, and SEG.WP, respectively. Each of these files
contains a "main" program in the first segment, and the other segments in
the file are used for specific tasks. '
END QUOTE
Alternatively, if you crave something like only Bob Sander-Cederlof can
deliver, here is his disassembly and explanation of the AppleWorks 1.3
'Application Overlay Manager' from the March 1988 Apple Assembly Line :
<http://www.txbobsc.com/aal/1988/aal8803.html#a1>
Finally, if you aren't already sorry that you asked, this is from the
AppleWorks 3.0 Entry Points Documentation by Claris Corporation (1989).
AppleWorks Host
10FA JMP CallSeg ;
CallSeg
Routine to load segments, which comes in handy. It keeps track of which Main
is in, and whether or not Organizer is in. As segments are loaded from
disk, it tries to store a copy in bank-switched. If still in bank-switched
at the next call of this seg, then the copy will come from bank-switched.
Reads segments 1-43 from several seg.xx files. Location is a series of
three byte pointers at the beginning of seg.xx.
LDA #SegmentNumber
JSR CallSeg
--------------------------------------------------------------------
Now back to your regularly scheduled program ...
Hugh Hood
mdj...@gmail.com wrote on 2/10/14 6:15 PM:
>
> I've often heard tales of the Appleworks Segment Manager, but I'm not aware of
> any documentation of its technical details. Could somebody supply a
> description ?
A masterfully detailed description of the AppleWorks 5.1 Segment Manager was
written by Christian Serreau in Issue #2 of Howard Katz's "The AppleWorks
Gazette" (TAG) in 1996.
He detailed virtually _everything_, and even included old school flowcharts
explaining the logic involved (used mousetext).
Several years ago I approached Howard about releasing the (4) issues of TAG,
but never really got a 'yes' answer from him, so the status is ??.
Fortunately, an abbreviated version of Serreau's article 'Inside AppleWorks:
AppleWorks Segments' is available for download in the 'sample issue' of TAG
that Howard did release. It is here:
<http://www.wbwip.com/tag/tagsamp.hqx>
I believe it to be 'fair use' to include Chris' intro here:
BEGIN QUOTE
' From the start, AppleWorks has been too large a program for the Apple //
"main" memory. The author had to cut it into "segments", that are called to
main memory only when needed. Of course, the subprogram that calls segments
must always be in main memory.
Early versions of AppleWorks had 40 segments (with room for 43), stored in
files "M0" and "M1". The most recent version, AppleWorks 5.1, has as many as
46 segments (and room for only one more). These are stored in files SEG.AW,
SEG.DB, SEG.DR, SEG.SN, SEG.SS, and SEG.WP.
When AppleWorks 3.0 was designed, the principle of two program files (SEG.M0
and SEG.M1), which had been used since the very first version of the
program, was changed; subprograms for desktop tasks, the data base, the
spreadsheet, and the word processor were stored in separate files, named
SEG.AW, SEG.DB, SEG.SS, and SEG.WP, respectively. Each of these files
contains a "main" program in the first segment, and the other segments in
the file are used for specific tasks. '
END QUOTE
Alternatively, if you crave something like only Bob Sander-Cederlof can
deliver, here is his disassembly and explanation of the AppleWorks 1.3
'Application Overlay Manager' from the March 1988 Apple Assembly Line :
<http://www.txbobsc.com/aal/1988/aal8803.html#a1>
Finally, if you aren't already sorry that you asked, this is from the
AppleWorks 3.0 Entry Points Documentation by Claris Corporation (1989).
AppleWorks Host
10FA JMP CallSeg ;
CallSeg
Routine to load segments, which comes in handy. It keeps track of which Main
is in, and whether or not Organizer is in. As segments are loaded from
disk, it tries to store a copy in bank-switched. If still in bank-switched
at the next call of this seg, then the copy will come from bank-switched.
Reads segments 1-43 from several seg.xx files. Location is a series of
three byte pointers at the beginning of seg.xx.
LDA #SegmentNumber
JSR CallSeg
--------------------------------------------------------------------
Now back to your regularly scheduled program ...
Hugh Hood
0 new messages