http://bugs.winehq.org/show_bug.cgi?id=6172
--- Comment #12 from Luke Bratch <l_bratch(a)yahoo.co.uk> 2008-01-10 04:48:23 ---
Alejandro, please post in Bugzilla, don't reply to wine-bugs. Email read:
"Thank you for this info. Currently there is a problem with the cable
conectivity here. I will download it when the ISP repairs it."
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=3894
--- Comment #3 from Luke Bratch <l_bratch(a)yahoo.co.uk> 2008-01-10 04:47:17 ---
Stefano, please post in Bugzilla, don't reply to wine-bugs. Email read:
"I am still running the 0.9.2 version of wine.
As of nobody contacted me to solve the problem, I have been abandoning=20
my attempts.
R14 has any ugly DLLs; maybe any previous version run but would have=20
some graphic card CRASH problem.
Stefano"
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #34 from Hans Leidekker <hans(a)it.vu.nl> 2008-01-10 03:40:16 ---
Created an attachment (id=10148)
--> (http://bugs.winehq.org/attachment.cgi?id=10148)
Return DRIVE_REMOVABLE for D: drive.
> 0034:Call KERNEL32.GetDriveTypeW(0034f154 L"D:")
> 0034:Ret KERNEL32.GetDriveTypeW() retval=00000001
00000001 == DRIVE_NO_ROOT_DIR which means that Wine is unable to
retrieve the drive type. My hypothesis is that TomTom HOME is looking
for a DRIVE_REMOVABLE type device which the attached hack should
confirm. Can you try it?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6179
Dustin Steiner <dustin.steiner(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
--- Comment #4 from Dustin Steiner <dustin.steiner(a)gmail.com> 2008-01-10 03:29:49 ---
(In reply to comment #3)
> Is this still an issue in current (0.9.52 or newer) wine?
>
The problem is fixed - i use wine 0.9.49
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6711
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #9 from Austin English <austinenglish(a)gmail.com> 2008-01-10 02:23:05 ---
Closing fixed.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6711
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Component|_obsolete_directx |-unknown
Resolution| |FIXED
--- Comment #8 from Austin English <austinenglish(a)gmail.com> 2008-01-10 02:22:51 ---
Reported fixed. Reopen if that's not the case.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6727
Jeff Zaroyko <jeffzaroyko(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeffzaroyko(a)gmail.com
--- Comment #5 from Jeff Zaroyko <jeffzaroyko(a)gmail.com> 2008-01-10 01:46:19 ---
betolley,
is this still an issue with the latest version of wine (0.9.52)?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6711
Jeff Zaroyko <jeffzaroyko(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeffzaroyko(a)gmail.com
--- Comment #7 from Jeff Zaroyko <jeffzaroyko(a)gmail.com> 2008-01-10 01:45:16 ---
wine-0.9.52, Ubuntu 7.10, nVidia FX 5200
had to install wmfredist.exe (WMP9) distributed with the demo before it would
run
the animations in the background of the main menu appear to work fine, this
looks fixed.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #33 from Alexander K. Seewald <alex(a)seewald.at> 2008-01-10 01:41:04 ---
Hans, it is exactly as you found. Once the device is plugged in when TomTom
Home is running, it regularily tries to find it, but fails. The new drive (D:)
now appears in Winefile when I plug the TomTom in even without the dosdevices
link, thus it works so far.
At the beginning, it enumerates all volumes. Again GetDriveTypeW seems to be
important. Here the TomTom does not seem to be plugged in.
0034:Call user32.SetWindowsHookExW(00000004,0189c1b0,00000000,00000034)
ret=0189d233
0034:Ret user32.SetWindowsHookExW() retval=00020056 ret=0189d233
0034:Call KERNEL32.FindFirstVolumeW(0034e8ec,00000104) ret=0189c7bc
0034:Ret KERNEL32.FindFirstVolumeW() retval=001744a0 ret=0189c7bc
0034:Call KERNEL32.GetDriveTypeW(0034e8ec
L"\\\\?\\Volume{00000000-0000-0000-0000-000000000043}\\") ret=0189c7db
0034:Ret KERNEL32.GetDriveTypeW() retval=00000000 ret=0189c7db
0034:Call KERNEL32.FindNextVolumeW(001744a0,0034e8ec,00000104) ret=0189c941
0034:Ret KERNEL32.FindNextVolumeW() retval=00000001 ret=0189c941
0034:Call KERNEL32.GetDriveTypeW(0034e8ec
L"\\\\?\\Volume{00000000-0000-0000-0000-00000000005a}\\") ret=0189c7db
0034:Ret KERNEL32.GetDriveTypeW() retval=00000000 ret=0189c7db
0034:Call KERNEL32.FindNextVolumeW(001744a0,0034e8ec,00000104) ret=0189c941
0034:Ret KERNEL32.FindNextVolumeW() retval=00000000 ret=0189c941
0034:Call KERNEL32.FindVolumeClose(001744a0) ret=0189c954
0034:Ret KERNEL32.FindVolumeClose() retval=00000001 ret=0189c954
0034:Call KERNEL32.GetLastError() ret=018bac8b
0034:Ret KERNEL32.GetLastError() retval=00000012 ret=018bac8b
After this, it focusses on specifically checking drive D:, which is the TomTom
device's mount point in Wine.
0034:Call hook proc 0x189c1b0
(id=WH_CALLWNDPROC,code=0,wp=00000000,lp=0034f5fc)
0034:Call KERNEL32.GetDriveTypeW(0034f154 L"D:") ret=018998f9
0034:Ret KERNEL32.GetDriveTypeW() retval=00000001 ret=018998f9
0034:Call KERNEL32.FindFirstVolumeW(0034ee50,00000104) ret=0189c7bc
0034:Ret KERNEL32.FindFirstVolumeW() retval=001860e8 ret=0189c7bc
0034:Call KERNEL32.GetDriveTypeW(0034ee50
L"\\\\?\\Volume{00000000-0000-0000-0000-000000000043}\\") ret=0189c7db
0034:Ret KERNEL32.GetDriveTypeW() retval=00000000 ret=0189c7db
0034:Call KERNEL32.FindNextVolumeW(001860e8,0034ee50,00000104) ret=0189c941
0034:Ret KERNEL32.FindNextVolumeW() retval=00000001 ret=0189c941
0034:Call KERNEL32.GetDriveTypeW(0034ee50
L"\\\\?\\Volume{00000000-0000-0000-0000-00000000005a}\\") ret=0189c7db
0034:Ret KERNEL32.GetDriveTypeW() retval=00000000 ret=0189c7db
0034:Call KERNEL32.FindNextVolumeW(001860e8,0034ee50,00000104) ret=0189c941
0034:Ret KERNEL32.FindNextVolumeW() retval=00000000 ret=0189c941
0034:Call KERNEL32.FindVolumeClose(001860e8) ret=0189c954
0034:Ret KERNEL32.FindVolumeClose() retval=00000001 ret=0189c954
0034:Call user32.CallNextHookEx(00000000,00000000,00000000,0034f5fc)
ret=0189c348
0034:Call hook proc 0x86abd8 (id=WH_CALLWNDPROC,code=0,wp=00000000,lp=0034f5fc)
Not sure what GetDriveTypeW is supposed to do, but the retval for D: is clearly
different from the one for the two other internal drives... so why doesn't it
work yet? Both the type and the fact that it is a new drive should be
sufficient for identifying the TomTom. The full +relay trace is at
http://alex.seewald.at/files/log.relay.new.gz, perhaps it helps.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.