| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 3997.1 |  | WJG::GUINEAU |  | Wed Aug 08 1990 09:05 | 10 | 
|  | > I use the grep utility supplied with lattice C V5 it searches all the files 
> correctly and then prints the message 
>
>	can't find file(s): gdos
Well, I don't know why that message is there, but I would get my copy of
NewZAP out and fig it to say ADOS, not gdos :-)
john
 | 
| 3997.2 | More information please! | SDOGUS::WILLIAMS | TOPGUN | Wed Aug 08 1990 18:38 | 5 | 
|  |     I don't know either.  But I'll try using my lattice C V5 grep and
    see what I get.  Got some more information on what you are configured
    as?  E.g.  expansion disk, memory, etc.?
    
    TOPGUN
 | 
| 3997.3 | Some more info...... | MAJORS::BASSETT | John Bassett. UKLEG DTN 7830-4017 | Thu Aug 09 1990 04:20 | 21 | 
|  | my configuration :-
	
	A500 + 1/2 Mb expansion
	A590 + 2Mb
Usually I have the following software running : ARP 1.3, Mackie (POPCLI 
replacement). 
As an example of the problem if I search all .c files using
grep garbage #?.c
then I get the message given in .0 If I then create an empty file called gdos
in the current directory everything proceeds normally and no message is 
produced. 
BTW As I never use workbench I have deleted most of the .info files 
from the system disk. Could this be causing the problem ?
thanks,
John.
 | 
| 3997.4 | Location 0 bug | FROCKY::BALZER | Christian Balzer DTN:785-1029 | Wed Aug 15 1990 11:50 | 15 | 
|  |     Re: *
    
    You have the classic A590/A2091 "Location Zero Bug". This is caused by
    improper programmed applications that read address zero (instead of
    using a NULL pointer) which got changed from zero to point to string
    with the contents (you guessed it) "gdos" by a debugging version of the
    FastFilesystem that got shipped with the early CBM controllers.
    To get rid of this, update the FastFileSystem on your RigidDiskBlock
    with the 1.3.2 release. Since I don't own a 2091 or 590 I can't tell
    you exactly how to accomplish this, but it has been descriped over and
    over again on UseNet.
    
    Regards,
    
    <CB>
 |