Actually, I cannot reproduce this. What is your operating system? 32/64 bit? Service Pack?

Hello,

I've just tried this on WinXP_SP3, DriveApp 2.9.3.0.
I don't see this behavior.

Can you ensure your driveapp version is 2.9.3.0 as well.

Thank

The only limit to the Pogoplug is your imagination... and C skills... and linux skills. ^_^ h\t\tp://download.pogoplug.com/opensource/pogoplug-gcc.tar.bz2

Sorry, this was poor choice of words. Toks was asking which version of Pogoplug software you have. You can find this by right-clicking on the Pogoplug icon in the lower-right hand side of your tray. It sounds like you have 2.9.3.

What we are seeing with all of our windows operating systems is:

- Turn on Remote Access with remote access shares that have not had their media scanned. hbplug.exe process starts consuming CPU resources as it scans media and in the Web UI, these Remote Access shares show up, and the media scanning operation for them can be viewed in Media Settings

- Turn off Remote Access and hbplug.exe stops consuming CPU. Also, these Remote Access shares can no longer be seen in the Web UI - either under files or in Media Settings.

When you say that your drives are still scanning, do you mean that hbplug.exe is still consuming resources, or that you can still see the remote access shares and their tasks listed in the Web UI, or both? If neither of these, how are you verifying that your remote access shares are still being "indexed"?

Morac said: What I noticed was that even though I turned of sharing and even shutdown the pogoplug service from the system tray, my hard drive was still thrashing (laptop drive so it's a 5400 RPM). I ran Process Monitor and saw that hbplug.exe was constantly accessing files which appeared to be indexing. Note at this point, the remote shares did not show up (offline) and the network connection icon added by Pogoplug was showing as disconnected. Basically sharing was off. Also hbplug.exe wasn't using much CPU time. So basically I used Process Manager and the fact that my drive was going crazy to verify that indexing was still occurring. You can also check the last modified time on the .cedata files being written to. I let it run overnight and it had finished or at least it had stopped indexing by the time I woke up.

I had this exact same problem. Got tired of it using the hard drive 100% of the time & uninstalled the software. Then came to the forums & seen your post. I didn't know it was indexing the shared folders & that was what was causing the hard drive thrashing. Anyway, on my computer my CPU resources were also low after I disabled sharing just like yours. I have a HP Pavilion a1600n Media Center PC. I'm running Windows XP Media Center Edition Version 2002 Service Pack 3. I should have all the latest service packs & security updates installed. I reinstalled the beta to get the version, it's 2.9.3.0. Also, this time I only shared a folder that had 15 files & only used 6MB of space. The thrashing pretty much stopped, but it still accesses the hard drive in little spurts. I had originally shared the My Documents folder which had 14,570 files across 1,187 folders & used 24.2gb of space. If indexing is the cause of the problem, then I highly recommend display a big warning message that indexing can cause heavy continued use of your hard drive even if you shutdown Pogoplug & stop the sharing. Is it possible that you could schedule the indexing to be done overnight? Doing it right after your install seems like could frustrate a lot of users especially if they are like me & have a large amount of files & folders to index. They'll probably do the same thing I did & uninstall the program. And I wouldn't blame them.

Tommy McClain

We're looking into different options with indexing, and are taking all this feedback into consideration.

@Morac, as far as the drive indexing when Remote Access is turned off, we are still not able to reproduce that; even Process Monitor shows the hbplug access stop. We will continue to investigate what might be going on there.

I had the same issue on my Mac.
I stopped the drive app but the service kept on going using 95%-100% of cpu power.
I restarted the drive software turned off pogoplug remote access. Not sure if it was the scanning process of folders but the cpu was still being used at 100% by the pogoplug service.
I removed all folders shown by default in the list for remote access and added only one folder of my own, with a small number of files. Then I turned remote access back on.
The drive software is now using normal amount of resources.

It is not strange if the software is indexing all these files at first launch and that it takes some time, but what seems weird is that the process is not stopped when quitting the app or turning off remote access.