And to be fair... theres no reason you can't run multiple DDLINKs in a multitasking environment

DDLINK is an end-to-end program and does assume you know what you are doing

You can run as many pairs as you lile with different packet types.

Or with same types, just started in pairs
(Server, client) .. once connected the lan is a simple wire

DaveDDS wrote on Yesterday, 23:04:

And to be fair... theres no reason you can't run multiple DDLINKs in a multitasking environment […]
Show full quote

And to be fair... theres no reason you can't run multiple DDLINKs in a multitasking environment

DDLINK is an end-to-end program and does assume you know what you are doing

You can run as many pairs as you lile with different packet types.

Or with same types, just started in pairs
(Server, client) .. once connected the lan is a simple wire

I totally agree, I was only looking for an interrupt function that could answer to simple questions like whether the program is active, which resources are being locked, instances running, type of interface being used (com, lpt, eth, other), version, etc., the more the merrier... Perhaps asking way too much... 😀

I perfectly understand I am not being realistic in this day and age, but I couldn't help myself for trying to ask anyway.

Does multitasking dos not have a method to show/query whats running?

Yeah, that might not tell you the command options that were selected... but... is there a standard for pgms reporting that?

Or should I spend a few days designing and implementing a proprietary comprehensive reporting interrupt so that 1 (or maybe 2) users could write the softwate which would be needed to make use of it?

Sorry for the snark hopefully this helps see a point!

DaveDDS wrote on Today, 00:24:

Does multitasking dos not have a method to show/query whats running? […]
Show full quote

Does multitasking dos not have a method to show/query whats running?

Yeah, that might not tell you the command options that were selected... but... is there a standard for pgms reporting that?

Or should I spend a few days designing and implementing a proprietary comprehensive reporting interrupt so that 1 (or maybe 2) users could write the softwate which would be needed to make use of it?

Sorry for the snark hopefully this helps see a point!

Your point has been already understood long ago. That doesn't invalidate making a polite request.
Your program, your goals, your design choices.

I am sorry if I insulted you somehow by asking. That was not clearly the intention.
Bye.

I don't feel "insulted", I'm just having a hard time figureing out how to reply to repeated responses which essentially say (paraphrased): "I completely get that the feature I requested may not be appropriate or desireable ...but... I'd like to restate the request while pointing out how appropriate and desireable this feature is" - still seems to be a lack of communiction...

BTW: If your mt-DOS can't tell you if a process called "DDLINK" is alreatd running, you MAY be able to tell via the network interface (but I don't know how your mt-DOS handles packets to self - YMMV)

Broadcast a LINK_INIT packet with a wrong/bad version ... if a DDLINK server is active it will respond with a reject (and indicate the version which is running)

The "from" MAC would tell you if it is local or remote.