int CLIENT_UPN_TYPE = 0xC;
    /**
     * Buffer type for client claims information.
     */
    int CLIENT_CLAIMS_TYPE = 0xD;
    /**
     * Buffer type for device information.
     */
    int DEVICE_INFO_TYPE = 0xE;
    /**
     * Buffer type for device claims information.
     */
    int DEVICE_CLAIMS_TYPE = 0xF;

    /**
     * Flag for extra SIDs in logon information.
     */
    int LOGON_EXTRA_SIDS = 0x20;

Android Test
============

A gradle module for running Android instrumentation tests on a device or emulator.

1. Add an Emulator named `pixel5`, if you don't already have one

```
$ sdkmanager --install "system-images;android-29;google_apis;x86"
$ echo "no" | avdmanager --verbose create avd --force --name "pixel5" --device "pixel" --package "system-images;android-29;google_apis;x86" --tag "google_apis" --abi "x86"
```

            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",
            "The process cannot access the file because it is being used by another process.",

            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",
            "The process cannot access the file because it is being used by another process.",

access modes, and other special-purpose flags....

    /** The handle is invalid */
    int NT_STATUS_INVALID_HANDLE = 0xC0000008;
    /** The parameter is incorrect */
    int NT_STATUS_INVALID_PARAMETER = 0xC000000d;
    /** The system cannot find the device specified */
    int NT_STATUS_NO_SUCH_DEVICE = 0xC000000e;
    /** The system cannot find the file specified */
    int NT_STATUS_NO_SUCH_FILE = 0xC000000f;
    /** End of file reached */

     */
    static Stream<Arguments> errorCodes() {
        return Stream.of(
                // Known NT status code - NT_STATUS_UNSUCCESSFUL
                Arguments.of(0xC0000001, "A device attached to the system is not functioning."),
                Arguments.of(0x00000000, "NT_STATUS_SUCCESS"),
                // An error that maps via DOS mapping

import jcifs.internal.smb2.ServerMessageBlock2Response;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Flush response message.
 *
 * This response confirms that buffered data has been
 * successfully flushed to the storage device.
 *
 * @author mbechler
 */
public class Smb2FlushResponse extends ServerMessageBlock2Response {

    /**
     * Constructs an SMB2 flush response
     * @param config the client configuration
     */

import jcifs.internal.smb2.Smb2Constants;
import jcifs.internal.util.SMBUtil;

/**
 * SMB2 Flush request message.
 *
 * This command is used to flush buffered data to the
 * underlying storage device for a given file handle.
 *
 * @author mbechler
 */
public class Smb2FlushRequest extends ServerMessageBlock2Request<Smb2FlushResponse> implements RequestWithFileId {

    private byte[] fileId;

    /**

 * server. Rather than represent each with it's own <code>Exception</code>
 * class, this class represents all of them. For many of the popular
 * error codes, constants and text messages like "The device is not ready"
 * are provided.
 * <p>
 * The jCIFS client maps DOS error codes to NTSTATUS codes. This means that
 * the user may recieve a different error from a legacy server than that of