D]3
P]00j:tlog.brush
]]P00 00
]]P00 01
]]P00 02

3]19,000 MORE BYTES
     You can free 19,000 more bytes of memory by eliminating commands made
resident by your computer's Workbench 1.3 startup-sequences. The cost will be
a slight loss of speed in execution of the commands CD, LIST, RESIDENT and
EXECUTE. You will have to know how to use a text editor to accomplish this.
Load the file StartupII, kept in the S directory of your boot disk, into an
editor. Add four lines just before the very last line of the file so it looks
like this:

resident CD remove
resident List remove
c:resident Resident remove
resident execute remove
break 1 C ;signal to other process its OK to finish

     This allows the commands to be used during boot but removed later so the
memory can be used for other things. To prevent the commands from being made
resident in the first place, thereby keeping your extra 19,000-plus bytes all
in one big chunk with the rest of memory, add a semicolon (;) to the lines
shown below, rather than adding the four resident remove lines:

;resident c:Resident pure
;resident c:List pure ;pre-load LIST and CD
;resident c:CD pure
;resident c:Mount pure ;the next 3 are loaded for speed during startup
;resident c:Assign pure
;resident c:Makedir pure  

     If you use this second method, you must also add a semicolon to the
three resident remove lines later in the file so they look like this (or
resident will try to remove them, causing a system lockup since they aren't
there to be removed):

;resident Mount remove ;if you have enough ram, keep these resident
;resident Assign remove  ;by removing these lines
;resident Makedir remove

     Finally, in the Startup-sequence file itself (also in the S directory)
add a semicolon to the line that makes Execute resident:

;resident c:Execute pure

     This second method will make your computer take longer to boot but
avoids "fragmented" memory. Neither method will make the Amiga work any
differently than before except for the time (and memory!) increases described.

3]2.0 ED'S HIDDEN MENU - Staff
     The ED program on Workbench 2.0 has pulldown menus. You can add an
additional three menu items if you either DELETE or change the name of the
file:

s/ed-startup

. . .on the disk. First, invoke ED and see what's available. Then delete the
file and try again, to see what you gained. Surprise!

3]IMPROVED VOICE - Alice Garcia, Miami, FL
     It's said the 2.0 operating system has an improved Amiga voice. It seems
to me the difference is that words are given more definite ending sounds,
resulting in an almost clipped style. Perhaps I will get used to it after a
while. Meanwhile, does anyone have two side-by-side Amigas on which the
differences could be qualitatively checked by inputing the same sentences
into both? Wish I could.

3]DOUBLE SEARCH FOR DOUBLE FINDS - Lee Rainey, Houston, TX
     The problem was to find data entries that included both a date
(06-05-90) and place (Dallas) from among more than a thousand lines. I
could've written a brief program seeking both these occurrences within each
line, but a simpler method presented itself through AmigaDOS SEARCH command.
     I first SEARCHed all occurrences of the date to a holding file in RAM:

search > ram:hold myfile 06-05-90   <press Return>

     Then I SEARCHed the RAM:HOLD file for all occurrences of the second
string:

search > ram:hold2 ram:hold Houston   <press Return>

. . .producing a RAM:HOLD2 comprised of all lines (but no others) including
both the sought date and place.
     Had there been a third string to find, I could've SEARCHed to a third
ram:file. Ad infinitum.
     But there weren't
     So I didn't.

3]VIDEO SOUND EXCELLENT - Robert Leitner, Bronx, NY
     Most portable tape recorders produce junky sound. I prefer to use my
video camera as an in-the-field recording device, then pipe the sound
directly into my sound digitizer. Video sound is superior. The video camera
is easier to carry than sound equipment and sometimes results in images worth
digitizing.

     FROM THE EDITOR: This issue's SOUNDSHOW may interest you. You could, as
example, aim your camera at a songbird, then wed a digitized still image and
digitized sound with Nico Francois' program.

3]TALK IT UP - Bruce Hill, Minneapolis, MN
     With AmigaDOS 1.2, to hear a file spoken in the Amiga voice it was
necessary to use the following:

say -x filename <press Return>

     With 1.3 came a considerable improvement. The SPEAK: device handler.
