Jump to content

Dave-H

Super Moderator
 View Profile  See their activity

  • Posts

    5,078

  • Joined

  • Last visited

  • Days Won

    66

  • Donations

    0.00 USD 

  • Country

    United Kingdom

 Content Type 

Everything posted by Dave-H

  1. Dave-H
    My best wishes for a full recovery to all who have had COVID, but back on topic now please.
  2. Dave-H
    The point is that on XP 360Chrome 13.x actually still works properly with the vast majority of websites. How long that will last remains to be seen of course! Yes, it's a resource hog, so not great for everybody, but on my machine it's very fast and stable.
  3. Dave-H
    I used to just have 98 and XP, which was no problem dual booting of course. When I added Windows 8/8.1 to the system, and later 10, originally I had to go into the BIOS setup on boot and change the first boot drive to get into it. The issue was that both Windows 98 and Windows 10 are on drive C: (Windows XP is on D:). Thanks to advice on MSFN I was recommended to use grub4dos to get over that problem, and what I now have is two OS menus. When I boot I'm offered XP as default, or 98/10 as a menu choice. If I select that, I'm offered the Windows 98 boot menu, which has 98 or 10 on it, and I choose the one I want. This works fine with no reboot necessary.
  4. Dave-H
    I hope it works for you. I've now changed my netbook, to a Lenovo IdeaPad, which already has a Bluetooth capable module fitted. The 6235ANHMW would be better though, but unfortunately the BIOS will not allow it to work as it's not in Lenovo's BIOS 'whitelist'!
  5. Dave-H
    LOL! We used to have two types of 'round pin' plugs when I was a kid, 5A ones for lower rated stuff, and 15A ones for heavy stuff, the latter were really big and heavy! I think the idea behind the present 1960s replacement 'square pin' plugs (the pins aren't actually square of course, but that's what they were called!) was that they were powerful enough but light enough not to need two different types. They were fine for the heavy stuff like electric fires, but not too big and heavy to use for the lighter stuff like table lamps. Whether they got the compromise right is a matter of opinion of course! The other plus point was that we got rid of reversible two pin plugs and sockets, which could be dangerous with the 'live chassis' TVs and radios which were still around at the time! I don't mind the European standard ones, but the American standard 'low current' plugs and sockets always seem really flimsy to me! Anyway, this is completely off-topic!
  6. Dave-H
    I'm not asking you to change them of course, but I've always wondered why, if you are German, that you put the dates in your posts in American format, not European format? The actual file names, I'm pleased to say, are the 'correct' way around!
  7. Dave-H
    Just as an off-topic aside, my latest 64 bit Firefox on Windows 10 only made 51.3 on Speedometer, and the latest Edge made 72.1. The mind boggles as to what you must have to have to get into the red zone on the speedometer graphic! Perhaps it's just for show......
  8. Dave-H
    Give it a try, as I said you can put whatever you like there. The string I quoted is what I have, as supplied, and I've never had a need to alter it.
  9. Dave-H
    Yes, you need to add (for instance) - --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36" Obviously you can modify the actual string between the quotation marks to be whatever you need.
  10. Dave-H
    It's actually 360Loader.ini, and it should be in 360Chrome's folder in Program Files, with 360Loader.exe and the Chrome folder.
  11. Dave-H
    Huge RAM use by 360Chrome 13.5 here too of course. No surprise to me, but fortunately it's still pretty fast on my system and doesn't seem to cause problems with anything else. With very few exceptions, websites work with it, which is the important thing!
  12. Dave-H
    Thanks for the heads-up, topic locked. Continues here -
  13. Dave-H
    Off-topic of course, but I'm still using a Microsoft 'Natural Keyboard' which must be around 20 years old! It's been dismantled, cleaned, and re-assembled at least four times during its life, and it's still working perfectly. The only sign of wear is a slight fading of the label on the'E' key, the most used of course (in English). It's built like a battleship, nothing like the cheap rubbish you usually get now, which falls apart in no time!
  14. Dave-H
    Have you tried replacing all of the registry files from the backup? They would normally all be written to simultaneously I would have thought, and the system may not like the fact that the SYSTEM hive has a different timestamp to the others. Just a thought.
  15. Dave-H
    Sorry yes! I monitored it for quite a while, intending to report back, but never got around to actually doing it! Yes, against all my expectations, the 'incorrect today' issue seems to be fixed. Quite why a one-hour discrepancy in the time that the browser thinks it is should cause that is still a bit of a mystery to me, but it obviously was the cause! I'll probably just set the time back an hour manually on the morning of the 30th, by changing the timezone back to London, and carry on doing that manual adjustment in the future when the clocks change.
  16. Dave-H
    @roytam1 In the past we have made a new thread here once the current one has gone over 200 pages, which this one now has! When you next publish new builds, could you make a new 'My Browser Builds (Part 4)' thread and use them for the first post? I will then close this thread. Thanks, Dave.
  17. Dave-H
    Back on topic now please guys.
  18. Dave-H
    Late response, but the yelp.com site seems to be working fine for me in 360Chrome 13.5.
  19. Dave-H
    OK, I've switched off the automatic DST adjustment, and set my timezone to Paris (where I've just been on holiday!) Everything looks fine, and as expected 360Chrome is now showing the correct timestamp for history entries. I'll let you know if it gets rid of the 'incorrect today' issue too, it's OK at the moment!
  20. Dave-H
    That's exactly the error message I got when I tried to use Avast some years ago. Although the version I was using was supposed to work on XP, I never succeeded in getting it to work, despite a lot of help from the Avast technical support people. We just eventually gave up as we couldn't find the answer, and I ended up using Malwarebytes Premium, which I'm still using to this day. POSReady updates, I hear you cry? Well perhaps, but we'll never now know!
  21. Dave-H
    I do understand the DST problem in 360Chrome, and as you'd expect, it's recording all the history items an hour adrift. That's not a big problem as far as I'm concerned, and I can't see any problem anywhere else. What I don't understand is why it won't display the history for the current day, and thinks that 'yesterday is today'! Surely the DST problem wouldn't cause that? Even more puzzling is how it seems to come good sometimes for a day or two, and then goes wrong again. I will wait and see what happens at the end of the month when we revert to GMT. The first problem I would expect to disappear, but the second one, I don't know!
  22. Dave-H
    My history has now gone wrong again, that didn't last long! As you can see, I now have two (identical) entries for Sunday, October 2nd, and no entry for the current day, Monday, October 3rd.
  23. Dave-H
    You can certainly load them from .crx files, I've done it several times. You have to be in developer mode to see the extra buttons. It may be that just dragging the file to the extensions window may work, I can't remember.
  24. Dave-H
    Just to chime in now I'm back from being away for six days, my 360Chrome is now again showing the correct day as 'today'. How long this will last for remains to be seen! As expected though, the timestamp on all the entries is an hour out.
  25. Dave-H
    Thank you very much, I think that shows the problem! Here's the page on 360Chrome - And here it is on Firefox 52.9.1 ESR - As you can see, they are an hour adrift, and the correct local time is being shown by FF 52.9, not 360Chrome. It's obviously a DST problem as you say, and it will almost certainly come good at the end of October when we go back to using GMT in the UK. However, where is 360Chrome getting this incorrect timestamp from, when everything else on the system as far as I can see is showing the time correctly? I will certainly investigate that registry changing article, but as I am away from home for the next week, it will have to wait until next weekend I'm afraid before I can do any experimentation. I wouldn't mind betting that 360Chrome is somehow reading the time from before the DST offset is applied, if that's possible, and that may well be because 360Chrome doesn't take DST into account as China doesn't use it. I realise that still doesn't explain why I appear to be the only one with the problem of course! Thanks again, that is extremely helpful, but still just as puzzling! Cheers, Dave.
×
×
  • Create New...