I have been experimenting further and found out some more :
-My setup is between 2 windows PC's, server is WinXP and client is Win7.
-When I start XBMC and navigate to a folder on the (suspended) server XBMC will always wake server and normally (but not always) read the contents of the folder.
-If I reboot server and then immediately put it into suspend and THEN wake it with the XBMC client it will resume but consistently fail to read the folder !
-Having a setup with a repeatable problem I have investigated what is root cause and identified that as being inside Windows networking itself :
FindFirstFileW fails if called to soon after server has started the process of resuming from suspend mode, it goes into timeout (error 53) after ~50 secs whereas on a successful connection it will return much faster.
This behavior may very well be dependent on OS (different with Linux or other flavors of Windows)
-I have tried adding a loop to read the folder twice when it fails but that does not help, it fails on second attempt as well
-I then tried adding a wait period after waking the server as has been suggested by several and that DID fix the problem for my setup. Both 10 secs and 8 secs seem enough to start successfully, I have not tried lower.
Therefore I have now submitted a new modified patch to the ticket and hope somebody will try it out
- new 'wait' parameter in advancedsettings.xml :
Code:
<onaccesswakeup>
<wakeup>
<host>10.0.0.6</host>
<mac>00:15:f2:1d:df:1e</mac>
<tmout>700</tmout>
<wait>8</wait>
</wakeup>
</onaccesswakeup>
-XBMC will also display the 'working..' dialogue while doing this wait
-The fix I showed in my last post is also included - this ensures that the 'working..' dialogue is shown while XBMC waits for reply from server