SPEAK works like other handlers such as PRT:, PAR: and SER: (for printer,
parallel and serial devices). The beauty is that it allows a simple AmigaDOS
command to hear a file spoken in the Amiga voice:

copy filename speak:  <press Return>

3]COLOR SPLITTER HOORAY - Jim Hogan, Tulsa, OK
     Weakest link in the otherwise excellent DigiView digitizer from NewTek
is its ticky-tacky color wheel. The first version I owned came with a square
of with red, green, blue and clear plastic for the various exposures required
to get full color. It got scratched and in time fell apart. The second
version of the program I bought had a wheel made of paper and thin
cellophane-like color squares. It was a joke. Once its holder was inserted,
it was a pain to store and in time was predictably squashed.
     Then I got MicroSearch's color splitter and my digitizing life was
simplified. The red-green-blue passes are as simple as flicking a switch to
the desired color. Both hue and saturation can be set. I've been using it for
four months now and am almost at the point of throwing away my backup -- the 
broken plastic color wheel.

3]`INVISIBLE' ICONX - K. D. Arthur, Charlotte, NC
     The magical effect of having IconX run a program is destroyed by the
appearance of the big IconX window on the screen before and after the run.
     My advice is on how to create an "invisible" IconX window. But first:
     IconX is an AmigaDOS command in the C directory of Workbench. It runs an
AmigaDOS batch file command or commands. In practice, it is often used to
execute a script file to activate iconless programs with the AmigaDOS RUN
command.
     Example: You find a program called HELEN. It has no icon. You write a
simple batch file called HELENRUN with the ED or any other text processing
program. Here it is:

run mydisk:helen

     Then you assign a PROJECT type icon to HELENRUN, for example by copying
it from another program, as in the CLI/Shell command:

copy somedisk:oldicon.info to mydisk:helenrun.info

     Then choose INFO from the pulldown Workbench menu (on 2.0 this is
INFORMATION from the ICONS pulldown menu). In the window named DEFAULT, type:

iconx

. . . and save the result.
     From this point, double-clicking the HELENRUN icon activates the
batchfile that runs the HELEN program. The large IconX window brags about
itself by being present before and, briefly, after the program run.
     Now, all this was for beginners.
     Open the INFO or INFORMATION screen again. In the tooltypes window,
type:

WINDOW=CON:0/0/1/1/

. . . and save.
     Now, when you run the program, the IconX window is an infinitesimal one-
pixel wide and deep window at the extreme northwest of screen. In essence, it
does not show and the user will be unaware IconX is even being used.
     Two warnings:
     -- Resist the temptation to make the CON zero pixels, as in 0/0/0/0/.
You'll just get a pyrotechnical lockup that will make you unhappy.
     -- This method presumes nothing is meant to be displayed in the IconX
window, as in TYPEd statements about what's happening and the like. It won't
be seen.
     In practice, I get around the awkward naming of the batch file by
renaming the original program with an "x" suffix and naming the batchfile as
the original was. In other words, RENAME helen as XHELEN and create the batch
file as HELEN for the same effect.

3]I'M JOE'S BRAIN - Kevin Smart, Cincinatti, OH
     This is your brain:  O
4]                                         \ | /
4]                                          \|/
4]     This is your brain on the Amiga:   ===O===
4]                                          /|\
4]     EXPERIMENT WITHOUT FEAR!            / | \

3]MONITOR FOR MOVIES - Jeff Stoker, N. Hollywood, CA
     You can use a color monitor such as the 1084 or 1084S as a TV for
playing videos from a VCR. Get two cords with RCA-type jacks -- the same kind
your stereo uses. On the 1084 (which I have) run the cords from the VIDEO-
OUT, SOUND-OUT on the VCR to the corresponding INs on the monitor. I think
you'll find picture quality superior to most regulation TVs.
     Yes, you can receive regular channels if you have, for example, a cable
TV decoder with channel-changing buttons.
     I discovered all this in the wake of my 10-year-old TV's demise and the
nearly immediate realization I preferred to buy more Amiga peripherals to
springing for a new TV.
     Plus, I'm getting fine exercise in the nightly tote of the monitor from
the computer room to the front room.

3]FASTER BASIC REFRESH - Fred Nally - Atlanta, GA
     Notice how slowly the Basic LIST window is redrawn when it is refreshed,
for example, after putting another window over it.
     The following patch improves the refresh time markedly by changing the
LIST window from SIMPLE_Refresh to SMART_REFRESH, which is much faster.

DEFLNG a-z
CHDIR "extras:basicdemos/"
LIBRARY "dos.library"
DECLARE FUNCTION xopen() LIBRARY
a=xopen(SADD("extras:amigabasic"+CHR$(0)),1005)
CALL seek(a,22289,0)
CALL xwrite(a,SADD(CHR$(0)),1)
CALL xclose(a)

3]NEAR NLQ ON THE MX-80 - Markley Groff, Upper Darby, PA
     If you have the old Epson MX-80 without near letter quality (NLQ) mode,
here is a way to get a good, nearly NLQ printout.
     You must select the EPSONXOLD driver from Preferences.
     In the command lines ahead, note that "ESC" means to press the ESC
key, not to type the characters "ESC". Press the ESC key, then type the rest
of the line.
     With Workbench 1.3, open a Shell window and type:

copy * to df0:utilities/nlq2   <press Return>
esc [1m                        <Return>
esc [4"z                       <Return>

     Then press the CTRL and \ keys together. Wait until all disk drive
lights go out and stay out. Then type:

copy * to df0:utilities/nlq        <Return>
copy df0:utilities/nlq2 to prt:    <Return>

     Again, press the CTRL and \ keys at the same time.
     Copy a Project type icon to NLQ. A Notepad file icon is an example.  A
template for the SHell/CLI command follows:

copy mydisk:projecttype.info to df0:utilities/NLQ.info   <Return>

     On your Workbench, open the Utilities drawer. You should see the icon
for the new file called NLQ. Click once on the icon, then select INFO from
the Workbench pulldown menu at top left of screen. In the INFO window that
opens, click on the right side of the DEFAULT TOOL window and backspace to
delete all type in the window. In that window, type:

c/iconx

. . . and click on SAVE at bottom left of screen to save the new version.
     That does it. From then on, when you wish to print in near-NLQ, double-
click the NLQ icon. An IconX window opens and the codes are sent to the
printer, an event proved by two line feeds. Printing will then be in the
near-NLQ mode.

3]AMIGA 3000 - WHAT DOES AND WHAT DOESN'T - Peter Margenau, Shohola, PA
     As an early buyer of the Amiga 3000, I will tell you about some of the
things that seem to work and some that don't.
     I am using the 16 Mhz A3000 with the original NEC multisync monitor.
The monitor was manufactured in 1986 (before IBM introduced VGA). These are
my observations and experiences, and I cannot guarantee that others will get
the same results.
     One can presently choose to boot the machine with Kickstart 1.3 or
Kickstart 2.0 when the first powers up. After turning on the power, hold down
both mouse buttons. In a few seconds, a menu appears that allows one to
choose which OS to use and whether to boot from the hard drive or floppy
drive. The default is Kickstart 2.0 on the hard disk, and no menu will appear
unless both buttons are pressed. If a user wants to change to the other
version of Kickstart, he must perform a cold boot --turn the power off, wait
about a minute, turn the power back on while holding both mouse buttons down,
and select the version of Kickstart he wants to use.
     JUMPDISK experiences no unexpected problems on the A3000 when one boots
with Kickstart 1.3. We already know AmigaBASIC and A/C Basic programs will
not work. The PLAY program that Jumpdisk uses to play music scores works as
expected. The reader program, jd, was modified for the September issue of
Jumpdisk. If readers move Jumpdisk to another disk (such as a hard disk),
they must be sure the util drawer resides in the root directory of that other
disk. If not, the jd (Articles) program will not work.
     When one uses Kickstart 2.0, the PLAY program does not work. I haven't
been able to figure out why yet. Basic programs do not work, and the util
drawer must still be in the root directory. Icons are placed on the screen
slowly and piled on top of each other. Is this the problem one user was
experiencing? Straighten out the mess in the window by selecting CLEAN UP
from the WINDOW menu on the Workbench screen. One can make the change
permanent by selecting SNAPSHOT ALL from the WINDOW menu.
     (JUMPDISK NOTE: We are now editing the appearance of icons within
windows for correct appearance under 2.0 --presuming the use of the default
8-point font.)
     I made an interesting discovery while working with some of the Newsflash
disks. I can use my setup as a PAL (European) Amiga. Many of the demos were
chopped off at the bottom and much of the music didn't play properly.
Problems were especially evident when I ran the disks with Kickstart 2.0. I
suggest people use the startup-sequence in the s directory on NF12, (or
something similar to it), in place of the regular startup-sequence. That may
be boring, but you'll have a lot fewer problems. Don't run the program,
openlook, on NF12.
     What I am about to describe should only be tried with the A3000 and a
multi-sync monitor. I also assume the monitor is connected to the VDE port.
If you try it, you are on your own. I cannot be responsible for any damages.
     Open the System2.0 disk. Open the Monitors Store drawer and Monitors
drawer. Drag the PAL icon from the Monitors Store drawer to the Monitors
drawer. Close the windows and reboot the machine. The program AddMonitor in
the startup-sequence tells the system there is a PAL monitor attached.
     In order to use the multisync monitor as a PAL monitor, you need to run
the ScreenMode program in the Preferences drawer. Select PAL:HIRES (that mode
seems to work best with my setup) in the choose display box on the left. With
your finger on the OFF switch for your computer system, click on the USE
gadget. If your monitor makes strange sounds or does other unnerving things,
SHUT THE SYSTEM DOWN! Forget you ever read this.
     Hopefully, your system will be displaying in PAL mode, although you may
very well have to adjust the display with the monitor's manual controls. You
now should be able to play the music that wouldn't work before, and see the
entire demo screens (some still don't exit very gracefully, though). Probably
the easiest way to try this out is to put a Newsflash disk in df0: and open
it. Select SHOW ALL from the WINDOW menu. Open drawers until you find a
hammer icon with a name you think is one of the demos or music pieces that
has been giving you trouble. It should work properly when you double-click on
it.
     I have rebooted in PAL mode after clicking on the Save gadget in the
ScreenMode program after selecting one of the PAL display modes, but the
results have been inconsistent. My dinosaur of a monitor is not able to
display the highest overscan resolutions, but I don't really care because I
don't have to look at the scan lines and flicker anymore.
     Here are other things I have noticed that don't seem to be documented:
     -- If one holds down both mouse buttons when he is doing a warm reboot, a
menu appears that allows him to choose which disk to reboot from, among other
things.
     -- If there is a bootable disk in df0:, the system will try to boot
from that disk.
     -- One can use Workbench 1.3 with Kickstart 2.0.
     -- One cannot use Workbench 2.0 with Kickstart 1.3.
     -- RAD: is still with us. After one issues the command, "Mount
RAD:", and accesses RAD: for the first time with a command such as, "Dir
RAD:", RAD: is automatically mounted and available after warm reboots.
     -- One can diskcopy a floppy disk from DF0: to RAD: by dragging the
icon of the disk in DF0: on top of the icon for RAD:.
     -- By pressing both mouse buttons when doing a reboot, one can choose
to reboot from RAD: if it is mounted. Once you select this option, the
computer will try to boot from RAD: on subsequent warm reboots.
     -- Press both mouse buttons when rebooting to access the boot menu if
you don't want to reboot from RAD:.
     -- You can execute scripts with the Execute Command in the Workbench
menu. Enter "Execute" (don't type the double quotes) and then the path and
script name in the requester.
     -- If the script protection bit is set, you do not have to preface the
script name with "Execute" in the Execute Command requester.

3]B.A.D. VERSUS X-COPY'S OPTIMIZE - Staff
     You may have noticed how quickly JUMPDISK icons appear on the screen.
They do so because the archive of every issue (and hence every copy) is
"optimized," that is, restructured for fast loading.
     For months we had been using B.A.D. (Blitz A Disk), which does the
restructuring by copying contents from one disk to another.
     We have switched to X-Copy's OPTIMIZE feature, which works better
because it restructures a disk IN PLACE, rather than to a new disk. 
Moreover, is gives a graphic verify record of the revision, track by track.
     X-Copy is the copy program we use to copy all JUMPDISKs. The OPTIMIZE
feature is just icing on the cake.

4]END OF TEXT