Home > An Error > An Error Occurred While Reading From The Disk Digital Performer

An Error Occurred While Reading From The Disk Digital Performer

My MOTU driver started working but wouldn't open the configuration application automatically, so reinstalling it and rebooting fixed it. I'm loading DP 6.0 for the first time. The bad news was that the procedure, though it went as described, did not work for me. I can't even guess how you got that article from them. http://dukesoftwaresolutions.com/an-error/an-error-occurred-digital-photo-professional-will-be-closed.html

Peterson) Visual Art Drawings Paintings Technology Computer Problems and Fixes Hard Drive Drama joomla Music Production Software Old Macs Ubuntu/Xubuntu/Linux WordPress Evil Robots Scam Email Mashups Marketing/Advertising In The Cloud SEO, Proudly Powered by WordPress. New Reply Facebook Twitter LinkedIn Google+ Reddit Search Forums Post Reply Welcome to Gearslutz Pro Audio Forum! It's a very useful program but it does cost like $40 bucks. http://www.motunation.com/forum/viewtopic.php?f=1&t=38402

It's only been a day so far, so I'll post an update if it happens again. All rights reserved. I was trying to share my whole hard drive, and not just my home folder. Share Quote 26th January 2010 #4 peter karr Gear interested error = -39 I'm becoming extremely frustrated with a very similar problem.

Instead, open up terminal (Applications > Utilities > Terminal) and cd to the directory the zip file is in, such as: cd ~/Downloads or cd ~/Desktop Then, type: unzip -P [password] So I found the solution and now it works perfectly. Design Based on the "Twelve" Theme. I did not get the message again, and so far so good.

Click." So I deleted some audio files in there and now I could make changes and save without the "can't save" dialogue, but I was still getting occasional machine crashes with Jeez. I have Waves, Protools, and Reason on my PPC G5. I read through a whole bunch of posts, and I am suspecting that this error has to do with plugins that are running on a TRIAL PERIOD.

After that I was able to boot again. The same thing happened with Check Permissions. Authorization will not help and the request SHOULD NOT be repeated. So I isolated a few things and went after MOTU by dialing-to-death and catching them between busy signals (G-d forbid they should have a decent hold system).

i waited a minute, hit "apple-s" again, and everything was fine. If you found this information helpful, please consider making a donation. Neither of those are what I'm looking for. I've had DP for 10+ years.

By the way, in the article Troubleshooting permissions issues in Mac OS X, it says 1) open Terminal 2) type: sudo rm -rf. Check This Out i only have one HD in my machine, so i can't save it to another disk. Hiro Hiroaki Honshuku mailto:hiro at a-no-ne.com A-NO-NE Music, Cambridge, MA http://a-no-ne.com Previous message: [MOTU-MAC] Tempo ATA66 & Interal ATA: Peaceful Coexistence? Try to re-export OMF to differnt disk Return to posts index<< PREVIOUS • VIEW ALL • PRINT • NEXT >>© 2016 CreativeCOW.net All Rights Reserved[TOP]

In finder, I used get info and saw similar permissions: Sharing & Permissions: System: Read & Write admin: Read & Write everyone: Read only Since it says "Sharing" above it it, and it happens with multiple projects as well. If you're not comfortable doing things in the Terminal, File Buddy is a great app for this sort of thing. Source Terms of Use Updated Privacy Policy Cookie Usage not registered yet?

You can also test your kernel extensions by running: kextload -t MOTUFireWireAudio.kext for example. Apparently, my old files with BFD (and the tracks connected with it) had already been created, so the warning opportunity during assignment had passed. Error Says: An Error occurred while writing to the disk.

I took a fresh file and created an instrument and tried to assign it to BFD drums, At that point, DP allows BFD to give me a warning dialogue if it's

I was still getting occasional kernel panics and other wierd stuff reconfiguring Audio MIDI Setup. I'm not sure if this is a Leopard thing or a Google Desktop thing (it installs its own widgets). So I'm crashing and even MOTU can't tell why (though they THINK they do). I did that, ran killall Dock, did the reverse, and ran killall Dock again, and it seems to be fixed.

Board index The team • Delete all board cookies • All times are UTC - 8 hours [ DST ] © 2002-2016 MacOS Audio. NOTE: This is an affiliate link so I do get paid if you sign up with BlueHost after following this link. *But* I only participate in their affiliate program because I It's censorship, but I understand why they do it. have a peek here This is what I did to solve the problem: - I trashed the DP "Preference" folder in User/Library/Preferences/Digital Performer (however, I am not certain that this was actually necessary) - I

That gave me verbose output that the permissions were wrong. I went back and changed the everyone permission on Macintosh HD to read only.