I have 3 laptops running Win7 for my task machines that I plan to leave there if at all possible. My main laptop that hosts AXti.me is on Windows 8, which I really don't like. It's also the one that is bugging me constantly to get assimilated... I mean get updated to Windows 10.

If I do drink the Koolaid, take the blue pill, surrender to our new robot overlords, become part of the Borg, etc etc etc, will it screw anything up with the database / server app? Thanks.

@Duke I recall Chris saying that Axti.me is compatible with Win10.

If it works in windows 8 <shudder> it'll work in windows 10.

We are considering doing the same. W8 on our backup machine and it's a real PITA. W10 sounds a lot better. Let us know how it goes!

OK, I upgraded to Win10, and now Chrome won't see the server app. It's looking for the timing hardware, which is not plugged in. But that never stopped the AXti.me Club Home screen from coming up before, and anyway, I can't connect to the interface to turn the timing hardware off in AXti.me.

Obviously I will try connecting the timing hardware, but did anybody else experience this?

Anybody successfully using the Farmtek with Win10? I previously had driver problems with the Farmtek / Prolific serial-to-USB adapter, which I solved by reinstalling the ancient Prolific driver instead of the most current one. But I can't seem to get that to work with Win10, even trying to manually reinstall the old driver from the disk.

@Duke I've been successfully using Win10 and AXti.me all season with no issues. It was a bit tricky to get running but once I did, it's been smooth all summer. Try downloading the old driver from the Farktek website. You need to force windows to use the old driver vs the newer windows update one. See my how-to and if that doesn't work please report back.

http://forum.axti.me/topic/146/make-farmtek-driver-work-on-windows-10

For the record, I've had no problem connecting with Chrome to localhost and accessing RM, regardless if the timing hardware is connected or not.

@MarcGSR said:

For the record, I've had no problem connecting with Chrome to localhost and accessing RM, regardless if the timing hardware is connected or not.

Normally I don't either, which is what is worrying me. It typically gives an error in the second batch window if the adapter isn't plugged in, but ignores the error in the browser interface. Thanks for your reply.