|
| | | |
N
F
O
_
S
M
L
_
D
A
T
A
| | | | |
SOURCE: qdev_structures.txt 1.10 (15/08/2014) English
struct nfo_sml_data
{
UBYTE *sd_dosdevice;
UBYTE *sd_handler;
LONG sd_hantype;
UBYTE *sd_device;
UBYTE *sd_unit;
UBYTE *sd_flags;
UBYTE *sd_control;
UBYTE *sd_startup;
LONG sd_stacksize;
LONG sd_priority;
LONG sd_globvec;
LONG sd_activate;
LONG sd_forceload;
UBYTE *sd_errors;
};
sd_dosdevice
- Normally mountlist scanner will attach colon free DOS device
name in here.
sd_handler
- This coresponds logical Handler, EHandler or FileSystem as
found in the mountlist.
sd_hantype
- Mountlist scanner tries to determine mountblock type by putting
one of QDEV_NFO_SCANML_#? here.
sd_device
- This will be non-NULL only when mountblock is a EHandler or
a FileSystem.
sd_unit - Unit can be literal name or a number. If the very first byte is
NULL then one should inspect LONG starting at byte 1.
sd_flags - Flags can be a s tring or a number. If the very first byte is
NULL then one should inspect ULONG starting at byte 1.
sd_control
- NULL terminated Control string, or NULL. Although redundant it
is being used by the mounter!
sd_startup
- This can either be a string or startup value. Syntax same as in
sd_flags.
sd_stacksize
- Amount of stack that will be used for new handler process. This
is analogous to the Stack in mountblock. Effectively this value
will be LONG aligned in dn_StackSize!
sd_priority
- Priority of the handler process. This can be -128 to 127 only!
sd_globvec
- Logical GlobVec value. Used commonly to kludge BCPL binaries.
sd_activate
- If this is set to one then handler will be loaded and mounted
right away, otherwise its stub will be added to the list.
sd_forceload
- Enforce handler(the binary) to load under any circumstances.
sd_errors
- Scanner will put all keys that were found erroneous in the
buffer. These keys will be '\n' separated. This member points
at that buffer, or should. It can also be NULL.
| |
| | | | |
|
