Hilarious. 10 minutes after I install protools it's already ****ing my computer.

[Chris]

So I went and picked up an mbox micro because I'm starting to work in studios that use protools and I needed a dongle to use protools with. I've never had any problems installing software or hardware.

Well now, until this. I set it up how they tell you to, plug in the micro and then insert the cd and run the install program. Halfway through installing it freezes. So eventually I figure it's not moving anymore and have to do a hard reboot. I figure I could uninstall anything that happened and then reinstall it again from scratch.

I go to the add/remove programs and try and remove it and it won't let me! It tells me I have a previous version and to reboot my computer. That of course doesn't work and it gives me the same error, so I can't reinstall, and I can't uninstall. If I plug in the micro to a USB port it just gives me a blue screen after a few minutes and I have to reboot.

If I try and start up protools it tells me: "This software requires installation of device driver TPkd an a reboot before running. Please reboot or reinstall the software."

Of course I have rebooted.



Any help on how to get this abortion off of my computer so I can start humping away again?

[hanuman]

Your topic suggests that PT is responsible for your crash.
That is not so. You might like or dislike PT, it's functionality whatever, but if your install goes wrong just sort it out. (You know the drill, uninstall, download latest version -or older if OS is older- hardware drivers, etc. )

[PlatinumSamples]

Revert to a Restore Point and try again... after checking your system is compatible.

Rail

[pigcat]

Out of topic post but...

I've earn my living for quite some time with windows and pro tools.

What's wrong with windows?

[Reptil]

LMAO!

[treblig442]

I used to run PT's on a Windows machine. It worked ok, but had its faults and errors. Actually quite a few of them. I switched to a Mac and ill never look back. Good Luck.. Try reformatting the PC, fully install all updates for windows and then try again? Is this XP or Vista? sorry if you already mentioned

[Chris]

Originally Posted by treblig442

I used to run PT's on a Windows machine. It worked ok, but had its faults and errors. Actually quite a few of them. I switched to a Mac and ill never look back. Good Luck.. Try reformatting the PC, fully install all updates for windows and then try again? Is this XP or Vista? sorry if you already mentioned

XP. I posted on the DUC and some guy suggested some PT Nuke program. Haha. I'll have to see if that works. I don't plan on using PT for anything other than importing sessions from the other studios and using elastic audio. Blah. What a headache.

[Studio Dweller]

I highly doubt that the fault lies with Pro Tools. I've been using it (on a Mac) since version 3 and it's really been one of the most stable and reliable pieces of software I own. I can probably count the number of crashes I've had over the years which are very few and I've had none as of recent. I honestly can't remember when it crashed last.

I'm also very careful about maintaining a compatible system and never doing things like OS updates until they're officially sanctioned by Digi or at the very least, until I see that other people are running it successfully. Preventitive maintenance goes a long way as well.

I'd take a closer look at your system.

[True North]

Originally Posted by Chris

XP. I posted on the DUC and some guy suggested some PT Nuke program. Haha. I'll have to see if that works. I don't plan on using PT for anything other than importing sessions from the other studios and using elastic audio. Blah. What a headache.

Have you tried calling their tech support - they are actually pretty good.

PT is working fine for PC. Dig are not huge MAC fans after Apple came out with Final cut which ate into their AVID sales. Logic and to a lesser extent Garage Band all compete directly with PT. 4 or 5 yearsa go, Digi's business was strongly biased towards MAC but alot has changed since then.

Good luck

[Chris]

Originally Posted by True North

Have you tried calling their tech support - they are actually pretty good.

If I can't get an answer on the forums I'll end up doing that.

And I'm sure there's no problem with PT when it gets installed. But there was obviously something messed up with the install.

[Gerax]

Originally Posted by Chris

If I can't get an answer on the forums I'll end up doing that.

And I'm sure there's no problem with PT when it gets installed. But there was obviously something messed up with the install.

