merlin

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by merlin

  1. Merlin, the registry "fix" ONLY works in cases where there's just plain text/no images/random layout in the UI. If you've got a completely blank UI - which you will have if you're using XP - this fix won't work.

    In your case, as you're using Windows XP (apologies, I missed that bit of critical info in your original post!), I'm afraid you're out of luck - Sync 1.4 isn't compatible with Windows XP, due to the fact that XP can't run anything higher than IE8.

    You would therefore need to use Sync 1.3.109 instead.

     

    OK, so I'm sad because to run BTSync at my work (WXP), I need the "Proxy" functionality...

    Also I want to use approvals for security !

  2. Not that I would retract anything I suggested so far, but I have actually debugged and resolved this issue [without the source code] - BTSync can send a cheque when they actually make money from it :)

     

    First, I simply assumed BTSync is not directly responsible and that it is the IE plugin's fault - which seems a safe assumption. The IE plugin works pretty straightforward, you simply give it files and it serves them.  Also, the symptoms seems pretty much that CSS was not being served to the embedded browser. I could especially reinforce this line of thinking when I also started looking at Syncthing and got almost an identical issue, but this time on three browsers FF, IE and Chrome.   So if neither BTSync and Syncthing explicitly set their CSS mimes in their HTML head tags, on windows, the registry would be used to determine the mimetype.  So I checked.

     

    For whatever reason, it seems there are a lot of Windows machines for which the HKCR\\.css type is set to text/plain - which according to W3C spec would be considered invalid by the UA (browsers).  I corrected this and suddenly Syncthing was up and running on 3 different browsers.  Then upgraded BTSync to 1.4 again and boom - now works like a charm!

     

    Suggestions:

    • I'll keep to my mantra of adding a HTTP daemon and CLI to windows distro instead of embedding IE
    • However, for now, BT should update 1.4 to explicitly set the type attr of the HTML linking the CSS so BTSync is independent of the OS mimetypes - minimizing points of failure
    • And in the meantime, win users could simply correct their registry mimetype to get BTSync 1.4 to work.

     

    Enjoy!

     

    Good news !

     

    But, how to make these changes in the registry on Windows XP?

    (HKCR\\.css does not exist)

     

    Thanks