Sat, Jan 11, 6:48 AM CST

Renderosity Forums / Carrara

All Forums

Welcome to the Carrara Forum

Forum Coordinators: Kalypso

Carrara F.A.Q (Last Updated: 2025 Jan 10 10:15 am)

 

Visit the Carrara Gallery here.

Carrara Free Stuff here.

 
Visit the Renderosity MarketPlace - Your source for digital art content!
 

 

Subject: "Error in: open" Message

SPACEY opened this issue on Jul 18, 2000 · 4 posts
Back to Forum Print
SPACEY ( ) posted Tue, 18 July 2000 at 5:14 PM · edited Sat, 10 August 2024 at 12:42 AM

Has anyone ever seen this message on a RD5.5 Mac file after an improper shutdown. I'm trying to save a file(s) that i was working on. I was able to find a bunch %100 recoverable saves with Norton Utility but they all refuse to open. is there any one who knows why this happens, if there is a bug fix for it, or if there is a way to restore those files?

Must've slipped my mind...but it's the thought that counts...

http//www.wholebitmedia.com

mclarsen ( ) posted Tue, 18 July 2000 at 11:50 PM

This error means the program doesn't recognize the file, either because it is corrupt or is missing the resource fork. My experience is that Norton is less successful in recovering program files completely (i.e. .rds, .ai, .fh, etc.) which require both forks of the file to be recognized as opposed to file formats like .tif or .jpg which may open with only the data fork intact. Norton sometimes recovers a program file without both forks intact (the data fork is there but the resource fork is not), even when it says it is 100% recoverable. Does the RDS icon show on the file? If not, you may be able to just re-add the creator/type codes using ResEdit or other program which adds creator and type codes. Sometimes opening the file from within the program as opposed to double clicking the icon works, but you probably already tried that. Also, rebuilding the desktop after a crash will occasionally make the file recognizable again. I wish I could be more helpful than that, but if none of these solutions work for me, I berate myself for not having a backup and accept that the file has been corrupted.

willf ( ) posted Wed, 19 July 2000 at 11:56 PM

You may also try to "import" the scene into a new document.

Oliver S ( ) posted Thu, 20 July 2000 at 2:34 PM

Hi, I get this message a lot when trying to open an .obj file created on a PC for Poser. There are 2 workarounds, one is to import it into Poser and re-export it as an .obj file. The other is to drop it onto Maconverter and it sorts out the resource forks. But if the files are just native RDS5 files and you use a PC - not much help. But error in Open does seem to be a bit of a catchall and not at all helpful. Sometimes of course it is a memory thing... Good luck, and Norton does seem to be getting a bad press recently Oliver S

Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.