Subj : RE: RIP
To   : All
From : MICHAEL PURDY
Date : Thu Jan 31 2019 19:12:12

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)

.