StarForce passed "CERTIFIED FOR MICROSOFT WINDOWS VISTA" tests.
StarForce is happy to announce that SF FrontLine has passed "CERTIFIED FOR MICROSOFT WINDOWS VISTA" tests.
The certification was run independently by VeriTest, a company that manages programs on behalf of Microsoft. The VeriTest lab report shows that StarForce® FrontLine complies with the requirements for both 32 and 64 bit versions of MICROSOFT® WINDOWS VISTA.
"Pass" status for each test case confirms that StarForce meets the strict security and compatibility requirements of Microsoft’s certification program.
Says Michael Kalinichenko, CEO of StarForce Technologies: “We are delighted that StarForce Frontline has passed the tests in time. We are also proud to be one of the first Russian software companies to complete the tests. StarForce will continue testing its libraries and drivers with further respected and independent test laboratories to ensure that our solutions benefit our clients and their customers.”
Test Results in the VeriTest Lab:
|
Test Cases
|
Pass
|
Fail
|
|
Security and Compatibility
|
|
|
| 1.1 Follow User Account Protection Guidelines |
|
|
|
TC 1. Verify all of the application’s executables contain an embedded manifest that define its execution level
|
X
|
|
|
1.2 Support 64-bit Versions of Windows Vista
|
|
|
|
TC 4. Verify application installer does not have a 16-Bit installer, does not use or rely on 16-Bit code or components and does not attempt to install any non 64-Bit drivers on x64 versions of Windows regardless if application is a Win32 application or is native to 64-bit
|
X
|
|
|
1.3 Sign Files
|
|
|
|
TC 5. Verify application installed executables and files are signed
|
X
|
|
|
1.6 Perform Version Checking Properly
|
|
|
|
TC 7. Verify application properly checks for Operating System version
|
X
|
|
|
1.8 Support Concurrent User Sessions
|
|
|
|
TC 8. Verify application launches and executes properly using Fast User Switching
|
X
|
|
|
TC 9. Verify application launches and executes properly using Remote Desktop
|
X
|
|
|
Install/Uninstall
|
|
|
|
2.1 Use Windows Components for Installation
|
|
|
|
TC 11. Verify application installer uses Windows Installer.
|
X
|
|
|
TC 12. Verify application’s MSI installer does not receive any errors from the Internal Consistency Evaluators.
|
X
|
|
|
2.3 Install to Correct Folders
|
|
|
|
TC 15. Verify application installs to the correct folders by default
|
X
|
|
|
TC 18. Verify Windows Installer package contains Manufacturer, ProductCode, ProductLanguage, ProductName, ProductVersion (major and minor), and UpgradeCode property tags and that they are not null
|
X
|
|
|
TC 19. Verify application creates uninstall registry key and values
|
X
|
|
|
2.9 Install Windows Resources Properly
|
|
|
|
TC 20. Verify application does not try to write to or replace any WRP registry keys or files
|
X
|
|
|
2.10 Follow Best Practices for Creating Custom Actions
|
|
|
|
TC 21. Verify the application does not use nested install custom actions
|
X
|
|
|
TC 22. Verify the application does not add custom columns to the Windows Installer’s standard tables and that any custom tables or properties are not prefixed with ‘msi’
|
X
|
|
|
TC 23. Verify the application rolls back the install and restores machine back to previous state
|
X
|
|
|
2.12 Avoid Reboots During Installation
|
|
|
|
TC 24. Verify the application does not force a reboot during install
|
X
|
|
|
TC 25. Verify the application properly handles files in use during install
|
X
|
|
|
2.13 Support Command Line Installation
|
|
|
|
TC 26. Verify the application can be installed quietly from the command line
|
X
|
|
|
2.14 Follow Component Rules
|
|
|
|
TC 27. Verify the application’s Windows Installer ComponentID table does not contain null values
|
X
|
|
|
TC 28. Verify the application’s Windows Installer Package does not contain more than one COM Server for each Component
|
X
|
|
|
TC 29. Verify the application’s Windows Installer Package does not contain more than one shortcut for each component
|
X
|
|
|
Reliability
|
|
|
|
3.1 Maintainable Software: Eliminate Unnecessary Reboots
|
|
|
|
TC 30. Verify the application is Restart Manager Aware
|
X
|
|
|
TC 31. Verify application does not break into debugger with the specified AppVerifier checks
|
X
|
|
|
TC 32. Verify that he application’s UI thread only handles exceptions that are known and expected
|
X
|
|
Microsoft, Windows and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.
