>Hi,
>
>I had found that the DLL is a generic DLL for window only. However,
>when I change the DLL to one meant for Foxpro, it didn't give me any
>blank white screen but
>my application cannot detect the hardware lock. Could it be due to
>WinNT server/Workstation not allowing any application to control hardware device. ?

It's not impossible to do, but it certainly requires a different strategy to access the device than writing code to access hardware under Win9x or Win3x. I'd suggest checking with the hardware vendor; they may have a different .DLL to work in the NT environment.

>Please advise. thank a lot.
>
>
>>>Hi,
>>>
>>>Thank for your advise and help.
>>>My foxpro 2.5/2.6 written application can be run on Win3.1/Win9x
>>>without any problem.
>>>I can't tell whether the protection DLL file is a 16 bit one as it is
>>>written by other programmer who had left the company
>>
>>Actually, you can find out by going into the Win9x explorer, right clicking the .DLL and using QuickView - it should tell you immediately the type of .DLL header found.
>>
>>>If the Dll is a 16 bit one, then I look for a 32bit DLL
>>>
>>>On the other hand, I trace to the CallFN() function that call the HASP
>>>DLL which will halt my system. If commented out, it run fine.
>>>So, it maybe the DLL file problem.
>>>
>>>Thank for your advise.
>>>
>>>
>>>
>>>>>Hi,
>>>>>
>>>>>I had a foxpro 2.5/2.6 written application that call HASP protection DLL file for protection which when run under WinNT 4, give me only a blank white screen, then halt my system.
>>>>>
>>>>>On the other hand, using the same HASH DLL file with my Vfp 3 application, my application run without any problem.
>>>>>
>>>>>Could it be the problem of Foxpro 2.5/2.6 REGFN function problem with my application. Please advise or help. Thank a lot
>>>>
>>>>Is the .DLL a Win16 or Win32 .DLL? If it's a Win32 .DLL, it's usable from VFP, but not from FPW, which is a 16 bit application.