| Re: Restore IDL code from .sav file? [message #37565 is a reply to message #37478] |
Mon, 29 December 2003 12:46   |
Haje Korth
Messages: 651
Registered: May 1997
|
Senior Member |
|
|
Rick,
you are asking the right question: How much is it worth? And the answer is
probably not enough to justify expenses. That is why I have given up. I will
just rewrite the code using my weekends while ticking off my family for
hiding in my office. :-)
By the way, proving ownership is actually not that hard, since detailed
information is actually contained in the sav files. Craig's documentation
describes the sav file format quite well and it is easy to retrieve these
info. However, his documentation skims over the way functions and routines
are encoded (probably for a reason). Consequently, it is more time consuming
to figure out how to disassemble the sav files in general then it is to
rewrite my code. Therefore, I have not bothered since.
Haje
PS: I bet all the fuss is about the embedded IDL licensing that could be
uncovered. And just looking at the sav files and the inofficial
documentation, you can see that you do not need prodis to fake the
licensing. But again, who cares???
--
"Rick Towler" <rtowler@u.washington.edu> wrote in message
news:bspt4f$l22$1@nntp6.u.washington.edu...
> I would guess that someone at RSI could do this. Either they have their
own
> internal tools, a copy of prodis, or both. The only question is whether
> they would be willing to perform this service and how much they would
> charge. Oh, and they would probably want some assurance that you were the
> original author of the code which could prove to be tricky unless your
> installation # is embedded in the save file.
>
> So how much is the code worth?
>
> -Rick
>
>
>
> "Haje Korth" wrote in message ...
>> Jonathan,
>> hey that story sounds familiar, happened to me too once. Unfortunately
> there
>> is probably nothing you can do about it at this point. Craig Markwardt
had
>> routines that do exactly what you want (and what I needed) included in
his
>> cmsvlib for a few days. But then a herd of people including RSI started
>> beating on him for publishing proprietary information, so he withdrew
the
>> routine prodis, which caused all this hassle. I tried to search the
> internet
>> forever to retrieve the library to recover my code that I spent quite
some
>> time on, without success. So the frustrating answer is that there is a
way
>> to recover source code from sav file, but it is illegal. If you are
>> ambitious, you can download info on the sav file format from Craig's
>> website. His documentation gives you an overview and you will find, why
> RSI
>> was upset about that particulat version of cmsvlib, even though he does
> not
>> elaborate on the particular info.
>>
>> Haje
>>
>> PS: If you find prodis somewhere, let me know, I would love to recover
the
>> source of my code too. I tried the wayback machine, but they do not
store
>> binaries...
>>
>> --
>>
>>
>> "Jonathan Joseph" wrote in message...
>>>
>>> Twas the night before christmas and I did something incredibly stupid!
>>>
>>> I edited a couple of .pro files in the wrong location (old versions of
>>> files). In a moment of temporary insanity, I didn't realize that they
>>> were old and different from the files in my working CVS directory, so
I
>>> copied them right over the top of my good files, which had MANY
changes
>>> I had made in the past 5 days and was just (really just) about to
check
>>> back in.
>>>
>>> After testing the code, I realized what I had done. Aaaaagh!
>>>
>>> Date of last incremental backup: 5 days ago, just after I started with
>>> these changes. Nothing useful to recover from tape.
>>>
>>> Emacs ~ backup files: None. (an emacs setting that I haven't changed
yet
>>> makes it so that when I edit files in a checked out CVS directory, it
>>> doesn't make ~ backups).
>>>
>>> Single strand of hope: I happen to have another recent IDLDE session
>>> open. It has compiled versions of the pre-trashed files (but does not
>>> have the source code in a buffer). I just made a .sav file of all the
>>> routines, so at least the compiled versions are not lost.
>>>
>>>
>>> Question: Is there any way to recover the actual source from the .sav
>>> file or from my IDLDE session that has the compiled versions of the
good
>>> code?
>>>
>>> Thanks and Merry Christmas.
>>>
>>> -Jonathan
>>>
>>
>>
>
>
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
