Brent's World Forums

It never worked that way for me. Once TCPser is closed, the connection to vice is broken, and both must be relaunched. That's the peril I've always had with that proxy. Mostly why I stuck with BBS Server for so long.

I believe the files for the C-64 and 128 version are on K-Guides Amiga BBS itself.

telnet: fw2.cnetbbs.net:6800

Thanks for the info Brent, I will have to check that out. In the back of my mind I thought I had tried to get on that board in the past but was never able to for some reason. I'm running some file transfer tests at the moment and then I will retry it again once the tests are done.

Hmmm,

I thought I had responded to this!

I believe the files are on his C-Net Amiga BBS. Future World..

telnet: fw2.cnetbbs.net:6800

I called Future World II and registered for an account. I haven't got any validation E-Mail yet but I'm watching for it.

I have an account over there, would you like me to connect and pull the current version for you? I will not be posting to the forum, due to legal issues but I can send to you in private....

Let's see if I get any reply and go from there. If I haven't been validated after a week or so, I may take you up on that offer.

Thanks.

The latest version I have is 2.6d which I downloaded from there in August of 2020. Since the only way to legally download it is to be a registered member of his BBS, I don't care at all to give you the credentials to my account so you can download it. I really need to call him and lay down some truth about being too busy to maintain a product that people are really interested in, or at least validate your users. I remember having to email and call him directly to get validated and that took a week almost.

And if Dan has issues with me personally, I see no reason why Spitfire can't host it on Reign of Fire II, he's at least active enough and appears to WANT to further the project, and has done nothing against the community in anyone's eyes. Me, I'm almost burned out at the inability to post my fixes on any legitimate platform that will do the product any good. I mean I literally am the only person in the world that has certain versions and modules for DS2, and have no ability to share it except on the down-low, and that's not really how I wanted this product to turn out. I mean look at poor C-Net Pro that has been without RLogin support or a potential future release since it's acquisition. Hell, look how the Vendetta release turned out: broken, with corrupt modules, and unsupported. I never have understood why it's not available to download from the website other than an attempt to gain tracking metrics on people who download it, and for a free product, who gives a shit? It's not like I want to re-release it as my own with my name plastered all over it. It's a well known product with a history of competent developers and writers behind it, let the damn thing live.

Anyway, that's my rant. I don't have a stake in the whole thing, I'm just a user. And technically, I'm a user of the pre-merger product (2.5) so the product that I am developing mods and fixes for is not even considering the future of 2.6, because God only knows in which direction he's taking it. So in that sense, what Dan has all but directly accused me of (forking the 2.5 and making my own "release") is true in a sense. (HVI-Mod)
But since I'm not sharing it with anyone, I am legally using the product for which I am legitimately licensed for the purpose in which it was intended: a developer's system with unlimited potential, depending on the skill of the owner. Mod it, create, host, and flourish.

Look at C*Base for example. The Holy Moses mod was built on 3.1 pretty much, and the Tao mod several versions later, but because I'm unfamiliar with that product I don't know how much difference there is in the base code. At least with DS2, we all know for certain that it came from a base of the 2.5 release and there it stayed for decades. The only discernable difference I've found in 2.6 is the following:
1. Addition of Strikelink Wifi modem using the #5 module (was originally an open source hayes compatible module written for the Supra 2400)
2. Addition of selectable RTC device during configuration (used as a basic workaround since the ML is hard coded for device 8)
3. Changing of any base module that had capital letters into lowercase (dsp.Local Mode, Modem, Restart, etc.)
4. Name changing from old company/writer to new owner in basic code, and sector edited into the ML where present.
5. Increasing the load of x$ from 6 drives to 8 by way of the RTC device addon.

There are probably others, but when the RTC stopped working naturally for me, I opted to not bother using it, and kept my 2.5 as is.

I hear and share your frustration.

I received a validation E-Mail from Dan this morning! It seems the auto-validation E-Mails were not being sent out and he only just caught it today. Progress is being made... Perhaps now I can get a proper copy of DS2 straight from the source. Stand by...