A (very bad) design decision Microsoft made, going all the way back to the first version of Windoze, is that programs put information in the system Registry file during install, instead of in a file that resides in a directory (folder) with the program, to be loaded only when the program is started
That Registry information is REQUIRED for a Windoze program to run
Since the Registry file is on the boot drive where Windoze is installed, that means you can't simply move an external hard drive to a different computer and have anything that was installed on that drive run... the Registry information is not there on the different computer, so the moved program won't run
Oh, well that's a shame. Could I at least get premiere to load the Media Cache folder onto an external HDD?
Search link http://www.adobeforums.com/webx?126@@.3bbe4d6a
Media Cache external
Media Cache configure
Read the other discussions to see if one of them has an answer
Thanks. I found that I could easily move the media cache folder anywhere through the Edit/Preferences/Media commands.
>That Registry information is REQUIRED for a Windoze program to run
For the sake of accuracy I must point out that this statement is incorrect. I regularly write MS Windows software that does not require the use of the Windows Registry to work.
Use of the Registry is not a requirement of the Windows OS. Application developers can use it or not as desired.
PremiereProPedia ( RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like you
>Application developers can use it or not as desired
Ok... but if they do use the Registry for program information, installing on an external drive would seem to mean that the program will not work if the external drive is moved to a computer without the required Registry information
Programs often install files all over the System drive which are required for proper function. That's why it's generally not recommended you change the default install location from the C: drive.
Project files you can move. Software installation is a whole different thing.
As long as your OS and your application (Premiere Pro in this case) are both installed on the same external drive (eSATA preferably), then yes, you can move the drive around to different computers. I have done this myself. I haven't run into any issues doing this, but others may have more thorough experience with this.
then you get into the problem of the os having to discover all the hardware and get drivers for them all. Each time you switch.
Back to your initial request. You might be able to get by with your current HDD config. by doing your editing to/from an external HDD. This would NOT be the same as having the program on the external, and would preclude moving PP between machines. You would need PP installed on all.
I've been spending more time on my laptop and doing smallish Projects with 2TB FW-800 externals. So far, things work very well for SD material, with only a slight slowdown in editing speed. If you go this route, set each external up as a unique drive letter, and attach a label to each with that drive letter. In the OS of each machine, set that drive letter. Might want to use W:\, X:\, Y:\, etc., so no conflicts. Remember to set the external's drive letter in the OS of each machine! Otherwise, you will have Asset location nightmares and never get a good night's sleep again.
Were I you, I'd just bit the bullet and re-work my system's I/O with more physical HDDs.
Now, none of this will allow one to move the program about, but maybe Adobe planned it this way?
Have you tried that with XP or Vista, Christian? Both have ties to the specific hardware, and significant changes to hardware, as are likely when switching boxes, can cause issues with the OS working, possibly even requiring a phone call to Microsoft to get it running again.
I understand it can be even worse with Vista.
Never tried it with Vista, so don't know about that one. On XP Pro, the machines were in separate locations, but were mostly identical (avoiding driver issues and hardware differences in general). Like I said, didn't really have any problems on that setup, but I can definitely see where a more loosely constructed environment could yield problems.
That makes more sense.