A RevG file of mine has just been made completely unusable, possibly due to a power failure. When trying to access this file, a group format error occurs. When I DUMP the file, I see that my pointers are completely messed up. The entire group of 1024 bytes consists of Hex `AE`. This of course means that all pointers and control info is meaningless. When I checked the ROSMEDIA.MAP for that volume, everything seems fine. When I view the actual data file (ROS10002.LNK) from a word processor however, I see all the data, but where I would expect to see the native filename of ROS10002.LNK in the file, I see ROS10057.LNK instead. I unsuccesfully tried to resolve the problem in the follow ways.

1. 1 - I did a global change of all occurances of ROS10057.LNK to ROS10002.LNK, Rev can no longer even give me GFE error.

1. 2 - I changed the ROSMEDIA.MAP to look at ROS10057.LNK instead of ROS10002.LNK and then renamed the file to ROS10057.LNK

Again, Rev could no longer even read the file.

Does anyone have any suggestions of what I could do to correct this?

Whenever I have a problem like that I first create a new empty file and copy as much of the data as possible from the corrupted file into the new file. When I receive the GFE messages during the copying, I select 'I' (ignore) to continue the process. I then delete the orginal file and then move the the salvaged data file to the old file name. Of course I lose data with this process but most of it is recovered. I then have to reconstruct from backup (or just from knowledge) the missing data and rebuild the indices.

Another option is to use the Group Format Error Recovery Utility found on the Utility diskette with RevG. Frankly, I have never had much luck with this one except in reporting errors but it may be worth a try.

Tom

The mismatch of the ROS number in frame headers could mean that at sometime either a FILECOPY or a DOS copy was done. The file system does not use this ROS number for reading/updating files.

By using a word processor to do a global search and replace on a binary file you probably corrupted the 'binary' structure of the file in some way. You would need a binary or sector editor to safely make this sort of replacement.

I hope you backed up the files.

There are two routines: RECOVER and RECOVER.LINK. I have used RECOVER with enough success to not mind it. Fortunately have no needed to other. I think the Utility Disk installed it in the PROG file in SYSPROG. I think. That's where they are now, anyway. It's been 12 plus years!!!

Much Luck.

Charles Schmidling

DATASCAN Systems, Inc.

cbms.at.juno.dot.com

View this thread on the forum...