It was not renaming problem, it was problem of telling Windows to open a file that did not exist. The clue was to hold the keys down and click Open. But when I clicked open, W7 was appending the .pl before issuing Open command.
Nonetheless that problem has been cured - I removed that behavior from IE Internet Options > General > Languages.
This does not change the fact that the above-mentioned routine did not help me at all.
Upon open with three keys down, I get Illegal Operand dialog with some mystery binary-like data.
The underscore file is not created.
Is this only affecting one file, or more/all files? If the latter, we may be looking at corrupt preferences or something, see this thread:
Thanks Jacob for your time!
I went through your recommended steps, I also tried to open the Ai file in Acrobat X - to no avail.
I did the prefs-busting routines in CS3 (removing the aiprefs file, shift-ctrl-alt launch). For CS6 I just set the flag to enable recovery, and resaved the file.
I don't really think it's prefs problem. I think that's the ai file that got corrupt. Firstly, other random files open just fine in both CS3 and CS6. secondly, I was having low memory condition when that happened - that might have affected the save that I performed.
Shame on me I wasn't smart enough to switch to Win Explorer and clone that file before saving when I saw something weird is going on. Shame on Adobe though, they don't provide recovery built-in tools for Ai as they do for Id.
I ran the http://www.illustrator.recoverytoolbox.com demo version on the file. After a 2-hour threadmill it seems to have coped with the file, it reported all objects, but as a demo version it did not actually save its result which is really promising.
So what I have know is dillema - pay 30 bucks for a yearly plan for something that looks like doing a good job, or wait for Adobe to kindly answer my ticket.
And BTW, do these credentials:
allow anyone to create a directory? Seems like permissions problem - all I can see is blank screen.
The Recovery Toolbox may very well be your best option. As far as I can see, the basic licence is $27 covering one year, and subsequent years will be $12. Depending on the conditions, you may be able to spend the first $27 on recovering this file (which may very well be worth it), and then renew the licence if/whenever you need it in the years to come.
I presume the Adobe support would also vcome at a price.
I shall certainly remember this option, and I have Bookmarked it. I will mention it in another recent thread with a hopeless case.
Thank you very much for sharing.
None big, Uncle Google to the rescue. While it's good to have an option like this, I certainly would not like Adobe to sit back and relax just because there are other paid options out there in the world.
But certainly Adobe should learn how to make such a tool user friendly, clean, with no dirty file hacking, removing, replacing, modifying, etc.
Have you had a chance to test FTP permissions perhaps, if you please?
I am afraid I am as much, or more, in the dark as are you in such matters.
I hope someone else can give an answer.
It is big: as far as I know, that option has never been mentioned here in this forum (in this millennium at least), where so many have struggled. And as you can see from this thread (where) I mentioned (it just now), we may be talking about weeks of work lost.
The trouble is that files might get damaged beyond repair. The repair routine in Illustrator CS6 does a pretty good jobs on specific kinds of wrecked files, but may completely fail on others. There is no guarantee that any magical function, third party tool or routine of tasks will be able to repair your file. It would be awesome, but it still doesn't exist after all these years.
Because of this, it is still important to maintain a workflow that always keeps different versions of files and fallback copies.
Also: the most common cause of ruined files still is working directly (that is: saving to or opening from) on removable or networked media.
Agreed on that. Myself I have been developing an app writing/reading my own binaries - I know the risks and weirdos happening every now and then. Two points though:
1. The file is not beyond repair, a $30 tool seems to eat it like a piece of cake with hands al clean. That's *only* and *as much as* $30 at the same time.
2. InDesign has had its recovery tool, perhaps not from corrupt file, just from unsaved changes loss. But at the same time it has indx feature which to me proved to be a life saver once.
And to answer your hint: I worked totaly locally. Low memory condition must have been the strongest factor in my case. I will be smarter next time it happens.
I know this discussion got somewhat philisophical and leads us to nowhere, sorry about that - there's always some frustration involved when you lose your work.
Let me now just sit and wait for my support ticket addressed.
OK. Thanks to Recovery Toolbox (RT), my document, full of logotype versions and their variants, was mostly restored. Lost text objects and effects were the only penalty - not a severe one in my case. Plus, a bit shifted gradients.
Below a few details that might help a lost soul one day.
The purchase confirmation page for RT contained both a download link to version 18.104.22.168 and serial number.
The first attempt was not successful - the recovered document still contained some offending PostScript attributes and would not open. This lead me to further search and I managed to google up version 22.214.171.124. It had to be installed on another CPU that never saw 126.96.36.199 serial number - a quirk I'm glad I pinned down.
The recovery was now much more successful. Even though Illustrator whined about some operands and such, it eventually opened the document. Unfortunately all text objects were lost, which was signalled by items on the layers pallete labeled "text objectwas lost" (original spelling).
I resaved the document under a different name to get it back to Illustrator's native compression state. Unfortunately for some reason it wouldn't open after closing.
Then I decided to create a new doc from scratch and pasted the layers from the recovered doc. I had to remove the lost objects though, as Ai whined about off-the-pasteboard action the objects were extending the selection's bounding box to infinity. This did not help either, so I started over, putting each layer in a separate doc. THAT WORKED. The docs now reopen successfully each time in CS3.
Now I managed to recreate my text objects - luckily I had exported JPG previews of all the variants and so I have a set of guiding pictures to follow.
Lessons learned to avoid/minimize penalty:
- Don't ignore low memory warnings from your OS.
- If you are designing multiple versions and variants, rather split them into separate docs and not let your document grow too complex. Just like with savings diversification.
- Export bitmaps once in a while.
- Convert fancy and meticuously caressed text to paths - it should not get lost.
- Should anything go weird on screen, before you save - clone the file in the Explorer/Finder.
- If you go without a support plan, do not count on Adobe.
- If you're on a deadline, don't wait - purchase RT right away, because even a partial recover might take significant amount of time.
I'm not too much satisfied with the quality of support and responsiveness of RT authors, but anyway I'm very grateful they have built the tool.