| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Problem solved |
In a message on Thursday 11-21-17 Ed Vance said to Holger Granholm:
GE Ed,
EV> I ain't meaning to nit pick but 11-16-17 was a Thursday, wasn't it?
YES it was, you're correct and the same error is on the top line of this
message. Nov. 21st 2017 was a Tuesday. Spooky!
I did now check everything I can set from the operating system, but
there's no way to tell the OS the weekday name, so I'll probably have to
reboot the machine to get at the BIOS settings.
As the Subject says the problem is now solved.
It wasn't in the BIOS, but in the head of the user. There is a variable
in the QWK-program named {at}DAY{at} that I had used in the replay string but
it gave the name of the day when I replied to the msg.
There's another variable, {at}MSGDATE{at} that I also use in that string, and
that one picks the date from the message in the QWK-packet.
Now, there's no day-of-week to pick from the QWK-packet so the program
picks that weekday from the system instead.
I have now experimented with various variants of the init string and
found that I simply have to abstain of the use of the weekday.
This message may still use one of the experimental strings, but from now
on, the weekday will disappear from all replies.
GN es CU AGN de Sam, OH0NC
aka Holger
..
-- MR/2 2.30
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)SEEN-BY: 20/228 154/10 201/0 111 121 420 203/0 124 221/0 1 6 360 229/426 SEEN-BY: 266/404 280/5003 320/219 423/81 460/58 633/0 267 280 281 410 412 SEEN-BY: 640/384 1384 712/620 848 770/1 2320/100 3634/24 @PATH: 20/228 201/111 0 203/0 221/1 0 640/1384 384 712/848 633/280 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.