a) when I google to wiki uac it indicates even back in windows 2008 they had UAC -- maybe turning that off would help?
b) if you're using a windows domain controller, you need to _not_ use the domain administrator's windows logon account to install the d3 even if that seems the safest experiment; instead the administrator account _for_that_windows_computer itself is the most likely account to work well during the install. If you have to ask 'what is a domain?' then no you are not on a domain arrangement, as regular workgroup only is the default, not a 'windows nt' style domain.
c) I'm biased, but don't forget the major vendors sell their databases in flavors for linux as well as in flavors for windows. But if you move to d3/linux remember that there is an option in d3 to cut file saves that are for use on d3/linux instead of d3/windows boxes -- without using that option the d3/linux box will choke trying to read the file-save due to extra 'fsi:' prefixes on account and file names found on the save 'tape'.
d) I'm confused how you even made the attempt to install your d3 on 2012 -- for many years now d3 install progs balk if you don't activate them during install.
You could try asking the vendor what it would take to get a 2 week activation on the new winbox to prove to your boss that that d3 can even run on win2012; the worst that can happen is that they refuse your request...
e) before you commit to the migration, make sure your new winbox can use any essential terminals or printers or modems; they may need a serial or parallel cable on the database winbox itself or they may just be unsupported {printers or modems} in win2012. And if you're using a multi-serial-port box or card, will it work in win2012?
John R. Stokka wrote: <snip>