-=> Quoting Mark Lewis to Nancy Backus on 09-25-06  20:24 <=-

 NB> I have a slightly amended version of Richard's BW-Y2K.ZIP file. 
 NB> Basically the only difference is that he rewrote the readme.txt to
 NB> be more helpful to the one trying to use the reader/door fixes. 
 NB> I'd like to u/l it to Waldo's Place, but I didn't know how the bbs
 NB> would handle something with the same name...  would it think it was
 NB> a duplicate file? 

 ML> if i leave the file(s) in the inbound like they are now, yes, they
 ML> would be duplicates...

That's what I expected.
 
 NB> Let me know how I should handle this...  thanks... :)

 ML> actually, it may be nice(r?) to give them a version number and
 ML> increment it each time there's a change... (???)

Well, since the only change is to the readme.txt, he didn't want to give
it a new version number... the actual meat of the fix isn't touched at
all.  An alternate idea would be for me to just upload the updated txt
file, and you could replace it in the zip file?  Maybe also have it
available for those (anyone besides Dale?) that may have gotten the
older readme?  But if you'd prefer to have two essentially the same on
the bbs, I guess I could just do the add a letter or something to the
file name for the one with the better readme...

 ML> i haven't dug into them enough to try the procedure on the BW-RA
 ML> door but might consider working toward that end...

It should work just fine.  :)

 ML> but i don't have a registered version... it
 ML> seems that it might also be possible to clear that hurdle as well as
 ML> the protection checking on the executable(s) since the author is long
 ML> gone (???) but i don't know how that would be viewed by the
 ML> constabulary... of course, that also depends on how deep the rev.
 ML> coder wants or is willing to dig in to the existing stuff...

Fixing the date stuff was doable by just being able to access the
"library" used for calling the dates...  He didn't really want to (I
think didn't have the tools to) get into any part of the program that
was protected.

 ML> i can say that something similar has been done with the "default"
 ML> fidonet nodelist management tool... some folk in europe
"decompiled" it
 ML> to ASM code and then fixed it up as needed... now there's a new
 ML> compilation with fixes of that much needed util...

It would seem that that was a more universally necessary fix, though.
But that could be a project for the ambitious programmer, I guess, to do
similar to our beloved BlueWave products.  :)
 
ttyl        neb

... Save changes?  (Y)es, (N)o, (W)hat changes?!?

___ Blue Wave/QWK v2.20

--- ViaMAIL!/WC v1.60d