similar problem, David can you please look at my file

Replies to This Discussion

Permalink Reply by David Rutten on April 24, 2017 at 2:03pm

Your file contains only zeroes. Which means that

1. The file was successfully composed in memory.
2. The file was successfully compressed in memory using a zip algorithm.
3. The file data was written to a local user temp folder and the operating system claimed this operation was successful.
4. The file was then copied to the actual target folder where it replaced the existing file and if you didn't get a warning/error message then the operating system claimed this operation was successful.

Since you ended up with a 106kb file which contains only zeroes, the most likely explanation (in fact the only one I can think of) is that the file was cached in some OS file system buffer and somehow the medium was disconnected without the buffer getting flushed. Did you save this file to a USB stick and did you remove the stick without ejecting it first?

I can think of another explanation in case the file was send through email or downloaded over the web, in that case it may just be a corrupt download.

Unfortunately since the file contains no information, nothing can be salvaged. And you won't find an autosave because autosave files are automatically deleted as soon as a save operation is thought to be successfully completed. I'm really sorry but it looks like it's gone.

Permalink Reply by adam on April 24, 2017 at 2:19pm

David,

the file was maintained on my desktop, in the "bootcamp" environment.

I closed the file, and saved it.

Today, I bought a rhino license, after i entered it, this file wouldn't open.

As the rhino license I last saved it on was 1 day to expiration, maybe this somehow wrecked it...?

Permalink Reply by David Rutten on April 24, 2017 at 3:12pm

As the rhino license I last saved it on was 1 day to expiration, maybe this somehow wrecked it...?

No. Grasshopper doesn't care about the license. And as long as Grasshopper runs at all the license is still valid anyway. Bootcamp also shouldn't matter, as it's not a virtual machine, it's just plain windows running directly on the hardware.

It is very strange, but whatever the problem was, there's nothing to be done now. Until I write a better file open/load/save mechanism for GH2 with more automatic backups you're going to have to use incremental saving on important files. Or, like me, you can hook up a backup drive to your machine and set it to update every 3 or 6 hours, that way you can always browse through the history of a file.