"Johann MacDonagh" <[email protected]> wrote in message news:[email protected]... > On 7/17/2011 6:41 PM, Nick Sabalausky wrote: >> "Johann MacDonagh"<[email protected]> wrote in message >> news:[email protected]... >> - Did you get that after it prompted you for a "yes/no", or did it not >> get >> that far? >> >> - Was that message displayed in the cmd prompt or in a dialog box? > > No prompt at all, and it was in the console window. >
Thanks. There's a point where it checks the registry to see if DMD already exists in the system PATH (and will prompt the user for further action if it's there, because it would get in the way of DVM's "default compiler" feature). Turns out I forgot to use read-only access (instead of read/write) to open the key for that check. > You can always create a restricted account for yourself to test it out. Yea, clearly I should have done that ;) > It will fire if you try dvm-installer.exe install dvm on a machine that > already has dvm installed. Turns out the problem occurs when trying to install DVM on any limited Windows user account, regardless of an existing DVM or DMD, and regardless of XP/Win7 or 32bit/64bit. Pretty bad since DVM currently only installs per-user. /facepalm I've fixed it and submitted a pull request (and this time I tested it with limited user accounts on both XP and Vista): https://bitbucket.org/doob/dvm/pull-request/2/
