Hi Will,

You have probably already tried the obvious, but in case you haven't, try a
detailed analysis of the OS timestamps assigned to each file.

Although the two are not always related, it may just be that the executable
was created immediately following an update to the top level vi.

If you are using llb's the problem should be simple but it sounds as though
your predecessor used dynamic vi calling and therefore timestamp of the
files may be an important clue - look for the most recently updated vi,
prior to the .exe's being created.

Regards,
 
Chris Harden
 
Test System Design Engineer.
 
FR HiTemp Ltd,
Brook Road,
Wimborne,
Dorset.  UK. BH21 3RD.


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Will Keogh
Sent: Thursday, June 03, 2004 3:44 PM
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]
--------------------------------------------------------


This e-mail and any files transmitted with it ("E-mail") is intended solely for the 
addressee(s) and may contain confidential and/or legally privileged information.  If 
you are not the addressee(s), any disclosure, reproduction, copying, distribution or 
other use of the E-mail is prohibited.  If you have received this E-mail in error, 
please delete it and notify the sender immediately via our switchboard or return 
e-mail.  

Neither the company nor any individual sending this E-mail accepts any liability in 
respect of the content (including errors and omissions) and timeliness of the E-mail 
which arise as a result of transmission.  If verification is required, please request 
a hard copy version



Reply via email to