remotevisitor

Members
  • Posts

    412
  • Joined

  • Last visited

Report Comments posted by remotevisitor

  1. Bug1 is a windows feature .... suggest you do a google search on "DontPrettyPath Windows".

     

    i suspect bug2 is possibly deliberate in order to make to remote end of the share (eg your windows system) take notice that the share name has actually changed.    
     

    Because windows (by default) is case insensitive a share called "tv" and "TV" is the same so the rename would be ignored.  By force the rename to go via a different name as you did will make the remote end take notice of the rename.

  2. Using the command xrandr ...

     

    OK system: AMD A10-6800K APU with Radeon™ HD Graphics @ 4100 MHz shows

    Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200
    default connected 1920x1200+0+0 0mm x 0mm
       1920x1200      0.00*

    while the problem system: AMD A4-3300 APU with Radeon™ HD Graphics @ 2500 MHz

    Screen 0: minimum 720 x 400, current 720 x 400, maximum 720 x 400
    default connected 720x400+0+0 0mm x 0mm
       720x400        0.00*

    They are connecting to the same monitor.

  3. I have 2 unRaid servers running 6.7 which are connected to the same monitor via a KVM.

     

    One server displays the GUI at the normal high resolution of the monitor, and the other server displays the GUI at the low resolution.

     

    Several releases back both displayed the GUI at the normal high resolution.

     

    Although I do suspect that the response the monitor gives to its capabilities, it possibly also depends on the something in the video driver, 

     

  4. And on that nfs issue you linked to, the last posting to it was from Tom over 2 weeks ago asking for a retest and posting of a diagnostics.zip on a failing system.   As none were forthcoming I guess Tom is assuming the changes in the last update fixed the problem .... hence I assume Tom question "What NFS problem?".

     

    Earlier in that thread Tom had said they were unable to reproduce the problem on their systems so were reliant on affected users to supply diagnostics for investigating the problem further.

    • Upvote 1
  5. I guess one question is when a shutdown condition of 20% is set, is the condition monitored to initiate the shutdown performed by the UPS itself or by the software on Unraid?

     

    The Original poster also hasn’t mentioned what make/model of UPS is being used, which might be relevant if the problem is actually in the UPS firmware not correctly supporting %usage left.

     

    Suggestion .... do you have another system which you can install the UPS manufactures official software and plug the UPS into that and set a % condition and see if it works as expected ... this would help to eliminate the UPS itself as being the problem.