Any chance any .bld file(s) used to create the executables were saved and are still lying around??? If so you might be able to find some important clues by examining the vi paths stored in the .bld file(s) with LV or a text editor. LV will fail with a error message giving you the stored path of any missing vis if any of their relative paths (to the .bld file) have changed.
Good luck, Tom http://neverworld.net Thomas G. Duffey Senior Instrumentation Specialist Engineering Research and Consultants, Inc. Air Force Research Laboratory Propulsion Materials Applications Branch 9 Antares Road Edwards AFB, CA 93524 661.275.6172 FAX 661.275.5073 [EMAIL PROTECTED] http://www.pr.afrl.af.mil/divisions/prs/research.htm > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Will Keogh > Sent: Thursday, June 03, 2004 8:44 AM > To: Info-Labview > Subject: Detective work on built executables > > > Dear built-executable gurus, > I have an ugly labview problem. I have inherited a suite of labview > programs, consisting of built executables that are known to > work, and a > vast, disorganised pile of vis. The challenge is to > reconstruct working > versions of the source code corresponding to each executable. > What makes it > hard is that there are 1/2 doz different versions of each vi, > and no obvious > way to tell which are the 'good' ones. I am hoping that it > may be possible > to dig into the exes and find out what vis went in to them (I > understand > that I certainly can't get the original source code out of > the exes, but any > clues would be helpful). Does anyone have any ideas? > > Thanks, > Will > > -------------------------------------------------------- > Will Keogh > Borehole Research Group > Lamont Doherty Earth Observatory of Columbia University > 61 Route 9W, Palisades NY 10964, USA > Ph: 845-365-8673 > Fax: 845-365-3182 > [EMAIL PROTECTED] > -------------------------------------------------------- > >
