Hi, On Tuesday, 25 December 2012 11:22:17 Matthias Apitz wrote: > Hello FreeBSD wine guru's, > > The software installs fine with wine 1.5.4 and it starts fine with:
Could you try with a newer version of wine, wine up to 1.5.20 has been released. > $ wine Reader.exe > > One can connect fine to the Adobe ID server, import and read DRM'ed > epubs. What does not work is that the T1 on the USB devices is not seen. > > I have mounted the two USB devices as: > > /dev/da2 on /settings (msdosfs, local, read-only) > /dev/da0 on /reader (msdosfs, local) > > and configured wine (with winecfg) to see the devices as K: and F: which > works fine, for example, with the Explorer.exe; but the software > Reader.exe does not "see" the T1; it says on start: > > fixme:win:FlashWindowEx 0x33f228 > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections > will fail fixme:iphlpapi:NotifyAddrChange (Handle 0x79f6e0, overlapped > 0x100cf2a0): stub fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: > heap list snapshot fixme:toolhelp:Heap32ListFirst : stub > fixme:win:RegisterDeviceNotificationA (hwnd=0x700f8, > filter=0xb6ed48,flags=0x00000000) returns a fake device notification > handle! fixme:volume:GetVolumePathNameW (L"C:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"C:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"F:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"F:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"H:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"H:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"K:\\", 0x8628a8, 4), stub! > fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 > fixme:volume:GetVolumePathNameW (L"Z:\\", 0x8628a8, 4), stub! > fixme:volume:GetVolumePathNameW (L"Z:\\", 0x8628a8, 4), stub! > fixme:win:FlashWindowEx 0x33d450 The line fixme:mountmgr:harddisk_ioctl unsupported ioctl 4d004 suggests to me that wine does not implement some functionality that Reader.exe requires... > and in the GUI it says that the reader T1 is not connected. Perhaps > the software is reading somehow the USB bus directly and looking for the > vendorID and productID... > > How I could nail down, what it is missing? Thanks You could try appdb.winehq.org and see if the software is supported. The website may also suggest fixes for various issues. If there is no page for the software try filing a bug report, if there is a page then look through the bug reports to see if focus is given to fix it. It is possible that this is a FreeBSD specific problem, in which case submitting a bug report may be required. Lastly, look at documentation for the WINEDEBUG environment variable as that could provide more information as to the source of the error. Good luck. Regards,
signature.asc
Description: This is a digitally signed message part.
