Complete DP Uninstall

[vonski]

I need to do a complete manual uninstall of DP. Can someone provide a step-by-step procedure for this? Thanks

[Frodo]

Not difficult.

1. Insert DP CD ROM

2. Choose "Uninstall" from the menu at the upper center of the window (Custom Install, Easy Install, Uninstall)

3. Uninstall

There is a trickier way, though, but if you want to hear about it let me know before you do the disc uninstall.

[vonski]

thanks. i have done the cd uninstall. i actually need the manual procedure which involves clearing certain folders. hope you can help me with this.
thanks.

[Frodo]

Hmm--

If you still have the DP app icon on the drive you could Control-click on it and choose Show Package Contents. Delete the entire DP package folder that appears.

If you don't have the DP app icon as a result of doing the CD uninstall, there are two ways to go about it. The easier of two ways is to use your Search feature in the Finder, or Spotlight. Do a search for "DP", "Digital Performer", "MAS", and "MOTU". Trash everything except for your projects and their folders.

The more difficult method is to locate your Installer Log for DP. This will be found:

User Library> Logs.

If you've updated DP, you should find installer logs for each version you've installed. The log file will contain every file that was installed at the time of installation. This is a great reference.

Now, don't get too overwhelmed about the amount of files that are listed. Look for the entries that begin with "Created Folder" and just search for those folders. Deleting folders created by the DP installer is going to be better than doing one file at a time.

Best of luck!

[Eleventh Hour Sound]

Not difficult.

1. Insert DP CD ROM

2. Choose "Uninstall" from the menu at the upper center of the window (Custom Install, Easy Install, Uninstall)

3. Uninstall

There is a trickier way, thought, but if you want to hear about it let me know before you do the disc uninstall.

4. Reinstall and Rock!

[Frodo]

4. Reinstall and Rock!

Always ROCK!!

[williemyers]

Hmm--The more difficult method is to locate your Installer Log for DP. This will be found:
User Library> Logs.
If you've updated DP, you should find installer logs for each version you've installed. The log file will contain every file that was installed at the time of installation. This is a great reference.
Now, don't get too overwhelmed about the amount of files that are listed. Look for the entries that begin with "Created Folder" and just search for those folders. Deleting folders created by the DP installer is going to be better than doing one file at a time.
Best of luck!

I think Frodo hit the nail on the head here. The last time I recall doing a clean install of DP, it seems like there were well more than 1000 files installed and I don't think "Uninstall" really gets rid of that many of them. If you *really* need to wipe all the DP related files, it's the Install Log that he pointed to that'll get you closest, I think. However, I think even the Install Log will only give you the *visible* files. The hidden ones?....that's another matter!

[zed]

Since DP 6 and DP 5 seem to share some files, I wonder if uninstalling one will disable functionality in the other. Probably. Perhaps not everyone took the risk that I did in installing both of them on the same system. The addition of DP 6 did compromise, somewhat, the stability of DP 5.

And now I'm getting ready install DP onto my new computer, and I want to avoid the same mistake. So I am thinking of dividing my new system drive into 2 partitions so that I maybe I could run DP5 on one and DP6 on another... but that will end up being a headache real quick. I am wondering if I should just install DP6 and make a clean break from DP5? I need stability and don't want to mess up my new system right from the get go. Decisions, decisions...

[williemyers]

Since DP 6 and DP 5 seem to share some files, I wonder if uninstalling one will disable functionality in the other. Probably. Perhaps not everyone took the risk that I did in installing both of them on the same system. The addition of DP 6 did compromise, somewhat, the stability of DP 5.

And now I'm getting ready install DP onto my new computer, and I want to avoid the same mistake. So I am thinking of dividing my new system drive into 2 partitions so that I maybe I could run DP5 on one and DP6 on another... but that will end up being a headache real quick. I am wondering if I should just install DP6 and make a clean break from DP5? I need stability and don't want to mess up my new system right from the get go. Decisions, decisions...

