Christian Costa wrote:
Eric Pouech wrote:
How is really DefineDosDevice called ? I'd like you to add a trace for
the parameters while entering DefineDosDevice and send it to me.
TIA
Here are the calls traces:
fixme:volume:DefineDosDeviceW 1, L"C:", L"D:\\"
fixme:volume:DefineDosDeviceW 1,
Eric Pouech wrote:
How is really DefineDosDevice called ? I'd like you to add a trace for
the parameters while entering DefineDosDevice and send it to me.
TIA
Here are the calls traces:
fixme:volume:DefineDosDeviceW 1, L"C:", L"D:\\"
fixme:volume:DefineDosDeviceW 1, L"D:", L"E:\\"
fixme:vol
How is really DefineDosDevice called ? I'd like you to add a trace for
the parameters while entering DefineDosDevice and send it to me.
TIA
--
Eric Pouech
Hi,
For those interesting in this issue here what happend to my drive
symlinks.
Btw, the app is none other that Myst.
Before launching Myst:
lrwxrwxrwx 1 titan titan 8 mai 1 2004 a:: -> /dev/fd0
lrwxrwxrwx 1 titan titan 5 sep 3 23:29 c: -> /wine/
lrwxr
Hi,
It seems there is something wrong with DosDefineDevice.
If we consider a drive declared as F: -> /mnt/win_e
Remapping the drive F: to G: with this function leads to F: -> G: with
G: non defined.
This makes, in my case, my app to break all my drives assignement.
It's seems the code lacks
