Navigation
« 

Anonymous




Register
Login
« 
« 

Amiga Future

« 

Community

« 

Knowledge

« 

Last Magazine

The Amiga Future 167 was released on the March 5th.

The Amiga Future 167 was released on the March 5th.
The Amiga Future 167 was released on the March 5th.

The Amiga Future 167 was released on the March 5th.
More informations

« 

Service

« 

Search




Advanced search

Unanswered topics
Active topics
« 

Social Media

Twitter Amigafuture Facebook Amigafuture RSS-Feed [german] Amigafuture RSS-Feed [english] Instagram YouTube Patreon WhatsApp
« 

Advertisement

Amazon

Patreon

« 

Partnerlinks

Is 3c589.device supported?

Support Roadshow

Moderators: AndreasM, olsen

duga
AFF Anwärter
AFF Anwärter
Posts: 15
Joined: 10.12.2012 - 21:21

Post by duga »

These ClassAct programs works with two different 3COM cards:
AmiFTP
AWeb-II 3.2 demo

DHCP still doesn't work (Software Failure 80000003).


MUI programs doesn't work, maybe some 020 version somewhere is the reason.
User avatar
Thorham
Newbie
Newbie
Posts: 6
Joined: 14.03.2008 - 08:00

Post by Thorham »

olsen wrote:The demo version shutting down is a delicate matter :-( Roadshow needs to tell all currently running programs that it has to quit, but not all programs are prepared to follow that signal. They may expect to be shut down through their user interface only, and the alternative method Roadshow employs may lead to undefined behaviour. Unfortunately, there is no telling what will happen. But the demo version has to do something.
Don't know if you're already doing this, but couldn't you just have Roadshow either disconnect without quitting, or just have it send bogus data to applications?
olsen
CygnusEd Developer
Posts: 167
Joined: 06.06.2006 - 16:27

Post by olsen »

Thorham wrote:
olsen wrote:The demo version shutting down is a delicate matter :-( Roadshow needs to tell all currently running programs that it has to quit, but not all programs are prepared to follow that signal. They may expect to be shut down through their user interface only, and the alternative method Roadshow employs may lead to undefined behaviour. Unfortunately, there is no telling what will happen. But the demo version has to do something.
Don't know if you're already doing this, but couldn't you just have Roadshow either disconnect without quitting, or just have it send bogus data to applications?
Roadshow currently shuts down completely, as far as the services it can perform are concerned. Once the timeout elapses, you can no longer establish network connections, for example.

Trying to shut down properly seems to be more difficult than I had expected. So maybe it is too much to ask application software to stop using Roadshow once it has closed up shop :(

On the other hand, how can you tell if the demo version has timed out if the software using it is unaware of this fact?
User avatar
Thorham
Newbie
Newbie
Posts: 6
Joined: 14.03.2008 - 08:00

Post by Thorham »

olsen wrote:On the other hand, how can you tell if the demo version has timed out if the software using it is unaware of this fact?
Maybe pop up a requester? It's just the demo version after all; people aren't supposed to use it so extensively that this would become annoying anyway.
Post Reply