#3308 - 01/24/0202:02 PMRe: Question about win compatability
You have the answer. If it has a resource fork you're going to lose it or have it seriously damaged. Also, Mac metafile data may be stripped.<br><br>With files that don't have a resource fork, say a Mac Word word processing file, always add .DOC to file before moving it to Windows machine. What about .doc? May or may not work. Should with newer Win OS but what about a Win program which might accidentally open it that should have been retired with Win95 on the WinXP machine? Your mileage may vary. It shouldn't. But it does.<br><br>Add capitalized file endings to all Mac files. They may wind up generic on return to Mac but the Mac application can still open it and the Mac's database files (directory) should then be updated, or problem solved by rebuilding the desktop file or through use of various utilities.<br><br>This is the "old fashioned" but still the safest approach. Use the precise file type ending and do it in caps. If it's a Mac Word word processing file saved as "text only" then you may want to resave it or resave it as text for DOS format, which is different, then make certain file ending is .TXT, not .DOC.<br><br>(Files with text are the most problematical. If it's a .pdf, .rtf, .txt. or .doc on Mac, for example, make certain it has a file ending that matches precisely on Windows and if there's an option to save in a "similar" DOS format, resave the file before use on the PC. Obviously irrelevant if not to be used on PC but merely stored for later use on Mac.)<br><br>Know precisely how the Mac file was saved, i.e. format.<br><br>Add the right file ending. Is is .DOC, .TEXT, .RTF or what?<br><br>The file ending should be all caps. (.JPG and .JPEG are not necessarily the same on Windows. Use the correct Windows file extension for best results, .JPEG)<br><br>Want to store Mac files with resource forks? No problem. Just don't attempt to open or use them. Put them in one folder and zip them with a Mac application fully compatible with the appropriate version of WinZIP or PKZip on the Windows box. If you don't know or can't use the precise version (on both ends) the worst that will (normally) happen will be loss of creator/file type info which you can later restore on Mac with ResEdit or other utility. Not recommended for a lot of files because it can be a pain.<br><br>(This technique can be used to backup a Mac System Folder, Applications folder, or Documents folder on a DOS formatted drive running under Windows. Just be certain you don't accidentally ever unzip it while parked on the Windows box. Something like rebuilding desktop or repairing apps later when returned to Mac beats having no backup at all.)<br><br>Some of these comments are overkill for mere storage but they avoid various liabilities while on PC and when later returned to Mac.<br><br>Been there and done this. More times than I care to remember.<br><br>128k_Mac<br><br>The box said "Requires Microsoft Windows or better" so I bought a Macintosh.
Xplain's use of MacNews, AppleCentral and AppleExpo are not affiliated with Apple, Inc. MacTech is a registered trademark of Xplain Corporation. AppleCentral, MacNews, Xplain, "The journal of Apple technology", Apple Expo, Explain It, MacDev, MacDev-1, THINK Reference, NetProfessional, MacTech Central, MacTech Domains, MacForge, and the MacTutorMan are trademarks or service marks of Xplain Corp. Sprocket is a registered trademark of eSprocket Corp. Other trademarks and copyrights appearing in this printing or software remain the property of their respective holders.
All contents are Copyright 1984-2010 by Xplain Corporation. All rights reserved. Theme designed by Icreon.