beyond the map tiles, the only 2 files APRSIS32 uses are the execuatable (APRSIS32.exe) and XML (APRSIS32.XML). There is a "safe file" backup of the xml (APRSIS32-safe.XML), but in theory, it isn't used (unless something is missed up in the working file).
The G and I filter functionality is still experimental. Because a bad configuration could have a major impact on the RF channel load, the setting are not saved between starts.
One reason is to ensure if you close APRSIS32 to quickly to stop an RF flood, it doesn't automatically re-flood when you start it.
Another reason is that there is still some experimentation and discussion on ways to ensure this feature doesn't flood the RF channel. Right now it is up to the user to ensure their settings are "RF friendly".
Lynn's implementation of filters is a bit more capable than the standard, server side filters. This includes additive filters for more control. I am not an expert, but specific questions can get great results as many people on the list are much better with them.
From: "iulianpt@... [aprsisce]" To: aprsisce@...
Sent: Sunday, June 24, 2018 11:06 AM
Subject: [aprsisce] Filters. IS/RF RF/IS on various ports.
Hi. I have to admit I haven't read the APRSIS32 manual page by page; headlines plus few paragraphs here and there. Work and family commitments in the last few years have taken a heavy toll on my free time.
1.) I am not very sure whether I understand the filtering in APRSIS32. I don't think I have a clear mental picture of some of the APRSIS32 functions or structure, something like a flow diagram (logic chart).
2.) RF to IS, IS to RF on an RF port versus the APRSIS port.
73, Julian, YO3FCA MØIPU