I think it would make our systems better if we could adapt RIP 1.54 with our systems since that format does not have too much propritary gunk.
I think it would make our systems better if we could adapt RIP 1.54 with our systems since that format does not have too much propritary
gunk.
I think it would make our systems better if we could adapt RIP 1.54 with our systems since that format does not have too much propritary gunk.
I don't know about RIP much or gunk :) But does rip have any embedded control sequences like Avatar seems to? Its been to long since I even thought about it to recall. But avatar sends SuperBBS into conniptions with all sorts of odd data being pumped out due to whatever is in its
code.
Isn't RIP unbelievable ugly by today standards? I vaguely remember that I once did run a BBS with RIP support for a short time. It was fun, because it was new. But HTML was much more interesting. Maximus 3 also supports RIP (never tested it).
AVATAR was great. Unfortunately there are only few programs that support it.
Isn't RIP unbelievable ugly by today standards? I vaguely remember that
I once did run a BBS with RIP support for a short time. It was fun, because it was new. But HTML was much more interesting. Maximus 3 also supports RIP (never tested it).
AVATAR was great. Unfortunately there are only few programs that
support it.
I've never actually seen avatar screens on a BBS but recall constantly having to select ansi on some bbses and seeing avatar as an alternative.
I was always curious but have zero context lol.
AVATAR was great. Unfortunately there are only few programs that
support it.
I've never actually seen avatar screens on a BBS but recall constantly having to select ansi on some bbses and seeing avatar as an alternative. I was always curious but have zero context lol.
It is not much different than ANSI. It is faster on slow modem connections, because the control codes uses fewer bytes than ANSI.
AVATAR was great. Unfortunately there are only few programs that support it.
Isn't RIP unbelievable ugly by today standards? I vaguely remember that I
I don't recall any instances of avatar looking anything different to ANSI, or appearing to be significantly quicker which was always the selling point I got given.
Avatar was significantly quicker than ansi for reasons I don't know.
Re: Re: RIP 1.54 and telnet
By: esc to Oli on Thu Dec 15 2022 11:03 am
It seems Avatar wasn't very common.
When I ran my original BBS in the
90s, the software I used (RemoteAccess) supported Avatar as one of the possible formats, so I saved my menu files in Avatar in addition to ANSI and plain text. One time I tried calling my BBS (or perhaps another BBS that had Avatar) with an Avatar-capable terminal program (probably Telemate), and it seemed somewhat noticeably faster than ANSI.
I remember RIP looked a bit like EGA graphics. IMO it wasn't too bad.
It was a step up from ANSI, at least. You could probably argue that ANSI looks even more "unbelievably ugly" by today's standards. :)
In Avatar, its 3 chars "^V^An" a 62.5% saving, to set both the foreground and background.
So if you had a very ANSI centric display (which BBSs had), the saving over a slow medium noticably adds up... Back in those days, where disk space was a premium, the savings on disk would be noticable too.
Back in the day my terminal was the terminal provided by FrontDoor. I used avatar when it was supported by the BBS. It was supported by RA, my BBS software back then.
I wonder, can I run RIP doors w/o supporting RIP on the main bbS... but alas; who knows.
I didn't use the FD terminal much, mostly either had the Apple II software which was pretty much just ASCII, followed by Telix and later Telemate. The code sequences for colour and cursor placement are shorter hence the "speed" difference especially in code heavy sequences. It may be because the ANSI I was using tended to be relatively simple, never used over the top pages so the speed was much the same either way.
I wonder, can I run RIP doors w/o supporting RIP on the main bbS... but alas; who knows.
It seems Avatar wasn't very common.
Depends. In parts of Europe RA was one of the most common BBS programs.
I don't recall any instances of avatar looking anything different to ANSI, or appearing to be significantly quicker which was always the selling point I got given.
I also don't recall seeing an avatar editor, but there
Avatar was significantly quicker than ansi for reasons I don't know.
Re: RIP 1.54 and telnet
By: Oli to Utopian Galt on Thu Dec 15 2022 12:28 pm
Isn't RIP unbelievable ugly by today standards? I vaguely remember th once did run a BBS with RIP support for a short time. It was fun, bec it was new. But HTML was much more interesting. Maximus 3 also suppor RIP (never tested it).
I remember RIP looked a bit like EGA graphics. IMO it wasn't too bad.
It was a step up from ANSI, at least. You could probably argue that
ANSI looks even more "unbelievably ugly" by today's standards. :)
Avatar was significantly quicker than ansi for reasons I don't know.
It's because Avatar used fewer bytes/characters for its codes than ANSI.
Avatar was significantly quicker than ansi for reasons I don't
know.
It's because Avatar used fewer bytes/characters for its codes than
ANSI.
I'm pretty sure you can. In the 90s, I remember trying a RIP terminal
on some BBSes that didn't have any RIP menus or anything, but RIP-supporting doors (such as Legend of the Red Dragon) could detect RIP capabilities in the user's terminal and RIP would work in the door.
Remember some of the old doors that had graphical clients? The blog 'Break into chat' wrote about some of these - I remember playing one or too using their own terminal softwares to get those graphics.
My first modem when I got hooked on BBSing was 300 baud. It was as if someone at the other end was typing it all in for you.. ;)
Yeah, RemoteAccess was very common in my area of the US too (I ran
I believe TheDraw (one of the most popular ANSI editors) could save in Avatar. I used TheDraw to edit my ANSI menus in the 90s, and I remember having it save in both ANSI and Avatar formats.
Remember some of the old doors that had graphical clients? The blog 'Break
Also, years ago, I found out that Operation: Overkill II has some
extended sound support, and SyncTerm supports that.. If you play Operation: Overkill II with SyncTerm, when the game asks you if you're using an OOII terminal, try answering Yes, and you should hear a sound when you first enter the game.
Neat. I'll have to do some testing, as I'd love to offer LoRD w/ RIP at
2o - but not system-wide... worth checking out.
pAULIE42o
Neat. I'll have to do some testing, as I'd love to offer LoRD w/ RIP 2o - but not system-wide... worth checking out.
If you guys get his going I would love to see this return to the scene. Back when this was out I was too lazy as a kid looks for the warez
boards and only played ANSI as a result. Would love to see what I
missed out on.
Re: RIP 1.54 and telnet
By: Oli to Utopian Galt on Thu Dec 15 2022 12:28 pm
Isn't RIP unbelievable ugly by today standards? I vaguely
remember that I once did run a BBS with RIP support for a short
time. It was fun, because it was new. But HTML was much more
interesting. Maximus 3 also supports RIP (never tested it).
I remember RIP looked a bit like EGA graphics. IMO it wasn't too bad.
It was a step up from ANSI, at least. You could probably argue that
ANSI looks even more "unbelievably ugly" by today's standards. :)
telnet://bbs.roonsbbs.hu:1212 <<=-
Although the first modem I bought was a 2400, I did play around with 300 and 1200 occasionaly. 300 was pretty much readable as it arrived. Wasn't any good on a busy chat BBS though.
Nightfox wrote to Spectre <=-
From watching "BBS: The Documentary", I remember someone there saying
some people thought 300 baud modems should be all you'd need because
that was "reading speed". :)
Well, just an FYI - there are several bbSes (and networks) that offer
LoRD w/ RIP. Fairly sure that DoorParty has a RIP option in RPG 1, and I've played using RIP at other bbSes, too... they're out there.
The easiest way to use RIP is with the newest (beta?) SyncTerm - you
have to create a ~/.syncterm/cache for any extra sound/files. If you run Windows, RipTel will get you connecting.
Black Flag bbS has two RIP-only bbSes; one uses RIP 1.5 and one uses RIP 3. (A Searchlight and a Mystic bbS.)
blackflag.acid.org:24 Searchlight RIP
blackflag.acid.org:23 Mystic RIP
pAULIE42o
.........
Well been using Netrunner this whole time. Going to have to finally give the one a try and probably re-enter my phone book. I didn't even
realize that Mystic had a RIP option. I will have to check that out.
Well been using Netrunner this whole time. Going to have to finally give the one a try and probably re-enter my phone book. I didn't even
realize that Mystic had a RIP option. I will have to check that out.
is there any good windows based rip graphics programs to make menus?
Al wrote to deon <=-
Yep, back in those days I started out with a 2400 baud modem, and
stayed that way for some time since modems were (very) exensive at the time.
Good times they were!
I know PabloDraw can create .rip graphics. I am not sure how you get mystic to display .rip however? do you just save the graphics file as an .asc and SyncTerm will display it properly? If someone could explain that part of it I would appreciate it.
I don't know about Mystic, but for Synchronet, RIP files are saved with
a .rip extension. And the filename extension doesn't matter for
Yeah, I tried saving them as .rip files. but mystic did not seem to show the file when requested. So not sure what you have to do in mystic to get it to show a .rip
I don't see a mention of RIP graphics there.. My guess would be Mystic doesn't support RIP, but I don't know for sure.
Yea, RIP is basically ASCII files that are converted by the terminal software - so Mystic has the capability of sending them; just like SIXE gfx... problem is not a lot of people DESIGN RIP anym0re - bbSes likeis there any good windows based rip graphics programs to make menus?
I don't see a mention of RIP graphics there.. My guess would be Mystic doesn't support RIP, but I don't know for sure.
I wonder, can I run RIP doors w/o supporting RIP on the main bbS... but alas; who knows.
My first modem when I got hooked on BBSing was 300 baud. It was as if someone at the other end was typing it all in for you.. ;)
can't get netrunner to work on my Lubuntu setup
My first modem when I got hooked on BBSing was 300 baud. It was as if
someone at the other end was typing it all in for you.. ;)
Same. 300bps internal manual modem on my Apple //e.
I don't see a mention of RIP graphics there.. My guess would be Mystic doesn't support RIP, but I don't know for sure.
I don't see a mention of RIP graphics there.. My guess would be
Mystic doesn't support RIP, but I don't know for sure.
Back in the good ol' days if you didn't have native rip support, you could substitute rip files for ans files and move your ans files to asc files. This would give you default rip with fallback to ansi in the case of missing rip/ans files. Never saw a rip client without ANSI support.
Yes, I don't think I said RIP clients don't have ANSI support..?
My first modem when I got hooked on BBSing was 300 baud. It was as if someone at the other end was typing it all in for you.. ;)
Same. 300bps internal manual modem on my Apple //e.
Weatherman wrote to Geri Atricks <=-
My first modem when I got hooked on BBSing was 300 baud. It was as if someone at the other end was typing it all in for you.. ;)
Same. 300bps internal manual modem on my Apple //e.
My 1st modem was a 300bps external Apple Modem - for my old Apple //c.
I seem to remember paying around $300 for it. That would be $1 per
bps. That would be like $600+ at today's pricing with inflation.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 418 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 15:47:09 |
| Calls: | 8,795 |
| Calls today: | 7 |
| Files: | 13,300 |
| Messages: | 5,966,648 |