Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


SD73

Member
  • Content Count

    170
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

24 Excellent

About SD73

Profile Information

  • OS
    XP Home
  • Country

Recent Profile Visitors

1,173 profile views
  1. I am using RealVNC. It's all in the same LAN so no NAT'ing on my end. They may have a cloud solution too, but I haven't used it and if they do it may not be compatible with their legacy products. You'll have to check. As we're finding out, going the XP route and sticking with it is just going to keep getting more and more of a challenge. Good luck.
  2. I've been using the venerable free version of VNC. They have their last working XP update still posted last I checked and you can use a more recent version for you master pc if it's a more modern o/s. I am not using it for a 2 way communication, but that's because I don't need that. You may want to check it out yourself to see if you can run both from your xp side. I suspect you can, but it's not something I've ever needed.
  3. Thanks for your input Thanks for your input. I'm glad it was solvable with a relatively easy fix. It never occurred to me to make the Linux/Windows connection to the problem until I posted the question.
  4. Any word on how well this works with our XP systems? I've been looking at hardening up mine a bit since our patches stopped and I used to have a good relationship with this stuff until one of the more recent patches broke it.
  5. Unfortunately, Linux Mint 19.1 didn't have a little check that I could find. I went with the procedure in the above link. 1-put the real time clock on the motherboard into local time. Linux will store the time in local time, just like Windows does: timedatectl set-local-rtc 1 --adjust-system-clock 2-To check your current settings, run: timedatectl * If you ever want to undo this change, run the following command: timedatectl set-local-rtc 0 --adjust-system-clock
  6. Thank you. I will have to check that out. Even with the registry hack the above method reverted back to the wrong time.
  7. I *THINK* I found the solution. And it's thanks to you mentioning you have the same dual boot issue so I'll share this with you to see if the fix works for you as well if you'd like to try. The info was at this link and listed as working with Windows 7. It works for us old XP'rs as well it appears. They also have a Linux sided solution but you'd have to repeat that procedure when Daylight Savings Time occurs. https://www.howtogeek.com/323390/how-to-fix-windows-and-linux-showing-different-times-when-dual-booting/ 1- Navigate to the following key in the left pane of the registry editor: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation 2- Right-click the “TimeZoneInformation” key and select New > DWORD Value. 3-Name your new value RealTimeIsUniversal. 4-Double-click the RealTimeIsUniversal value you just created, set is value data to 1, and click “OK”. 5- You’re now done, and you can close the Registry Editor. Windows will store the time in UTC, just like Linux does. *If you ever want to undo this change, return to this location in the registry, right-click the RealTimeIsUniversal value you added, and delete it from your registry.
  8. Well thanks. At least for now I know I'm not going crazy.
  9. So I've noticed an issue for the last few months. I figure I'll run it past the usual suspects while I still have the chance. My XP machine is a dual boot setup. I usually run it in Linux Mint where I don't notice the problem. However when I boot into XP on occasion it will have the wrong time by 7 hours in the future. The timezone is setup correctly. I've tried changing time servers and that does not appear to have helped. I don't think it's the cmos battery as I haven't notice the problem while I'm in Linux. After I do a re-sync with the Time Server it does get back on track. Any ideas?
  10. Dude, I can't leave. Even if it's just to come here for a monthly XP'ers reunion. I'll be hanging on as long as possible. I've made some good backups using macrium reflect that should keep me in business in a worst case scenario event. Other than that, if there were a dang easy way we could incorporate our thread with a monthly dues to get those corporate updates they're still publishing I'd be doing the happy dance.
  11. I'm almost sad to report, all 14 installed without incident. sniff sniff...I'm going to miss the excitement of troubleshooting these things with you guys.
  12. The official end of support may be near, but they'll have to pry my XP keyboard from my cold dead hands.
  13. I am happy to report Automatic Updates found all 14 updates and they all installed without incident. One more Tuesday left for those playing along at home.
  14. v2 did the trick for me. I had no issues with the Office updates either; however, I'm using the 2003 version.
×
×
  • Create New...