If you remember the start of the saga a few weeks ago, the problem began when I upgraded one of my machines to Windows10 and my Apache didnt work. So rather than try to figure out why, I decided to switch to using IIS instead. (the only place I use Apache any more is on my dev machines so I figured I'd change my dev environment to match my servers)
That's when everything went pear-shaped on me. And I've never got back to working out either why Apache didnt work under Windows10 (other people have said it works just fine , so I must have some difference in my setup somewhere) or how to make CF work under Windows10 and IIS. It's all still sitting in the 'too hard' basket waiting for Adobe, while I get on with life. On Wed, Sep 23, 2015 at 12:23 PM, Charlie Arehart < charlie_li...@carehart.org> wrote: > Happy to help, but FWIW, if you mean you’ll put off upgrading to Windows > 10, I’d point out that I’ve upgraded multiple machines to Windows 10 that > already had CF 10 and 11 on it and it’s no problem. > > Where you get into trouble is if you try to install CF10 or 11 (or > earlier, of course) on a machine that is running Windows 10, or if you had > any reason to try to run the web server config tool on Windows 10. > > So if you have other benefits of running Windows 10, this doesn’t have to > be a show-stopper. > > Anyone else have other experience (upgrading to Windows 10 on a machine > already running CF)? > > > > /charlie > > > -- Cheers Mike Kear Windsor, NSW, Australia Adobe Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To unsubscribe from this group and stop receiving emails from it, send an email to cfaussie+unsubscr...@googlegroups.com. To post to this group, send email to cfaussie@googlegroups.com. Visit this group at http://groups.google.com/group/cfaussie. For more options, visit https://groups.google.com/d/optout.
