ÿ@SUBJECT:Date and time please on this one?
N @MSGID: 1:114/201@fidonet.org 34764cee
@PID: GED+W32 1.1.5-b20070503
@CHRS: CP437 2
@TZUTC: -0700
I just upgraded to the latest GoldEd+ CVS snapshot (05/03/07). How
does the date/time look on this message please? Thanks.

It's adding a date of May 2008. :(

Looks fine. 11/18/2007 03:29 .


Jeff

--- PCBoard (R) v15.3/M 10
* Origin: (1:226/600)

Looks fine. 11/18/2007 03:29 .

Thanks, Jeff. Michael's not seeing the same thing though; I wonder if his QFront is "fixing" the date when it tosses the packets for other nodes?? Must be..

... "Captain! I sense millions of minds...staring at my cleavage!" - Troi

--- QScan/PCB v1.20a / 02-1000
* Origin: The BABBLE BBS * Tucson * babblebbs.no-ip.org * (1:114/201)

Looks fine. 11/18/2007 03:29 .

Thanks, Jeff. Michael's not seeing the same thing though; I wonder
if his QFront is "fixing" the date when it tosses the packets for
other nodes?? Must be..

Could be. I am using PCboard's internal tosser.


Jeff

--- PCBoard (R) v15.3/M 10
* Origin: (1:226/600)

ÿ@SUBJECT:Date and time please on this one? N
I just upgraded to the latest GoldEd+ CVS snapshot (05/03/07). How does the date/time look on this message please? Thanks.

It's adding a date of May 2008. :(


--- QScan/PCB v1.20a / 02-1000
* Origin: The BABBLE BBS * Tucson * babblebbs.no-ip.org * (1:114/201)

ÿ@SUBJECT:Date and time please on this one? N
Dane Beko wrote in a message to All:

I just upgraded to the latest GoldEd+ CVS snapshot (05/03/07). How
does the date/time look on this message please? Thanks.

It's adding a date of May 2008. :(

I don't know what you and others are seeing, but it looks fine here. I show the same thing Jeff Binkley wrote you.

Regards,

Roger
--- timEd/386 1.10.y2k+
* Origin: NCS BBS - Houma, LA - (985) 872-9448 (1:3828/7)

Looks fine. 11/18/2007 03:29 .

Thanks, Jeff. Michael's not seeing the same thing though; I wonder if his QFront is "fixing" the date when it tosses the packets for other nodes?? Must be..

... "Captain! I sense millions of minds...staring at my cleavage!" - Troi

--- QScan/PCB v1.20a / 02-1000
* Origin: The BABBLE BBS * Tucson * babblebbs.no-ip.org * (1:114/201)

ÿ@SUBJECT:Date and time please on this one? N

I don't know what you and others are seeing, but it looks fine here.
I show the same thing Jeff Binkley wrote you.

I think it's because my hub, Michael Luko, is fixing the date when he tosses mymessages for other nodes. I'm guessing anyway.

Michael: Do you have QFront setting the date/time to the current date/time whenyou toss messages? I looked at that setting in QFront but it's only for importing, not exporting. I wish it were for both. :(

... CP 2.00 #19 * ********** - ***** ****&h***m*** ** ***** ** h****

--- QScan/PCB v1.20a / 02-1000
* Origin: The BABBLE BBS * Tucson * babblebbs.no-ip.org * (1:114/201)

Looks fine. 11/18/2007 03:29 .

Thanks, Jeff. Michael's not seeing the same thing though; I wonder
if his QFront is "fixing" the date when it tosses the packets for
other nodes?? Must be..

Could be. I am using PCboard's internal tosser.


Jeff

--- PCBoard (R) v15.3/M 10
* Origin: (1:226/600)

ÿ@SUBJECT:Date and time please on this one? N

Michael: Do you have QFront setting the date/time to the current
date/time whenyou toss messages? I looked at that setting in QFront
but it's only for importing, not exporting. I wish it were for both.
:(

Nope. I looked at an outbound packet for another downlink and no date in
those packets. My uplink or some other system along the path must be
fixing the date.

--- QScan/PCB v1.20a / 01-0462
* Origin: Christian Fellowship | cfbbs.dtdns.net 856-933-7096 (1:266/512)

ÿ@SUBJECT:Date and time please on this one? N

Nope. I looked at an outbound packet for another downlink and no date
in those packets. My uplink or some other system along the path must
be fixing the date.

Thanks. While I don't like using broken software, if it's not affecting the traffic, may I continue using GoldEd+? I've seen messages with Origin: lines but no tearlines so the messages must still be getting passed along.

... CP 2.00 #19 þ Þ<iÞÜÞ_ iË..á䟧Rä iÒ SȼCÞ<s ÑÅÅä CØØR[]ÉË»ä OŸŸ!

--- QScan/PCB v1.20a / 02-1000
* Origin: The BABBLE BBS * Tucson * babblebbs.no-ip.org * (1:114/201)

ÿ@SUBJECT:Date and time please on this one? N

Nope. I looked at an outbound packet for another downlink and no date
in those packets. My uplink or some other system along the path must
be fixing the date.

Ben Ritchey sent me a batch file and the name of a binary to fix these packets,Michael. PKTFIX.EXE is the name of the file and it's already been installedand is working.

You shouldn't see any more munged headers from me now.

... CP 2.00 #19 þ ÜþßþÜ Coincidence, my !@#$^&*()_+! ÜþßþÜ

--- QScan/PCB v1.20a / 02-1000
* Origin: The BABBLE BBS * Tucson * babblebbs.no-ip.org * (1:114/201)

ÿ@SUBJECT:Date and time please on this one? N

You shouldn't see any more munged headers from me now.

This one has a date and valid time.

Yessir since I'm now running PKTDATE.EXE against every .PKT that leaves this BBS. :-) It's a kludge but it works.

... CP 2.00 #19 þ äx›æî mî ­Õ º ”æïë á­ÅÅîçúúúº ÅàÅî ÅhàÅ wà˜ Å””ú

--- QScan/PCB v1.20a / 02-1000
* Origin: The BABBLE BBS * Tucson * babblebbs.no-ip.org * (1:114/201)