Forum > General

Windows header files

<< < (2/2)

engine32:
  Thank you all, now it works

  @PascalDragon, that code I found while wandering on internet for the header file with GUID. I just did a test like this:

--- Code: Pascal  [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---  IOC_IN = $80000000;  IOC_OUT = $40000000;  IOC_INOUT = IOC_IN or IOC_OUT;  IOC_WS2 = $08000000;  SIO_GET_MULTIPLE_EXTENSION_FUNCTION_POINTER = IOC_INOUT or IOC_WS2 or 36; // 3355443236; // $C8 00 00 24  WSAID_MULTIPLE_RIO : TGUID = '{8509e081-96dd-4005-b165-9e2ee8c79e3f}';  WSA_FLAG_REGISTERED_IO_BP = 8;..  u32OutBytes := 0;  rRioExtensionFunctionTable.u32Size := 0;  i32Err := WSAIoctl(hSockTest, SIO_GET_MULTIPLE_EXTENSION_FUNCTION_POINTER, @WSAID_MULTIPLE_RIO, sizeof(WSAID_MULTIPLE_RIO), @rRioExtensionFunctionTable, sizeof(rRioExtensionFunctionTable), @u32OutBytes, 0, 0); 
  It looks that the issue was that before I provided the GUID as an array of bytes and it did not work. Now with the new format it works, although sizeof(WSAID_MULTIPLE_RIO) reports the same size of 16.

  I will install Visual Studio and Indy for Lazarus just for this issue, still better than spending hours for it.

  Does Indy for Lazarus supports REGISTERED I/O ?

KodeZwerg:

--- Quote from: engine32 on September 25, 2022, 11:00:57 pm ---  Does Indy for Lazarus supports REGISTERED I/O ?

--- End quote ---
Yes.

KodeZwerg:
But I do not know how Indy works hand-in-hand with selfmade Api calls together, so I would realize everything within Indy.

Remy Lebeau:

--- Quote from: KodeZwerg on September 26, 2022, 12:20:33 am ---
--- Quote from: engine32 on September 25, 2022, 11:00:57 pm ---Does Indy for Lazarus supports REGISTERED I/O ?

--- End quote ---
Yes.

--- End quote ---

Actually, no.  Although Indy does declare the RIO types and constants, it does not actually use them for anything.  They are provided strictly for end-user code to make use of.  Why, I don't know (I didn't write that code). It seems a little counter-intuitive for Indy to waste effort declaring APIs it doesn't use for itself.

Navigation

[0] Message Index

[*] Previous page

Go to full version