From clyne@niwot.scd.ucar.EDU Tue Jun  2 10:40:10 1992
Return-Path: <clyne@niwot.scd.ucar.EDU>
Received: from niwot.scd.ucar.EDU by sting.hao.ucar.edu.hao (4.1/SMI-4.1)
	id AA10534; Tue, 2 Jun 92 10:40:09 MDT
From: clyne@niwot.scd.ucar.EDU (John Clyne)
Received: from miranda.scd.ucar.edu by niwot.scd.ucar.EDU (5.65/ NCAR Mail Server 04/10/90)
	id AA12346; Tue, 2 Jun 92 10:40:06 MDT
Date: Tue, 2 Jun 92 10:40:05 MDT
Message-Id: <9206021640.AA00563@miranda.scd.ucar.edu>
Received: by miranda.scd.ucar.edu (5.65/ NCAR Mail Client 04/19/90)
	id AA00563; Tue, 2 Jun 92 10:40:05 MDT
To: foster@sting.hao.ucar.edu
Subject: Re: bad metafile
Status: R

> John:
> 
> I have a large (~45Mb) cgm file that has everything I want on
> it except, that my program bombed at the very end, and did not
> do the clsgks call. I guess this means it does'nt have some
> end-of-metafile mark. Will this screw up TAGS? Is it easy to
> add the EOF?
> 
> --Ben
>  
> 

I've had good luck using med to fix metafiles that were corrupt. Try
the following:

	% med valid_ncgm
	med> 1,$d
	med> r your_corrupt_file
	med> w new.ncgm
	med> quit


where 'valid_ncgm' is any ncgm and 'your_corrupt_file' is the file you
want to try and repair. The new file will be named 'new.ncgm'.

jc