Roadshow for 68K -Needs your support!

[pVC]

There have been cheap offers for amigaish programs lately, and when it's stayed around 10e, I've bought them even if I don't need it that much. I think it's a good tactic in today's situation.

That 10e, for example, is cheap enough to attract even occasional Amiga triers to buy the software instead of pirating or giving up. At least when it's easily available (web download, paypal). And also for long time Amiga hobbyists, who are thinking if it's worth to buy new software or stick with old options.

I don't think there are that much heavy users who are willing to pay tens of euros anymore. Low price and availablility would benefit whole Amiga community, and I believe author too, better than rarely bought expensive product.

I'm happy with AmiTCP/IP Genesis on my classic Amigas with my current usage, but if it will be around 10e I'll promise to buy it anyway

EDIT: same apply to CED too. I've been thinking of buying later version, but it's just too expensive in current form and situation (I bought CubicIDE when it was on <20e offer, but I'd rather use CED ).

[pVC]

Honestly, we haven't quite decided yet. Given the price range discussed in this very thread, my best guess is that the price will be in the 20-25€ range for the digital download (yes, I am aware of the irony of downloading a TCP/IP stack from the Internet), plus some extra money should you prefer a CD-R (with the installation software and the SDK on it) mailed to your home (no idea how that much would cost, though).

I'd say that 20-25e would be ok for physical copy, but if download version would be considerably lower (10-15e), then it would sell a lot more. It would be easier to toss the money for occasional hobbyists which the most of the users seem to be nowadays.

With that 20e for download copy I'll stick with the old stacks. With 10e I'd buy this new for sure, even when I could do with the old stacks.

I downloaded and tested. It feels faster than Miami. I'm using SANA-II and a Mediator with 100 Mbps card.

Yeah, it doesn't need much to be faster than Miami I think it's about the same speeds with AmiTCP.

[pVC]

I'm curious about the setup process. The installation script should put everything on the boot volume, but you still need to edit the networking device configuration. I know how to do that, but is there something you think could be done better? It's not exactly user-friendly :-/

Yes, that will cause complains by less experienced users for sure. Maybe installation script should ask basic network settings and apply it to configuration file in devs:. Doesn't need much, just little playing with scripts. And then you could reconfigure it by running installation script again. Pretty old fashioned, but would be better than nothing if you're not up to write full prefs program.

And btw. could you add preconfigured interface file for 3com driver too? And Hydra & X-surf too...

[pVC]

It should include preconfigured interface files for cnet.device/g-rex/prometheus/xsurf/... otherwise users will complain.

It has for cnet...

[pVC]

I'd be happy to. The current set of files represents only the hardware which I had access to and could test by myself. If you could point me to working configurations (e.g. what goes into the "device=" line of the respective Storage/NetInterfaces config file), I'll update the demo version and the release version archives.

These to devices:
3c589.device (3Com Etherlink III PCMCIA cards)
hydra.device (Hydra Systems' Amiganet cards)
norway.device (Norway ethernet add-on for Highway USB controller)
x-surf.device (Individual Computers' X-Surf cards)

I haven't tested them with Roadshow, but they do work without any tricks with old amitcp at least. I may be able to test at least some of them later, if needed.

[pVC]

Thank you, I have just added new ready-made configuration files for these devices, and these changes will hopefully soon appear in the demo version, and eventually the commercial release in January next year.

And one more thing... you have Mediator configuration file, which has FastEthernet.device. Mediator software has actually two different network devices. FastEthernet.device is for RTL8139 compatible 10/100Mbps cards, while MediatorNET.device is used for  RTL8029 compatible 10Mbps cards. So, you should make two different config files for Mediator use.