<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/02/2017 01:38, Alessandro Volpi
wrote:<br>
</div>
<blockquote
cite="mid:CA+dGRsneOki4CPM5+QO7F27RVODMzkM3mBWYc8fZYeQbH+JfHw@mail.gmail.com"
type="cite">
<div dir="ltr">
<table
class="gmail-m_-2506534758597483614moz-email-headers-table"
border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td><br>
</td>
</tr>
</tbody>
</table>
<br>
<div class="gmail_quote">
<div bgcolor="#FFFFFF">
<div
class="gmail-m_-2506534758597483614moz-forward-container">
<br>
-------- Forwarded Message --------
<table
class="gmail-m_-2506534758597483614moz-email-headers-table"
border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">Subject:
</th>
<td>Re: Fwd: importing smarttrak slg logs</td>
</tr>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">Date:
</th>
<td>Fri, 3 Feb 2017 23:15:55 +0000</td>
</tr>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">From:
</th>
<td>Alessandro Volpi <a moz-do-not-send="true"
class="gmail-m_-2506534758597483614moz-txt-link-rfc2396E"
href="mailto:alessandrovolpi@fastwebnet.it"
target="_blank"><alessandrovolpi@fastwebnet.<wbr>it></a></td>
</tr>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">To:
</th>
<td>Salvador Cuñat <a moz-do-not-send="true"
class="gmail-m_-2506534758597483614moz-txt-link-rfc2396E"
href="mailto:salvador.cunat@gmail.com"
target="_blank"><salvador.cunat@gmail.com></a></td>
</tr>
<tr>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">CC:
</th>
<td><br>
<br>
</td>
</tr>
</tbody>
</table>
<div class="gmail-m_-2506534758597483614moz-cite-prefix">Dear
Salvador,<br>
<br>
I have imported my (large) dive_log.slg file, relying on
smtk2ssrf_test.AppImage. The program did find data
formatting errors in several dives in the slg file, but,
surprisingly, such errors did not result in any visible
flaw in the imported data for the concerned dives. The
log of the import operation is attached, in case you are
curious to have a look at it.<br>
<br>
I have opened the imported xml file with the subsurface
version installed from the Fedora 24 repo.<br>
I was very impressed by the quality of the application
you are developing and maintaining ... I cannot find
good words for qualifying it, other than EXCELLENT !<br>
<br>
Al details of the dive, including gas switches during
sidemount dives, were perfectly imported. Before trying
subsurface I was planning to edit the notes of every
single dive in order to insert the data concerning fish
species spotted during the dive. I was very glad to
discover that also this information has been
automatically added to the dive's notes. Therefore the
log is perfectly good as it is and no manual editing
intervention is needed!<br>
<br>
Also the management of dive sites and their coordinates
is better than my more optimistic forecasts.<br>
<br>
I am very grateful to you for your prompt answer to my
messages concerning my difficulties in building
subsurface and smtk2ssrf on Fedora 24.<br>
<br>
I do not need to do that once again, since I have a
working instance of both programs. MoreoverI think I
will never have in the future any reason for importing
the dive_log. slg file: I am not going to keep on using
SmartTrack on my Windows XP virtual machine.
Unfortunately I cannot ditch it right now, since I
occasionally need to modify my dive computer settings
and it is easier to do that by means of SmartTrak,
instead of fiddling with the Galileo button driven menu.<br>
<br>
Since am am a curious man, I have anyway tried to build
the objects and the executables, after having created a
suitable symbolic link : ln -s /usr/lib64
/usr/lib/x86_64-linux-gnu .<br>
After having done so, I was guessing the the required
library should have been made available to build.sh .The
available libmdb shared objects were thus:<br>
<br>
ls -l /usr/lib/x86_64-linux-gnu/<wbr>libmdb*<br>
lrwxrwxrwx. 1 root root 15 2016-02-04_09:38:43
/usr/lib/x86_64-linux-gnu/<wbr>libmdb.so.2 ->
libmdb.so.2.0.1<br>
-rwxr-xr-x. 1 root root 87280 2016-02-04_09:38:49
/usr/lib/x86_64-linux-gnu/<wbr>libmdb.so.2.0.1<br>
lrwxrwxrwx. 1 root root 18 2016-02-04_09:38:44
/usr/lib/x86_64-linux-gnu/<wbr>libmdbsql.so.2 ->
libmdbsql.so.2.0.0<br>
-rwxr-xr-x. 1 root root 40096 2016-02-04_09:38:49
/usr/lib/x86_64-linux-gnu/<wbr>libmdbsql.so.2.0.0<br>
<br>
I created a ~/src/ folder in my home folder, since you
say that it is a bad idea to build subsurface as root.<br>
<br>
I then went through the build operation, but the
procedure failed once again, the script being unable to
find a suitable libmdb shared object.<br>
See the attached file build.log .<br>
<br>
In any case, as far as I am concerned, everything is now
OK with subsurface. The only problem is now that I am
not able to get a working the irda interface in Fedora
23.<br>
The module mcs7780.ko.xz is present on my system and is
loaded with modprobe. Nevertheless the irda interface is
not working on my system. I guess that one possible
explanation for that is the absence of any irda
configuration file in the system.<br>
<br>
It is obvious that my troubles with the irda interface
have nothing to do with your excellent software and that
I am not therefore asking for your help about that.<br>
<br>
In case I do not succeed in setting up the irda
interface in my desktop PC with Fedora 24 I am going to
try to do that in my Dell XPS 13 Developer Edition with
Ubuntu trusty.<br>
<br>
Thank you once again for your help and your development
activity.<br>
<br>
Best regards.<br>
<br>
Alessandro<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Dear Allessandro,<br>
<br>
The IrDA upload has been working flawlessly on by Ubuntu box since I
started using Subsurface. I cannot see that this can be a
fundamental stumbling block, even on Fedora. But I have never done
this on Fedora myself. The basic procedure I followed is the one I
documented in the Subsurface user manual: download (from Linux-IrDA
project) and install the driver, then execute an irattach
instruction AS ROOT (i.e. using sudo) before starting Subsurface.
Only snag with the Galileo is it downloads the full memory of the
dive computer every time, even if only the last dive is needed.
Fortunately Subsurface knows which dives have been downloaded
previously and only shows the new dives for download.<br>
<br>
Salvador is working hard on the AppImage for smtk2ssrf that can
execute on a wider range of Linux flavours.<br>
<br>
Kind regards,<br>
willem<br>
<br>
<br>
</body>
</html>