I'm having a bit of trouble getting WinMerge to accept command line arguments, although it does seem to run nicely under wine. I am using Wine under Mac OSX. From selecting files manually within WinMerge, I can see that it uses a Z: drive letter to reference the OS filesystem. I have tried this: Code: open -a Wine "/Applications/WinXP/drive_c/Program Files/WinMerge/WinMergeU.exe Z:\Users\usera Z:\Users\userb" and this: Code: open -a Wine "/Applications/WinXP/drive_c/Program Files/WinMerge/WinMergeU.exe -- Z:\Users\usera Z:\Users\userb" with no luck so far. Can anyone offer some advice? I'm not a stranger to the command line, but I am new to wine.
> open -a Wine "/Applications/WinXP/drive_c/Program Files/WinMerge/WinMergeU.exe Z:\Users\usera Z:\Users\userb"You don't need to use the open -a on the wine executable on MacOSX. Also, you cannot use your WinXP directory to run programs from for Wine. You need to install this program in the wine file structure. Can you provide the command line you used to initalize Wine with? If you mapped your Windows C: drive to be your Wine c: drive, you just hosed up your Windows install and broke Wine. The FAQ provides information on why not to do this and what you need to do to recover from it. James McKenzie
Hi, I think my naming conventions might be causing some confusion. I created a prefix called WinXP using WineBottler. It's not a copy of a Windows installation. I installed WinMerge within Wine, not by copying the binaries from a Windows box. I'll try it again without the open -a, but I've tried it using many different permutations already and I don't recall that causing a difference in what I was seeing. WinMerge starts fine, I just can't get the command line arguments to pass to the Windows exe