. RECOMMENDED. HP ProLiant Smart Array Controller (AMD64/EM64T) Driver for Red Hat Enterprise Linux 5 (AMD64/EM64T) By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement. Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

However, with the small time difference, WinRAR generates significantly smaller archives after the process. Free download winqsb 64 bits. A WinRAR file compression application must be present in every modern computer toolkit.This application not only includes support for rendering almost any type of compressed file format, it also reduces file size and runs on almost all versions of Windows.Some people will argue that WinRAR is not as fast as WinZip when compressing files. If you're still stuck there, there's a simple wizard system that guides you through the process of unpacking or compressing. Also, the application allows you to save files in both.ZIP and.RAR formats, with a heap of options to speed up the compression time and reduce the file size.While many new users may be overwhelmed by the abundance of features and settings inside WinRAR, its interface does not take long to get used to. All of these combine to make WinRAR a better tool than any other tool of its kind.Declaring more compression options, higher compression rates and smaller file size than WinZip, WinRAR is no longer arguing to be the market leader in file compression.

Metastock installation problem. Discussions » Special Interest Groups » Plugins & Addons » ICE 2.62/Metastock 11 installation problem ICE 2.62/Metastock 11 installation problem - ICE 2.62/Metastock 11 installation problem Options. HelloI hope that anybody can help me out of follwing isue I have and couldn't understand at the moment: 1. I've installed MS 8.01. MetaStock is a software program that is designed to help you make better decisions about when to buy and sell in the stock, FOREX, futures, and commodities markets. MetaStock Pro is our real-time product that is powered by XENITH - without it, your MetaStock Pro product will not have data. Paste all the metastock installation files a copy in the folder, in which setup.lid file is not found. Here it is 'temp' folder now start installing from your metastock folder (not 'temp' folder) Again if you get an error with 'MSXML4.DLL' file Place the installation folder on desktop and try.

Hello,
i have her a couple of server (HP DL380 G5) with an SmartArray P400 Raid-controller. This controller is not supported(by RH) anymore by the current hpsa-driver which is be the replacment vor the older cciss-driver in rh7, centos 6.5 works fine.
So the question is, is it possible to bring the cciss-driver in the plus-kernel? if not, what would the best way to use this driver, and keep it current with the kernel-upgrades(also generate an images for install on the server, pxe-boot prefered)
regards
IngoOk, a TREMENDOUS amount of further work done only to discover that there is nothing I can *currently* do about this. Some things I have discovered with further experimentation..
1. You do not apparently need the kmod-cciss.x86_64 driver module for this to work. The hpsa module is enough.
2. There is a bug that in the hpsa module that was introduced NOV2016 as a fix for other problems (the fix created a problem). This bug is what prevents the P400 from being recognized as a driver. It also causes consistant entries in your dmesg log about an error that will not be fixed until another patch is released for the hpsa module.
What happened that prevented it from working was that the older RAID controllers started their first drive as SCSI target 0 reporting to the OS. Additionally the controller itself was also reporting 0. There was a patch created that was supposed to detect the collisions and move the controller over to slot 3 (by default) but if your controller didn't respond to SCSI v5 correctly, it wasn't detected as a controller (the P400 is old enough that it had this problem).
What this created was a situation where the P400 tried to register itself with the SCSI system and it used the same registration ID as the first drive hence causing a conflict. As such, you'd see the error:
So the controller never gets added to the device chain. The system/drives work fine (they all were correctly added using the hpsa driver as listed in my last post) but your hpacucli program won't. This means that you can't look at the SMART status, drive status, controller status, etc while the machine is running. Your only option is to look at it during the reboot/controller initialization phase.
This issue was raised as a bug and is being addressed as of JAN2017. I do not know however when the fix will be released into the kernel patches nor how long it will take to propagate down to my level. But at least I'm not spinning my wheels trying to figure this one out anymore. I can live with the constant log entries about the failed insertion, at least until the patch comes out.
So.. in summary..
I only did the 'hpsa.hpsa_simple_mode=1 hpsa.hpsa_allow_any=1' on both the install and the grub update to get things to work. It does require that your P400 firmware is >v4.0 to work (or even the hpsa can't find it). v7.22 is the last 'free' version out there that I was able to find although the latest is actually v7.24 (with fixes that I'd like, but free support from HP is difficult, even for an HP employee). Your BIOS must be dated later than 2008 for this to work as well.
Easiest solution for the firmware problems of your DL360G5? Use the Smart Firmware DVD v10.10 (last free version) located at http://h20564.www2.hpe.com/hpsc/swd/pub .. 925937f38b to burn a DVD and autoupdate with it. Running it on my machines found typically around 30 things to update (even the hard disk firmware amazingly enough). Sadly, the last patches you really want for your DL360G5 are from around 12/2012 whereas the last free update was 06/2012. If anyone has the Firmware ISO from 2013 or later, I'd love to hear from you.
Marcos