error - 39 ... i am so f#$%^ !!
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
-
- Posts: 26
- Joined: Tue Nov 27, 2007 9:16 am
- Primary DAW OS: Unspecified
Re: error - 39 ... i am so f#$%^ !!
and i will try that time machine too ..
Re: error - 39 ... i am so f#$%^ !!
arnopolaris,
The following is from a different forum, but deals with Error -39 issues, so might be applicable to your situation:
The following is from a different forum, but deals with Error -39 issues, so might be applicable to your situation:
http://forums.quark.com/t/15898.aspx?PageIndex=1Re: [-39] error in Quark 6.52 on OSX 10.5.1 - Workaround!!!
Hmmm. I don't have this issue, but I'm not working in Leopard. Just one comment though. Temp files are a known bug with XPress 6.x (Mac), particularly on a network. Doesn't matter what OS. Things that cause the temp files are listed below:
1. Autosave on
2. Autobackup on
3. Spotlight XT installed (Tiger or above)
4. Anti-virus software
5. Out of synch clocks between client/server.
The first three are the worst offenders. Turn those off, remove the Spotlight XT (if installed) and no issues. BTW, some people were lucky enough never to experience this even on a network, but those were a minority.
Perhaps then the issues with Leopard are because people have either 1, 2, or 3, or a combination of those going? Just speculating here, since most people having this issue with Leopard have never brought it up. Temp files were'nt ever mentioned either.
MacPro5,1 2012, six core 2 x 3.06, 10.12.5, Digital Performer 9.13, 40 gb ram, 828mkIII, 2408 mkII, MTP AV, Logic Pro X 10.3.1, Studio One v 3.2, Pro Tools 12.7.1
Re: error - 39 ... i am so f#$%^ !!
Have you tried Disk Warrior???
2.66 Mac Pro, 10.6.5, 16 G RAM, DP 7.22, 6 SATA internal drives (2 RAIDS & 2 singles), Ozone 4, 2 UAD 2 Quad card with most of the plugs, Waves Diamond(V7), V- Series (V6) & SSL4000(V7), PLAY 1.25, EMI TG12413, URS CSPro, Autotune Evo, Scarbee KGB, EWQLSO Platinum Pro XP, Drumagog, BFD2, NI Komplete 7, Breverb, Ivory w/ Italian Grand, USB Plugsound Pro & Synths Anth, Ampeg SVX, Amplitube3 (And Fender), Altiverb, Melodyne, MOTU 24 I/O with Black Lion Mod.
-
- Posts: 26
- Joined: Tue Nov 27, 2007 9:16 am
- Primary DAW OS: Unspecified
Re: error - 39 ... i am so f#$%^ !!
nothing seems to repair that file .. i tried disk warrior too ..anyway thank u guys
Re: error - 39 ... i am so f#$%^ !!
Do you have Spotlight enabled?arnopolaris wrote:nothing seems to repair that file .. i tried disk warrior too ..anyway thank u guys
MacPro5,1 2012, six core 2 x 3.06, 10.12.5, Digital Performer 9.13, 40 gb ram, 828mkIII, 2408 mkII, MTP AV, Logic Pro X 10.3.1, Studio One v 3.2, Pro Tools 12.7.1
Re: error - 39 ... i am so f#$%^ !!
Sorry to hear of your troubles. Having been there myself, I can only give you some advice. Get yourself a spare external drive and use it for your your DP projects.Then make DVD-R backups of the projects as well. I even have a third HD dedicated to samples and sound libraries as well. You can always create a shortcut to the DP projects on the desktop.If you're pressed for cash, you could even make a separate partition on the Mac HD for DP projects, separate from the apps.The point I'm making is,BACKUP your stuff!!! I'm sorry if you have heard this a dozen times or so, but it is that important. Espsecially when installing critical upgrades, like Snow Leopard. It will definitley save you some heartache in the future......arnopolaris wrote:few days after updating on snow leopard , i got a corrupted file , cant open a project anymore ...an error occured while redaing from the disk ... no back up ...i tried to open it in another computer same , tried to open it in MIDI only , and without anything else , i mean just the file itself ..nothing worked . i am really ••••ed !!! what a desaster , one week work gone !!!
any idea ? though i am quite pessimistic ...
pleeeease if someone has a solution ..
Tony
- syntonica
- Posts: 53
- Joined: Thu Sep 21, 2006 12:18 pm
- Primary DAW OS: MacOS
- Location: The Wild Pacific NW
Re: error - 39 ... i am so f#$%^ !!
Sorry to hear you lost some work.
Unfortunately, it appears the DP does the same thing as Quark does. Instead of making a temp copy to work on (like MS does with Word, Excel files since like dinosaurs roamed), it works on the original. If the program dies a horrible flaming death, the file is easily corrupted. While I am no Time Machine lover, that or any backup regime is your best friend (even if you copy your project folders to another spot every morning by dragging and dropping.). I have had one file saved, but it was still broken.
Maybe DP7 is betterer in this regard.
Unfortunately, it appears the DP does the same thing as Quark does. Instead of making a temp copy to work on (like MS does with Word, Excel files since like dinosaurs roamed), it works on the original. If the program dies a horrible flaming death, the file is easily corrupted. While I am no Time Machine lover, that or any backup regime is your best friend (even if you copy your project folders to another spot every morning by dragging and dropping.). I have had one file saved, but it was still broken.
Maybe DP7 is betterer in this regard.
-
- Posts: 26
- Joined: Tue Nov 27, 2007 9:16 am
- Primary DAW OS: Unspecified
Re: error - 39 ... i am so f#$%^ !!
billf wrote:Do you have Spotlight enabled?arnopolaris wrote:nothing seems to repair that file .. i tried disk warrior too ..anyway thank u guys
yes i think it is unabled , though i am not sure because i never really used it to say the truth , so do u think it can be e reason for my problem ?
i am not sure but i think the problem came from my powercore , because i have some major freeze of the computer when i open some track with powercore plug ins used in the track . then i need to force the computer to switch off and open the project again .then it works . it happened with the project 's dp file corrupted..
-
- Posts: 26
- Joined: Tue Nov 27, 2007 9:16 am
- Primary DAW OS: Unspecified
Re: error - 39 ... i am so f#$%^ !!
i usually always do back up too ..the same day i had the same problem with another track but as i had a back up i could reopen a quite recent version so that was not so bad . and then i did a full back up of all my last track again to update that back up . i was so wrong to do this because unfortunately it did replace the working version of that track with the corrupted one ... i didnt realise it was corrupted because didnt remember i had a computer freeze when tried to open it ..so the file was corrupted and i did back up it like that ...erasing the old working version ...really no luck ! i dont know if i explain myself clearlytonester wrote:Sorry to hear of your troubles. Having been there myself, I can only give you some advice. Get yourself a spare external drive and use it for your your DP projects.Then make DVD-R backups of the projects as well. I even have a third HD dedicated to samples and sound libraries as well. You can always create a shortcut to the DP projects on the desktop.If you're pressed for cash, you could even make a separate partition on the Mac HD for DP projects, separate from the apps.The point I'm making is,BACKUP your stuff!!! I'm sorry if you have heard this a dozen times or so, but it is that important. Espsecially when installing critical upgrades, like Snow Leopard. It will definitley save you some heartache in the future......arnopolaris wrote:few days after updating on snow leopard , i got a corrupted file , cant open a project anymore ...an error occured while redaing from the disk ... no back up ...i tried to open it in another computer same , tried to open it in MIDI only , and without anything else , i mean just the file itself ..nothing worked . i am really ••••ed !!! what a desaster , one week work gone !!!
any idea ? though i am quite pessimistic ...
pleeeease if someone has a solution ..
Tony

so to resume i had 2 corrupted file , one i could read the back up and one ( the finished one ..) that i couldnt because i just replace the right version with the corrupted as i didnt know it was corrupted ...i should have tried to reopen it again after the computer crash before to back up it ! it wont happen again for me as i will "save as" many time from now and alreday have a time machine working now in my computer .