-=> Quoting Mark Lewis to Nancy Backus on 02-02-11  21:00 <=-

 ML>> patch by manually patching the RA version of the door... everything was
 ML>> found as the patch scripts and readme state and the manual hex editing
 ML>> of the binary was no problem... TTBOMK, everything works as desired and

 NB> So you worked with hubby's patch...  :)

yes, to a point... that point being to manually apply it to the RemoteAccess
version of the door... everything appeared to be where it needed to be and the
hex replacements went with no problems... IIRC, preliminary testing was fine,
too... but i believe, as i wrote earlier, that i had to take it back offline
because the data structures for the info passed during the shell were slightly
different and different enough to through certain other date related items
off... i don't believe that i stated it that clearly, though...

[trim]

 ML> i might have removed it by the time you became a regular user... but
 ML> then again, as i think about it, i may also have removed it due to my
 ML> running a beta of the BBS software and the door supporting an older
 ML> version of the data structures... i don't recall if i had written or
 ML> otherwise used a glue program to convert the structures back and forth
 ML> between what the door needs and what the BBS actually uses... yeah, it
 ML> has been quite a while ago ;) 

 NB> Well.. for a time line of sorts... the date on the latest version
 NB> of the patch (as on my computer) is 2006.  That IS a while ago.  :)

yup and i'd have to go digging to see if i still have the patched exe here and
see if its date was even altered by my patching... it may not have been since
i did it manually... 

 NB>   But I think I may have been lurking on the bbs, just reading
 NB> messages to me or something similar, until you offered the offline
 NB> option at all...  I don't remember ever seeing the true BW door
 NB> available... although I might be misremembering...  :)   Maybe the
 NB> problem was* a mismatch between versions of softwares... 

yep... i'm running a beta of the BBS software that uses a couple of extra
sections in the fields for full date format storage... the original places in
the fields for dates are still maintained but they are not full 4 digit
capable whereas the new ones are... so the problem comes up with software that
only updates the old date fields and if they have a y2k problem in that
area... the BBS software updates both sets of fields but i do not recall if it
reads the new field and updates the old field on import... if couldn't do this
if the external software doesn't use the new fields, anyway so there's still a
bit of a sticky wicket there... the only real answer is a glue program that
will create the old binary dropfile format on exit to the external door and
then fix up the new format on return... i just don't recall if i actually did
this glue program or if i got started and then distracted or what :/

)\/(ark

 * Origin:  (1:3634/12)