Jump to content
Macro Express Forums

Jimco

Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by Jimco

  1. Thanks, Cory. The problem is that I have no macro if I can't load the macro file. I'm also a bit hesitant to do that since I might encounter other problems along the way. It seems that whatever ME is doing to access the file isn't compatible with SharePoint's SSO authentication mechanism. I think the best option is to use a non-DFS share outside of the SharePoint environment. Jim
  2. I'd like to store my shared macro file on a SharePoint DFS share. This works fine, but only if I've accessed the share via a program other than ME first. If I reboot and check ME, the shared file isn't loaded. If I go to \\server\share via Windows Explorer and then reload Macro Express, it loads the shared file without problem. I got a Process Monitor log while launching Macro Express and I see it trying to hit the share. The result is BAD NETWORK NAME. Has anyone else seen this particular issue? Macro Express seems to be using the GetFileAttributesW API when this happens, and according to the docs on that API, the error I see would result if you use this API to access the share without specifying a subfolder, but that doesn't apply in this case. ME is using \\sharepoint\sites\mysite\mex\macros.mex for the path. I know this is a fringe issue, but just hoping that maybe someone might have an idea of what's going on. Thanks. Jim
  3. To close this out and for anyone who happens to run into this same issue: You can set the shared macro file location (whether per-user or per-machine) using the .wcfg file and it works perfectly. However, if you have an underscore in your macro file name, it won't work because Macro Express replaces the underscore with a space in the Registry. I have filed a bug on this. Jim
  4. I take it back. All is working except that when my configuration is imported, it's not using the <Files> section. I see all of my other configuration settings are added to the Registry, but the macro file that should be loaded isn't loaded and the Files Registry key just has the default macex.mex entry. Still working on it. Jim
  5. Thanks again, Cory. I have all of this working fine now. It's unfortunate that Macro Express Pro will simply crash with an AV if there's an error in your configuration file. It would have been nice to have an error message that points out the problem, but all is good now. Jim
  6. I've been working on this to try and get it to work, but it doesn't seem to be working. If anyone has any experience in multi-user installs with preconfigured paths to shared macros, etc., I'd love to hear details on what you did. Thanks. Jim
  7. I'm creating a custom setup for my organization and I want to export my configuration for use with the CONFIGFILEPATH in my setup. The documentation says to specify the path to the .wcfg file using the CONFIGFILEPATH setting in my setup file. No problem. However, I'm not sure how to use that .wcfg file in my setup. In the Help file, it shows an example like this: CONFIGFILEPATH=c:\macexpro.wcfg However, it seems to me that you would want to include the .wcfg file in whatever folder contains the Macro Express setup files so that it can be applied when users install the app. Has anyone used this setting? Can you offer any insight? Thanks. Jim
  8. Paul, You are correct. I am using Text Type, and the steps that you gave me solved the problem. Thank you! It took a bit of retooling since my steps were defined in a variable and the "%windir%" instance was about half way through them, but it's all working fine now. Thanks to both of you for the assistance. Jim
  9. The macros I'm working on are for a Macro Express Pro pilot for a very large computer software company. The reliability of the macros is extremely important, and instead of convoluting the macro to get this done and risking failure in some environments, I've decided to simply add wording that says, "The location of your Windows directory may differ from these instructions." That ought to cover it. Thanks for the help, Corey. Jim
  10. Hi, Cory. Yeah, I tested that exact scenario. In my macro, I have this in a Text Type command. "Enter %windir%\System32" When that runs, it outputs "Enter C:\Windows\System32" to the focused window. Even if I rename my windir system environment variable, I get the same thing. I'm not sure if this might not be a subtle OS difference. I'm testing this on Windows Server 2008 R2 x64. I attached a debugger to the macexp.exe process and dumped the process environment block. In that, I can see that there's still a windir variable set to C:\Windows. I suspect that's why it's still not working. If I close Macro Express and relaunch it, the new PEB contains the renamed variable. So much trouble that really may not even be worth it, but I do appreciate your help. Jim
  11. Well, easier said that done. As it turns out, the Macro Express process has its own environment block, so even if I modify the environment variable via script, the environment block that ME has still contains the original variable. The only around that (that I know of) is to restart the ME process after modifying the variable with my script. I'm still working on a solution to this, but it may not be possible. Jim
  12. Very clever, Cory. Thank you. I can take care of it using that technique. Jim
  13. Hi, Cory. No, it's not. I am setting a string variable that includes the literal value "%windir%" and then I am using the Text Type command to output the variable to an open email message. Thanks. Jim
  14. I am writing a macro that will output technical instructions to an email to be sent to a customer. One of my steps has the user change to the Windows directory at a command prompt. Because I don't know in advance what the Windows directory will be, I want my step to appear as follows. 3. Enter the following to change into the Windows directory. cd %windir% No matter how I try to avoid it, Macro Express is always evaluating this and outputting "cd c:\Windows" instead of just outputting the literal text. I have tried checking the "Don't process embedded variables" checkbox, but it has no effect. I tried changing my literal value to "%%windir%%", but that just causes ME to output "%c:\Windows%" which is still not what I want. Does anyone have any ideas? Thanks! Jim
×
×
  • Create New...