Beruflich Dokumente
Kultur Dokumente
/ __ \ / \/ \ | | / ___| / __ \ / __ \ | _ \ / __ \ / ___|
| |__| || || || | _ | |__| | __ | | | || | \ \| | | | \_ \
| __ || |\/| || || |__| || __ | |__| | |_/ \| |_/ /| |__| | __\ \
|_| |_||_| |_||_| \____/ |_| |_| \___/\/|____/ \____/ |____/
S O F T W A R E Q D O S E M U L A T O R F O R T H E A M I G A
--------------------------------------------------------------------------
--------------------------------------------------------------------------
--------------------------------------------------------------------------
--------------------------------------------------------------------------
QUICK OVERVIEW
--------------------------------------------------------------------------
QL FILESYSTEM
--------------------------------------------------------------------------
,--------------------------------------------/|/|/|/|/|/|/|/|/|/|/|
/ /_//_//_//_//_//_//_//_//_//_//_//_//_//_/ / /|
/ /_//__//_//_//_//_//_//_//_//_//_//_//_/ / / / /
/ /_//____//_//_//_//_//_//_//_//_//_//____/ / / /
/ /_//__//_//_//_________________//_//_//__/ /_____________________/ /
/_'__________________________________________/|__.====== .====== __|/
|_____________________________________________:======================/
|________________________________________________________________|/
--------------------------------------------------------------------------
QUICK START
Under WB2 with crossDOS, make sure that you have at least MOUNT 40.4
and SETPATCH 40.16 installed (distributed with AmiCDFS). Then install
as in WB3 below. If you do not have crossDOS, install as in WB1.3.
Under WB3 copy the provided QL0 and QL1 definition files to
devs:dosdrivers. Check that your start-up sequence contains the
command 'MOUNT Devs/dosdrivers/~(#?.info)', then REBOOT.
2. At the F1/F2 prompt, insert QLutils: into DF0: and press F1.
--------------------------------------------------------------------------
When you first switch on a QL (or when you run the emulator) you are
presented with a screen requiring you to press F1 or F2.
Upon pressing F1 or F2, the system will attempt to load and run a file
called 'BOOT' from the disk inserted in the internal drive (FLP1_). With
the QDOS QLutils: disk inserted, a BASIC BOOT program will run that loads
a number of toolkits and installs a small RAM disk.
In any case, you will eventually be presented with a flashing cursor. This
is your bog-standard home-computer flashing-cursor, waiting for a NEW
program to be typed-in and RUN, or LOADed from floppy disk.
NEW
10 PRINT "Hello World!"
RUN
20 GOTO 10
RUN
...then the same words will be repeatedly printed until you BREAK the
program with the keys <CTRL><SPACE>.
You can save the program to the disk in the internal drive with the
command:
SAVE FLP1_HELLOWORLD_bas
or, if there is no room on disk, you can FORMAT a new disk with the
command:
FORMAT FLP1_WORKDISK
...which formats the disk in the internal drive and gives it the name
'WORKDISK'. Remember there is no going back once a disk is formatted.
DIR FLP1_
LIST
RUN
EXEC_W FLP1_XCHANGE
...will load and execute the stated program from the disk in the
internal drive. At the same time it will suspend BASIC ( _W = wait ).
To multi-task, use EXEC and press CTRL-C to task switch.
--------------------------------------------------------------------------
CUSTOM STARTUP
QDOS_128K
CHIP_ONLY
Run QDOS from CHIP memory, and ignore all memory expansions.
A500_RANGER_ONLY
For A500s only. Ignore all other memory ranges and run QDOS from RANGER
memory (address $C00000 onwards). A memory board fitted in the trap-door
beneath the machine gives you this type of memory.
A500_EXPANSION_ONLY
For A500s only. Ignore all other memory ranges and run QDOS from EXPANSION
memory (address $200000 onwards). Some A500 peripherals that fit to the
expansion port on the left of the machine give you this type of memory.
If none of the provided custom start-up icons reflect the set-up you
require for your machine, it is possible to create your own. Click on any
start-up icon and select copy (WB 2.0), or duplicate (WB 1.3). Click on
the copy and rename it accordingly. Go to information from the workbench
menus and change the tool type arguments as follows:
-m<lomem>-<himem>
This sets the area of memory available to QDOS. <lomem> corresponds to the
start of the system variable area and <himem> corresponds to RAMTOP.
-q<QDOS system ROM>
This sets the name of the required QDOS system ROM. The default name is
'SYS_cde'
-p<patcher ROM>
The patcher ROM does most of the work of getting the almost QL-like system
ROM to work on the Amiga. The default name is 'MAIN_cde'
--------------------------------------------------------------------------
--------------------------------------------------------------------------
O/S HOOKS
The external ROM "MAIN_cde" does most of the work necessary to get the
QDOS system ROM operating correctly by hooking itself into the relevant
system vectors. L_QDOS currently puts "MAIN_cde" at $1C000, well within
the first 512 K of CHIP RAM. Once loaded, "MAIN_cde" searches for
expansion ROMs situated in areas of memory peculiar to the Amiga.
RESET_TOP <oldtop>,<newtop>
For example on an A500, having booted Amiga-QDOS to make use of ranger RAM
at $C00000-$C80000 and wishing to reboot leaving ranger RAM free and using
the bottom 512K only, one could use the command:
RESET_TOP hex("C80000"),hex("80000")
RESET_TOP 13107200,524288
RESET_TOP 524288,13107200
RESET_SV <newsv>
This keyword allows users to reposition the system variables and re-boot.
For example to move the system variables so as to free the second screen
area:
RESET_SV 196608
RESET_SV 163840
RESET_EXTENTS <oldtop>,<newtop>,<newsv>
For example on an A4000 with 2MB CHIP and 2MB of expansion ($7E00000-
$8000000), one could move the QDOS work area from CHIP to FAST RAM with
the following command:
RESET_EXTENTS HEX("200000"),HEX("8000000"),HEX("7E00000")
QDOS tasks loaded into FAST RAM, run significantly faster. Running QDOS in
FAST RAM relies on QDOS tasks being 32-bit clean.
These two commands allow the instruction cache to be turned on and off
respectively. Amiga-QDOS boots with the instruction cache disabled.
Turning the instruction cache on can speed up QDOS tasks considerably but
relies on tasks to be well behaved (and not self modifying).
These two commands allow the data cache to be turned on and off
respectively. Amiga-QDOS boots with the data cache disabled.
--------------------------------------------------------------------------
CLOCK
INITIALISATION
The system fully supports the Amiga's battery backed-up clock, and will
provide you with the correct date and time by way of the SuperBASIC
commands DATE and DATE$ or the equivalent machine code TRAP instruction.
If your Amiga does not include a clock, the system time will default to a
value passed from AmigaDOS.
BUGS
Doesn't find the battery backed-up clock in the A4000. The hardware has
probably moved.
--------------------------------------------------------------------------
VDU
SECOND SCREEN
The JS system ROM is altered to allow the system variables to be moved and
for the second screen to be used. The MODE command is altered accordingly,
to act more like the Minerva version.
If you are familiar with the way Minerva handles its screens then you
should be able to understand the following.
The normal parameters for MODE still apply but if a second parameter is
given, then both parameters are passed on to the MT.DMODE system trap in D1
and D2 without alteration. D1 then takes on the following meaning:
Thus to clear, set or toggle just ONE attribute of the display mode, the
mode command takes the following form:
MODE -128+n*(k-256),-1
where:
(k=0) | (k=1) | (k=257)
Note that the default screen is set BEFORE any other operations are
performed.
CTRL-C will switch screens if the enabled task requires it. You can also
switch screens by pressing CTRL-TAB, or by poking the relevant hardware
register.
HARDWARE REGISTERS
MOUSE POINTER
The emulator can display, and return the screen co-ordinates of a simple
mouse pointer (SPRITE). Although the mouse routines work correctly with
QRAM pointer software, the co-ordinates of the sprite do not correspond
with the co-ordinates of the QRAM pointer. When using QRAM, you should
therefore not have the Amiga SPRITE pointer active.
BLIT_OFF
The BLIT_OFF command turns all blitter activity off. This will prevent the
VDU driver from refreshing the QL screen.
BLIT_ON
The BLIT_ON command turns blitter activity back on allowing the VDU driver
to properly refresh the QL screen.
This command sets the speed at the VDU driver refreshes the QL screen. It
allows the blitter to move (inc/bnd)*(1/16) th of the screen every 1/50th
of a second - for example:
SCR_PRIORITY 4,1
This will refresh (4/1)*(1/16) = 4/16 =1/4 of the screen every 1/50th of
a second.
SCR_PRIORITY 8,1
This will refresh (8/1)*(1/16) = 8/16 =1/2 of the screen every 1/50th of
a second.
SCR_PRIORITY 16,1
This will refresh (16/1)*(1/16) = 16/16 = whole of the screen every 1/50th
of a second.
If you want maximum CPU speed and don't mind a slow display, you could
try:
SCR_PRIORITY 1,2
Please experiment, but remember - refreshing more than half the screen in
1/50th of a second is just not physically possible. The default setting is
SCR_PRIORITY 4,1.
PTR_ON
PTR_OFF
This command hides the SPRITE relating to the position of the mouse
pointer.
BUGS
Due to a timing fault, for certain values of SCR_PRIORITY the first byte
of every 32 nd line flickers spuriously. The VDU driver could time BLITTER
access to screen memory more precisely, if the BLITTER commands were part
of a general COPPER list. This would reduce screen flicker since memory
access would sync with the vertical refresh automatically.
--------------------------------------------------------------------------
ACE
This ROM takes over from the blitter providing QL screen emulation via the
processor. On 68030 processors and above, screen emulation is both
smoother and faster. On earlier processors it can be too processor
intensive - so is not enabled on the F1/F2 boot screen but can be enabled
with the ACE_ON command. The ACE routines (written by S N Goodwin) have an
advantage over the blitter routines in that they fully support BOTH MODE 4
and MODE 8.
Why?
The 32 bit CPU can convert the QL interleaved display into two Amiga bit
planes faster than the Blitter in the AGA chip-set. If the CPU is used the
Qdos kernel in chip RAM runs faster and the top display update rate is
increased to a full flicker-free 50/60 Hertz. You might also like to try
it on OCS/ECS systems with a processor accelerator, but the 16 bit chip
RAM will limit the cpu's advantage. If you only have a 68000 you're almost
certainly better off using the blitter.
How?
Really, How?
The method relies on the caches for code and data and is optimised for the
68040. We copy alternate bytes from Qdos screen memory to alternate
bit-planes. The method used in ACE_CODE reads eight bytes at a time then
swaps registers around to generate two or three long words for the
bitplanes. This is much faster than the use of MOVE.B or MOVEP for byte
access.
This program detects the data cache on the 68030/40/60 and temporarily
turns it off for top speed when reading and writing chip memory.
TEST RESULTS for ACE runing on a CBM A4000/040 with Chip RAM only or with
copyback on or off in Fast RAM. These tests used ACE version 3.15, MODE 4
and the DIY Toolkit timers to time one 10,000 iteration FOR loop.
In a system with 32 bit fast memory the speed of tasks and extensions is
much increased, but the screens, Qdos and SuperBASIC interpreter routines
remain in chip memory, for compatability reasons, and that is relatively
slow. CPU caches can soak up some but not all of the difference.
Both blitter and CPU display updates are slowed if chip memory is already
busy, e.g. because of Qdos ROM reads or screen writes. The difference is
that the blitter contention is asynchronous, while the CPU is the only
thing (other than DMA) accessing chip memory during ACE screen updates.
ACE_OFF
The ACE_OFF command turns off ACE screen emulation and re-enables blitter
screen emulation.
ACE_ON
The ACE_ON command disables blitter screen emulation and enables ACEs'
processor dependent screen emulation.
This procedure determines the number of 2K chunks and number of fields per
update, 1..16 and 1..255 respectively. The default 8,2 is the equivalent
of SCR_PRIORITY 4,1.
Qdos does not allow an interrupt server to take more than 20 mS to run -
the time up to the next interrupt - so you should not experiment with high
values for ACE_PRIORITY unless you have a fast processor. Ignore this and
Qdos may lock up!
The second parameter controls the number of fields that are displayed
between one full (or partial) update and the next. A value of 1 means that
ACE runs 50 times per second (every 1 field) which imposes a heavy CPU
load but gives the most rapid screen response. A value of 2 means that ACE
runs every other frame; 3 means ACE runs once every three frames, giving
more time for programs at the price of only about 17 full or paritial
updates per second. The second value can be up to 255, which leaves 99.6
per cent or more of the CPU time for 'real' programs but gives a very slow
screen update - about one update every 5.1 seconds! If you have fast
memory you're probably better off using the blitter than ACE in this case.
ACE_ON and ACE_OFF link and unlink the interrupt handler. ACE_PRIORITY
reports 'not found' if you try to use it when ACE is not linked in.
ACE_RATE%
This function returns the number of fields that are output to the screen
between one ACE update and the next.
ACE_SIZE%
Together these functions ACE_RATE% and ACE_SIZE% let you read the current
ACE_PRIORITY settings.
--------------------------------------------------------------------------
KEYBOARD
QL RESET
SECOND SCREEN
It is possible to flick between the second screen and the standard screen
by pressing CTRL-TAB.
INTERRUPTS
SPECIAL KEYS
KEYDT
KEYUK
PTR_LIMITS [<Xleft>,<Ytop>,<Xright>,<Ybottom>]
This command sets limiting bounds for the position of the mouse pointer.
The default limits are 0,0,256,256
PTR_INC [<Xdist>,<Ydist>]
This command sets how far the mouse must be moved before the KEYROW
function registers cursor movement. By default Xdist is 4 and Ydist is 8.
PTR_X%
PTR_Y%
--------------------------------------------------------------------------
SOUND
QDOS sounds are supported in full, via the SuperBASIC BEEP command and its
equivalent machine code MT.IPCOM command (Trap#1 with d0=$11).
--------------------------------------------------------------------------
SER DEVICE
SER DESCRIPTION
On input, CR, LF and the CR/LF couple are translated into a single LF
character - unless RAW is selected as the end of line protocol.
In future releases 'IH' may be extended to 'IHX', allowing for Xon/Xoff
(software) handshake.
--------------------------------------------------------------------------
PAR DEVICE
PAR DESCRIPTION
In future releases 'IO' may be added to the syntax, allowing for input
and output to the parallel device.
--------------------------------------------------------------------------
FLP DEVICE
The floppy driver has a number of associated keywords. The commands MOUNT
and DSKCNG are necessary for older drives that do not respond correctly to
disk changes, or do not supply a disk ID. The command DISKCOPY is included
because it is incredibly useful. FLP_USE, PROG_USE, DATA_USE etc are
implemented for compatibility with QL disk interfaces that invariably
include such commands.
MOUNT <drive>
Use MOUNT 1 for FLP2_, MOUNT 2 for FLP3_, or MOUNT 3 for FLP4_. The
emulator tries to read a disk ID from every drive, and only allocates
drive buffers for those drives that respond correctly. Unfortunately some
older drives do not have this feature, and on such drives you will need
to use the MOUNT command. Issue this command once only, immediately after
a boot, and only if the drive is not recognised.
DSKCNG <drive>
Use DSKCNG 1 for FLP2_, DSKCNG 2 for FLP3_, or DSKCNG 3 for FLP4_. The
Amiga hardware automatically recognises when you insert a new disk into a
drive. Unfortunately some older drives do not have this feature, and on
such drives you will need to use the DSKCNG command each time you insert
a disk afresh.
DISKCOPY [#<channel>]
DISKCOPY duplicates the disk in Flp1_ onto the disk in Flp2_. You require
two drives in order to use this command. DISKCOPY will ask you to insert
the source and destination disks before proceeding. Messages are printed
on the specified channel, or to #0 if no channel number is given. It is
possible to BREAK from this command with CTRL-SPACE.
FLP_USE <name>
Sets the name of the floppy disk system. By default the name of the floppy
disk system is 'FLP', but this can be changed for example to 'MDV' or any
other three-character string.
PROG_USE <name>
DATA_USE <name>
SPL_USE <name>
DEST_USE <name>
As SPL_USE except that this command appends an underline the the <name> if
none is present.
PROGD$
DATAD$
DESTD$
--------------------------------------------------------------------------
JAN DEVICE
The JANus device driver gives you access to the Harddisk from the IBM
Sidecar within QDOS.
The JANus device driver expects the program QLDISK.COM running on the IBM
side. This program is also included in source format (QLDISK.PAS) and must
be compiled with TURBO pascal 3.0! Any filename has the form: JAN1_name_ext
where 1 [,2,3,4,5,6,7,8] has no function. The extension is converted from
_ext to .ext automatically. Names consist of capital letters only and must
not be longer than 8 characters.
Subdirectories and file conventions of MS-DOS are used. If you try to read
MS-DOS files from QDOS, you will experience some trouble, since QDOS needs
a 64 byte fileheader, which is of course not present in MS-DOS files. The
other way around, you will find 64 additional bytes at the top of any QDOS
file, when you try to read QDOS files from the IBM side.
CHDIR <"path">
MKDIR <"name">
SHODIR
JAN_USE <"abc">
At present, the emulator cannot access data on hard-disks, except via the
JAN device on JAN drives on a machine with a Bridgeboard installed.
--------------------------------------------------------------------------
HARDWARE DIFFERENCES
The Amiga hardware does not allow the CPU two contiguous bus cycles. This
means that any READ-MODIFY-WRITE cycle fails, and as a result the machine-
code instruction 'TAS' does not function correctly on the Amiga.
NO_TAS
If the code is less than 32K in size, NO_TAS will attempt to replace all
TAS instructions by a branch to an equivalent subroutine. The subroutine
is tagged onto the end of the code, so any file processed in such a way
will 'grow'. The result is a task that is compatible with both
Amiga-QDOS and a 'real' QL, but which might confuse tasks that make
assumptions upon their own length.
With both the small and large code fixes, a disassembly is shown and you
will be asked whether or not to replace the code. Note however that the
program may display TAS instructions where none are present (i.e. within
program DATA). A good rule-of-thumb is that true CODE is usually
surrounded by other machine code instructions, whereas DATA is liberally
sprinkled with DC.Ws
RESTORE_TAS
Use this program to 'put-back' TAS instructions into programs that have
been altered by NO_TAS.
--------------------------------------------------------------------------
SOURCE FILES
The complete assembly source for the emulator is included with this
release.
If you need to alter a source file in any way, use an editor that
preserves TABS. If you use an editor that expands tabs to spaces during a
SAVE, you will find that file will increase in size dramatically - to a
point where it may exceed available disk space.
In order to view the source files correctly, tabs should be set to NINE
characters.
Expansion ROMs handle all Amiga specific functions, freeing the QDOS ROM
of any hardware dependent source. There are separate ROMs for VDU, Clock,
Keyboard, PAR device, SER device and FLP device. This makes de-bugging a
lot easier.
Each ROM has its own MAKE file. CD into a make directory and type the
name of the relevent script file to rebuild a particular ROM.
I have commented the QDOS ROM source wherever it differs from either the
original JS source, or from Rainer Kowallik's version. Comments begin with
the characters ";*/" so are easily found. There are a number of keys
following these characters, that identify the kind of modification. These
are:
;*/note
;*/mend
;*/modify
;*/overlay
This indicates that the code differs significantly from the JS version.
;*/insert
KEY MODIFIERS
undo
;*/undomend
This means that an apparent bug, fixed in a previous release, was not a
bug after all.
These indicate the start and end of a section of code that is inserted
anew.
--------------------------------------------------------------------------
SER_TRANSFER_bas
POKE_DIGITS_bas
BOOT
The boot program on the 'QLutils' disk loads a number of toolkits into
memory, and sets up a small RAM disk.
PD RAM-disk
PDTK_rext
D68K_rext
SYS_REF_task
SYS_REF is a utility that patches tasks & M/C which rely on the system
variables being at $28000, to work when the sys vars are elsewhere (i.e.
with the second screen enabled).
It has been tested on several programs (even TURBO) under Minerva and
Amiga-QDOS (with 2nd screen enabled), and WORKS!
--------------------------------------------------------------------------
I bought my first QL in 1984 in Berlin, and since this time the QL has
proved to be a very handy tool for all kinds of computer work.
Unfortunately the QL was not very popular. It has an active user group,
but little software or hardware. With the arrival of the ATARI 520 ST and
the increasing popularity of the IBM clone the QL became less and less
interesting to new users, until eventually even Sinclair himself lost
interest.
So far so bad, but after checking the possible alternatives, there was no
computer that was any better than the QL. Then came the idea of building a
new computer with QDOS, a 68000 CPU and a reasonable keyboard -- but why
build a new computer, when you can buy one?
For this purpose the AMIGA seemed best suited. It is highly expandable and
has excellent hardware. Furthermore, it seemed easier to emulate a QL
screen on the AMIGA, than on the ATARI.
Apart from the MicroDriVes and NETwork, the emulator implements all the
standard QL devices (CON_, SCR_, PIPE_, SER1, PAR, FLPn_).
RAINER KOWALLIK
--------------------------------------------------------------------------
ADDENDUM
CONTINUING DEVELOPMENT
I am under the impression that due to recent commitments, Rainer has very
little time to make any further improvements to the emulator. Therefore,
in Rainers absence, I have taken on the responsibility for the emulators'
continuing development.
MARK J SWIFT
--------------------------------------------------------------------------
SOFTWARE OVERVIEW
Most of the descriptions do not mention which version of the emulator the
software was tested on, or who did the testing. I have included a version
number and my initials wherever I have been able to confirm the validity
of a particular statement. If you would like to add you're own comments on
a particular program, please let me know.
MARK J SWIFT
--------------------------------------------------------------------------
This Toolkit is almost an essential for Working with QDOS. It provides you
with JOB handling, parameter passing facilities, a full screen BASIC
editor, a command line stack, wild card file functions, default devices,
definable keys and many other useful commands. It's a shame there's no
public domain equivalent.
For those who miss the Workbench and mouse handling, this is the QDOS
equivalent. There are more and more programs appearing on the QL that use
this interface as a front-end. It takes some getting used to.
At the very least PTR_GEN must have TAS instructions removed. Other
files may also need to be fixed. Be very careful however not to
TAS-replace DATA.
Bundled with the pointer environment and the QRAM 'workbench' equivalent.
IMPLEMENTATION NOTES
--------------------------------------------------------------------------
This compiler has almost the same degree of usefulness as the T. Tebby
toolkit. The compiled programs are not among the fastest, but the compiler
can cope with nearly every program. It can include M-Code toolkits in the
object file, and produces small code when used in conjunction with the
resident runtime library. Compiled programs can be linked as resident
toolkits to the interpreter, and procedures can made accessible to BASIC.
Much faster than the Qliberator, but can not pass parameters back to the
caller, and has many small quirks. Supercharge was a precursor to Turbo
with a very remarkable copy protection 'device'. Turbo itself is not
protected anymore.
If you wish to make use of the second screen under Amiga-QDOS (or
Minerva) you must use SYS_REF to remove all references to the system
variables (which are moved with 2nd screen enabled)
The SYS_REF'ed version of TURBO works under Minerva and Amiga-QDOS with
the second screen enabled. It produces code identical to the unpatched
version, so remember to patch all TURBO-compiled tasks!
These are the QDOS Versions of the widely used Prospero compilers. There
are few bugs (in my Version the Double Precision Arithmetic gives problems
when passed through Functions), and they give access to all QDOS
functions. They produce QDOS standard relocatable format and use the same
Linker that comes with the GST Macro assembler and the GST QC compiler.
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
Forget it !
Lattice C [Metacomco]
The only full scale C implementation for the QL. There are bugs and the
Floating-point arithmetic is terribly slow. It uses QDOS standard
relocatable format as opposed to Metacomco's own format. As with Lattice
standard #ASM is not allowed, you have to write machine code programs
separately.
IMPLEMENTATION NOTES
QC [GST]
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
Not tested on Amiga-QDOS.
BCPL [Metacomco]
IMPLEMENTATION NOTES
LISP [Metacomco]
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
The professional Assembler for QDOS. Macro facilities far beyond the
standard. The assembler is small, fast, and produces standard QDOS
relocatable Format. Recently re-vamped by QUANTA programmers.
Very big (3 overlays), very slow, lots of bugs. Can be used to link
M-Code routines to other Metacomco programs, since the linker for all
Metacomco programs are compatible.
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
GenQL [HiSoft]
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
Cannot cope with addresses longer than 20 bits, so you can only debug
programs in CHIP memory. Perhaps some day HiSoft will make a new Version
for Atari/Amiga/Thor2 users. We will be grateful.
--------------------------------------------------------------------------
Slow, but CGA graphics is included and it is said to be faster than the
Amiga Transformer.
IMPLEMENTATION NOTES
--------------------------------------------------------------------------
--------------------------------------------------------------------------
IMPLEMENTATION NOTES
ED [Metacomco]
The editor supplied with all Computer one programs. It is menu driven, but
not very advanced.
IMPLEMENTATION NOTES
IMPLEMENTATION NOTES
Quill [Psion]
The original wordprocessor that was bundled with the QL. Handles
formatting well, supports bold, italic underline etc., and can create text
only files via print-to-file option.
Archive [Psion]
The original Data Base that was bundled with the QL. Although not very
advanced, and though it doesn't handle pictures or sound, it is still
sufficient for most applications. (This is the kind of Data Base, that
makes use of a special Language that looks a little bit like BASIC)
Easel [Psion]
The original Business Graphic program that was bundled with the QL. You
may find better programs on the IBM (for example Boing graph), but it is
still state of the art.
Abacus [Psion]
The original Spreadsheet that was bundled with the QL. It cannot handle
graphics, but is still state of the art.
Xchange [Psion]
Text 87
IMPLEMENTATION NOTES
GraphiQL [Talent]
IMPLEMENTATION NOTES
TechniQL [Talent]
Another drawing program but for high resolution mode. It has interesting
features, including a plotter driver, and may well be worth using.
IMPLEMENTATION NOTES
QL Art
IMPLEMENTATION NOTES
The first picture drawing program for the QL that supported the mouse. It
is a Basic program with some M-code extensions.
IMPLEMENTATION NOTES
The cracked and compiled Version runs on Amiga-QDOS, but with problems
--------------------------------------------------------------------------
Games are mostly protected against copying and many are only available on
Microdrive cartridges.
Chess [Psion]
IMPLEMENTATION NOTES
Another classic.
IMPLEMENTATION NOTES
It works on the Amiga, but is too fast to play, since the QL had only
1/4 of the Speed.
QL Cavern [JMF]
IMPLEMENTATION NOTES
Not too bad, runs on the Amiga with modifications (Interrupts must be
enabled!)
--------------------------------------------------------------------------
BIBLIOGRAPHY
AMIGA BOOKS
680X0 BOOKS
PUBLICATIONS
QL World Magazine
(Alas, mo longer in print).
--------------------------------------------------------------------------