Cache building problem

By hau | December 26th, 2008 | 9:33 pm

Hello, I am using b482 and try to add the USB devices and the program detect the wrong size of  USB drive

1_a

So, when I am using this size to build the Cache drive, it cannot build the cache more than 1 %.

I think it makes sense that cannot build the Cache.

21

After adjust the size matched to my USB free space, it can work normally.

But maybe it is my problem because I am not using standard USB driver for this USB. I am using Hitachi Global Storage Driver such that I can partition the USB driver with different driver letter.

4

THANKS

5 Responses to “Cache building problem”

  1. fehmi
    Dec 27, 2008

    You do not have to use any special driver to assign different drive letters. Just go to Control Panel -> Administrative Tools -> Computer Management -> Disk Management and find the drive you want to assign a different drive letter. When you right click on that drive, you will see the option to change the drive letter.


  2. fastest963
    Dec 27, 2008

    @fehmi that didn’t really answer his whole question about how the space is being calculated wrong…


  3. fehmi
    Dec 27, 2008

    Correct me if I am wrong, the Patriot Memory USB Device is a flash drive, isn’t it? Judging from the screenshots, eBoostr thinks that it is a hard disk. Based on my experience, if the default Microsoft driver works for a generic device (such as a storage medium), you should stick to it. Using a third party driver brings headache…


  4. Andrey Zarudnev
    Dec 29, 2008

    Space is calculate correctly. Please note that 1KB is 1024 bytes. Thus we get:
    4,375,748,608 bytes / 1024 = 4,273,192 KB
    4,273,192 KB / 1024 = 4,173.0390625 MB

    1% cache fill is OK at the beginning. As eBoostr will gather more statistics your cache will be filled up with more data.


  5. hau
    Dec 29, 2008

    Thanks for your reply.
    I have tried to use b482 with this size(4173MB) of USB device, the cache is still 1% and did not increase after I used 5 hours. So, I tried to decrease the cache size to 4000MB and build the cache again, it becomes 70% cached.
    In the begining, I guess that would it be calculated the wrong cache size.