This is wrong. Explorer has nothing to do with file associations. You should be using "start <foo>" instead. Regardless Wine's explorer doesn't support this.
I do agree with you although I could not locate any more or less official documentation on that from Microsoft..
Unfortunately I am not the author of the program running in wine that shoots this "explorer.exe" command to open associated files.
The "start.exe" command did not work with the program although it works perfectly in cmd.
I'll dig deeper into why the start.exe didn't do it's job.
This is wrong. Explorer has nothing to do with file associations. You should be using "start <foo>" instead. Regardless Wine's explorer doesn't support this.
I would rather say that this is bad usage ..
Anyway, for some strange reason the explorer version does work in Windows..but I don't even want to know why
you have some program made for Wine that is using Explorer? or its some windows program thats using that as a command line argument to open files? Sounds like a really lazy programmer to do something like that....
heck you could always try to make a dedicated bottle just for this one program and rename start over to explorer and see what happens
doh123 wrote:you have some program made for Wine that is using Explorer? or its some windows program thats using that as a command line argument to open files? Sounds like a really lazy programmer to do something like that....
It's a windows program, in fact it's SBClient (SystemBuilder from http://www.rocketsoftware.com/u2/) and yes it shoots a pdf opening command using explorer.exe.
doh123 wrote:heck you could always try to make a dedicated bottle just for this one program and rename start over to explorer and see what happens
I could but I don't think I have to..I think I've found the troublemaking piece: start.exe was called but this is non-existent on Windows..hence the trouble. start is an internal MSDOS command and hence is called by just typing