daveh@cbmvax.UUCP (Dave Haynie) (09/19/88)
Well, maybe it's not all that DANGEROUS...
But in any case, there appears to be a bug in DiskSalv V1.2. The
symptoms are that issuing a "DiskSalv DF0: DF1:" command always turns out
reporting "DF1: FULL". The strange part is that this only happens in some
setups, and so far it hasn't happened on either of my home machines, which
are fully loaded B2000 and nearly empty (1 meg) A1000. I plan to fix this
bug as soon as I can find it. In a related story, the NOCHECK options,
which was the obvious workaround, doesn't really work either. SO, if you
happen to come by DiskSalv V1.2 anywhere, you probably don't want to bother
with it. PLEASE don't pass it on anywhere if you have it; the fixed version,
DiskSalv V1.21, will be released in a day or two. If you do have this program,
and do find the aforementioned bug happens on your machine, I'd appreciate it
if you could just send me a quick note explaining the machine type you have
and the tasks you're running at the time.
THANKS!
--
Dave Haynie "The 32 Bit Guy" Commodore-Amiga "The Crew That Never Rests"
{ihnp4|uunet|rutgers}!cbmvax!daveh PLINK: D-DAVE H BIX: hazy
"I can't relax, 'cause I'm a Boinger!"daveh@cbmvax.UUCP (Dave Haynie) (09/21/88)
in article <4768@cbmvax.UUCP>, daveh@cbmvax.UUCP (Dave Haynie) says: > Xref: cbmvax comp.sys.amiga:24915 comp.sys.amiga.tech:2439 > Distribution: > > But in any case, there appears to be a bug in DiskSalv V1.2. It's fixed. But I couldn't resist adding another enhancement. It'll make it worth your while DLing DiskSalv V1.21 if you already have the V1.2, other than the fact that it now works. It will be sent around this week; please avoid distributing V1.2 in the meantime; it's embarrasing enough already 16 BIT INTS STRIKE AGAIN! -- Dave Haynie "The 32 Bit Guy" Commodore-Amiga "The Crew That Never Rests" {ihnp4|uunet|rutgers}!cbmvax!daveh PLINK: D-DAVE H BIX: hazy "I can't relax, 'cause I'm a Boinger!"
stevex@ziebmef.uucp (Steve Tibbett) (09/21/88)
Sounds like something I've run into... VirusX works fine on my machine, on all the machines I use at work, yet a lot of people report that it will GURU if run from WB then closed. I have no idea why - The GURU # given is 81000005, I believe, indicating that I freed something twice (I may be wrong, speaking from memory). The weird thing about it is that I cannot reproduce the bug, but many people have no problem crashing it. Hmmm. (I've tried it on an A2000, an A500 and an A1000, no crashes). [Look! A single line signature!] ...Steve
thad@cup.portal.com (09/24/88)
Steve Tibbet, You've been on my BBS, you've seen the messages, Andy Levy CALLED you, etc. Re: VIRUSX, please look (again) at line 545 in ANY of the last several versions of VirusX.C ... the ``if'' should have TWO (2) ``=='' instead of ONE (1) Either Chad Netzer or I have had to fix the bug in every version from 1.5 to 2.01 and attempt to re-distribute the fixed version to all the BBS systems in Silicon Valley. Another caller alleges there are additional bugs in VirusX. I'm *NOT* trying to insult you publicly; your program has saved the hides of many people! But this seems to be the only way to contact you since you haven't called BBS-JC in over 2 weeks. Thad Floryan [thad@cup.portal.com (OR) ...!sun!portal!cup.portal.com!thad]