Hi All,

Not that it's too important, I just can't remember what this program
was called.
I'll describe. It may be a Fast Hack 'em version, but I seem to
remember track/sector editing with hex and ascii editing. What set
this apart was the raster bar redraw when you returned through menu
options. The menu would redraw it's border lines from top to bottom in
semi-slow way, then display the text within the drawn border. Black
background. Could have been a red border. I can't remember the
character color.

Now all the Fast Hack 'ems I've seen on the net draw their menu
characters from the middle of the screen outwards, left and right.
None of them have a disk track/sector editor either.

Just thought it was an intersting looking program I'd like to see
again.

Don't email my listed address, it has been overrun and destroyed by
spammers.

Christian

c_lott0@lycos.com (Christian) wrote in message news:<2ad3f75e.0405061505.7e11945e@posting.google.com>...

> I'll describe. It may be a Fast Hack 'em version, but I seem to
> remember track/sector editing with hex and ascii editing. What
> set this apart was the raster bar redraw when you returned
> through menu options. The menu would redraw it's border lines
> from top to bottom in semi-slow way, then display the text
> within the drawn border. Black background. Could have been
> a red border. I can't remember the character color.

I don't know what a raster bar is, but KWICK COPY's sector editor
had a black background.  The sector data is in red.  It runs on a
C64 or 64 mode on a C128.  I am unable to run it on a 1581 or a
1571 in 71 mode.   I have run it on 1571's in single sided mode.
It may run on 1541 clones.  I used it once to rescue a disk with
a badly corrupt BAM and other systems data.  A sector editing
program using ordinary sector access was completly stymied by
this disk.  It must use advanced sector access techniques.

> I used it once to rescue a disk with
> a badly corrupt BAM and other systems data.  A sector editing
> program using ordinary sector access was completly stymied by
> this disk.  It must use advanced sector access techniques.

Thanks,
  That was it. Kwick Load (Kopy).
I'd like to hear more about your disk rescue.

Christian

c_lott0@lycos.com (Christian) wrote in message news:<2ad3f75e.0405120858.7eff5368@posting.google.com>...
> > I used it once to rescue a disk with
> > a badly corrupt BAM and other systems data.

>   That was it. Kwick Load (Kopy).
> I'd like to hear more about your disk rescue.

The problem with KL is that it won't work on a 1571
in 71 mode.  I am almost positive that it won't work
on a 1581.  It may choke on 1541 clones as well.

I used to use a program loading accelerator from the
December 1989 issue of RUN magazine.  Michael Miller
(BIG BLUE READER) is the author. It accelerates loads
from either 1571's and 1581's on my C128 in 64 mode.
It may even work on a stock C64.  I modified the
program so that it works with the C64 system LOAD
command rather than its own user directory interface.

These kinds of programs store a program segment in
the drive's memory.  This particular program worked
perfectly on the 1581.  Mr. Miller chose the location
used by 1571's for the disk's systems data.  There are
circumstances in which the drive would replace the systems
info on a disk with a portion of the accelerator program
in the drive's memory.  Subsequent ordinary access
attempts would fail because the corrupted disk systems
info.  The problem was corrected by including a disk
INITIALIZE command in the program's endjob processing.
Complaints to RUN and Mr. Miller proved futile.  RUN
insisted that my program modification were the cause of
the problem.  Mr. Miller had BBR on his plate and couldn't
be bothered with issues that would be of no profit.

Fortunately for me the KL sector editor uses nonstandard
commands for disk sector access.  None of my other sector
editors were able to penetrate the disk's corrupt system barrier.

> The problem with KL is that it won't work on a 1571
> in 71 mode.  I am almost positive that it won't work
> on a 1581.  It may choke on 1541 clones as well.
> 
> I used to use a program loading accelerator from the
> December 1989 issue of RUN magazine.  Michael Miller
> (BIG BLUE READER) is the author. It accelerates loads
> from either 1571's and 1581's on my C128 in 64 mode.
> It may even work on a stock C64.  I modified the
> program so that it works with the C64 system LOAD
> command rather than its own user directory interface.
> 
> These kinds of programs store a program segment in
> the drive's memory.  This particular program worked
> perfectly on the 1581.  Mr. Miller chose the location
> used by 1571's for the disk's systems data.  There are
> circumstances in which the drive would replace the systems
> info on a disk with a portion of the accelerator program
> in the drive's memory.  Subsequent ordinary access
> attempts would fail because the corrupted disk systems
> info.  The problem was corrected by including a disk
> INITIALIZE command in the program's endjob processing.
> Complaints to RUN and Mr. Miller proved futile.  RUN
> insisted that my program modification were the cause of
> the problem.  Mr. Miller had BBR on his plate and couldn't
> be bothered with issues that would be of no profit.
> 
> Fortunately for me the KL sector editor uses nonstandard
> commands for disk sector access.  None of my other sector
> editors were able to penetrate the disk's corrupt system barrier.


On GEnie Commodore File Library I found :

http://usa.cmdrkey.com/cbm/genie/C64ToolkitListing.html

14285 KWIK KOPY  J.SZCZAP 940203 10240
in the C64Toolkit directory.

I also found a program :

http://usa.cmdrkey.com/cbm/genie/C64-128ToolkitListing.html

4774 DISASSEMB.ARC  ML-BUG 870905 13860
Desc: 256 OP-CODE Dis-Assembler
 
in the C64-C128Toolkit directory.
In a seq file for this Disassembler I pulled this:

"The best use of un-implemented op-codes I've seen yet is KWIK LOAD
track #$11, sector #$00. It is the loader, and becomes 3 or 4
different programs."

He says it's the loader that uses the unimplemented opcodes, but would
it also be the editor?

Wish we had a commented disassembly.

Christian