03-24-2007 02:53 PM
03-27-2007 11:58 AM
03-28-2007 02:56 AM
Hi Mike,
I don't know if you're the beta-tester-type. This VI has only been tested on a few VIs, but seems to do what you need. Two minor points of caution:
1) It's cunningly crafted to fail at a moment calculated to cost you maximum embarrasement and
2) Vista may complain when this VI tries to open/read EXE!
Besides that, hope it helps!
Cheers!
03-28-2007 07:01 AM
hi tbd,
How to use Ur VI ? What should be given in the path control ?
First time, I gave a VI, it threw an error from the Open VI Reference.
Second time, I gave an exe, then also it threw an error in the same place.
What could posibily be wrong with my approach ?
Can U explain the correct way to use the VI ?
03-28-2007 02:22 PM - edited 03-28-2007 02:22 PM
Hi Partha,
I'm sorry you had trouble with "exe_miner.vi" - see warning #1. >
> What could posibily be wrong with my approach ?
Well, if you were to select a .VI instead of an .EXE, or select an EXE that wasn't created with app. builder - then that could explain error-messages!
Like I said, I tested this on just a few .exes. If it doesn't work for you, maybe it can be fixed. The VI chops-out the last 4096 bytes of the target EXE. If you wire this string to an indicator. Enable "\" codes, cut/paste the string into a .txt file, then attach the file, I'll work on making the "exe_miner.vi" handle a wider class of VI(s). Note, exe_miner.vi is basing it's search on a particular character-sequence ("LVARLBVW") if this doesn't appear in the last 4096bytes, that could be a problem.
Cheers!
Message Edited by tbd on 03-28-2007 02:30 PM