wine users - Aug 2009 - App stupidly looking for drive T:

I'm mystified by this one.  I just installed an app in a
brand new ~/.wine directory and when I started it up for
the first time it wouldn't run.

There was an error on the command line saying that it was
unable to create T:\LOGFILES\ and was quitting.

Well, of course it couldn't because there was no drive T:
to write to.  I made a symlink for T: pointing to /tmp
and the app worked just fine after making /tmp/LOGFILES.

The next time I ran the app, it was happy using C:\LOGFILES
instead of T:\LOGFILES. :-/

Anyone have a clue why it wanted drive T: in the first place.
How does wine keep track internally of what letter to use for
each virtual drive?

Thanks!

No idea about why T, but from what I know the only information wine uses
concerning virtual devices are the symlinks in ~/.wine/dosdevices/ and the type
of the device in system.reg (HKEY_LOCAL_MACHINE\Software\Wine\Drives). At
runtime then the drives appear in
HKEY_LOCAL_MACHINE\System\MountedDevices
.