From Peter Deane · 1996-04-04 00:35 · #77338 in IBM
PD> Gee, it should validate without that, unless more than one file has PD> been corrupted, tending to point to another program doing something PD> to another file at the time of the crash. DF> It checks all the files and says they are okay. At the very end DF> of the check it comes up with invalid bitmap (or something like DF> that) and then goes on to say something like replacing disk DF> bitmap, then everything works fine. Except that TrapToss crashes. Looks like your dupe table is on the part of the drive still corrupted. I'd suggest you backup everything off that partition, reformat it, and put it back. I don't like the sound of your disk salvage program's diagnostics. And possibly start off the dupe table afresh, from the looks of things. DF> I've not bothered to set a dupetable size, assuming it will DF> default to 8196 as per the instruction manual. Well, 8192, but let's not mince words. If there WAS a problem with the dupetable size, TrapToss will tell you the tabel has a problem and commence a new one automatically. You'll see that logged. But that's not the problem. DF> A beta tester pointed out that this problem has occured with DF> later test versions, perhaps it's been there all along??! I think YOUR traptoss is still getting over the hard drive partition corruption. Until you've re-formatted and restored, it'd be difficult to draw any serious conclusions about the effect the dupe table is having on TrapToss's operations. Mea Culpa, Peter Deane --- Plutonic 2.13 #1 * Origin: Inquestor. Hydra for TrapDoor, THANX! +61-43-961587 (3:711/476)