etj01

Was doing some testing and during a 'file copy' got error 267. Rebooted, no joy, and just before escaping time. Running 3.5c. First loop of code worked, second pass went no where.

Do exported playable macros need to be re-exported after a sub-macro (module) is modified? Does the main module need to refresh the calls or pointers? Ernie

Thanks for the prompt response. I have all the latest bits and pieces. Was wondering how to better use the logging. Ernie

Am trying to understand the why and how to use the { Program - Log Event } feature in the PGM library. Been through the PGM Functions Library and the help file. Something is not sinking in or it's just Friday. I would like to log some process events that I could turn off and on. What happens to the registry entries when additional events are ready? Hope I've made this clear. Right now I feel the same "wow" when I saw the Direct Editor in ME3. I'd hate to overwrite something in the registry. An option to create a backup of registry changes that gets updated each time thngs are changed, could be used to recover or debug a very bad day of writing and runningcode, from where I am today. Later, I'm sure I'll feel more confortable writing to the reg with PGM calls. Ernie

Just curious and not sure this will help but... "Using the command line for Removable StorageYou can use the command-line utility for Removable Storage to manage media resources and to write batch scripts for applications that do not currently support the Removable Storage API (are not aware of Removable Storage). You can run the command-line utility from a command prompt by typing rsm. For help using the Removable Storage command line utility, see rsm. For information about other command-line utilities, see Command-line reference. " If the device does exist and Send the RMS commands to eject the disk. If unattended could you set a timer? Hope this helps. Ernie