Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Dec 2012 10:22:17 +0100
From:      Matthias Apitz <guru@unixarea.de>
To:        freebsd-emulation@freebsd.org, David Naylor <naylor.b.david@gmail.com>
Subject:   Wine: Sony Reader for PC software in wine
Message-ID:  <20121225092217.GA2710@tinyCurrent>

next in thread | raw e-mail | index | archive | help

Hello FreeBSD wine guru's,

I owned an ebook reader Sony PRS-T1 which can be connected via USB to a
Windows, Mac or UNIX PC to transfer files (epub, PDF, ...) or other
purpose. On connect via USB it offers a FAT and a FAT32 file system,
which can be mounted in Linux or FreeBSD fine. One seems to be
containing firmware (it appears in Windows as K:(SETTINGS)), while the
other (F:(READER)) contains the media files. The device itself runs
some kind of Linux, perhaps an Android and it is possible to root it
(not yet done by me).

Sony delivers for free some software for Win and MAC, the so called
"Sony Reader for PC", which allows:
- import of DRM'ed epub files
- use (i.e. human read) the files with your Adobe account ID
- authorise the T1 against the Adobe servers with your ID
- transfer DRM'ed files to the T1 to be read there

The software installs fine with wine 1.5.4 and it starts fine with:

$ 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

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

	matthias
-- 
Matthias Apitz               |  /"\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: guru@unixarea.de     |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211       |  / \ - Respect for open standards



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121225092217.GA2710>