Super-slow operations with iPhone xDrive

Hi guys, sorry for posting about a problem with my first post, but, there ya go. :stuck_out_tongue:

I'm using 9.5.2.0.3660 x86 on Windows 7 32 Bit. ON my jailbroken iPhone 3gs, I have a program installed called xDrive which is basically a Samba server, allowing me to browse the phone as a network share.

Using Windows Explorer I have no problems whatsoever, but using dopus every file operation takes a long time, even to the point where dopus freezes and the program not responding message appears on the taskbar. Nothing fails outright, but it is annoying that something as simple as directory navigation should prove so problematic.

Has anyone else experienced this? Can anyone offer up some sort of explanation or solution?

Cheers, guys.

PS - is it really necessary to have a captcha on the new post page??

Try adjusting the Copy Buffer size in Preferences. Some USB devices really don't like the default size but will work much better with a smaller or larger buffer. (AFAIK there isn't any particular size that works with everything so you have to experiment a bit.)

The captcha is only for the first few posts.

Thanks Leo.

I think you've misunderstood - my problem lies with network operations.

Open \192.168.0.3\ (0 Sec)
Open \192.168.0.3\Root (0 Sec)
Open \192.168.0.3\Root\var (5-10 Sec)
Open \192.168.0.3\Root\var\mobile\ (5-10 Sec)
Open \192.168.0.3\Root\var\mobile\Media\ (5-10 Sec)

After that, any operation - be it merely clicking in the destination/source pane, right-clicking files, left-dragging files - results in the same 10 second delay with everything frozen.

I shall attempt to post a video somewhere showing what I mean.

Can you try running Process Monitor and see what it is that Opus is actually freezing on? It must be some specific function call that for some reason is particularly slow with this device.

Maybe something Opus does that Explorer doesn't based on Opus Preferences->File Operations->Copying Files settings is flipping out the iPhone? Perhaps it's worth disabling everything in there and testing?

If there's no clues from playing around with those settings - maybe also look at all options in Preferences related to network...

Ok, I ran Process Monitor, filtering for dopus*, and it captured a huge slew of registry requests, with alot of name not found errors. I've attached the logfile in native format for you. It covers a single doubleclick, until Opus became responsive again :

From \192.168.0.3\iPhoneRoot\var
To \192.168.0.3\iPhoneRoot\var\mobile

... I think. I just woke up and I've closed them already, lol. :stuck_out_tongue:

I've grabbed a video of this in action :

OpusProblem.7z

XviD, low quality yet clear enough I think.
Logfile.zip (335 KB)

steje : I can't see how, as it is affecting ANY operation, not just copying. Even left-button dragging, which I do on bad DVDs to stop it trying to populate the context menu.

Any idea what's causing it, guys? Not trying to push, just curious.

Dunno... i see what you mean - guess I just read "file operations" and thought it was restricted to that - but you did indeed explain that it was affecting other things. So it's even just simply "navigating" the folders through the xDrive Samba server that looks ridiculously slow. Not sure what Opus could be doing differently than Explorer in that regard... though perhaps you could turn off anything obvious in Opus that is not present in Explorers view. You probably had the "Size" column turned on in Explorer but just scrolled to the right perhaps? If not, try disabling that in Opus as well as your Opus statusbar... essentially, try and ensure that Opus is not doing anything (even if it seems "mundane") that Explorer doesn't seem to be doing in order to see if that helps isolate the cause to something definitive.

Without an iPhone to test with (and not wanting to pay for xDrive :slight_smile:) I don't think anyone will be able to try and repro. You could open an official support request through GPSoft to see if they can help - but it would be good to at least exhaust all possible troubleshooting to help narrow down the issue...