Recent content by UKAspie

  1. UKAspie

    Windows 10 DirectX VertexShader 2.0 is not supported

    Good idea, but when I checked "DirectPlay" it was already enabled. This is probably a temporary fix, but re-installing the video card driver, followed by: DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow has worked.
  2. UKAspie

    Windows 10 DirectX VertexShader 2.0 is not supported

    Oh dear - the problem has come back, and this time the 2010 version doesn't fix it.
  3. UKAspie

    Windows 10 DirectX VertexShader 2.0 is not supported

    I'm somewhat behind the times in games ... Bugs aren't so bad if there is a known work-around. My concern now is if I'll have to re-install the good version of DirectX every time Windows decides to do a non-optional 'update'.
  4. UKAspie

    Windows 10 DirectX VertexShader 2.0 is not supported

    I've found a fix - I've installed the 2010 version of DirectX. This leaves unanswered the question of whether the latest version is buggy or a "Break AMD Graphics" version.
  5. UKAspie

    Windows 10 DirectX VertexShader 2.0 is not supported

    After the latest huge pile of Windows Updates I get this error message when I try to run a game that was previously working. I've re-installed DirectX and the driver for the graphics card - not change. Is it possible to roll back to a working version of DirectX?
  6. UKAspie

    Windows 10 One computer won't talk to the others

    I've found the problem - or at least the main one. The network was correctly set to Private, but the firewall hadn't picked it up and was set to Public. Now the Win-10 systems can see each other and the Linux system. The Linux system still can't use shares on the Win-10 systems.
  7. UKAspie

    Windows 10 One computer won't talk to the others

    No - 70 and 74 are Win-10. 30 is Linux.
  8. UKAspie

    Windows 10 One computer won't talk to the others

    I don't see how to attach a file to a PM here, but I have had a try with Wireshark on one system. On an outgoing ping I can see an IPv6 ARP request and response followed by an IPv4 ping but no response. On an incoming ping I can see the IPv6 ARP messages but no ping. When I ping from the...
  9. UKAspie

    Windows 10 One computer won't talk to the others

    Yes, the default "upgrade" pushed out to XP users is Windows 10 Home. W10 Homegroup isn't usable as it is designed to block the other OSes I use. Shares don't work properly on a mixed network if Windows is allowed to use Homegroup, but fortunately even W10 can use normal shares. This sounds...
  10. UKAspie

    Windows 10 One computer won't talk to the others

    I don't know if this adds anything useful, but all systems can ping an XP machine.
  11. UKAspie

    Windows 10 One computer won't talk to the others

    Linux Mint has a filestore "Properties" pane that looks a bit like the Windows one, and includes a "Share this folder" check box. I didn't dive into the details so it probably is using Samba. I said in my first post, but not clearly - this was all working with the old router but doesn't work...
  12. UKAspie

    Windows 10 One computer won't talk to the others

    The network is now three systems. Two are running Windows 10 with automatic updates. The third is running Linux Mint. The topology is three computers connected to the broadband router by RJ45. No server or proxy. The "models" of the Win-10 boxes is "homebrew". One and two can ping three...
  13. UKAspie

    Windows 10 One computer won't talk to the others

    Three Windows computers on the LAN. Internet upgrade requiring new router. All three have Internet access, two can talk to each other but the third can't see the two and they can't see it. Any ideas?
Back
Top