>>Correction:
>>
>>

DECLARE SHORT SystemParametersInfo IN WIN32API ;

>
>Hmm, forgot about that one. Actually, with the code you posted earlier, too, at least in this case. If pvParam gets used by other GETs or SETs, it'll become an issue.

SPI_GETs return values through pvParam, and SPI_SETs pass values via uiParam, and there are a ton of constants associated with it, so it really requires the detailed docs; the MSDN Platform SDK + the VB API Viewer are enough. You can limit the scope of visibility of a change using the last parameter so that existing apps don't see a change, but anything started uses the current setting, so performance can be very wierd.

You need to read the description of each SPI option carefully to make sure that you pass the right things, especially when interpreting pvParam from a SPI_GET return, and you can upset users very easily.