• RIP

    From GREG YOUNGBLOOD@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Sat, 09 Nov 2013 12:33:42 -0400
    From: GREG YOUNGBLOOD
    To: MICHAEL PURDY
    Subject: RIP
    Newsgroups: win.server.program
    Message-ID: <1384018422.32.1366763878@winserver.com>
    References: <1366763878.32.1366749266@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 12


    Hello Michael

    Could you tell me if WinServer still supports RIP?

    Thanks


    Greg


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From LEE GREEN@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Mon, 11 Nov 2013 18:13:02 -0400
    From: LEE GREEN
    To: GREG YOUNGBLOOD
    Subject: RIP
    Newsgroups: win.server.program
    Message-ID: <1384211582.32.1384018422@winserver.com>
    References: <1384018422.32.1366763878@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 13

    Winserver (WC5+) never did have RIP support, only WC4 did.

    Hello Michael

    Could you tell me if WinServer still supports RIP?

    Thanks


    Greg


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Tue, 12 Nov 2013 21:58:20 -0400
    From: MICHAEL PURDY
    To: all
    Subject: RE: RIP
    Newsgroups: win.server.program
    Message-ID: <1384311500.32.1384018422@winserver.com>
    References: <1384018422.32.1366763878@winserver.com>
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 24

    In light of the obsolete status of 16 bit centric BBS RIP I doubt this
    thread will attract a great deal of attention. However, as it may assist someone in the future I will make a couple of observations.

    The capacity to detect RIP exists in Wildcat! v5 to v7, but it is not implemented by default in MAIN.WCC.

    The code to display an alternate set of *.RIP or dispR.BBS files does not currently exist at all in the relevant ANSI Side modules.

    You can implement the ability to detect RIP and its associated Version

    Connected with Telnet. Ansi detected. - Detected RIP Version: 030001

    As you will see above I am successfully detecting RIP Version 3. I do not
    have a working RIP v1 or v2 emulator so I cannot test backwards
    compatibility. However, my testing was based on the RIPv1 Specification so
    it should work with v1 to v3.

    Once you have detected RIP you can set a global session variable for the
    user and then display an alternate set of RIP files. I tested the concept
    of HELLOR1-HELLOR9.BBS and it worked fine.


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From GREG YOUNGBLOOD@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Wed, 13 Nov 2013 21:24:46 -0400
    From: GREG YOUNGBLOOD
    To: LEE GREEN
    Subject: RIP
    Newsgroups: win.server.program
    Message-ID: <1384395886.32.1384211582@winserver.com>
    References: <1384211582.32.1384018422@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 16


    Winserver (WC5+) never did have RIP support, only WC4 did.

    Hello Lee

    Mike stated to me that in fact WC5 did have support after looking at the
    source code as soon as WC6 came out it was no longer supported!


    Greg





    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Thu, 14 Nov 2013 00:37:21 -0400
    From: MICHAEL PURDY
    To: GREG YOUNGBLOOD
    Subject: RE: RIP
    Newsgroups: win.server.program
    Message-ID: <1384407441.32.1384395886@winserver.com>
    References: <1384395886.32.1384211582@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 40

    I think what I have to say for completeness/fairness is that it was there
    on the MSI Windows95/v5 Preview CD-ROM I received in the lead up to their closure.

    A previously mentioned there is no evidence that it was active in the SSI
    v5 code and beyond.

    http://www.mapurdy.com.au/public/mapapps/rip1.jpg
    http://www.mapurdy.com.au/public/mapapps/rip2.jpg

    As the two screen captures above show its still works fine in PRELOGr.BBS
    under Wildcat! v7 so the capability is there its just not implemented.

    This is quite different to BBS packages that completely removed all RIP capacity in the 1998-2000 period.

    If someone was a keen RIP artist there is no reason why they could not reintroduce it progressively over time.



    On 11/13/2013 9:24 PM, GREG YOUNGBLOOD wrote to LEE GREEN:


    Winserver (WC5+) never did have RIP support, only WC4 did.

    Hello Lee

    Mike stated to me that in fact WC5 did have support after looking at the source code as soon as WC6 came out it was no longer supported!


    Greg







    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From LEE GREEN@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Fri, 15 Nov 2013 20:53:14 -0400
    From: LEE GREEN
    To: GREG YOUNGBLOOD
    Subject: RIP
    Newsgroups: win.server.program
    Message-ID: <1384567322.32.1384395886@winserver.com>
    References: <1384395886.32.1384211582@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 24

    The code might have been there but it wasn't available to the user (me),
    when I went from wc4 to wc5.(4?) it disappeared, there were no longer
    any .rip files in the WCx\Disp folder and it didn't work for me the way
    it did in wc4. I've still got my .rip files and wc4 running it rips! I
    would use it in wc5/6/7 if it was as easy as it was in wc4, ie: if rip
    was detected and you had a .bbs and .rip file it would automatically use
    the .rip for display.


    Winserver (WC5+) never did have RIP support, only WC4 did.

    Hello Lee

    Mike stated to me that in fact WC5 did have support after looking at the source code as soon as WC6 came out it was no longer supported!


    Greg





    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From LEE GREEN@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Fri, 15 Nov 2013 21:08:54 -0400
    From: LEE GREEN
    To: MICHAEL PURDY
    Subject: RE: RIP
    Newsgroups: win.server.program
    Message-ID: <1384567734.32.1384311500@winserver.com>
    References: <1384311500.32.1384018422@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 30

    How do you connect with ANSI AND RIP?
    Connected with Telnet. Ansi detected. - Detected RIP Version: 030001

    Can you give a step by step instructions how to achive this using the
    methods via variables and alternate display files, etc.

    In light of the obsolete status of 16 bit centric BBS RIP I doubt this thread will attract a great deal of attention. However, as it may assist someone in the future I will make a couple of observations.

    The capacity to detect RIP exists in Wildcat! v5 to v7, but it is not implemented by default in MAIN.WCC.

    The code to display an alternate set of *.RIP or dispR.BBS files does not currently exist at all in the relevant ANSI Side modules.

    You can implement the ability to detect RIP and its associated Version

    Connected with Telnet. Ansi detected. - Detected RIP Version: 030001

    As you will see above I am successfully detecting RIP Version 3. I do not have a working RIP v1 or v2 emulator so I cannot test backwards compatibility. However, my testing was based on the RIPv1 Specification so it should work with v1 to v3.

    Once you have detected RIP you can set a global session variable for the user and then display an alternate set of RIP files. I tested the concept of HELLOR1-HELLOR9.BBS and it worked fine.


    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)
  • From MICHAEL PURDY@1:124/5013 to All on Thu Jan 31 19:12:12 2019
    Date: Sat, 16 Nov 2013 02:55:24 -0400
    From: MICHAEL PURDY
    To: LEE GREEN
    Subject: RE: RIP
    Newsgroups: win.server.program
    Message-ID: <1384588524.32.1384567734@winserver.com>
    References: <1384567734.32.1384311500@winserver.com>
    X-WcMsg-Attr: Rcvd
    X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
    Lines: 66

    Its quite possible that Sysops still offering ANSI would use it if
    available, especially those with Dial-up customers.

    Unfortunately there is no way to detect it using the Display Macro language.

    However, creating an IFRIP=v macro and supporting the INCLUDE macro is one
    way SSI could implement RIP support albeit in a sub-optimal manner.

    The alternative would involve SSI modifying the current DisplayFile()
    function to serve *.BBS or *.RIP depending upon the user terminal type
    and/or RIP Version. Regardless of the approach I strongly suspect
    customers would need to supply their own RIP Files.

    I made a small change to MAIN.WCX in order to detect RIP and the RIP
    Version Number. In order to serve the ANSI and RIP sets a 3rd party
    developer would need to rework a number of the ANSI modules which it would
    not be prudent to redistribute.

    If someone is interested in RIP support they can always raise it with SSI and/or perhaps find out whether or not other Sysops are interested in it.

    I don t think it would be worth pursuing unless it can be determined that
    RIP v1 and v2 Terminals are supported. I only have access to a v3 Terminal Emulator so I cannot test v1 or v2 support.

    If someone wants to test with earlier versions let me know.




    On 11/15/2013 9:08 PM, LEE GREEN wrote to MICHAEL PURDY:

    How do you connect with ANSI AND RIP?
    Connected with Telnet. Ansi detected. - Detected RIP Version: 030001

    Can you give a step by step instructions how to achive this using the methods via variables and alternate display files, etc.

    In light of the obsolete status of 16 bit centric BBS RIP I doubt this thread will attract a great deal of attention. However, as it may assist someone in the future I will make a couple of observations.

    The capacity to detect RIP exists in Wildcat! v5 to v7, but it is not implemented by default in MAIN.WCC.

    The code to display an alternate set of *.RIP or dispR.BBS files does not currently exist at all in the relevant ANSI Side modules.

    You can implement the ability to detect RIP and its associated Version

    Connected with Telnet. Ansi detected. - Detected RIP Version: 030001

    As you will see above I am successfully detecting RIP Version 3. I
    do not
    have a working RIP v1 or v2 emulator so I cannot test backwards compatibility. However, my testing was based on the RIPv1
    Specification so
    it should work with v1 to v3.

    Once you have detected RIP you can set a global session variable for the user and then display an alternate set of RIP files. I tested the
    concept
    of HELLOR1-HELLOR9.BBS and it worked fine.



    --- Platinum Xpress/Win/WINServer v3.1
    * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013)