HP System Software Manager Utility 2.10 Rev A
SSM 2.10 Rev A - SoftPaq Number SP42536
- BIOSCONFIGUTILITY.EXE: BCU looks for the BCUErr.cfg in the path of the executable. Previously it needed the file in the current path. If no error translations is needed, use the default configuration file included in the softpaq.
- SSM.EXE: Updates to SSM User Guide to include Win 7 support and clarify the usage of OS tag in DetailFileInformation section. Use [,] to specify OS instead of [;].
- SSM.EXE: Reverted the DetailFileInformation section processing to the same as v2.00G. In version 2.10 A1, we had changed the behavior to 'AND' so SSM would look for ALL the files applicable to the current OS and would install the app if any one or more files were missing or of older version. This broke a number of softpaqs which relied on the previous functionality where SSM would consider the application as installed if atleast one key file was found and the version was the same or newer than the update. Otherwise, if no key files were found or the version of all key files found were older, SSM will install the application. To support the 'AND' behavior we would need to add some syntactical knowledge to the CVA specification which SSM would support in a future release.
- BIOSCONFIGUTILITY.EXE: Added support for error translation using a configuration file. BCU will translate return error codes from BCUErr.cfg, if present. Otherwise it returns the original error code. A default BCUErr.cfg is included in the softpaq.
- BIOSCONFIGUTILITY.EXE: Non-Readonly HP_BIOSInteger fields are written to the GetConfig file. Previously BCU completely ignored the HP_BIOSInteger settings.
- SSM.EXE: Msi based installs which return 3010 (ERROR_SUCCESS_REBOOT_REQUIRED) are written in the 'Updates Performed' section of log file. Previously they were written to the 'Errors' section.
- SSM.EXE: Since the Windows 7 Product types are still not fully defined in MS SDK, SSM will put 'XX' for the product types it does not yet understand. For ex: W732XX. Accordingly, in DetailFileInformation section of cva, SSM now will only match the first 4 characters of the OS tag.
SSM will look for the key file, TestReturnApp.exe in all types of 32 bit Vista. The above key file in effect can be written as,
- BIOSCONFIGUTILITY.EXE, SSM.EXE : Added support for PwdSetFrom flag in WMI for EFI notebooks. Now setup password is encoded in keyboard scan codes if PwdSetFrom is set to F10 (=0)
- SSM.EXE: Added CVA version to log and ssm trace files.
- BIOSCONFIGUTILITY.EXE : Added version information to the command-line output display.
- SSM.EXE: For BIOS updates, if HPQFLASH.EXE is specified in the SilentInstall key of the .CVA file, use the command-line provided by the .CVA file instead of SSM's internal BIOS flash code.
If password is set, the password encryption utility, HPQPSWD.EXE is invoked in silent mode to create a password encryption file which is used by HPQFLASH.EXE.
This support requires HPQFLASH.EXE version 4.20C1 or above.
- SSM.EXE: Removed the "version is older than or same as the installed version and hence is not installed" message from the SSM log (.htm) file.
However, this entry still exists in the SSM debug trace (.ssmtrace) file.
- SSM.EXE: If multiple key files are listed in the [DetailFileInformation] section of the .CVA file, SSM will verify that every file is available (installed) and if any file is missing SSM will install the Softpaq. Previously, SSM.EXE would not install the Softpaq if at least one key file of required version was found.
- SSM.EXE: Fixed an issue which would prevent the Microsoft Data Access components (DAO350.DLL) from being initialized.
- CPQMC.DLL: Added support for the Microsoft Windows(tm) 7 operating system.
In a hurry? Add it to your Download Basket!
It is highly recommended to always use the most recent driver version available. Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games. Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.
- Graphics Board
- Other Drivers & Tools
- Digital Camera / Webcam / Camcorder
- Sound Card
- Printer / Scanner
- Network Card
- Keyboard & Mouse
- Joystick, Gamepad & Wheels
- TV Tuner / Capture Card
- Mobile Phones
- Card Readers
- HDD / SSD / NAS / USB Flash
- TV / HDTV / Projectors
- DVD / Blu-Ray / Media Players
- Router / Switch / AP
- Doesn't matter
- 3 months
- 6 months
- 12 months
- 24 months