Can you zip up and e-mail me the renamed file? And include any other journal files with the same name. They're not supposed to be able to corrupt themselves. But if you have one that

I just closed APRSIS32, renamed my OSMTiles.mbtiles file, and restarted. Mapping fetching is working properly here. Robert Giuliano KB8RCO

There should be some OSM* trace logs available. Bring those up and enable them then pan around a bit and see what they may have to tell you. Also, can you e-mail your APRSIS32.XML file

Is internet access enabled?? When did you last fetch tiles from the non-OSM servers? The links change occasionally or may not be available anymore. Fred N7FMH

Responding here as requested. Running Verison 2020/05/01 21:21 of APRSIS32. Map configure set to original with the tile server of "tile.openstreetmap.org" it appears to be only loading tiles that were

So, I'll need more details on what tile set, what zooms, and what behavior you're seeing.  A callsign-SSID would also be helpful if you're accessing my (ldeffenb.dnsalias.net) tile server. Lynn (D)

I agree. I’m going to search for an older version of WINE. My old version worked well, and they replaced it with a mess, at least as far as USB to serial adapters are concerned. Software

Hi Rob, Digging deep into the mental memory banks, probably beyond what they contain (i.e., this is a guess!). I seem to recall the original Unix system console interface wasn't on a

I would argue their purpose was to ensure anything Linux 'sees' is mapped to WINE. Why does Linux have tty - okay I know this one! tty0 - tty63 ttyS0 - ttyS32 when only a few devices are

Hi Rob, It sounds like the Wine team is trying to be annoyance-for-annoyance compatible with Windows :(. I'm on Wine 1.8.6 on an old OpenSuSE LEAP 42.1 system, and the

I'll try a few more things and update the wiki - soon. Robert Giuliano KB8RCO

Thanks guys! I added both symbols and it appears that I am now receiving EQ information. AL M KF5SMH

As near as I can tell, there is something in the WINE setup that automatically (and "unchangeably") links every ttyS## device in /dev to a com## in the .wine folder. Linux (at least my XUbuntu) has

And when the details are determined, we can update the Wiki at: http://aprsisce.wikidot.com/doc:linux Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

Hi Rob, WINES’s handling of com ports flummoxed me. What used to be a simple symbolic link became something else indeed ver 2.8 and later. The people at Codeweavers tried to help, but they had

I completely lost track of all the emails lately. But then I appreciate all the work you and all the others contributing to APRS. Mike K6MFW

Upgraded 3 computers and ran them for 2 or 3 hours with no problems. One of them (KE6BB) will be on all night with wind advisory objects for the interstate 5 corridor north of Los Angeles, until

Just upgraded my setup. This includes latest XUbuntu (20.04) with WINE 5.0. Some features are new to me with the updated WINE version. APRSIS32 ran the normal update after clicking HELP. Other than

I just pushed the subject version to development.  Please let me know if you successfully upgrade to this and if it initially looks ok. The only change since the last Development release is a

s//Q is the proper symbol. I added that to my filter and haven't gotten flooded with BrandMeister but DO have quakes showing up. A quick test filer shows the following source of earthquake