No similar topics found.
+3
Mailheader in RMSexpress
Regarding to the new message precedence categories: When an email with a higher priority than the R/ flag will be received, the email header in RMS-express should be highlighted in i.e. red. Or in an invdividual color, depending from the flag.
73 de OE7FTJ
73 de OE7FTJ
+3
Add RMS Express P2P option using local WLAN like UBIQUITI BULLET M2HP
Using the B2F compressed type of telnet through such a "wlan" can speed up intercommunication delivery between clients which needs most of their time transmitting longer haul pactor, winmor or even packet.
73 Finn/LA7UM
73 Finn/LA7UM
+3
Time stamp RMS Express 00:00
I find that date is ok when RX, but that the clock time is always set as 00:00
Why is that? Seems like a bug.
Why is that? Seems like a bug.
+3
Under review
RMS HF Station Channel Status
I note that the information summary for January 2011 no longer includes the quantity / number of bytes received / forwarded.
Would like to see this information replaced for January, and maintained in future.
Is this just a temporary glitch?
Would like to see this information replaced for January, and maintained in future.
Is this just a temporary glitch?
Answer
Winlink Moderator
14 years ago
The status report pages are being revamped to allow for display of WINMOR channel data. Throughput byte count type data may not return. You can use your station logs. They have similar information.
+2
Allow for a quick and easy way to back out from an RMSE upgrade
The auto update works really well, and the ability to approve an upgrade is the cat's meow. Thanks!
But no matter how well an upgrade it tested, there is always the potential that some unintended bug will be introduced that can knock a station right off the air. Making that station stay off the air until a fix is found, coded, tested, and pushed out does not seem right. Plus, there is the potential that the station might be needed right away.
Some ground rules to address WDT concerns: the back out would only be available to stations that are on the very latest release, and can only be backed out to the immediately previous release. As before, no support for stations running anything but the latest release.
But no matter how well an upgrade it tested, there is always the potential that some unintended bug will be introduced that can knock a station right off the air. Making that station stay off the air until a fix is found, coded, tested, and pushed out does not seem right. Plus, there is the potential that the station might be needed right away.
Some ground rules to address WDT concerns: the back out would only be available to stations that are on the very latest release, and can only be backed out to the immediately previous release. As before, no support for stations running anything but the latest release.
+2
Mke propagation updating a background process
Please consider making the propagation index update a background process and putting a date/time of last update on the channel selection screen.
+2
Add Date and Time to Website info
Add date and maybe time to information (posts, etc.) on the website. Then a reader would know how old the information is.
Bob, WB8ILI
Bob, WB8ILI
+2
Send history files to Sysops
I would strongly recommend to add a history file to each software update with a short description of changes in format, function, bugfixes etc.
This is good practice in software development and would help the sysop and clients to properly test the software and be aware of changes and bugs.
+2
RMS Trimode: please add TRX control via PTC-2
Especially for sysops who use Bluetooth connection to the modem (better RF isolation) the CAT control of the transceiver direct via PTC or Dragon is needed. It should not be a major problem to add this - the TRX CAT can be accessed via a dedicated hostmode channel. The commandset is the same as via a second comport. (transfer command)
Customer support service by UserEcho