Msg: 2426 *Conference*

04-20-92 07:02:27

From: LEX JENKINS

To : RICHARD HANSON

Subj: GREMLINS II

I've done a bit of experimenting since I first mentioned the gremlins I noticed
in merging T-Base comma delimited data files into T-Word files.  I can now  
regularly duplicate the error, which is progress of a sort, if you can call  
consistently making mistakes progress.  It is, at least, consistent.
 
If you have a taste for bug, here's the recipe:
 
 1. Take any comma delimited data file;
 
 2. Using ^Q#, merge gently into a T-Word file;
 
 3. From the T-Word menu, press F4 (Disp) to preview your merged file - it  
should appear normally;
 
 4. Now press F2 (Plot) - wait for FUN TO BEGIN!
 
 5. A pixel-approximation of your merged file will appear, accompanied by a  
friendly "Out of Memory" message;
 
 6. Try to unlock your constipated laptop.  Try like hell;
 
 7. Never mind, you can't.  Press the RESET button;
 
 8. If the RESET has landed you in the UR-II menu, stifle that sigh of relief  
until you've examined the FUN THINGS that have happened to your files;
 
 9. If, on the other hand, the RESET has landed you in the system menu you've  
probably already discovered some of the FUN THINGS, i.e., garbled filenames,  
garbled data in files and, if you're very lucky and experienced an
exceptionally FUN CRASH, your files have played musical names and swapped
titles with their  promiscuous neighbors.
 
 10. Now, let that sigh go!  I expect, however, by this point you will be  
expelling sounds of a different sort.  But wait!!  FUN is not yet over!!!
 
 11. Try to recover your text files.  Forget the .BA and .CO files - they're  
gone.  Try using T-Word to edit and correct your text files.  Try using
ROM-View 80.  Discover that MORE FUN THINGS have happened, i.e., the Nanytes
that plagued the Enterprise on Star Trek-Next Gen. appear to have invaded your
UR-II ROM and  reprogrammed it into an instrument of mental torture.
 
Actually, it's not all that bad.  If you're using a standard UR-II ROM just
kill the UR-2 file, cold start your laptop and reinitialize the ROM.  If you're
really paranoid, with a tendency toward wearing crystals and calling dial-a-
psychics, you might also want to yank your ROM from the guts of your laptop and
let it heal overnight in one of those pyramid-shaped cartons for Pharaoh  
Pretzels.
 
If, however, you're using extRAM with a UR-II image you'll have to kill the  
current image (I used MEMTST.BA from the extRAM disk) and reload the image.   
Somehow the merge-crash that started this mess corrupts the extRAM image.  So  
apparently the extRAM is not completely immune to cold starts, crashes and the
odd Nanyte.
 
My solution: tape over the F2 key when performing data file merges in T-Word.
Not very elegant, but when it comes to programming I'm more of a tool user than
a tool maker.
 * * * * *
DISCLAIMER: The opinions expressed are strictly those you have just read and do
not neccesarily refract the policemen of this mismanagement.  Opposing  
viewpoints usually are.  For further information write or call your
grandmother.
  Residents of TX, MN, AX, NF, PU include .07(5/8)^2% thumbtacks.  Void where  
neccesary.  Not responsible.
 * * * * *
 
<Lex>