Hi everyone, just a simple question. According to this bug, winefile and explorer are bit-by-bit identical, but yet 1 crashes when run with no command line, while the other does not. As the subject of this email says, explorer crashes but winefile doesn't. This particular has no problem with running winefile to open his explorer window, but I agree with comment 3 on this one, that users should be able to run explorer with no command line args to get an explorer window. That makes more sense to windows users who run explorer.exe to open up Windows Explorer.. Is this something that is worth looking into? For right now the bug is wontfix because we do have winefile working, but if someone wants to reopen it to figure out why (if it isnt supposed to) explorer crashes, feel free.
Tom
Tom Spear (Dustin Booker, Dustin Navea) wrote:
Hi everyone, just a simple question. According to this bug, winefile and explorer are bit-by-bit identical, but yet 1 crashes when run with no command line, while the other does not. As the subject of this email says, explorer crashes but winefile doesn't. This particular has no problem with running winefile to open his explorer window, but I agree with comment 3 on this one, that users should be able to run explorer with no command line args to get an explorer window. That makes more sense to windows users who run explorer.exe to open up Windows Explorer.. Is this something that is worth looking into? For right now the bug is wontfix because we do have winefile working, but if someone wants to reopen it to figure out why (if it isnt supposed to) explorer crashes, feel free.
Tom
If they are bit-for bit compatible, maybe there is a weird dependency on the filename of the application somewhere.
Phil C
-
Phil Costin -
Tom Spear (Dustin Booker, Dustin Navea)