Sage 100

We have a client with Mas 4.2 , who needs to install workstation setup on a Windows 10 64-bit workstation for about a month. We are getting a message that we are installing from a UNC path, although we mapped a drive and browsed from the drive to the wksetup folder in order to run the WS installation. We are running everything as Admin. We also get a message that MDAC 2.7 or 2.8 is not detected. Apparently those versions only run on 32bit OS, so we have not been able to install MDAC either. UAC is disabled, and PC was rebooted. I have a copy of their software running on my Win 10 PC, although I don't remember any special procedures I went through to make it work. Does anyone have any install pointers on workstation install in this scenario?

I don't know about v4.2 but I've been able to run the basics on some older version by installing a current version (so shared program resources and prerequisites get installed) and manually creating the shortcut to the old version.

Thanks Kevin. I'll give that a try.

Try runninng workstation setup from the source CD instead of wksetup

Thank you for the replies. The client decided to wait for us to get Sage 100 2016 loaded.

Not that it matters now but here is the answer on why the UNC msg appears. I was working at Sage at the time and Vista was being supported for the 1st time and on 4.20. One of its developer requirements was to support UNCs. What Sage ended up releasing for Vista support was both a specific 4.20 SP and a special wkstn update. That updated needed to be installed on every wkstn if any 1 wkstn was ran Vista at all. So back to your Win 10 situation, when all the above is is true on 4.20 or you upgrade them to 4.30 or higher (not that you should do < 2016), then the UNC msg will cease. But it doesn't mean you would have further problems once you got past that so waiting for 2016 seems prudent.