Mac Os 9 Because An Error Of Type-39 Occurred
& System 7) Please enter a title. You can not post a blank message. Please type your message and try again. This discussion is locked MSG-PWRBkG3 Level 1 (0 points) Q: Mac OS 9.2.2 Update.smi can't open error -39 Hello All,In order to prepare my Powerbook G3 Wirewire for OS-X Panther, I downloaded the OS 9 Updates from www.Apple.com using another much newer (and faster connected) Mac:Update 9.1Update9.2.1Update9.2.2Update firmware 4.1.8I burned them onto a CD-ROM and also put them onto a portable external USB drive.I copied them onto the desktop.Now when I try to open them I get the error..The application program "Mac OS 9.1 Update.smi" could not be opened, because an error of type -39 occurred.any suggestions?-----------------------------------------------------Also, I am preparing to install a 512mb RAM SoDIMM and a 40GB hard drive, before I perform the Upgrade to OS-X Panther. I was told that OS-X Tiger would not fit on the existing 10GB drive when combined with the existing OS-9 system (however,the existing Hard Drive's total contents only uses up only 1.95GB.)So....I will install the new RAM module and the larger Harddrive, then install the OS 9.0.4 from my original CD-ROMs... I'll put all the files onto the new drive... then run the OS 9.1 update, then run the firmware update, then follow with the 9.2.1, and the 9.2.2 updates... then do an archive and install with the OS-X Panther using those CD-ROMS..... If I start this tommorrow after FedEx delivers the new Drive and RAM, I should be up and running before August!! (kidding, I hope)I read tons of posts about Upgrading my Powerbook G3 Firewire and wasn't that clear about still being able to use older software and access old files if I did a "Full" install with the Panther CD-ROMs then follow with an OS 9.0.4 system later. I think it would skip the all-important "keep the OS 9 drivers" choice.any further suggestions about this upgrade plan would be appreciated.THANKS!!MSG-PWRBkG3 Powerbook G3 400mhz, Mac OS 9.0.x, wish I could upgrade to OS X Posted on Mar 8, 2006 5:01 PM I have this question too Close Q: Mac OS 9.2.2 Update.smi can't open error -39 All replies Helpful answers by Don Archibald, Don Archibald Mar 8, 2006 8:31 PM in response to MSG-PWRBkG3 Level 10 (101,455 points) Mar 8, 2006 8:31 PM in response to MSG-PWRBkG3 Hi, MSG -Re the -39 error - that error is most commonly caused by Stuffit Expander intruding where it should not. The download is in a .smi (self-mounting imag
remain constant. If you know of a category of errors that are not included here, please let me know. error -32768 svTempDisable: Temporarily disable card but run primary init. error -32640 svDisabled: Reserve range -32640 to -32768 for Apple temp disables. error -32615 fontNotOutlineErr: bitmap font passed to routine that does outlines only error -23048 outOfMemory: Not enough memory is available to issue the needed DNR query or to build the DNR cache. error -23047 dnrErr: The domain name server has returned an error. error -23046 noAnsErr: None of the known name servers are responding. error -23045 authNameErr: The domain name does not exist. https://discussions.apple.com/thread/395376?start=0&tstart=0 error -23044 noNameServer: No name server can be found for the specified name string. error -23043 noResultProc: No result procedure is passed to the address translation call when the resolver must be used to find the address. error -23042 cacheFault: The name specified cannot be found in the cache. The domain name resolver will now query the domain name server and return the answer in the callback procedure. error -23041 nameSyntaxErr: The <
card Apple II and II+ character roms Apple IIgs programming THIS is Laughable! more Macintosh Support York, Harrisburg, and Lancaster, PA. New forum topics Trying to identify some old Apple II games http://www.applefritter.com/node/6030 Apple IIgs programming ProTERM Special Emulation Creation program. Titus Larson Apple Interfacing MacOS 7.6.1 http://osxdaily.com/2015/02/21/fix-error-code-36-finder-mac-os-x/ ISO more Who's new trueman Jorpho trick-1 Mrarkus wyattwong Who's online There are currently 1 user and 101 guests online.Online usersPolymorph69 Home » Forums » Discussion » 680x0 Macs and Lisa Error Type -39 Login or register to post comments 6 replies [Last post] January 14, 2005 - 2:07am DanDaMan Offline Joined: Jun 8 2004 Posts: mac os 78 Hi all. Whenever I try to open a file that is a smi type file, it opens, tries to run, and then gives me an error message of type -39. Can anyone help me? I would REALLY appreciate it. Thanks in advance. Sincerely, DanDaMan
__________________ Daniel M. Beringer Top Login or register to post comments Comment viewing options Flat list - collapsedFlat list - expandedThreaded list - collapsedThreaded mac os 9 list - expanded Date - newest firstDate - oldest first 10 comments per page30 comments per page50 comments per page70 comments per page90 comments per page150 comments per page200 comments per page250 comments per page300 comments per page Select your preferred way to display the comments and click "Save settings" to activate your changes. January 14, 2005 - 2:25am #1 williamahearn Offline Joined: Aug 15 2004 Posts: 359 minus sense http://www.rustle.com/mac/system8.html#aec.targ You can download an error code decoder from the link above. Top Login or register to post comments January 14, 2005 - 3:33am #2 DanDaMan Offline Joined: Jun 8 2004 Posts: 78 Then What? I don't know what to do. It just tells me an error code, but I know the file is good because it is directly from Apple. I don't get what I'm supposed to do. I now know the code, but how to fix it? I would GREATLY appreciate an answer. Thanks (once again) in advance. Sincerely, DanDaMan __________________ Daniel M. Beringer Top Login or register to post comments January 14, 2005 - 3:43am #3 dankephoto Offline Joined: Dec 20 2003 Posts: 1900 Use Disk Copy to mount it Drop the file onto Disk Copy. BTW, what's the file and on wcompletely halts the copy or move process in the OS X Finder. The full error is usually read as "The Finder can't complete the operation because some data in "FileName" can't be read or written. (Error code -36)". The filename is sometimes .DS_Store, but it can happen with just about any file. If you run into Error Code -36 on a Mac, there's usually a really simple solution thanks to a handy command line tool called "dot_clean". If you've never heard of dot_clean, you're certainly not alone, and the manual page for the command explains that it "merges ._* files with corresponding native files." which may not sound like much to the casual user, but given the oft cause of Error 36 are files prefixed with a dot, that can be exactly what you need to do. How to Resolve Error 36 in OS X Finder with dot_clean To use dot_clean, you'll want to point it at the directory which is being copied and throwing the Error Code 36, the basics look like this: Launch the Terminal (found in /Applications/Utilities/ or with Spotlight) At the command prompt, type: dot_clean /Path/To/Directory/With/Problem/ When dot_clean is finished, attempt the file copy again and it should succeed with no error code For example, if copying ~/Documents/FileBackups/ is the problematic directory, use: dot_clean ~/Documents/FileBackups/ That should be all that is necessary to resolve the issue, just be sure to attempt the file/directory transfer immediately after the command is run. Technically you could point dot_clean at an entire volume but that's probably not necessary unless the -36 error is continuously triggered in Finder when trying to backup an entire drive manually. If the problem is recurrent and you get it constantly when trying to copy files to and from a networked Mac, a network share, external drive of some sort, or to and from a Windows computer, you can also try to delete all .DS_Store files on a Mac using the command line, which can work as a temporary workaround if for some reason dot_clean fails. That was actually what I had done in the past to get around this and other similar input/output error messages before discovering this specific command approach. I just ran into this recently and