Jump to content











Photo
- - - - -

"Device is not ready" problem with uTorrent


  • Please log in to reply
3 replies to this topic

#1 Victor Milovanov

Victor Milovanov

    Newbie

  • Members
  • 15 posts
  •  
    United States

Posted 14 September 2012 - 10:56 AM

I'm using ImDisk + Devio + my custom devio provider. All other programs function normally, but uTorrent often stops downloading to my virtual disk with "Error: WriteToDisk: The device is not ready."
The problem does not exist on ordinary virtual disk vhd image mounted with ImDisk control panel applet.
What can be a cause for this error?

#2 Olof Lagerkvist

Olof Lagerkvist

    Gold Member

  • Developer
  • 1365 posts
  • Location:Borås, Sweden
  •  
    Sweden

Posted 14 September 2012 - 11:06 AM

Hard to say. Could you try to log requests and your responses and see if there is any particular things that could give clues, such as very large buffer sizes etc. Otherwise I would say that a kernel debugger with a version of ImDisk with debug output is the only practical way to debug issues like this.

#3 Victor Milovanov

Victor Milovanov

    Newbie

  • Members
  • 15 posts
  •  
    United States

Posted 14 September 2012 - 11:10 AM

Hard to say. Could you try to log requests and your responses and see if there is any particular things that could give clues, such as very large buffer sizes etc. Otherwise I would say that a kernel debugger with a version of ImDisk with debug output is the only practical way to debug issues like this.

Do you mean to log read and write requests in DevioManagedProvider implementation?

#4 Olof Lagerkvist

Olof Lagerkvist

    Gold Member

  • Developer
  • 1365 posts
  • Location:Borås, Sweden
  •  
    Sweden

Posted 14 September 2012 - 11:25 AM

Yes, to make sure that everything is handled correctly. Even for example if you get unexpected buffer sizes and similar. You can also check and see if it makes any difference to switch to TCP/IP proxy communication instead of shared memory communication (if that is what you are currently using). Shared memory communication itself introduces a largest possible buffer limitation because of the size of the shared memory buffer. There is nothing like that in the TCP/IP implementation.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users