On Mon, Aug 11, 2008 at 2:08 PM, Austin English <austinenglish@xxxxxxxxx> wrote: > On Mon, Aug 11, 2008 at 1:03 PM, jorl17 <wineforum-user@xxxxxxxxxx> wrote: >> >> Zachary Goldberg wrote: >>> On Mon, Aug 11, 2008 at 1:28 PM, vitamin <wineforum-user@xxxxxxxxxx> wrote: >>> >>> > >>> > Zachary Goldberg wrote: >>> > >>> > > On 8/11/08, Austin English <austinenglish@xxxxxxxxx> wrote: >>> > > >>> > > >>> > > > On Sun, Aug 10, 2008 at 9:46 AM, D3RGPS31 <wineforum-user@xxxxxxxxxx> wrote: >>> > > > >>> > > > >>> > > > > Because, I'm not on windows, I'm on Linux using Wine, as you should know, Linux filenames are case-sensitive... Windows are not. As you look at my example, you'll see files, with the same names, different cases, being used. How is it decided which file will be used when the plugin for the application calls TX_SKIN? >>> > > > > >>> > > > >>> > > > Right, but since you're using a windows application, you shouldn't >>> > > > have files with similar names (only different in casing). How did that >>> > > > occur? Different versions of the file, etc.? >>> > > > >>> > > >>> > > >>> > > I think he installed a plugin or a patch of some sort which was meant >>> > > to overwrite the file and would have in windows but whoever provided >>> > > the module used different casing. >>> > > >>> > >>> > >>> > That should not happen and never does. >>> > >>> >>> >>> Why is that? It seems completely possible as described above and... >>> >> >> >> I'm guessing that you didn't try to go to windows and create two folders with the same name but with different cases. It won't work. >> >> that means you can never have those two plugins in the same directory. >> >> Windows allows to 'browse' and 'search' with case insensivity but it doesn't allow you to have two files with the same name, for the exact same reason. (Correct me if wrong, but I tested this a while ago)... >> >> >> >> >> >> > > Right. But here's most likely what happened: > > User installs game, comes with some file called TX_Skin. > > Installs mod/update that comes with a new file, called tx_SKIN. > > In windows, tx_SKIN would replace TX_Skin, but under wine, they can coexist. > > Now, when run under wine, it's ambiguous which is chosen. > > Right, which means we're back to my post on 8/10 about what the op should do in this scenario. Unless the op has further questions, I think this thread is closed.
