Hi Rob.
Some questions about Sync's QWK.
I have the date system set to use DD-MM-AA mode, 24 hour format and
GMT-3 time zone (Rio de Janeiro).
When downloading a QWK package, the file always comes with more 3
hour time attribute - if is 10:00 local time the file come with
13:00 - and all messages show the date in MM-DD-AA mode. There is
no point in adjusting settings in Bluewave or Sync. It always
indicates the same way. The same at Multimail.
It is not a real problem, but if possible I would like to correct
it. :-)
TIA
Quoting Mortifis to Mauro Veiga at 06-24-20 07:43 <=-
Hi Rob.
Some questions about Sync's QWK.
I have the date system set to use DD-MM-AA mode, 24 hour format and
GMT-3 time zone (Rio de Janeiro).
When downloading a QWK package, the file always comes with more 3
hour time attribute - if is 10:00 local time the file come with
13:00 - and all messages show the date in MM-DD-AA mode. There is
no point in adjusting settings in Bluewave or Sync. It always
indicates the same way. The same at Multimail.
It is not a real problem, but if possible I would like to correct
it. :-)
TIA
AFAIK, the timestamp is set by the QWK hub, in this case
vert.synchro.net Pacific Time ( GMT -7 ) ...
AFAIK, the timestamp is set by the QWK hub, in this case
vert.synchro.net Pacific Time ( GMT -7 ) ...
No problem with Sync's QWK network.
I refer to my system's QWK Offline Mail Reader.
Quoting Rampage to Mauro Veiga at 06-25-20 19:16 <=-
Re: QWK questions
By: Mauro Veiga to MORTIFIS on Thu Jun 25 2020 17:06:00
AFAIK, the timestamp is set by the QWK hub, in this case
vert.synchro.net Pacific Time ( GMT -7 ) ...
No problem with Sync's QWK network.
I refer to my system's QWK Offline Mail Reader.
QWK offline mail readers do not have the smarts to display the message dates in local time... they display whatever is in the message packet
they get from the bbs...
Quoting Rampage to Mauro Veiga at 06-25-20 19:16 <=-
Re: QWK questions
By: Mauro Veiga to MORTIFIS on Thu Jun 25 2020 17:06:00
AFAIK, the timestamp is set by the QWK hub, in this case vert.synchro.net Pacific Time ( GMT -7 ) ...
No problem with Sync's QWK network.
I refer to my system's QWK Offline Mail Reader.
QWK offline mail readers do not have the smarts to display the message dates in local time... they display whatever is in the message packet they get from the bbs...
This is exactly the problem. My system provides me with a QWK
package with + 3 hours from my local time (GMT-3) *and* messages in
the package with MM-DD-AA format, instead DD-MM-YY like i configured
on SCFG. Two diferent problems.
I tried to change time zone and date mode on SCFG but no effects on
QWK packages and messages.
Quoting Mortifis to Mauro Veiga at 06-26-20 22:44 <=-
Quoting Rampage to Mauro Veiga at 06-25-20 19:16 <=-
Re: QWK questions
By: Mauro Veiga to MORTIFIS on Thu Jun 25 2020 17:06:00
AFAIK, the timestamp is set by the QWK hub, in this case vert.synchro.net Pacific Time ( GMT -7 ) ...
No problem with Sync's QWK network.
I refer to my system's QWK Offline Mail Reader.
QWK offline mail readers do not have the smarts to display the message dates in local time... they display whatever is in the message packet they get from the bbs...
This is exactly the problem. My system provides me with a QWK
package with + 3 hours from my local time (GMT-3) *and* messages in
the package with MM-DD-AA format, instead DD-MM-YY like i configured
on SCFG. Two diferent problems.
I tried to change time zone and date mode on SCFG but no effects on
QWK packages and messages.
did you make sure both bluewave and scfg to use the same date format?
Quoting Rampage to Mauro Veiga at 06-25-20 19:16 <=-
Re: QWK questions
By: Mauro Veiga to MORTIFIS on Thu Jun 25 2020 17:06:00
AFAIK, the timestamp is set by the QWK hub, in this case vert.synchro.net Pacific Time ( GMT -7 ) ...
No problem with Sync's QWK network.
I refer to my system's QWK Offline Mail Reader.
QWK offline mail readers do not have the smarts to display the message dates in local time... they display whatever is in the message packet they get from the bbs...
This is exactly the problem. My system provides me with a QWK
package with + 3 hours from my local time (GMT-3) *and* messages in
the package with MM-DD-AA format, instead DD-MM-YY like i configured
on SCFG. Two diferent problems.
I tried to change time zone and date mode on SCFG but no effects on
QWK packages and messages.
Hi Rob.
Some questions about Sync's QWK.
I have the date system set to use DD-MM-AA mode, 24 hour format and
GMT-3 time zone (Rio de Janeiro).
When downloading a QWK package, the file always comes with more 3
hour time attribute - if is 10:00 local time the file come with
13:00 - and all messages show the date in MM-DD-AA mode. There is
no point in adjusting settings in Bluewave or Sync. It always
indicates the same way. The same at Multimail.
It is not a real problem, but if possible I would like to correct
it. :-)
Quoting Digital Man to Mauro Veiga at 07-01-20 10:28 <=-
The "date mode" in SCFG will have no affect on created QWK packets.
The time zone only affects locally-created messages at that time - it
has no affected on previously-posted messages or messages imported
from networks.
digital man
Quoting Digital Man to Mauro Veiga at 07-01-20 10:24 <=-
The QWK format does not allow for different date/time formats. It's up
to your offline reader to parse and re-display the date/time in the
format you like, if the reader has that feature.
The QWK format does not allow for different date/time formats. It's up
to your offline reader to parse and re-display the date/time in the
format you like, if the reader has that feature.
Quoting Daryl Stout to Digital Man at 07-01-20 20:27 <=-
Rob,
The QWK format does not allow for different date/time formats. It's up
to your offline reader to parse and re-display the date/time in the
format you like, if the reader has that feature.
I noted when using SyncTerm (which I prefer) the QWK Mail Packet is
in the time zone of the BBS you get it from. However, if you use MTel, it's in UTC Time on the QWK Packet.
I noted when using SyncTerm (which I prefer) the QWK Mail Packet is
in the time zone of the BBS you get it from. However, if you use MTel, it's in UTC Time on the QWK Packet.
Yes! That is!
I'm using MTelnet. I tryed Netrunner and works fine with correct
date stamp. :-))
Quoting Daryl Stout to Mauro Veiga at 07-03-20 09:35 <=-
Mauro,
I noted when using SyncTerm (which I prefer) the QWK Mail Packet is
in the time zone of the BBS you get it from. However, if you use MTel, it's in UTC Time on the QWK Packet.
Yes! That is!
I'm using MTelnet. I tryed Netrunner and works fine with correct
date stamp. :-))
I haven't tried NetRunner, but it's included with the Telnet BBS
Guide monthly file, done by David Perussel.
I use MTel on the local console to do a quick check of things in
local mode, as at times, the hight speed internet here has been
erratic. But, there have been numerous thunderstorms to deal with,
as Arkansas is in a very unsettled weather pattern right now. More
are forecast right through at least the middle of next week.
Otherwise, I use SyncTerm for the telnet client, since it will
enter my user name, password, and the BBS Sysop Password for me automatically. Macros are great...except for when you forget that
you're not at the host console. :P
Years ago, I was visiting my girlfriends house (she eventually
became my wife, but I lost her to a heart attack 3 weeks shy of
our 4th wedding anniversary over 13 years ago)...and my BBS was
at my parents home (I'm back here now...both of them are dead
and gone). Well, at the host console, I hit a macro for the
dial-up BBS to log me in...but, I forgot I was elsewhere when I
did that (I was at my future wife's apartment). I hit the macro,
and when nothing happened, it hit me...
"You're not at the host console. You don't know your password,
and can't logon to your own BBS, you dumb $*!+" <G>
I felt like a fool. :P
I felt like a fool. :P
These things happens.
I use macros. MTelnet has this using Alt-L. I like MTelnet
because
it's simple and have nice visual.
When need SSH i use ZOC. It's another powerfull terminal program.
Syncterm is good but don't run on some machines here.
Quoting Daryl Stout to Mauro Veiga at 07-04-20 19:59 <=-
Syncterm is good but don't run on some machines here.
I'm running it under Windows 10 64-bit. The other day, it installed
a new version of Microsoft Edge, and it royally corrupted Firefox. I
had to uninstall and reinstall Firefox for my web surfing. I also use
the DuckDuckGo search engine for privacy.
I hate Windows 10. Not the system, but the interface. I prefer
Windows 7. At the moment, using a old Toshiba laptop with Windows
XP. And W7 x64 on the main machine. I like WinXP to run DOS
programs.
Mauro,
I hate Windows 10. Not the system, but the interface. I prefer
Windows 7. At the moment, using a old Toshiba laptop with Windows
XP. And W7 x64 on the main machine. I like WinXP to run DOS
programs.
IObit utilities (www.iobit.com) has Start Menu 8, which will, if
you choose, CHANGE that Windows 10 Start Up menu to the Windows 7
or 8 style instead...which is what I've done. I think a one year
license for 3 PC's, is $8 in US funds.
IObit utilities (www.iobit.com) has Start Menu 8, which will, if
you choose, CHANGE that Windows 10 Start Up menu to the Windows 7
or 8 style instead...which is what I've done. I think a one year
license for 3 PC's, is $8 in US funds.
You should take a look at Classic Shell which is a Windows-7-like shell/start menu that is free: http://classicshell.net/downloads.
Works *really* well.
... Have you hugged an electric fence today?
Quoting Daryl Stout to Mauro Veiga at 07-06-20 14:55 <=-
...
I use most all of the IObit products, as does my FIDONet Hub, and
we're both very pleased with them.
Quoting Digital Man to Mauro Veiga at 07-01-20 10:24 <=-
The QWK format does not allow for different date/time formats. It's up to your offline reader to parse and re-display the date/time in the format you like, if the reader has that feature.
ÉÍÍ 1 Jul 20 ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ 17:36 º Preferences Global Archivers External Directories Registration Qui ÌÍÍÍÍÍÍÍÍÍÍÍÍÍÍ?ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ?ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ º±±±±±±±±±±±±±±³ Global Reader Settings ³±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±± º±±±±±±±±±±±±±±³ ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿±±±±±±±±±±±±±±±± º±±±±±±±±±±±±±±³ ³ On-Screen Date/Time Yes ³±±±±±±±±±±±±±±±± º±±±±±±±±±±±±±±³ ³ On-Screen Date Format DD Mmm YY ³±±±±±±±±±±±±±±±± º±±±±±±±±±±±±±±³ ³ On-Screen Time Format 24:mm ³±±±±±±±±±±±±±±±±
It has but ineffective.
On BW package format work fine.
Quoting Digital Man to Mauro Veiga at 07-01-20 10:28 <=-
The "date mode" in SCFG will have no affect on created QWK packets.
The time zone only affects locally-created messages at that time - it has no affected on previously-posted messages or messages imported
from networks.
digital man
The messages don't be affected by time zone.
Only date stamp of QWK packet.
Syncterm is good but don't run on some machines here.
I use most all of the IObit products, as does my FIDONet Hub, and
we're both very pleased with them.
Good hint. Thanks. :-)
... DOS=HIGH? I knew it was on something...
Quoting Daryl Stout to Mauro Veiga at 07-07-20 22:25 <=-
... DOS=HIGH? I knew it was on something...
I think Windows is a stronger drug. <G>
Quoting Digital Man to Mauro Veiga at 07-07-20 15:44 <=-
Re: QWK questions
By: Mauro Veiga to DIGITAL MAN on Wed Jul 01 2020 06:06 pm
Quoting Digital Man to Mauro Veiga at 07-01-20 10:28 <=-
The "date mode" in SCFG will have no affect on created QWK packets.
The time zone only affects locally-created messages at that time - it has no affected on previously-posted messages or messages imported
from networks.
digital man
The messages don't be affected by time zone.
Only date stamp of QWK packet.
Which time zone? The time zone of the message author is not contained
in the original/legacy QWK message header. Synchronet has extensions
which include the timezone of the original message posting, but the
QWK mail reader would have to support that/those extensions: http://wiki.synchro.net/ref:qwk
digital man
Quoting Digital Man to Mauro Veiga at 07-07-20 15:42 <=-
It has but ineffective.
On BW package format work fine.
That's a feature of your QWK mail reader, not the packet format. And likewise, if it's not working, then it's a problem with the QWK mail reader. Which one is that? Maybe file a bug report with the author? digital man
Quoting Digital Man to Mauro Veiga at 07-07-20 15:54 <=-
Re: QWK questions
By: Mauro Veiga to DARYL STOUT on Sat Jul 04 2020 10:51 am
Syncterm is good but don't run on some machines here.
Syncterm is good but don't run on some machines here.
SyncTERM should run on a lot more machines (OSes and architectures) than mTelnet!
I noted when using SyncTerm (which I prefer) the QWK Mail Packet is
in the time zone of the BBS you get it from. However, if you use MTel, it's in UTC Time on the QWK Packet.
Yes! That is!
I'm using MTelnet. I tryed Netrunner and works fine with correct
date stamp. :-))
I hate Windows 10. Not the system, but the interface. I prefer
Windows 7. At the moment, using a old Toshiba laptop with Windows
XP. And W7 x64 on the main machine. I like WinXP to run DOS
programs.
Quoting Daryl Stout to Mauro Veiga at 08-22-20 20:42 <=-
I noted when using SyncTerm (which I prefer) the QWK Mail Packet is
in the time zone of the BBS you get it from. However, if you use MTel, it's in UTC Time on the QWK Packet.
Yes! That is!
I'm using MTelnet. I tryed Netrunner and works fine with correct
date stamp. :-))
The ANSI displays better with SyncTerm, IMO. Plus, it enters the
Sysop password, if required. MTel doesn't have that option.
Yes, i'm using Syncterm now.
Only on laptop with winXP i still need MTelnet.
Quoting Daryl Stout to Mauro Veiga at 09-10-20 12:20 <=-
Yes, i'm using Syncterm now.
Only on laptop with winXP i still need MTelnet.
The other thing with MTel compared to Synchronet is that the
time in the QWK Packets is in UTC Time with MTel, but prevailing
local or the BBS System Time with SyncTerm.
Plus, I think the ANSI animation is better with SyncTerm.
| Sysop: | Chris Crash |
|---|---|
| Location: | Huntington Beach, CA. |
| Users: | 611 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 57:16:23 |
| Calls: | 10,849 |
| Files: | 5 |
| Messages: | 504,411 |