Reply to thread

Message

<blockquote data-quote="joz" data-source="post: 514588" data-attributes="member: 70244">First of all thanks a lot for your work on this plugin! Just what I've been looking for. Well ofcourse I do have some suggestions <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />1) in my usage scenario it would be nicer to have the client tool be a MP process plugin. Why? Cause I use desktop PCs as clients and when MP is not running, those clients would not have to keep the server awake.2) Would it be somehow possible to wake the server if a clients accesing stuff thru network shares? That would be really cool, for me that is. For example my server has a computername of //server. Whenever a client tries to access //server this tool wil send a WOL package if the server is not already awake (or just always, sending wol when server is on won't mather anyways)Just suggestions, would make it even more usable for me.</blockquote>

[QUOTE="joz, post: 514588, member: 70244"] First of all thanks a lot for your work on this plugin! Just what I've been looking for. Well ofcourse I do have some suggestions :) 1) in my usage scenario it would be nicer to have the client tool be a MP process plugin. Why? Cause I use desktop PCs as clients and when MP is not running, those clients would not have to keep the server awake. 2) Would it be somehow possible to wake the server if a clients accesing stuff thru network shares? That would be really cool, for me that is. For example my server has a computername of //server. Whenever a client tries to access //server this tool wil send a WOL package if the server is not already awake (or just always, sending wol when server is on won't mather anyways) Just suggestions, would make it even more usable for me. [/QUOTE]

Verification