WineHQ Bugzilla – Bug 13407 – The Bat! Voyager fails to accept the master password

Bugzilla

Last modified: 2014-01-03 13:10:24 UTC

The Bat! Voyager fails to accept the master password

Bug 13407 - The Bat! Voyager fails to accept the master password


Summary:	The Bat! Voyager fails to accept the master password

Status:	CLOSED FIXED

AppDB:	Show Apps affected by this bug
Product:	Wine
Classification:	Unclassified
Component:	-unknown
Version:	1.0-rc2
Hardware:	x86-64 Linux

Importance:	P2 normal
Target Milestone:	---
Assigned To:	Mr. Bugs

URL:	http://www.ritlabs.com/en/products/th...
Keywords:	download

Depends on:
Blocks:
	Show dependency tree

Reported:	2008-05-24 19:16 UTC by Borut Maricic
Modified:	2014-01-03 13:10 UTC (History)
CC List:	3 users (show)

See Also:
Regression SHA1:
Fixed by SHA1:
Distribution:	---
Staged patchset:

Attachments
Add an attachment (back traces, logs, proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Borut Maricic 2008-05-24 19:16:58 UTC

Introduction:
I am trying to use The Bat! Voyager mail client (http://www.ritlabs.com/download/the_bat/voyager_install_4-0-18-4.exe) under Ubuntu 8.04 desktop via Wine 1.0-rc2. (Although my systemm is an AMD Athlon 64, my Linux is just plain Ubuntu 8.04 - not a 64bit version.) The problem I am describing here is a show stopper for me.

Background:
The Bat! mail client will, due to being developed in Delphi RDS, never be ported to Linux. For me it is, however, the only obstacle in a transition from Windows to Linux, due to the fact that there is no comparably robust and sophisticated e-mail client for Linux to be found (and my e-mail base is almost 1.5 GB in size).

Your testing problem:
One needs a valid user license for The Bat! Professional, in order to be able to activate and use Voyager. There is a small number of activations allowed and activations are bound to drive serial numbers.

Details:
Voyager does not use Registry - the idea is to have both the program, configuration and e-mail database on the same drive (for instance an USB-drive). I installed and activated Voyager under Windows XP Home SP2, on a "virtual drive" powered by TrueCrypt (http://www.truecrypt.org/). There is a Linux version of TrueCrypt and I can mount the same drive under Ubuntu.

The first thing Voyager asks for after being started is the mail database encryption password (="the master password"). When being started under Ubuntu via Wine, right before this dialog comes up, the following lines are being logged in the console window (there are only a few, so I am not making a separate attachment here)...

Console log:
fixme:reg:GetNativeSystemInfo (0x11579e1) using GetSystemInfo()
fixme:imagehlp:CheckSumMappedFile (0x1bc0000, 6544892, 0x11869fa, 0x11869fe): stub
fixme:system:SystemParametersInfoW Unimplemented action: 95 (SPI_GETSNAPTODEFBUTTON)

Whatever I enter, Voyager does not accept my input, reporting an unacceptable password being entered. The last logged line ("Unimplemented action: 95") is being repeated for every repeated try of a password entry.

Although Voyager tests internaly also for the drive serial number, I do not think this is the problem, since I defined an appropriate drive letter and attached a serial number to it in a Wine configuration.

Am I doing something wrong? Could I do some more testing; try something in a different way? Can you do anything? Thanks a lot!

Comment 1 Austin English 2008-11-24 16:08:09 UTC

Is this still an issue in current (1.1.9 or newer) wine?

Comment 2 Dominik Reichardt 2009-12-20 17:16:34 UTC

Finally, after Ritlabs abandoned the Themida protection, they released an alpha version of Voyager that finally starts again (issue #19158).
The master password I set on real Windows is accpeted on startup.
It has other issues, though. Mostly with the serial number of the drive it is installed to. As *I* can't seem to make Wine use the USB-Drive's real serial number, I have to reactivate Voyager again. But that will mess up using it on a real Windows machine, since then the real serial number doesn't match the one that got acivated under Wine. And you only have that many activations free before you have to contact Ritlabs support people again.

So, the actual bug seems to be fixed in current versions of Voyager, others remain :)
I'll ask on the forum for confirmation on how the detection of drive serial number works or doesn't work and will open a new bug.

Comment 3 Joerg Schiermeier 2011-06-11 21:44:48 UTC

Is this still an issue?
In the German 'The Bat!' forum (www.Batboard.net) I found similar error descriptions, but also a notice that this mistake didn't happen anymore.

Is this also your experience?
If so please close this bug. Otherwise please send new information about.

Comment 4 butraxz 2013-12-07 02:22:11 UTC

Link broken.

This ticket has not been updated for over 900 days. Development recommends
to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it.

Is this still an issue with 1.7.8 or higher ?

Comment 5 Anastasius Focht 2013-12-28 13:23:21 UTC

Hello folks,

reported working (comment #2), resolving 'fixed'.

Regards

Comment 6 Alexandre Julliard 2014-01-03 13:10:24 UTC

Closing bugs fixed in 1.7.10.