@MichaelMerkel

Yes but is there a enhancement request for Internet Wizard?

There are two different issues talked about in this topic.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Hypex

Quote:

I thought a crash would be serious enough.

I have not seen any crashes related to network interface issue, just silly messages and general problems with it. If some one can make RoadShow crash I'm sure Olsen be happy to get the config files that make it crash.

Last edited by NutsAboutAmiga on 15-Sep-2014 at 10:32 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Quote:

NutsAboutAmiga wrote: @MichaelMerkel Yes but is there a enhancement request for Internet Wizard? There are two different issues talked about in this topic.

sorry - haven't read everything in detail
there is a bug report regarding the crashes when starting.
what enhancement request do you mean? i can check and add it then.

regards...
michael

_________________
Michael Merkel
(Michael.Merkel@gmx.net Home)
Member of Amiga-Freunde Pfalz, OS4 Welt

@MichaelMerkel

The problem that users are allowed to make many "network interfaces" with different names on same network.device and unit.

User is now can run internet wizard more then once.
And crate 100 of network interfaces" names linked to the same network.device and unit, this should not happen.

What should happen is that internet wizard should ether check all configures and look for the device and unit number, when it found it should fill in the input box for "network interface" name, and make the input box read only so the user can't change it.

Another option is to have internet wizard delete the old config file, when new name is given.

Question does Internet Wizard stop the old network interface, when you configure a new network interface? If not then it should also do that.

Last edited by NutsAboutAmiga on 15-Sep-2014 at 06:25 PM.
Last edited by NutsAboutAmiga on 15-Sep-2014 at 06:24 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

I've had the network lock up and had NetShutDown sitting there forever. So had to reboot. Don't recall any crashes of late but got them in the past.

Last edited by Hypex on 17-Sep-2014 at 04:54 AM.

@Hypex

That's not the issue I was taking about.

I have not experienced that. But my question to you will be does that happen after a reboot or after runing some applications, it might be that roadshow is not at fault, it might be that the connection is kept open by a program. Do you use network monitoring software?

Last edited by NutsAboutAmiga on 17-Sep-2014 at 06:42 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Yes I know it wasn't the issue.

IIRC it was after running applications but those were shut down. I can't recall if It also happened after reboot, but it would be if the cable was out.

I didn't run any monitoring software at the time. But all net software was quit. Then NetShutDown would just hang and wouldn't respond to Ctrl-C break. Whatever it was doing it should break.

Last edited by Hypex on 18-Sep-2014 at 03:29 PM.

@Hypex

Quote:

Whatever it was doing it should break.

Software can only break when waiting on or checking a signal, so that ideal of always being able to stop on a CTRL-C is a bit mythical.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

Depends if the software supports it. Bui I have found one must disable Ctrl C checking in their code if it isn't needed so programmers have to aware of it. Otherwise a user pressing Ctrl C can get a crash.

In this case, NetShutDown waits five seconds by default, so it should have exited regardless afer that time.