Something that always pissed me off was I wrote QE to handle and pass long file and directory names from scratch yet thee has been a problem with both for some years. I bothered to chase the problem down and its very simple, unless the long dir/file path is quoted as it is passed to the batch files, it generates an error that it cannot find the source file.
All that needed to be done was place the notation {b} within quotes "{b}" so the complate path was received by the batch file. With the run file option in the menus.ini you add the .exe extension so you have "{b}.exe" and it all works correctly. The new batch files no longer use quotes internally as the changes to the menus.ini file already place quotes around the path that is passed.
Put the ini file in the same dir as QE and put the batch files in the BIN directory of MASM32 and it all should work correctly.
"H:\asm3\long dir name\long file name"
Microsoft (R) Macro Assembler Version 6.14.8444
Copyright (C) Microsoft Corp 1981-1997. All rights reserved.
Assembling: H:\asm3\long dir name\long file name.asm
Microsoft (R) Incremental Linker Version 5.12.8078
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.
Volume in drive H is WIN2K_H
Volume Serial Number is 20E8-3719
Directory of H:\asm3\long dir name
11/25/2006 06:23p 583 long file name.asm
11/25/2006 07:55p 935 long file name.obj
11/25/2006 07:55p 2,560 long file name.exe
3 File(s) 4,078 bytes
0 Dir(s) 20,985,626,624 bytes free
Press any key to continue . . .
[attachment deleted by admin]
Ummm, you only just now figured out that quotes are necessary?
Paul
:bg
Thats not the problem, it was where to put them. Not quoted in the batch files and not quoted in the parsing guts of QE, just in the notation in the menus.ini file.
Oh, I knew you knew about the spacing problem so your post was confusing to me, thanks for the explanation.
Paul