Cache is not recognized until the flash drive is accessed
Already posted the issue on the thread above for eBoostr 3.0.and it still persists in v4.0.
On every boot of the computer, the eBoostr control panel shows that no cache drives are active until I launch My Computer for the first time. I am pretty sure that eBoostr is not functioning as I neither see the animated icon nor feel any speed boost before the drive is properly shown on the eBoostr control panel. It seems that for some reason I have to access the cache drive before eBoostr recognizes it because accessing the flash drive using any program’s file dialog seems to fix the problem.
I have narrowed down the problem to an incompatibility issue with NOD32’s egui.exe. If I disable the executable via msconfig, eBoostr correctly recognizes the cache drive. Otherwise, I need to launch My Computer each time the system reboots.
Same issue with NOD32 3.0.684.0 and 4.0.437.0 (tried putting both eBoostr’s path and the cache drive in the exclusion list but it didn’t help).
Running Windows XP SP3, all security patches are up-to-date
Tags: flash drive, NOD32, removable drive
Sep 14, 2009
So your Anti virus is causing the issue? The issue is not a compatibility issue but a safe feature in EST. From what I gather is, EST will not let others read any USB untill the user has ask to do so. This way a virus on the computer will not spread to a usb or vis vers.
Sep 16, 2009
@fehmi,
I have tried to reproduce this behaviour on Windows 7 with NOD32 4.0.437.0
It totally blocks access to the flash drive and it is not activated even after trying an access from My Computer.
Can you please check your setting for the following check box in NOD32?
Sep 16, 2009
@ Andrey:
That box is not checked in NOD32 v4 (I don’t remember whether v3 had such an option). I just need to launch My Computer for eBoostr to recognize the flash drive.
Sep 16, 2009
I’m using NOD32 v4 too. It has this option “block removable media” too. It is unchecked and after full startup of system, Flash drive is “released” and normally recognised automatically. It does mean that when using NOD only RAM-Cached Devices will work and boost the startup-sequence. Flash drives are locked untill NOD completes it usual startup-routine…
Sep 17, 2009
In my tests on Windows 7 — everything was working fine if I disable this check box. I mean all drives are visible and working right from the beginning without any additional accesses.
Sep 17, 2009
I’m running it on Windows XP SP3…
Sep 17, 2009
@ medeni73, thanks, I understood. Seems to be XP specific issue.
Oct 31, 2009
I no longer experience this problem on build 538. I didn’t make any configuration changes or update NOD32 so I guess it was the new eBoostr build that did the trick!