Hi Peter!
Do you use Total Commander?
Is configured to use as editor
ueFastStart.exe in settings of Total Commander?
Do you use
F4 or
Shift+F4 in Total Commander to open a file with
ueFastStart.exe in UltraEdit?
If the three questions are answered three times with
yes and UltraEdit v27.xx is not already running, than there is indeed a problem caused by how
ueFastStart.exe is starting UltraEdit with the name of the file to open specified on the command line as I could find out with Sysinternals Process Explorer.
ueFastStart.exe starts the UltraEdit executable with the file name
not enclosed in double quotes as it must be done on file name containing a space or an ampersand or an equal sign.
ueFastStart.exe starts UltraEdit for example with the command line:
"C:\Program Files (x86)\IDM Computer Solutions\UltraEdit\uedit32.exe" G:\01\014_IDM\01-U-Edit\Mal sehen\perlcgi.txt
UltraEdit versions prior version 27.00 find out by itself that there are not to open the two files
G:\01\014_IDM\01-U-Edit\Mal and
sehen\perlcgi.txt, but the file
G:\01\014_IDM\01-U-Edit\Mal sehen\perlcgi.txt.
But UltraEdit v27.xx parses the command line arguments different because of the additional feature to get the hash value for a file from command line (with the help of uedit32.com or uedit64.com). See also
Command line parameter -f does no longer work with UE v27.00 on search string containing space (fixed).
UltraEdit for Windows v27.xx is not anymore as fault tolerant as former versions regarding to file names with spaces not enclosed in double quotes.
ueFastStart.exe should use the following command line to start UltraEdit and open the example file:
"C:\Program Files (x86)\IDM Computer Solutions\UltraEdit\uedit32.exe"
"G:\01\014_IDM\01-U-Edit\Mal sehen\perlcgi.txt"
That is the command line used by Total Commander if uedit32.exe is configured as editor in settings of Total Commander instead of
ueFastStart.exe.
It also does not work anymore to start UltraEdit by
ueFastStart.exe and open multiple files of which full qualified file names are written line by line by
ueFastStart.exe into a temporary list file created in
%TEMP% and starting UltraEdit with the command line:
"C:\Program Files (x86)\IDM Computer Solutions\UltraEdit\uedit32.exe"
/f%TEMP%\CMD265E.tmp
UltraEdit v27.00 and later versions require now a space between option
/f and the full name of the list file which should be additionally always enclosed in double quotes as the path to folder for temporary files can contain a space character. So
ueFastStart.exe should use in this case:
"C:\Program Files (x86)\IDM Computer Solutions\UltraEdit\uedit32.exe"
/f "%TEMP%\CMD265E.tmp"
Note:
ueFastStart.exe does not really start UltraEdit with
%TEMP%.
ueFastStart.exe uses the real full path to folder for temporary files.
The space character between
/f and list file name was prior v27.00 optional, but is required now.
Opening files using
ueFastStart.exe works still fine on UltraEdit 27.xx already running as in this case the file name(s) are passed to UltraEdit using the message sent also by Windows to UltraEdit on drag and drop one or more file names to UltraEdit's main application window.
Windows File Explorer and Total Commander itself start UltraEdit with the file name of the file to open always enclosed in double quotes. So this issue occurs only with
ueFastStart.exe used from Total Commander as done by me for many years now or from Windows File Explorer.
In case of
ueFastStart.exe is not used by you, but UltraEdit is started from another application or a script with the full qualified file name of the file to open specified on the command line, make sure that the file name is always enclosed in double quotes, even on not containing a space or
& or
=.