Intel Extensible Firmware Interface Specification page 451

G.4.7.3 Checking Command Execution Results
After command execution completes, either successfully or not, the
contains the result of the command execution.
StatCode
SUCCESS
INVALID_CDB
INVALID_CPB
BUSY
QUEUE_FULL
NOT_STARTED
ALREADY_INITIALIZED
DEVICE_FAILURE
NVDATA_FAILURE
StatFlags
Check the StatFlags to see if there is an active connection to this network device. If the no media
StatFlag is set, the UNDI and network device are still initialized.
•
PXE_STATFLAGS_INITIALIZED_NO_MEDIA
Before Using the DB
#pragma pack(1)
typedef struct s_pxe_db_initialize {
// Actual amount of memory used from the supplied memory buffer.
// This may be less that the amount of memory supplied and may
// be zero if the UNDI and network device do not use external
// memory buffers.
// allocated from the lowest memory buffer address.
PXE_UINT32 MemoryUsed;
// Actual number and size of receive and transmit buffers that
// were allocated.
PXE_UINT16 TxBufCnt;
PXE_UINT16 TxBufSize;
PXE_UINT16 RxBufCnt;
PXE_UINT16 RxBufSize
} PXE_DB_INITIALIZE;
#pragma pack()
Version 1.02
Reason
Command completed successfully. UNDI and network device is now
initialized. DB has been written. Check StatFlags.
One of the CDB fields was not set correctly.
One of the CPB fields was not set correctly.
UNDI is already processing commands. Try again later.
Command queue is full. Try again later.
The UNDI is not started.
The UNDI is already initialized.
The network device could not be initialized.
The non-volatile storage could not be read.
Memory used by the UNDI and network device is
12/12/00
32/64-bit UNDI Specification
field
CDB.StatCode
433