1. Forum
  2. Fidonet Message
  3. DOORGAMES

  • wcNav file search bug

    From RUBEN FIGUEROA@1:124/5013 to All on Friday, January 04, 2019 15:22:02
    Date: Tue, 04 Jan 2000 15:22:02 -0400
    From: RUBEN FIGUEROA
    To: ALL
    Subject: wcNav file search bug
    Newsgroups: win.navigator
    Message-ID: <1036425035.34.0@winserver.com>
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 6

    If you try to do a search for new files using wcNav's File Client, and
    specify the date manually, then wcNav only accepts a 2-digit year. If you
    enter "00" for the year, it appears to assume 1900 rather than 2000, so
    if you search for all the files from 1/1/00, you see every file on the
    system.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From RUBEN FIGUEROA@1:124/5013 to All on Friday, January 04, 2019 15:26:36
    Date: Tue, 04 Jan 2000 15:26:36 -0400
    From: RUBEN FIGUEROA
    To: EARL BORAH
    Subject: RE: wcNav file search bug
    Newsgroups: win.navigator
    Message-ID: <1036425036.34.947017322@winserver.com>
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 12

    Good one Earl. I'll check it out and I'll see if the correction can
    be done first at the server side first.

    ---

    On Jan 04, 2000 03:22pm, EARL BORAH wrote to HECTOR SANTOS:

    If you try to do a search for new files using wcNav's File Client, and specify the date manually, then wcNav only accepts a 2-digit year. If
    you enter "00" for the year, it appears to assume 1900 rather than
    2000, so if you search for all the files from 1/1/00, you see every
    file on the system.
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From RUBEN FIGUEROA@1:124/5013 to All on Saturday, January 05, 2019 01:17:12
    Date: Wed, 05 Jan 2000 01:17:11 -0400
    From: RUBEN FIGUEROA
    To: EARL BORAH
    Subject: RE: wcNav file search bug
    Newsgroups: win.navigator
    Message-ID: <1036425045.34.947043359@winserver.com>
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 18


    Nope, it has to be a WCNAV update. It will pass a ILLEGAL date (12/31/1969) to the server if its bad on input. So that means the
    server can't make any correction.

    Any idea why it picks that date in particular? Is it a DOS thing of some sort, or what?

    No real important reason why I'm asking...just curious.

    I think its was 1 less the minimum date 1/1/1970 for a unix time stamp,
    to signify a bad date. But wcnav isn't doing anything about it, like
    saying "bad date, try again".




    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From RUBEN FIGUEROA@1:124/5013 to All on Monday, January 14, 2019 07:48:18
    Date: Fri, 14 Jan 2000 07:48:17 -0400
    From: RUBEN FIGUEROA
    To: EARL BORAH
    Subject: wcNav file search bug
    Newsgroups: win.navigator
    Message-ID: <1036425049.34.947017322@winserver.com>
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 10


    If you try to do a search for new files using wcNav's File Client, and specify the date manually, then wcNav only accepts a 2-digit year. If
    you enter "00" for the year, it appears to assume 1900 rather than
    2000, so if you search for all the files from 1/1/00, you see every
    file on the system.

    I've observed the same problem here. When I search for new files using WcNavigator but under the terminal mode its running fine.
    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)