Command line 8.3 macro path names

PaoloFCantoni · May 31, 2005#12005-05-31T13:31+00:00

It would appear that even though the macro path name on the command line (/M switch) is enclosed in quotes, the path can't contain spaces.

Can anyone else confirm this?

I've logged a bug with IDM, but if there's a work around I'd like to know.

I can't always guarantee that the 8.3 name will be the same even though the full name is...

For example:

D:\Document management\Fred

requires:

D:\DOCUME~2\Fred

Cheerz,
Paolo

Mofi · Jun 01, 2005#22005-06-01T06:18+00:00

Have you set the quotes correct?

Wrong: "/M,E,5=full path of macro file/macro name"

Wrong: /M,E,5="full path of macro file"/macro name

Correct: /M,E,5="full path of macro file/macro name"

PaoloFCantoni · Jun 01, 2005#32005-06-01T07:05+00:00

Hi Mofi,

thanks for the the input. I actually had:
/M,E="full path of macro file"

There's only one macro in the file and (naturally) it's the first, so I guess I assumed (according to what the UE help implies) that it would execute the first macro...

Any other ideas?

Paolo

Mofi · Jun 01, 2005#42005-06-01T09:59+00:00

I tested it with UE V10.10c with a macro file with many macros and a macro file with only one macro. No problems with long macro file and path name (spaces included).

In such situations, I always use Filemon from SysInternals. This little tool (unzip and run it, no installation) monitors and logs every disk access. Set input filter of Filemon to uedit32 to monitor only disk accesses of UltraEdit and not other tasks in the background. Maybe you then can see, what's going wrong.

PaoloFCantoni · Jun 01, 2005#52005-06-01T10:42+00:00

Thanks again Mofi,

I aready had FileMon - but when I set it up to record UEdit32 - It all started working!

I'll have to check the other machine tomorrow (at work) in case the problem is specific to that machine....

Paolo