Scribd
Upload
28 views

MSTOOLS-Project Audit To List Objects and Flag Corrupt Objects-200712

Uploaded by

Kenny Casilla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
28 views

MSTOOLS-Project Audit To List Objects and Flag Corrupt Objects-200712

Uploaded by

Kenny Casilla
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

MineSight in the Foreground

Tip of the Month: MineSight Project Audit to List Objects and Flag Corrupt Objects
Like every other tool that is used everyday, MineSight needs periodic tune ups and preventive maintenance. Since the objects created in a MineSight project belong to the company, it is a good idea to get a list of the objects to find out how many you have and where they are. This is also a method of checking your organizational style. Mintec provides a tool, MSRESCLEAN which creates a list of all the objects in a project and checks each of them for corruption. The tool consists of two programs working together, msresclean.exe, the front end and msrestest.exe, the engine program. The programs create logging files named msresclean.log and msrestest.log. The msrestest.log file has the complete listing of all the objects, including the corrupt files. The msresclean.log file has a list of all the objects that were corrupt. Msresclean.exe tests all MineSight resource files: the *.msm and *.msr files in a project folder and all of the subfolders, as well as dialogs.ptf files. MSRESCLEAN should be started in the project folder directory, not in the _msresources folder. not shown in the Data Manager lists. If a MineSight object is corrupt, msrestest. exe will change the extension from *.msr to *.msr_corrupt. This will make the object invisible to MineSight 3-D. If the backup file exists and is corrupt, it will also be renamed, to *.msr%_corrupt and you will have to recreate the object. If the backup file is not corrupt, you can use Microsoft Explorer to change the extension from *.msr% to *.msr and the object will be visible in Data Manager. While msrestest.exe will rename the corrupt object so that it will not be displayed or checked by MineSight, it does not remove the file. To remove them, you will need to use Microsoft Explorer, set the display options to show details and sort by type. Then select all the *.msr_corrupt and *.msr%_corrupt files and delete them. MineSight objects can become corrupt for a number of reasons that can occur during the normal work process. Electrical power fluctuations during the opening/saving of an object, imperfections on the hard disk surfaces, errors in copying the file to/from a network location, and failing network infrastructure are all rare but real risks. Periodic auditing with msresclean.exe to check all your MineSight objects is the preferred method of finding these errors. Version 1.1 of msresclean.exe has been enhanced to eliminate the twin problems of false positives and false negatives, that were possible with the earlier version. A false negative results when a corrupt file was judged okay and a false positive when a functioning object was judged corrupt. The helper programs used to test the resource files may fail during the resource testing process. In this case, the following dialog window may appear:
(continued on page 13)

MineSight 3-D works with *.msr files and creates *.msr% as backups. The *.msr% are

12

December 2007

MineSight in the Foreground


(MineSight Project Audit to List Objects and Flag Corrupt Objects continued from page 12)

If you encounter the above window during your audit process, simply click on the Close button. The dialog window will close and msresclean.exe will continue on with the audit. If corrupt files were encountered during the testing process, MSRESCLEAN will post a notice and display the msresclean. log file which lists all the corrupt objects found. Below is an example of an msresclean.log file: E:\Projects\csamp\_msresources\dialogs.ptf IS CORRUPT E:\Projects\MineSight II - July 2006\_msresources\0001 junk\acq.msr IS CORRUPT E:\Projects\MineSight II - July 2006\_msresources\0001 junk\acq.msr% IS CORRUPT E:\Projects\abc_mining\_msresources\DH\acq.msr IS CORRUPT E:\Projects\my_project\_msresources\DDH\acq.msr IS CORRUPT E:\Projects\my_project\_msresources\DDH\acq.msr% IS CORRUPT E:\Projects\my_project\_msresources\DDH\D.S. 14.msr IS CORRUPT E:\Projects\my_project\_msresources\DDH\og.msr% IS CORRUPT E:\Projects\my_project\_msresources\resources2006\LAB14\LAB14.msr IS CORRUPT The msrestest.log file can be used to categorize the objects in a MineSight project. E:\Projects\01 Minesight_MSOP\01demo.msm IS OK E:\Projects\01 Minesight_MSOP\AutoSlicer.msm IS OK E:\Projects\01 Minesight_MSOP\BlockModelCoding.msm IS OK E:\Projects\01 Minesight_MSOP\Daily-Update.msm IS OK E:\Projects\01 Minesight_MSOP\Deforma.msm IS OK E:\Projects\01 Minesight_MSOP\EllipseInterpolation.msm IS OK E:\Projects\01 Minesight_MSOP\GradeShell.msm IS OK E:\Projects\01 Minesight_MSOP\ImportPolygons.msm IS OK E:\Projects\01 Minesight_MSOP\IPToolExample.msm IS OK E:\Projects\01 Minesight_MSOP\Linking.msm IS OK

To summarize, the MSRESCLEAN tool provides auditing and flagging of corrupt provide auditing and flagging of corrupt MineSight objects and should be a part of the routine project maintenance plan.

December 2007

13

You might also like