Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site aesat.UUCP
Path: utzoo!aesat!rwh
From: rwh@aesat.UUCP (Russ Herman)
Newsgroups: net.micro.cbm
Subject: Re: Info on kwik load vs. 1541 flash wanted
Message-ID: <379@aesat.UUCP>
Date: Thu, 11-Apr-85 09:18:43 EST
Article-I.D.: aesat.379
Posted: Thu Apr 11 09:18:43 1985
Date-Received: Thu, 11-Apr-85 11:17:09 EST
References: <1376@amdahl.UUCP>
Organization: AES Data Inc., Mississauga, Ont., CANADA L5N 3C9
Lines: 25

I can tell you about kwikload - someone else will have to tell you about FLASH!

Kwikload is functionally the same as the TURBODISK program published in COMPUTE!
All it does is speed up loading of programs; saving and transferring data
are unaffected. Most slow-loading games do their own loading as part of their
protection schemes, so Kwikload/TURBODISK won't help you there either. If
all you want to do is load large BASIC or ML programs that start running
immediately when you type RUN, get TUBODISK - no need to spend any money.
Otherwise you'll have to spring for FLASH!

If you have the PAL assembler package and a disassembler, TURBODISK is readily
disassembleable for recreating a self-relocating version (under RPAL) that will 
coexist with your wedge. Just add a preamble to print out where the entry is
upon loading, and save/restore the LOAD vector on activation/deactivation.
Details on request.

I tried to modify Kwikload to do the above sorts of things, and couldn't get
it to work. Its code is obtuse by my standards.
-- 
  ______			Russ Herman
 /      \			{allegra,ihnp4,linus,decvax}!utzoo!aesat!rwh
@( ?  ? )@			
 (  ||  )			The opinions above are strictly personal, and 
 ( \__/ )			do not reflect those of my employer (or even
  \____/			possibly myself an hour from now.)