It had to happen sooner or later...
I'm running Windows 10 on a separate HD from my trusty Win7 setup. This is not an upgraded setup, it's a new, clean install for evaluating the new OS.
Yesterday I got CFS3 installed from scratch on my Windows 10 hard drive and the installation went smoothly. BUT... CFS3 won't run in Windows 10. It doesn't seem to know how to look for the CD to authenticate the install each time it runs. FS9 users have reported the same problem with their CDs.
The answer is well known to many of us, and it's the no-CD patched version: CFS3 starts and runs with that every time. I don't see any reason ETO, MAW and the rest shouldn't also work that way.
As many of us also know, discussion of this patch on SOH is barred as a longstanding policy. Please refer to Tom Clayton's post in the FS9 forum for the reasons and do any file hunting away from SOH.
Thank you!
Edit: Recent updates borked that too, see hypercide's post (#13) below for the current answer.
I'm running Windows 10 on a separate HD from my trusty Win7 setup. This is not an upgraded setup, it's a new, clean install for evaluating the new OS.
Yesterday I got CFS3 installed from scratch on my Windows 10 hard drive and the installation went smoothly. BUT... CFS3 won't run in Windows 10. It doesn't seem to know how to look for the CD to authenticate the install each time it runs. FS9 users have reported the same problem with their CDs.
The answer is well known to many of us, and it's the no-CD patched version: CFS3 starts and runs with that every time. I don't see any reason ETO, MAW and the rest shouldn't also work that way.
As many of us also know, discussion of this patch on SOH is barred as a longstanding policy. Please refer to Tom Clayton's post in the FS9 forum for the reasons and do any file hunting away from SOH.
Thank you!
Edit: Recent updates borked that too, see hypercide's post (#13) below for the current answer.
Last edited: