Path: utzoo!attcan!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!rutgers!att!occrsh!occrsh.ATT.COM!mwood.UUCP!okcusr.UUCP!bn
From: bn@okcusr.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Help with buffers, Amax, etc...
Message-ID: <6600012@okcusr.UUCP>
Date: 5 Jul 90 18:58:00 GMT
References: <2085@gould.doc.ic.ac.uk>
Lines: 32
Nf-ID: #R:gould.doc.ic.ac.uk:-208500:okcusr.UUCP:6600012:000:1537
Nf-From: okcusr.UUCP!bn    Jul  5 13:58:00 1990



>  A few months ago, there were some discussions on the harddisk controller
>  not clearing memory location 0. Well, I found that a few of the PD programs
>  ( eg VirusX4.0, IconMaster ) will crash. Since I haven't got a compiler or
>  assembler ( at the moment ), the only thing that I can do is to do a POKEL
>  in AmigaBasic. Does anyone out there has a summary of the consequences of
>  doing a POKEL 0, 0? Also is there a better way of doing this?

I am also having this problem with my brand new A590. I found that VirusX3.2
works like a charm, but 4.0 crashes when it's trying to set up. Another 
problem that I'm having is that ever since I installed the HD, some of my
file requesters contain the string "gdos" as though the DOS already selected
this for me. This can be quite annoying when used with some terminal programs
such as Handshake. For example, when I'm trying to upload something with
Ymodem batch to my UNIX machine, the transfer gets stuck in an endless loop,
because the term assumes I want to upload a file called "gdos". Does
anybody know a cure for this??? By the way, the problem mentioned in the
article quoted above could be cured by running the program called "memwatch"
which continuously monitors location 0 and if there is anything else besides
0 there, it will fix it. 
Plese, if anybody knows a fix for my "gdos" problem, post it here, or
email me dirrectly. 
Thanks,

Bo Najdrovsky

...att!mwood!attcc!ulab!bn
	  or try
...uunet!occrsh!mwood!attcc!ulab!bn
           and
attcc!ulab!bn@MWOOD.ATT.COM