wine users - Aug 2008 - ElderScrolls - case-sensitivity, many of the same file

hypothetically, i have 2 different textures, one names TX_Skin, another named
tx_skin. a plugin calls TX_SKIN, which texture does it choose?

D3RGPS31 wrote:
> Hypothetically, I have 2 different textures, TX_Skin, & tx_skin.
You shouldn't have those two if you were using Wine to
install/create/download those files.


D3RGPS31 wrote:
> A plugin calls TX_SKIN to be applied to an ojbect, which texture does it
use?
Not defined. It can be one of the other depending on which one was returned from
the file system listing first.

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?

Zachary Goldberg wrote:
> On 8/11/08, Austin English <austinenglish at gmail.com> wrote:
> 
> > On Sun, Aug 10, 2008 at 9:46 AM, D3RGPS31 <wineforum-user at
winehq.org> 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.

I'm sure what he did is extracted files on Linux. In that case there is not
much Wine can do about it.

Zachary Goldberg wrote:
> On Mon, Aug 11, 2008 at 1:28 PM, vitamin <wineforum-user at
winehq.org> wrote:
> 
> > 
> > Zachary Goldberg wrote:
> > 
> > > On 8/11/08, Austin English <austinenglish at gmail.com>
wrote:
> > > 
> > > 
> > > > On Sun, Aug 10, 2008 at 9:46 AM, D3RGPS31 <wineforum-user
at winehq.org> 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)...

austin987 wrote:
> 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.
Wrong that should never happen on Wine. And never does. _IF_ everything was done
_UNDER_ Wine. If user created second file (with different case) with system Wine
has no control over that.

Zachary Goldberg wrote:
> On Mon, Aug 11, 2008 at 2:18 PM, vitamin <wineforum-user at
winehq.org> wrote:
> 
> > 
> > austin987 wrote:
> > 
> > > 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.
> > > 
> > 
> > Wrong that should never happen on Wine. And never does. _IF_
everything was done _UNDER_ Wine. If user created second file (with different
case) with system Wine has no control over that.
> > 
> > 
> 
> You don't explain why what you say is true; thus I am unconvinced.

Of course you can always read the source code yourself... if you don't trust
developers.