Hi Herman,

Thank for your help anyway,
That is my nickname, what do your think ? cool

For the declaration in win2k, maybe like what you
said, win2k had better protection, so it does not
work.


>Hi Virusim :)
>Is that a nick or what ? Which one is the real one ? *bg*
>
>>Hi Herman,
>>
>>Thank a lot for your help for the Winio, it working for me as I
>>am able to detect change in the bit of the parallel port of my
>>printer.
>>
>I'm glad to hear it works for you. But remember though it's not for commercial (I guess). Contact the author and who knows maybe he can offer you more helps, right ?
>
>
>>For the DLL declaration, I had tried but it don't seem to be
>>working in Win2k for my case, any suggestion why ?
>
>Like I said before, It actually does not design to work for VFP.
>In W9X maybe it works because the system doesn't use a lot of protection scheme, maybe because of hybrid system. So in many cases the system can still gives permission even the dll gives the system wrong pointer/address
>In NT the protection is much much more strict, cause the system using 32bit pointer/address only. If the pointer is incorrect or maybe just mis-align in the asembly code, the system simply reject it. Or even worst, crashing your system.
>
>So the declaration is actually works. But the call to procedure can not get the result because of the wrong addressing. If you want to know whether your dll declaration is loaded or not, declare it in VFP command window, and then Display the Status. If it shows the declaration, then it is loaded.
>
>BTW, the sample I sent you also tried on 2K. Doesn't work either :(
>
>HTH