calling ISession::close(). Otherwise, when the calling process end, the machine will receive the state “aborted”, which can lead to loss of data. So the sequence to change a machine’s memory to 1024 MB Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work Reading the IMedium::state attribute no longer automatically performs an accessibility check; a new method IMedium::refreshState() does this. The attribute only returns the state any more. • There were

calling ISession::close(). Otherwise, when the calling process end, the machine will receive the state “aborted”, which can lead to loss of data. So the sequence to change a machine’s memory to 1024 MB Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work Reading the IMedium::state attribute no longer automatically performs an accessibility check; a new method IMedium::refreshState() does this. The attribute only returns the state any more. • There were

Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work ISession::unlockMachine(). Otherwise, when the calling process end, the machine will receive the “aborted” state, which can lead to loss of data. So, as an example, the sequence to change a machine’s memory to 1024 example, the VirtualBox GUI waits for machine events and can thus update its display when the machine state changes or machine settings are modified, even if this happens in another client. This is how the

Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work on ISession::unlockMachine(). Otherwise, when the calling process end, the machine will receive the “aborted” state, which can lead to loss of data. So, as an example, the sequence to change a machine’s memory to 1024 example, the VirtualBox GUI waits for machine events and can thus update its display when the machine state changes or machine settings are modified, even if this happens in another client. This is how the

Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work on ISession::unlockMachine(). Otherwise, when the calling process end, the machine will receive the “aborted” state, which can lead to loss of data. So, as an example, the sequence to change a machine’s memory to 1024 example, the VirtualBox GUI waits for machine events and can thus update its display when the machine state changes or machine settings are modified, even if this happens in another client. This is how the

Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work ISession::unlockMachine(). Otherwise, when the calling process end, the machine will receive the “aborted” state, which can lead to loss of data. So, as an example, the sequence to change a machine’s memory to 1024 example, the VirtualBox GUI waits for machine events and can thus update its display when the machine state changes or machine settings are modified, even if this happens in another client. This is how the

Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work ISession::unlockMachine(). Otherwise, when the calling process end, the machine will receive the “aborted” state, which can lead to loss of data. So, as an example, the sequence to change a machine’s memory to 1024 example, the VirtualBox GUI waits for machine events and can thus update its display when the machine state changes or machine settings are modified, even if this happens in another client. This is how the

Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work ISession::unlockMachine(). Otherwise, when the calling process end, the machine will receive the “aborted” state, which can lead to loss of data. So, as an example, the sequence to change a machine’s memory to 1024 example, the VirtualBox GUI waits for machine events and can thus update its display when the machine state changes or machine settings are modified, even if this happens in another client. This is how the

Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work ISession::unlockMachine(). Otherwise, when the calling process end, the machine will receive the “aborted” state, which can lead to loss of data. So, as an example, the sequence to change a machine’s memory to 1024 example, the VirtualBox GUI waits for machine events and can thus update its display when the machine state changes or machine settings are modified, even if this happens in another client. This is how the

Web service operations are entirely procedural, and one cannot normally make assumptions about the state of a web service between function calls. In particular, this normally means that you cannot work on ISession::unlockMachine(). Otherwise, when the calling process end, the machine will receive the “aborted” state, which can lead to loss of data. So, as an example, the sequence to change a machine’s memory to 1024 example, the VirtualBox GUI waits for machine events and can thus update its display when the machine state changes or machine settings are modified, even if this happens in another client. This is how the