> With all those things to keep unique by machine, why do you want a > single pcf?
I'm trying to slowly move to less-manual-upkeep of my critical files/programs/configs. Less duplicate changing of items in several configs depending on what device I'm on. I'm starting to use Syncbackse configured with my ftp server on my main box to start replicating files I'd want many places so everywhere is kept the same and up to date. As it was, I was starting to loose track of where/what had my most current info, where needed updating, did I forget to add/change something from one config that I wanted in another config, updating client data in one word file on my PDA, which I needed access to on my laptop, home system, and work machine, and if I update on one...was the copy I was working on at work current etc. And as an added bonus with the same info replicated on several devices for regular use, backups are automatically taken care of! :) > On the assumption that there are a whole bunch of other things that > you did not mention that are the same for each machine, you may want > to have one pcf that is common for all and which does at text import > at startup of unique keys and command lists for each machine; > you will > also need to repeat imports in reconfigure command list. > > Since stuff imported from text files supplements stuff from the pcf, > this should work... Maybe so...and then all I have to do is (especially for the hotkey items) put updates into the text files for the configs I want. Which I can do at command-addition/modification time. For each device, I create a global variable, that I use to test where I am at the time of powerpro start and load/reload the appropriate text files. Probably the biggest scripting item will be that startup/reconfigure script that will define who and what to load, depending on the system it's running on. I'll have to keep mulling on it, see if it's worth the effort. --------------- I've already started work on separating my .pcf folder, and powerpro folder so they're not in the same tree... C:\Program Files\Powerpro\powerpro.exe (used to be c:\dave\ppro\powerpro.exe) C:\dave\ppro\dave.pcf (used to be c:\dave\ppro\configs\dave\dave.pcf) The main impetus for this was because of the work config...I want to distribute powerpro.exe as GPO, and have config files maintained in the user area (or My Documents that are redirected to a network share). Many users jump from system to system and I'd rather maintain powerpro with one thing that just installs the program onto all computers, and different configs for different users in another area. Thanks bruce! David Troesch | Atlanta, GA | ICQ# 2333123 Powerpro Resources. Find 'em here - http://powerpro.pcrei.com Funstuff: I'm only wearing black until they make something darker. Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
