Can I get some insight, meanwhile, on making the move manually? Otherwise it absolutely kills using MC in a setup I've got that depends upon using domain users and roaming profiles. The login times are cripplingly slow.
Can I alter the User Settings.ini or other files in-between the install and the first run? In a way that will lead MC17 to default to using directories of my choosing instead of the roaming %APPDATA%? Can I change the "[App Data Path\]" string to another path? If so, can it be based on an environmental variable, or would it have to be a static string? Could it be a UNC share path, or would it have to be based on drive letter?
In checking this in-between time after install, but before accepting the license on a first run, I don't see much in the registry or in files that shapes path name locations. Not as many as I've seen on an install of MC on a different machine after it's already fully operational. I'm guessing a lot of what it chooses is decided programmatically? Is there a place where a string miight be consulted before an programmed choice is made? As in, a value that, when present, MC can/will use instead of querying the OS for the locations?
I realize, of course, this might pose other issues down the line, but those won't matter if the install doesn't get off the ground to start with.
I'd really like to have the configuration parts of MC to be in the roaming profile without all the data itself. That I'd want on a network share as individual access to those files isn't terribly slow. It's just the burden of a whole transfer during login/logoff that's killing me here. But I'd still like a user to be able to move from machine to machine (assuming it has MC on it already) and get their MC setup to follow them.
How does a portable install work? Might that be an alternative?