I have been away a long time and ordered a TSU9300 to replace one of the two TSU7000ís I own. Iíve made enough changes to my systems that I donít use the TSU7000's anymore so I want to migrate what I have and then customize from there unless I should update the 7000 system files and then migrate them to the 9300.
Iíve searched the forum for answers but would appreciate confirmation to a few questions; 1)Is ProntoPro Edit 2_4_18 supported in W7 64? 2)Snow Leopard? 3)Can I migrate TSU 7000 .pcf configurations into ProntoPro Edit 2_4_18 or do I need to first convert the file in ver. 1.1, save in the compatible format that escapes me at the moment, and then open in 2_4_18?
While it is possible to go throuch PEP1 and bring your TSU7000 program to the TSU9300 with "no hands", I'll agree with gopronto. At the very least you'll want to visit every button and change the artwork. Unless you have an odd device that is not in the current database, and you'll need to bring the learned IR codes across, I think that you'll spend as much or more time dragging the old program accross as you would spend starting over. There will be a learning curve for PEP1 that is hard to justify because you'll be using PEP1 briefly.
PEP1 will seem more familiar to you, but PEP2 is the future. Potentually, you could have a very different looking, working program in a few minutes using PEP2.
Had you programmed the original TSU7000? PEP2 is a different environment, but replacing model A with model B is much easier in PEP2 than PronotEdit Pro.
Click on the "Equipment & Codes" tab, select a component, and use the Replace Component button. Note that this operation is not always 100% effective because the button operation spellings might vary between the ancient program and the current database. For example, and old "Skip Track" function, might be known as "Next" in the current database. You'll need to check each button, but most of this type of error will be flagged with a yellow caution triangle in the Component Function area or on the button itself. One can step through a program in a minute or two and find all of these issues.
There are various means of fixing the problem. One can simply drag a line from the Component Function area to the "Actions" list, use [drag], or double click in the middle of a line in the "Actions" list. Try each of these techniques and use what works best for you.
Note that there may be a little annoying detail about the current program. During the transfer into PEP2, it is possible that a given device might appear several times in the "Project Components" list. This is more of an issue in multi-room programs. I suspect that your program is very straight forward. If this is true for you, I suggest that you consolidate all of these components into one component and delete the others. This may seem like an ugly task and in many ways it is, but one can burn more time fretting about needing to do it, than actually jumping in and doing it. And -- this only needs to be done once.
A good technique for accomplishing this is to enter a short, unique name in the "Component Location" area for each occurrence, then use the double click on an action line method to reassign the action to one of the Components, then delete the others. This will result in a simpler, much easier to maintain program going forward.
However, before doing any of the above, you should try the wizard and start a new program from scratch. In a few minutes you can generate a program that you may enjoy very much. You can always move, add, or delete buttons that are not to your liking. Or, if you don't like the wizard result, you can always continue to update the original program.
Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.