http://bugs.winehq.org/show_bug.cgi?id=22428
--- Comment #4 from Andrew Nguyen arethusa26@gmail.com 2010-04-19 20:17:14 --- A difference I noticed between the bad log and the good logs is that the bad log has the installer executable's path as "I:\Installer.exe" whereas the good CD log has "Z:\mnt\wisotool\Installer.exe" and the good disk log has "Z:\home\dank\wow\Installer.exe" for the respective executable locations.
In the case of the failure situation, what caught my eye was what GetVolumeInformation does when given I:\ for the path:
0019:Call KERNEL32.GetVolumeInformationW(0033f440 L"I:\",0033f498,00000104,00000000,00000000,00000000,00000000,00000000) ret=004a32ab trace:file:CreateFileW L"\\.\I:" GENERIC_READ FILE_SHARE_READ FILE_SHARE_WRITE creation 3 attributes 0x0 ... trace:file:CreateFileW returning 0x78 trace:file:DeviceIoControl (0x78,24000,(nil),0,0x33e7d2,804,0x33eb08,(nil)) fixme:ntdll:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0) ... 0019:Ret KERNEL32.GetVolumeInformationW() retval=00000001 ret=004a32ab
My guess is that the installer might be acting differently given the information from GetVolumeInformation for I:\ and the fact that the installer resides on I:. Figuring out what GetVolumeInformation is reporting exactly might yield some insight.