[comp.sys.amiga] TRASHED DISKS.

MOLNARRM@UREGINA1.BITNET (01/22/89)

Has anyone tried the program FastDisk?  I tried it on my WB 1.2 disk, and
it reduced my startup-time by 30 secs (I copy C dir to ram).  However,
I tried it several times on WB 1.3 disks, and it never worked.  The
result was always a disk that had a corrupt directory, I believe.
Whenever I would try to do a DIR of one of these disks, my A1000 would
promptly guru.  Someone suggested it was my drives or bad disks, but I
have used high quality disks, and can repeat the error by using the above
program.  The disks will also crash computers besides my own.

Is it normal for AmigaDOS to crash just because it encounters a garbage
directory?  I don't expect anyone has a solution, but I would appreciate
an explanation of how the above guru is caused.

--> Dennis Gorrie
    MOLNARRM AT UREGINA1.BITNET
           ''Chain-Saw Tag... Try it, You'll Like it!''

dzenc@hermes.ai.mit.edu (Daniel Zenchelsky) (03/12/89)

Help!

Something is trashing my disk directories, and I don't think it's a virus,
because I have VirusX 3.20 running.  It seems to happen while I'm downloading
files, using either A-Talk III, Online 2.11, Azcomm, or JRComm. It's
happened to me three times in a row today, on different disks, and has
happened sporadically on other occasions, although I've always dismissed
it as flakey disks.  Now that I only use Sony's, I'm not as quick to dismiss
it...


There are a lot of programs I keep in my startup-sequence, so I will list
them here, and pray that someone who has had this problem, and discovered the
cause will be able to help me.  Meanwhile, I will have to go and systematically
check each program... (AHHHH!!!!!!)
 
Here goes:
----------

Kickstart 1.2
Workbench 1.3 ( 34.20 )
RAD: 
dmouse
setfont 2.0
Fast Fonts
Gomf 3.0
VirusX 3.2
SetPatch
setclock,setmap usa1
spudclock
snipit V1.2
JR-Beep
muddlebar
Facc II
newshell, newcon:


Thanks everybody, I'm gonna start removing things from my startup-sequence
and see if it helps.  It sounds like something falls into the sinister
Delay 0 bug...
 
-DAn

+-----------------------------------------------------------+
|  ______                                                   |
| ||   |o|  Daniel Zenchelsky  --  dzenc@hermes.ai.mit.edu  |
| ||___| |                                                  |
| |   _  |  "If it's not in the computer, it doesn't exist" |
| \_[]_|_|                                                  |
|                                                           |
+-----------------------------------------------------------+

kenneth.tam@canremote.uucp (KENNETH TAM) (03/16/89)

This probably sounds really idiotic, but I recall the docs in JR-Comm
specifically stating that JRBEEP is NOT to be run and is called directly
by JRComm.  I don't suppose this would affect your disks, but it IS
something ;-)
 
-Kenneth
---
 * Via ProDoor 2.9a 

--- MaS Relayer v1.00.00
   Via Fidonet node 1:223/224.0 - MaS Network Software and Consulting/HST
 Internet: kenneth.tam@canremote.uucp
 UUCP:     ...tmsoft!masnet!canremote!kenneth.tam