Status response to BIOS_SDTI_OUT.
Trigger: Sent after SDTI has received a valid BIOS_SDTI_OUT.
Target: The link number that sent the BIOS_SDTI_OUT call.
link_message(integer sender_num, integer [ident], string "BIOS_SDTI_OUT_RESP", key [status])
| • integer | [ident] |
| • key | [status] |
| Parameter | Description |
|---|---|
[ident] |
Integer. The [ident] sent with BIOS_SDTI_OUT when the connection was created. |
[status] |
String. The result of opening the connection as one of the following strings. |
[status] |
Description |
|---|---|
| "ok" | The outbound connection is open and attempting to send data. Software should wait for a BIOS_SDTI_CLOSE call. |
| "ident conflict" | The outbound connection was not created. [ident] is already in use by another connection.This may also be a spurious call sent in response to other software using the SDTI that should be ignored; see the Caveats section for more information on this. |
| "invalid ident" | The outbound connection was not created. [ident] is not within the valid range (100,000,000 to 999,999,999, inclusive). |
| "invalid memory bank" | The outbound connection was not created. [memory_bank] is not a valid memory bank number. |
[ident]. In that case, the software will receive its original BIOS_SDTI_OUT_RESP call - which may return "ok" - but it will later also receive a spurious BIOS_SDTI_OUT_RESP call intended for the other software with "ident conflict" because the SDTI cannot target individual scripts. If the software is not aware that this second BIOS_SDTI_OUT_RESP call should be ignored, it may inaccurately assume that the connection was not created due to a conflict.