Bill wrote: In fact, any use of a "c" - even when naming par files brings up the
DOSBox-x configuration dropdown.
My setup (which is exactly as I distributed it) the "c" key works as expected for me. Could you try a fresh unzip of my file and see if the "c" key works as expected with uzipped Fractint and DOSBox unchanged as opposed to your setup? Bill, you are going way above the call of duty for this because you are not the target audience (though your expert efforts are VERY much appreciated by me). My purpose for providing the dosbox/fractint zip file is to provide a quick answer to the question "Oops, can I run Fractint under 64 bits Windows?" My setup provides no value added for someone with your experience in both Fractint and DOSBox; I just distribute stock versions of both, integrated in one package. The good news is that as near as I can tell, running my versions of Fractint and DOSBox does not interfere with other installations of either package that the user might have.
From your experience, it looks like I need to find out what triggers "c" working with DOSBox vs being passed through to Fractint. So far I have heard back from several folks who were asking about running on Windows, and they reported no problems, but then I am quite certain they weren't testing as thoroughly as you are!
Thanks for your help. Tim