f78ae0fb2a
All checks were successful
Source release / source-package (push) Successful in 48s
Wire NCP 0x16/0x33 Get Extended Volume Information to a real reply instead of returning 0xfb. The WebSDK documents NCP 0x2222/22/51 as taking a VolumeNumber and returning a low-high VolInfoReplyLen, an NWVolExtendedInfo structure, and a length-prefixed volume name. The SDK headers define NWVolExtendedInfo as 33 32-bit fields covering volume type, status flags, sector and cluster geometry, free-space counters, suballocation/limbo/compression/migration counters, directory counters, EA counters, a Directory Services object id, and a last-modified timestamp. Map the Unix filesystem data already used by the older volume-information calls to the core extended-volume fields: report a NetWare 386 v3.1 style volume type, 512-byte sectors, 8 sectors per cluster, total/free clusters, and directory-entry counters derived from fs_usage. Report NetWare-specific suballocation, limbo, compression, migration, EA, Directory Services, and timestamp fields as zero for now. Add the SDK request/reply semantics to the inline endpoint comment and remove the corresponding TODO entry. This enables the documented endpoint path while keeping the mapping conservative; fields MARS-NWE cannot currently model remain zero rather than guessed.