Hi,
"Why is it so?" (PSM ;)
./wine --help
quote:
"Usage: wine [--bottle BOTTLE] [command]
[options] [application arguments]
Runs Windows, Winelib or Native applications in the Wine environment. With the
--start command, documents can also be opened using the Windows associations.
Where command is one of:
--cx-app FILE Run the specified Windows executable
--wl-app FILE Run the specified Winelib executable
--ux-app FILE Run the specified Native executable
Native paths are not converted to Windows paths
--start FILE Open or run the specified document "
end-quote:
So we see here, the --start command is specifically to open a document, as opposed
to an executable (which is what you're...or the scripts...are trying to do).
Dropping the --start command, I'm pretty sure makes wine drop back to it's default position ;
which is run an executable. Conversely, if you specify --start, wine is expecting a document
for the FILE statement, so it knows which executable to start that is associated with that FILE
and it would do this by the file extension ..ie; .txt -> open notepad, .doc -> open word etc,
unless overridden by a system registry entry on the windows side of the book. My guess is,
when FILE is some .exe file when used in conjunction with --start command, it forms an illegal
command syntax and nothing is started at all.
That's why...but what you describe shouldn't be happening, if what you're saying here is that
the links are being generated by the cxinstallwizard process? Omitting --start is going to be
'shorthand' for the command --cx-app by the looks of it...you could check if that works or not,
however as even --cx-app is seemingly optional as well, it must serve some other purpose..apart
from forming a pseudonym for using no [command] switch at all...but I'm not that familiar with
the source code ; whatever, it shouldn't be creating links so...ie; mistaking the executable
for a document. If it is CO doing this and your can reproduce the error, it'd probably be a
something to lodge in the support ticket system.
