@infinidim & others with a working set up. I am curious to find out how its working out.
My EC setup seems to be working. Cache fills up. I see speed changes in apps.
But I am not so satisfied with boot speed.
There are two stages to boot up. First with the windows logo and circling dots. Then enter password to get to desktop when you also have circling dots. I am gauging bootup speed based on number of complete cycles of the dots on both stages. (A complete cycle = 2 cycles of the dots when the dots disappear before reappearing. Reappearance is the start of the next complete cycle).
–First stage takes two and a half complete cycles (Dots circling around five times+) (Doesn’t feel like EC is working fully)
–Second stage takes around one complete cycle. At this tage EC seems to be working as I am jumping straight to desktop skipping an additional blank screen which was a third phase before EC started working.
How many complete cycles of the dots are you seeing with EC?
My upgrade to Windows 10 from Windows 7 deluxe home 64 on a HP desktop with a 32GB Sandisk ReadyCache SSD worked flawlessly. First before I started the Windows upgrade I uninstalled the readycache software & driver. Second ran the upgrade to Windows 10. After the upgrade was complete I installed ReadyCache ver. 1.3.2 and every thing works as it should. I have been folowing this forum after my first attempt at the Windows 10 failed to work with ReadyCache and I went back to Windows 7 using a disk image that I made before the upgrade. I used EaseUS todo backup free to make a disk image. As for performance I see a definate improvement by using the cache. I hope that Sandisk will optimize the driver for Windows 10 sometime soon, but for now I am satisfied. With the prices of SSD disks falling I am planning to purchace one and the cache ssd will be no longer matter.
@infinidim & others with a working set up. I am curious to find out how its working out.
My EC setup seems to be working. Cache fills up. I see speed changes in apps.
But I am not so satisfied with boot speed.
There are two stages to boot up. First with the windows logo and circling dots. Then enter password to get to desktop when you also have circling dots. I am gauging bootup speed based on number of complete cycles of the dots on both stages. (A complete cycle = 2 cycles of the dots when the dots disappear before reappearing. Reappearance is the start of the next complete cycle).
–First stage takes two and a half complete cycles (Dots circling around five times+) (Doesn’t feel like EC is working fully)
–Second stage takes around one complete cycle. At this tage EC seems to be working as I am jumping straight to desktop skipping an additional blank screen which was a third phase before EC started working.
How many complete cycles of the dots are you seeing with EC?
RedCache,
I am seeing very similiar things to you in boot speed.
I do have to say that the apps are running faster and also some of the operating system oprions as well - Store is almost
instantaneous, Settings the same, Excel and Word are also very fast as well, Outlook is a bit slower but faster than not having ReadyCache working (think that is because of the loading of the “addins”.
Assuming you have a W10 system with ReadyCache working and fast boot enabled, there’s a way to further decrease Windows load time if your system is suitable. Windows 10 can compress system files, and should automatically do it if it detects a small SSD as OS drive.
This uses a very light compression algorithm, and can also be used on a HDD, so that it needs to spend less time reading, with also the slight advantage of less cached lbas on the cache drive. The downside is a little extra CPU occupancy when accessing system files, but overall the decompression time of all of those acessed files to RAM can take less time than the slow hdd loading extra KBs.
To verify current state, on admin prompt you do:
compact /CompactOS:query
To enable OS files compression you do:
compact /CompactOS:always
To disable OS files compression you do:
compact /CompactOS:never
Both enabling and disabling takes some time, and probably it’s a very bad ideia to interrupt both processes. End the end, you’ll be notified of the achieved compression ratio (usually close to 1.6:1).
To see results, you must give it time for ReadyCache to cache sensitive boot files again (three restarts after waiting some minutes after each to fill cache should do). After that, when the Windows own fast boot works in conjunction this compression, it can give you even faster boot times.
Not every computer is the same and, in some PC’s where there’s less CPU to spare, it can have a negative effect. But then, it’s easy to revert.
There was a manual fix that was posted few weeks ago. If that doesn’t work, please let us know and we’ll send you an installer that should fix it.
Since, this problem occured on early Windows 10 adopters, we are only releasing a manual fix at this time. This issue should not occure if you upgraded to Windows 10 recently.
The Win8.1 to Win10 upgrade for early adapter can possibly cause the folder to be removed, solution is to copy the files from the Windows.old path and attempt a manual fix above. There is possbly some interference from the account permission, so you need to STOP the ExpressCache service so that it would uninstall fully. This doesn’t appear to happen with a Win 10 upgrade THEN putting in the ReadyCache after. If you don’t have the Windows.old file, Sandisk support can provide that, they should just put up a download link for it, I’m not gonna do it because I dont’ work for Sandsik.
You need to remove as many files as you can from your %tmp% path before you start, for some reason the extractor doesn’t overwrite the files OR is picking up some old files from the %tmp% path, and the installation will go wrong. (in my case, eccmd returns license issue AND ExpressApp launch issue). While you are at it, delete the Condusiv folder under Program Files as well just to be clean.
You want to delete of the partition on the ReadyCache drive, after the installation you will see a new partition being created, that’s usually a good step to verify if the installation is even working.
Hope these tips would help. It took me a long while crawling numerous forums and finally solved this.
I have faced the same (Windows 7 upgraded to Windows 10 adopter) issue and I have been patiently waiting for the fix just like the others on this forum. I must have tried the manual fix a few times but it doesn’t work. It gives me the dreaded message about the missing msihelper.dll file. I cannot uninstall the program from the control panel due to the same missing dll error.
If there is a custom installer file to fix this error I would love to have it.