Subj : not ignoring you... but...
To   : Scott Little
From : mark lewis
Date : Fri Jul 09 2004 02:44 pm

 WS>> I've done further investigations into this EleBBS/WEB
 WS>> 1 day message problem and found that if I have a
 WS>> hudson or a Squish message base the DATE is correct
 WS>> so it is only in a JAM message area... As far as I
 WS>> can tell EleBBS uses Mark May's Source code... So
 WS>> would this narrow it down to maybe a MKMSGJAM.PAS
 WS>> problem?

 SL> Gawd DAY-EM!  What a rats' nest.

where? in ele or the mk library?

 SL> First, you should have your TZ environment variable set.
 SL> TZ=EST-10 if you're in Sydney/Melb/etc.

 SL> Second, it looks like unix2norm() is FUBAR.  Which is really

i don't see unix2norm in the mkmsg stuff... it must be something in the ele 
code...

 SL> odd since a simple unix2norm(norm2unix()) would tell you it's
 SL> broken,

hummm... wonder what that compares with in the mkmsg stuff? mkmsg uses UnixToDT 
and DTToUnix to convert the datetime record format back and forth...

 SL> and this is a piece of code that's been floating around for
 SL> ages (and obviously used by many people).

makes me even more curious, now...

 SL> The fix eludes me (at 5am), so I rewrote it.  This isn't
 SL> well tested, but it Works For Me.

did you test leapyears ;)

 SL> I can compile Win32 and Linux binaries, if you're running
 SL> OS/2 or something you'll have to compile it yourself.
 SL> Just replace unix2norm with the following in
 SL> elebbs/src/unixdate.pas.

ahhh... thought it would have to have been some ele code and not the mkmsg 
code...

 SL> Procedure Unix2Norm(Date: LongInt; var Year, Month, Day, Hour,
 SL> Min, Sec: Word);

hummm... very similar to the datetime record format... just all in pieces 
instead of in one record...

)\/(ark

 
* Origin: (1:3634/12)

.