int offset = 64; // Start at offset to test proper indexing

        int written = request.writeBytesWireFormat(buffer, offset);

        // Verify bytes written
        assertEquals(24, written);

        // Verify structure size (should be 24)
        assertEquals(24, SMBUtil.readInt2(buffer, offset));

        // Verify Reserved1 (2 bytes at offset+2, should be 0)

        @DisplayName("Should handle buffer with offset correctly")
        void testReadWithBufferOffset() throws Exception {
            int offset = 10;
            byte[] buffer = new byte[64];
            byte[] fileId = createTestData(16);
            byte oplockLevel = 0x02;

            // Fill some random data before offset
            Arrays.fill(buffer, 0, offset, (byte) 0xAB);

            assertEquals(ttl, ref.getTtl());
        }
    }

    // Buffer Offset Tests

    @Test
    public void testDecodeFromNonZeroIndex() {
        int offset = 100;
        ByteBuffer bb = ByteBuffer.wrap(testBuffer).order(ByteOrder.LITTLE_ENDIAN);

        bb.position(offset);
        bb.putShort((short) 1);
        bb.putShort((short) 24);
        bb.putShort((short) 1);

// Case 2: bytes=1-10 (absolute start and end offsets) -> RangeSpec{false, 1, 10}
// Case 3: bytes=10- (absolute start offset with end offset unspecified) -> RangeSpec{false, 10, -1}
// Case 4: bytes=-30 (suffix length specification) -> RangeSpec{true, -30, -1}
type HTTPRangeSpec struct {
	// Does the range spec refer to a suffix of the object?
	IsSuffixLength bool

	// Start and end offset specified in range spec
	Start, End int64
}

        buffer[offset] = 0x01; // revision
        buffer[offset + 1] = 0x00; // padding
        SMBUtil.writeInt2(0x8004, buffer, offset + 2); // type
        SMBUtil.writeInt4(0, buffer, offset + 4); // owner offset
        SMBUtil.writeInt4(0, buffer, offset + 8); // group offset
        SMBUtil.writeInt4(0, buffer, offset + 12); // SACL offset
        SMBUtil.writeInt4(20, buffer, offset + 16); // DACL offset

Adding an offset to the name refers to that offset from the symbol's address, so
<code>foo+4(SB)</code> is four bytes past the start of <code>foo</code>.
</p>

<p>
The <code>FP</code> pseudo-register is a virtual frame pointer
used to refer to function arguments.
The compilers maintain a virtual frame pointer and refer to the arguments on the stack as offsets from that pseudo-register.

    /**
     * Test integer overflow protection in security buffer offset calculation.
     */
    @Test
    public void testSecurityBufferIntegerOverflow() {
        byte[] buffer = createBasicNegotiateResponseBuffer();

        // Set security buffer offset close to Integer.MAX_VALUE to test overflow protection
        SMBUtil.writeInt2(32767, buffer, 56); // Large offset (will be added to header start)

        assertEquals(0xFFFF, SMBUtil.readInt2(buffer, 14));

        // Test different offsets
        for (int offset = 0; offset <= 8; offset++) {
            SMBUtil.writeInt4(0x12345678, buffer, offset);
            assertEquals(0x12345678, SMBUtil.readInt4(buffer, offset));
        }
    }

    @Test
    void testNegativeValueHandling() {
        byte[] buffer = new byte[8];

        }

        bufferIndex += 12;

        // Validate sufficient buffer space for timestamps and offsets
        if (buffer.length < bufferIndex + 8 + 8 + 4 + 4) {
            throw new SMBProtocolDecodingException("Buffer too small for timestamps and offsets section");
        }

        this.systemTime = SMBUtil.readTime(buffer, bufferIndex);
        bufferIndex += 8;

//
//	var spd sparseDatas = []sparseEntry{
//		{Offset: 2,  Length: 5},  // Data fragment for 2..6
//		{Offset: 18, Length: 3},  // Data fragment for 18..20
//	}
//	var sph sparseHoles = []sparseEntry{
//		{Offset: 0,  Length: 2},  // Hole fragment for 0..1
//		{Offset: 7,  Length: 11}, // Hole fragment for 7..17
//		{Offset: 21, Length: 4},  // Hole fragment for 21..24
//	}
//