| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2901.1 | Insane pointers... | FRAMBO::BALZER | Christian Balzer DTN:785-1029 | Fri Sep 08 1989 03:55 | 14 |
|
First of I would like to know what kinda file this is, who/what
installed it on the HD and what it's exact name is.
You most likely have a FileInfoBlock there which is totally messed
up and drives AmigaDOS insane when trying to access it.
One thing you should do in any case is to back up the partition
in question before you proceed (w/o that offending file).
Then you might start fiddling with that file using DiskDoctor and
the various disk editors out there...
Good luck,
<CB>
|
| 2901.2 | More Info | KYOA::MIANO | Dallas is gone...Buckey is next. | Fri Sep 08 1989 10:39 | 14 |
| The file is a .o that was created by Lattice C. I though it was
the compiler that was crashing the system until I tried to delete
the file. I was in the process of writing a program that used
a lot of dynamic memory and it was crashing the system.
I think that I need something like Analyze/disk/repair. I don't
think the disk is trashed.
The manual says that Disk Doctor is for floppies. Will it work on
hard disks? If so, can I DiskDoctor in place (use diskdoctor to repair
the disk not to recover files)? At this point I do not think I have lost
any files.
John
|
| 2901.3 | | DICKNS::MACDONALD | WA1OMM 7.093/145.05/223.58 AX.25 | Fri Sep 08 1989 10:49 | 1 |
| I believe DiskSalvage will work on hard disks.
|
| 2901.4 | Some feedback... | FRAMBO::BALZER | Christian Balzer DTN:785-1029 | Fri Sep 08 1989 10:57 | 17 |
|
Both DiskDoctor and DiskSalv (by Dave Haynie) will work on HD's.
You should try to use the 1.31 version of DiskDoctor, since it fixes
some quirks.
DiskDoctor will try to correct any errors by writing on the media
in question, whereas DiskSalv will copy salvageable data from corrupt
media to another destination.
Since DiskDoctor may cause major havoc to your disk while trying
to correct it, it's a good idea to back it up first.
You may get away with Sectorama or some other disk editor (Disk-X
is VERY buggy!!!) by resetting some pointers, but this would be
too much to describe here...
Hope this helps,
<CB>
|
| 2901.5 | At least I lost no files | KYOA::MIANO | Dallas is gone...Buckey is next. | Sat Sep 09 1989 14:32 | 19 |
| I backed the thing up (About 15 floppies - what a pain in the ass!)
then ran DiskDoctor. If anything DiskDoctor made the situation worse.
At the end it put up a message that it could not validate the disk.
After that I could not delete anything. However, I had the backup.
It appears that the I had a soft problem. I reformatted the Work:
partition the subdivided it into 4 10MB partitions. I had the system
partitioned the way it came with the small boot and wb partitions and
one large work parition. If I had had addition partitions I could have
copied all the files to another partition and fixed the corrupted
partition. You live and learn.
I think this problem was probably caused by my software development
activites. I have been crashing the system with great regularity.
I wish there were, or I knew about, an ANALYZE/DISK/REPAIR equivalent
that will repair a disk in place. Such a utility would have fixed
this problem painlessly.
John
|
| 2901.6 | | KYOA::MIANO | Dallas is gone...Buckey is next. | Sat Sep 09 1989 18:36 | 7 |
| Some day it is going to sink into my head that
free( malloc(0) )
in Lattice C is a perscription for disaster.
John
|