note to me
-----------------------------------------------
@TZ: 412c
Hi Folks,
Web pages updated for Virtual Net FDN at filegate.net:
http://www.filegate.net/vnet/
takes you to main page where all Virtual file areas are listed.
http://www.filegate.net/vnet/vadv/ takes you right to the VADV file area.
Take care,
Janis
--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)
* An ongoing debate between Janis Kracht and All rages on ...
Whomever is hatching files into the VADV area should be apprised of the 8.3 filename convention. LFNs are not supported here, sorry. :(
note to me
-----------------------------------------------
@TZ: 412c
Hi Folks,
Web pages updated for Virtual Net FDN at filegate.net:
http://www.filegate.net/vnet/
takes you to main page where all Virtual file areas are listed.
http://www.filegate.net/vnet/vadv/ takes you right to the VADV file area.
Take care,
Janis
--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)
sorry about this, ment to send to my e-mail to take care of when I get home from vaction
Rats, missed that .. I'll let Timothy know.. Sorry about that.
* An ongoing debate between Janis Kracht and Ben Ritchey rages on ...
Rats, missed that .. I'll let Timothy know.. Sorry about that.
{chuckle} 30 lashings, with a wet noodle lol
Tim is talking to the team working on VADV to allow Replace and a new
file will be coming out sooner or later.. and he'll watch subsequent
file releases.
note to me
-----------------------------------------------
Hi Folks,
Web pages updated for Virtual Net FDN at filegate.net:
http://www.filegate.net/vnet/
takes you to main page where all Virtual file areas are listed.
http://www.filegate.net/vnet/vadv/ takes you right to the VADV file >>area.
Take care,
Janis
--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)
sorry about this, ment to send to my e-mail to take care of when I get home from vaction
Not a problem, I understand..
That said a working source copy of pktdate might be useful not
that I have seen bad dates on net or echo mail but ....
apparently you do not have folks feeding from your system that get
nostalgic and restore their old BBS setup from 15+ year old tapes or
CDs... BBS software that is not y2k compatible... software that mucks
up the year because the code doesn't do modulo arithmetic [eg: "year = (year-1900) mod 100"]... they get a result of 1xx when they subtract
1900 from the current year while trying to make it a two digit year
because they use math manipulation instead of string manipulation...
this is a quite common problem seen in C code of that era... it is
sometimes seen in code written in other languages but it is very
common in C code... today, that code will return 116 for the year
after they subtract 1900 and don't modulo it...
that's only ONE of the various problems that can happen... depending
on the rest of the processing it may make the PKT header one byte too
long or it could result in the last byte of the PKT header being truncated... then you get to the dates in the packed messages and they
could have headers that are one byte too long or be the proper length
but missing the last byte of the message header...
anyway, i thought i'd toss that out there to try to help explain the
problem of non-y2k compliant software and the possible date problems
they can cause...
For your interest here is the o/p from the attempt to compile it under Mageia v5 X64 Linux : -
-----------
[mbse@Applewood a]$ gcc pktdate.c
pktdate.c:38:6: warning: conflicting types for built-in function 'log'
void log(int loglevel, const char *fmt, ...);
^
pktdate.c: In function 'process_pkt':
pktdate.c:152:9: warning: overflow in implicit constant conversion [-Woverflow]
return FATAL_ERROR;
^
pktdate.c:159:9: warning: overflow in implicit constant conversion [-Woverflow]
return FATAL_ERROR;
^
/tmp/ccoDkgoG.o: In function `write_pkt':
pktdate.c:(.text+0xe5c): warning: the use of `tmpnam' is dangerous, better use
`mkstemp'
-----------
No I don't understand them other than a basic level :(
For your interest here is the o/p from the attempt to compile it under Mageia v5 X64 Linux : -
-----------
[mbse@Applewood a]$ gcc pktdate.c
pktdate.c:38:6: warning: conflicting types for built-in function 'log'
void log(int loglevel, const char *fmt, ...);
^
pktdate.c: In function 'process_pkt':
pktdate.c:152:9: warning: overflow in implicit constant conversion [-Woverflow]
return FATAL_ERROR;
^
pktdate.c:159:9: warning: overflow in implicit constant conversion [-Woverflow]
return FATAL_ERROR;
^
/tmp/ccoDkgoG.o: In function `write_pkt':
pktdate.c:(.text+0xe5c): warning: the use of `tmpnam' is dangerous, better use
`mkstemp'
-----------
No I don't understand them other than a basic level :(
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,038 |
Nodes: | 15 (0 / 15) |
Uptime: | 197:11:53 |
Calls: | 500,233 |
Calls today: | 2 |
Files: | 95,197 |
D/L today: |
451 files (497M bytes) |
Messages: | 464,125 |