Be sure that your hardware is spec'ed as compatible with Digi's standards. PT is a bit finnicky on what hardware it likes to run on on the Windows side of things. On the DUC you can find lots of proven configurations that work, are rock solid, smoke a Mac in terms of performance (go read the real numbers if you think I'm joking) and the price factor is out of the question...It's not PT's fault or Windows fault. It's that you should check the compatibility first.
We're running 5 (3 desktops and 2 laptops) Windows XP and Vista machines with Pro Tools LE and HD in the post facility I collaborate with, plus 2 more in my personal studio...all get 10 to 12 hours of work every day...no need to reboot...a single time...so you can be sure that PT on Win works.
Ah, and btw I really can't belive there's still somebody so desperately in the past to belive this "Mac" myth anymore...and if you want to flame me for this comment, then by all means do that, that's the ordinary answer for this , I'm here to prove what I'm saying with real facts...not myths.

[KingDaddyO]

There is nothing inherently unstable using Windows vs. the Mac OS for audio production, other than knowing how to keep either platform running. This guys needs help, not the old 'my god is greater than your god' platform wars.

Booting from a previous good restore point was a good one, as was the suggestion to check h/w & s/w compatibility requirements.

Also check Device Manager for any Yellow alerts or Red disabled device alerts (at the Desktop, right click on My Computer, select Manage, select Device Manager -or- Start - Programs - Control Panel - System - Hardware - Device Manager). If you have any undesired or unintentional alerts or disabled devices, resolve those first before proceeding with new installs.

If you still are unable to uninstall the aborted first instance, you can rip it out by deleting the HKLM & HKCU software registry keys, and then deleting all related program folders & config files, then rebooting. Make sure you backup the full registry first, and also make a rescue disk. If you are computer savvy all of this isn't too terribly difficult (with instructions if needed). However if you are capable of destroying computers by simply sitting down at the keyboard, then this approach probably isn't the best one . Let me know if you need help with this approach and I'll try to supply additional details.

Having said that, the suggestion to seek DigiDesign vendor & support forum assistance first, is the best one to start with. Microsoft is likely to point the finger at the audio vendor anyway so I wouldn't waste any time there. Besides they will want a CC number first, to charge you $250, unless you have a support contract already with them.

Good Luck.

[Chris]

Originally Posted by KingDaddyO

There is nothing inherently unstable using Windows vs. the Mac OS for audio production, other than knowing how to keep either platform running. This guys needs help, not the old 'my god is greater than your god' platform wars.

Booting from a previous good restore point was a good one, as was the suggestion to check h/w & s/w compatibility requirements.

Also check Device Manager for any Yellow alerts or Red disabled device alerts (at the Desktop, right click on My Computer, select Manage, select Device Manager -or- Start - Programs - Control Panel - System - Hardware - Device Manager). If you have any undesired or unintentional alerts or disabled devices, resolve those first before proceeding with new installs.

If you still are unable to uninstall the aborted first instance, you can rip it out by deleting the HKLM & HKCU software registry keys, and then deleting all related program folders & config files, then rebooting. Make sure you backup the full registry first, and also make a rescue disk. If you are computer savvy all of this isn't too terribly difficult (with instructions if needed). However if you are capable of destroying computers by simply sitting down at the keyboard, then this approach probably isn't the best one . Let me know if you need help with this approach and I'll try to supply additional details.

Having said that, the suggestion to seek DigiDesign vendor & support forum assistance first, is the best one to start with. Microsoft is likely to point the finger at the audio vendor anyway so I wouldn't waste any time there. Besides they will want a CC number first, to charge you $250, unless you have a support contract already with them.

Good Luck.

Good post. Thanks. I am mostly looking for a way to get PT off of my computer so I can try reinstalling it. So far I have the PT Nuke tool and your way with the registry. I'm computer savvy so if the nuke doesn't work I'll probably try the registry edit.

[KingDaddyO]

Originally Posted by Chris

Good post. Thanks. I am mostly looking for a way to get PT off of my computer so I can try reinstalling it. So far I have the PT Nuke tool and your way with the registry. I'm computer savvy so if the nuke doesn't work I'll probably try the registry edit.

That's cool. The critical thing is to be sure you know which keys to delete in the registry before proceeding. Hope the PT Nuke thing works out.

[drew]

How can it be this difficult to uninstall an App?

PT comes with an uninstaller.

[Chris]

Originally Posted by drew

How can it be this difficult to uninstall an App?

PT comes with an uninstaller.

I looked and didn't find one.

And yes, that's the point. Why is it so damn hard to uninstall an app.

[drew]

Get someone to email it to you. If the install went haywire, it might not have gotten to it.

[drBill]

Originally Posted by Studio Dweller

I highly doubt that the fault lies with Pro Tools.

Exactly. Go online and you can find dozens of people whining about how PT messed up or PT won't work or PT's Satan's domain.

But after 10+ years of using it every day,, installling hundreds of plugs on close to a dozen computers, I've really never had a problem that wasn't traced down to me being a knucklehead.

[KingDaddyO]

Originally Posted by drew

How can it be this difficult to uninstall an App?

PT comes with an uninstaller.

Sometimes a random glitch during the installation process, makes it possible for the system (the OS) to 'read' the application's status in conflicting ways. For ex, the system reads a registry key that reports ver. x, while the app fails to launch or operate properly, or if it does start, might not allow you to download a patch you need because it thinks it is already installed ... all because the install never completed fully, or there is a bug in the released version you're using. So you get into a catch 22 type of situation.

It's important to remember - not all software is created equal, and the same holds true for software developers. And there is also that whole 'adhering to the Windows API' thing that many developers don't always bother to comply with, or test extensively for.

So it isn't always the end users fault. The latest version of Adobe CS3, has this type of poor coding, built into the apps 'check for updates' function, as I've described as an example above.

[drew]

Originally Posted by drBill

Exactly. Go online and you can find dozens of people whining about how PT messed up or PT won't work or PT's Satan's domain.

But after 10+ years of using it every day,, installling hundreds of plugs on close to a dozen computers, I've really never had a problem that wasn't traced down to me being a knucklehead.

I install new builds all the time and I've never had it mess up.

[docbop]

When things like this happen during installs its usually because something else hardware or software is running in the background interrupting the install program. Unless working on servers I reboot before doing installs to make sure the system isn't busy during install.

I've been in this situation with other software. What the person said about deleting all the files and folder PT created then whatever reg settings PT has made should do the trick. Some installers will put a status file on the drive, so if a install abends it knows where it left off and can pickup from that point. I wish all installer did that.

[RickZ]

You wrote "This software requires installation of device driver TPkd an a reboot before running. Please reboot or reinstall the software."

I had a similar mess-up recently just installing PSP Xenon plug, with the TPkd message. Turns out I'd skipped the new Ilok driver step. After uninstalling and doing the Ilok driver update during install, all was well.

Macecraft RegSupremePro has helped in times past uninstalling things that normal XP Add/Remove won't. The Registry Cleaner also seems to work well, at least hasn't screwed anything up.

Hope this helps . .
Rick Z

[Chris]

The PT Nuke worked (haha, a .zip file with the uninstaller in it).

Thanks for the constructive replies.