swensont wrote:What about making a more normal version of PING where you ping an IP address (ICMP request) and see if you get a response? If you are creating a PING command that really does not work like a normal PING, then I would suggest changing the name of the command to something like QPING to distinguish it from the normal PING command.
I'm no expert on networks, and I don't know how the normal 'DOS' ping commands works, or if it possible to to do it in the QDOS IP Device driver.
I was originally going to call it IP_PING, I can easily go back to that. I could always call it QPING, but it's always bugged be a bit how just about anything to do with the QL gets a 'Q' stuck in front of it.
Giorgio Garabello wrote:Tried on my network and works perfectly.
I only have a doubt if the computer responds correctly to the first attempt, why do the other nine?]
The PING command does not know how many Ping Servers/emulators are running on the PC you are PINGing (you can get multiple responses). So It checks all 10, and gives you a 'No server' response for the ones it did not find. I could just return an empty response (with or without a line feed at the end) from missing servers, but you could be sitting there for up to 30 seconds thinking 'what's happening?' as nothing may be appearing on the screen.
When you start a Ping Server, it scans the port range it can use, and picks the first unused one. So if you start eight Ping Servers, then remove the first seven of them. Then do a PING, you will get back something like
** No server found **
** No server found **
** No server found **
** No server found **
** No server found **
** No server found **
** No server found **
Your message
** No server found **
** No server found **
If you did not have a 'no server found' message, you would sit there for about 20 seconds seeing nothing, until Your message appeared. But if this change is wanted please say.
QLvsJAGUAR wrote:I would like to see it as part of the IPNet /LocalIPNet drivers or the IPBASIC toolkit rather than another stand-alone binary.
I would go for a limit of one Ping Server instance per “QL”.
The free string for Ping Server is somewhat nice, but what about 100% Windows/Linux type output of PING?
I may incorporate it into IPNet/LocalNet/IP_BASIC when I'm/everyone's happy with the way it works.
I was going to limit it to one Ping Server per 'QL', But I thought someone might want to have more than one message available. For example you might want to have a program running on an emulator (foreground or background task) that either supplies a message that it has finished what it was doing, or sends a message that it is busy doing something.
What's the general view?
As to a 100% Windows/Linux type output, As I said above I don't know how the normal Ping commands works, or if it possible to to do it in the QDOS IP Device driver.
Martin