Posts Tagged ‘SafeNet’

Sort by: Oldest
 

System.AccessViolationException at HASP login call on Windows 7

Problem: System.AccessViolationException was caught at hasp login() “Attempted to read or write protected memory. This is often an indication that other memory is corrupt.” Source=hasp_net_windows Cause: hasp_net_windows.dll is not recognized and loaded properly Solution: This is specific to Windows 7 settings. On few systems the issue is resolved after checking…

 

Sentinel Cloud v3.0

Feature Highlights/Enhancements: • Introduction of Sentinel Cloud Web Services Sentinel Cloud Web services offer a framework to integrate licensing and monetization abilities of Sentinel Cloud directly in an application. Any platform or language that supports HTTP call with SSL server authentication can integrate Sentinel Cloud Web Services. • Tamper detection…

 

Sentinel Protection Installer v7.6.6 Windows

Sentinel Protection Installer is an integrated installer of the Sentinel System Driver, Sentinel Security Runtime, Sentinel Protection Server, and Sentinel Keys Server. Feature Highlights Sentinel System Drivers certified for Windows 8 and Windows Server 2012 SHK License Monitor and SSP License Monitor supports Internet Explorer 8, 9 and 10 (in…

 

Sentinel LDK Runtime 6.55

Feature Highlights: RTE installers for Windows, Linux and Mac OS X Support for Windows 8 and Windows Server 2012 (previously only available with command-line installation), as well as Mac OS X 10.8 Packages that enclose the readme are available at: http://sentinelcustomer.safenet-inc.com/sentineldownloads/

 

Why does the size of protected executable (64bit) decrease after applying Envelope to the unprotected one?

The size of protected application decreases because Envelope also applies compression while protecting the application. The Win32 engine also applies some compression that is ‘LZ’ compression however Win64 engine includes different compression algorithm. This is the reason why our protected x64 application is almost 1/3rd the size of the original…

 

RTE fails to install: Error code 16 5 37xx 0

In case of error “Accessing the SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers…. ErrorCode: 16 5 37xx 0” Solution: Uninstall RTE using the cmdline installer command haspdinst –fr -purge Check from the registry if the key “SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers exists” (must not) Back up the registry Create the key “SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers” Reinstall the RTE