zed, I think you're quite correct that; when you install DP6 on the same system as DP5, 6 will "overwrite" some files that it and 5 might share. all fine for 6, but it causes 5 to have to use "6" versions of those files, making 5 somewhat less stable. I think, yes - if you want to "cleanly" run 5 and 6, you should to 2 partitions, two clean OS's and do 5 and 6 on each one. a pain? maybe yes but it'll get the job done.
once 6 gets really "right", you can always wipe the 5 partition that you created.

[zed]

...when you install DP6 on the same system as DP5, 6 will "overwrite" some files that it and 5 might share. all fine for 6, but it causes 5 to have to use "6" versions of those files, making 5 somewhat less stable.

Thanks for writing that... I hadn't spent too much time thinking about *why* it had happened, but your explanation about files being overwritten is very logical and I'm sure that this is exactly the reason. It probably would have been better for MOTU to have programmed it so that those files had a different name. In some respects it is useful, however. I have updated key commands and other settings and then found them working in the other version of the program.

I think, yes - if you want to "cleanly" run 5 and 6, you should to 2 partitions, two clean OS's and do 5 and 6 on each one. a pain? maybe yes but it'll get the job done.
once 6 gets really "right", you can always wipe the 5 partition that you created.

Do you, or does anyone have any opinions on the integrity of system data if it is cloned from one partition to another? Should it work just as efficiently as the original, or are there likely to be some minor problems introduced into the system? I'm gonna be using the latest version of Leopard.

[Frodo]

Do you, or does anyone have any opinions on the integrity of system data if it is cloned from one partition to another? Should it work just as efficiently as the original, or are there likely to be some minor problems introduced into the system? I'm gonna be using the latest version of Leopard.

If it's the same version of the same OS, there should be no problem. I still don't trust anything like migration assistant. A few people I've spoken to recently have had some file corruption of one type or another.

But cloning should be fine, I would think. The only thing I don't know is how different third-party plugs and VIs handle their authorizations. Some use a system ID as part of the authorization. In my case, the system ID is different for my two OS drives, but I'm running 10.4.11 and 10.5.6 and am not sure if running two different drives with the same OS would make the system ID the same. In any case, some third-parties needed two completely independent authorizations.

Call me old fashioned, but the safest thing for me was to just install everything and do the updates. I have very good reasons to be paranoid about this stuff, but I know some people have never had any troubles.

I also kept DP5 and DP6 on separate drives in separate OS's from day 1. I've got DP5.13 in 10.4.11 and DP6 in in 10.5.6.

[williemyers]

Do you, or does anyone have any opinions on the integrity of system data if it is cloned from one partition to another? Should it work just as efficiently as the original, or are there likely to be some minor problems introduced into the system? I'm gonna be using the latest version of Leopard.

zed, if you're talking about cloning your 10.5.x OS from one partition to another - using a good clone program - one thing to consider is that you would probably also be cloning the OS's Admin. acct., password, etc. You'd have two identical OS's, with identical Admin. Acct.s, passwords, etc. And - if you use auto login - that could get the Mac *very* confused the next time it tried to boot it up! I would think you'd be better off doing a clean install of 10.5.x in to that new partion, with a unique Admin. acct., password, etc.
If it were me, I'd go with Frodo's suggestion:

I've got DP5.13 in 10.4.11 and DP6 in in 10.5.6.

although I am having good luck with DP 5.13 on 10.5.6

[Shooshie]

While I don't miss the performance of the old MacOS, when subjects like this come up, I do miss the simplicity of fixing the system. There were a finite number of files, basically all visible, and it all behaved in predictable ways. You didn't have to create a separate OS drive for DP, just a different "Location." That would determine which extensions were loaded, drivers, printers, network connections, Appletalk settings, and so on, so when you wanted to work on music, the whole system was easily set up just for DP.

The UNIX system under OSX is less visible, but what we see of it isn't as intimidating as it may seem at first. I don't think DP installs any invisible files, unless they may be copy protection files. Reading through the installer log may scare you, but remember that most of those files are inside the app itself. Deleting the app deletes the files. Just a handful of files get installed in /Library/Audio, and /Library/Application Support. There may be some installed at the System Folder level, but the only ones I know about are in the extensions folder.