--- Mystic BBS v1.05/OS2
Yeah, but it's the latest version for OS/2 that I could find :) It will pick up with VMODEM, but then disconnect when the user is prompted for
the username.
If you want the last OS/2 version what you need to do is install
1.07/DOS then upgrade the DOS version to 1.0.7.2, then there is an
OS/2 release of 1.0.7.3 on the filegate.net web. I have this setup
running on eComstation on real hardware and that's what I had to do, otherwise I was back in the stone age on 1.05 as you are
Ok, I will see about doing that if I decide to go that route on the OS/2 BBS. Thanks for the pointer.
130/20
229/275 426
266/404
320/119
2320/0 1
On 07/26/17, Robert Wolfe said the following...
Ok, I will see about doing that if I decide to go that route on theOS/2
BBS. Thanks for the pointer.
If you are having difficulty finding what you need let me know and I'll post
the links to the 3 seperate ZIP files I downloaded to get the last OS/2 version running
--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ≈ idbbs.dlinkddns.com ≈ port 59 (1:229/275)
ok, this would be awesome. :)
130/20
426 452
267/155
100 102
On 07/31/17, Robert Wolfe said the following...
ok, this would be awesome. :)
Mystic 1.07/DOS - http://www.filegate.net/mysticbbs/mystic/mysd_107.zip Mystic 1.07.2/DOS - http://www.filegate.net/mysticbbs/mystic/mupd1072.zip Mystic 1.07.3/OS2 - http://www.filegate.net/mysticbbs/mystic/mupo1073.zip
Install 1.07/DOS first, upgrade to 1.07.2/DOS then use the 1.07.3 OS/2 version and bob's your uncle. Keep in mind that there is no internal support
for Telnet/BinkD so you still need to use SIO2K/VModem and your favorite OS/2
FTN tosser
BinkD OS/2 - http://www.filegate.net/aftnbinkd/binkda73.zip
---
Enjoy - Dave
--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ≈ idbbs.dlinkddns.com ≈ port 59 (1:229/275)
All done and working -- except for the OS/2 version which crashes in
the text editor. I use Internet Rex for binkd transfers and
registered SIO 1.60d 16 port.
130/20
426 452
267/155
100 102
On 07/31/17, Robert Wolfe said the following...
All done and working -- except for the OS/2 version which crashes in the text editor. I use Internet Rex for binkd transfers and registered SIO 1.60d 16 port.
Crashes in the text editor???? You have something wrong then cuz I've
never
see mine crash..
I tried SIO 1.60 but when I try starting VMODEM.EXE it just seg faulted so I
had to use SIO 2K...
Are your telnet sessions choppy with a proper registered version of SIO 1.60?
--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension ≈ idbbs.dlinkddns.com ≈ port 59 (1:229/275)
As far me not having something set right, then how come I don't have
an issue with the FSE in the same DOS version as the OS/2 version?
Did you have message bases already setup when you switched to the
OS/2 version (since this is FSE related only)? If so, you may want to
try either wiping all your message bases and starting fresh, or move
them to another location to test new data files.
Then you could also try wiping mbases.dat and creating a new one,
etc. You have it narrowed down to one thing causing you issues, so
you basically know where to start looking.
On 07/31/17, Robert Wolfe said the following...
All done and working -- except for the OS/2 version which crashes in the text editor. I use Internet Rex for binkd transfers and
registered SIO 1.60d 16 port.
Crashes in the text editor???? You have something wrong then cuz I've never see mine crash..
I tried SIO 1.60 but when I try starting VMODEM.EXE it just seg faulted so I had to use SIO 2K...
Are your telnet sessions choppy with a proper registered version of SIO 1.60?
SIO 1.6 is compatible with OS/2 up to Warp 4.0. SIO2k introduced compatibility with the TCP/IP that was introduced in 4.5+. There is
no way to make SIO 1.x compatible with anything beyond 4.0.
Yes, I already have JAM format message bases set up.
Then you could also try wiping mbases.dat and creating a new one,
etc. You have it narrowed down to one thing causing you issues, so
you basically know where to start looking.
Again, I thought of that, too, but the problem seems to be only
limited to the OS/2 code. Unless something has changed in OS/2 5.0.1
that is causing that to happen in the Mystic/OS2 code.
Yes, I already have JAM format message bases set up.
The JAM message bases in 1.07.3 were not 100% compatible with JAM message ->bases, for one. That was fixed somewhere in 1.08-1.10 I believe. However, I ->mention "mbases.dat" because these are Mystic's data files, and have nothing ->to
do with JAM message bases.
Starting over with fresh Mystic data files once you convert to OS/2 may ->actually fix your FSE problems. Since you're already deep into this, it's ->probably worth a shot.
Actually, I am not too deep into it. I still have EleBBS/OS2 running
as my main system on the ArcaOS VM for now with FastEcho doing the
mail processing.
I gave it a valiant effort to give some.
1.0.7.3 on the filegate.net web. I have this setup running on eComstation on real hardware and that's what I had to do, otherwise I was back in the stone age on 1.05 as you are
things in the OS seem to lock up, with win-os2 being one of them.
why oh why would anyone install that old thing? it is really old win3/wfwg stuff... ancient doesn't even begin to describe it... i would reinstall and don't touch anything that has anything to do with winwhatever...
i'm curious what hardware you are running eComstation on... i
picked up a copy of arca noae and haven't been able to get it to be
I started off by looking for a WinXP replacement to run Iniquity on, and
figured it would be cool to play with old win3 software too. I've gotten the ->win-os2 system to run on *one* of my systems, an older amd A6 system, but ->that's the only one. Another issue seems to be with video in DOS sessions...
I can't start a windowed DOS session without an error, but if I alt-home to ->full screen it and then bring it back to a window it works, but basic things ->like cls don't actually clear the screen. I know arca noae is doing the best ->they can, and hope they can continue to move towards getting this old/ancient ->OS to working on modern hardware. I was just doing it for fun, nothing other ->than that =) For now, I think I'm just going to use a WinXP vm to get my ->board
back online, and continue to experiment with ArcaOS in a vm. Another major ->issue is that there is apparently no way to purchase a copy of SIO any ->longer... I'm not sure how much work would be involved in coding a ->fossil/telnet replacement.
This is weird, because what you are having issues with with the DOS session (switching from windowed to full screen and back again) I can't duplicate even though I've tried.
Oh, I forgot to mention this earlier, and I'm surprised nobody else has, this is a Fidonet echo, Please inform your sysop that it is supposed to be a Real Name area not an alias area (If you are not the sysop that is) :)
message on to the sysop here. This is not my BBS, although I'm looking forward to joining with my own BBS once I get it a little more stable (hopefully under OS/2) :D
Oh, I forgot to mention this earlier, and I'm surprised nobody else
has, this is a Fidonet echo, Please inform your sysop that it is
supposed to be a Real Name area not an alias area (If you are not the sysop that is) :)
has, this is a Fidonet echo, Please inform your sysop that it is supposed to be a Real Name area not an alias area (If you are not the sysop that is) :)
I don't believe this has ever been an area that required real names. Nor does it have any specific set of rules people are required to follow,
like other areas of Fidonet.
Oh, I forgot to mention this earlier, and I'm surprised nobody else has, this is a Fidonet echo, Please inform your sysop that it is supposed to
be a Real Name area not an alias area (If you are not the sysop that is)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,090 |
Nodes: | 15 (0 / 15) |
Uptime: | 60:45:48 |
Calls: | 232,716 |
Calls today: | 3 |
Files: | 60,050 |
D/L today: |
66 files (55,056K bytes) |
Messages: | 299,362 |