Looks to me you lost that file then, unless WinNT doesn't do system events... ;-)

The sensapi.dll library is used by windows applications when performing synchronization with mobile devices using SENS (System Event Notification Service). Sensapi.dll is required for synchronization (using SENS) to function correctly. If you don't perform any form of sychronization between devices, you can safely remove this file.

If you want, you can download it from here. It probably lives in \\WinNT\\system\\ or \\system32\\

Well, that seems to have fixed my issue. Although, how did I lose a file between versions? Or is this a new file requirement for BOINC v5.4.x?

---

Looks to me you lost that file then, unless WinNT doesn't do system events... ;-)

The sensapi.dll library is used by windows applications when performing synchronization with mobile devices using SENS (System Event Notification Service). Sensapi.dll is required for synchronization (using SENS) to function correctly. If you don't perform any form of sychronization between devices, you can safely remove this file.

If you want, you can download it from here. It probably lives in \\WinNT\\system\\ or \\system32\\

---

I fired up my NT 4 machine just to review the error I was having.

It is during the installer I get the message "Unable to locate SensAPI.DLL", then another error pops up immediately stating "Error 1904: Molule BOINC.DLL failed to register. HRESULT -2147220473. Contact your support personell"

I click on OK for both error boxes, the BOINC installer tells me that everything installed fine, but then I get the error message "Unable to locate SensAPI.DLL" again. Click OK. Try to launch BOINC Manager, and every time I get the same "Unable to locate SensAPI.DLL" error and BOINC Manager refuses to start.

Uninstall, revert back to 5.2.13 and I have no problems whatsoever. How did you get 5.4.11 to work?

---

I put a retired NT server back into service just for SETI crunching with no problems. BONIC ver - 5.4.11
NT - 4.0 sp 6a (latest available before the plug was pulled a year ago)
Installed and Run logged in as administrator equivalent. Not one problem. Actually went smoother than my XP install.
After uninstall did you check to make sure all directories with different versions were deleted. Sounds to me like there is a piece in registry pointing to a spot with old app and part to new.
my 2 cents.

---

I couldn't get 5.4.11 to work on NT 4.0 myself (even with SP6a installed). I believe the last known version to work well with NT 4.o is 5.2.x.

I tried 5.2.x with no luck. Went back to 4.45.

4.45 will not give you consistent requested credits. It uses the old method of figuring them and your requested credits will be all over the map. With the majority of users using a newer version, 5.2 or newer, you should still get the right amount of credits though.

---

I couldn't get 5.4.11 to work on NT 4.0 myself (even with SP6a installed). I believe the last known version to work well with NT 4.o is 5.2.x.

I tried 5.2.x with no luck. Went back to 4.45.

---

I couldn't get 5.4.11 to work on NT 4.0 myself (even with SP6a installed). I believe the last known version to work well with NT 4.o is 5.2.x.

---

Is there still support for Windows NT?

I get this: (stderrgui.txt)
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x77F88D33 read attempt to address 0x00000018

---
I have un-installed, re-downloaded and reinstalled and get the same error. The trouble started when updated to 5.4.11

---