View Single Post
Old 06-20-2016, 10:28 AM   #10
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,682
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I'm guessing a display issue of some kind. No crashes, no errors, and a new instance was being properly launched and reported as running in the task manager--it just wasn't displaying on the screen. That's why I asked about dual displays. It acted exactly as if everything was running correctly, just not on a portion of the screen the user could see.

Doesn't Windows 10 have virtual desktops? Seeing as how the 32-bit version is a different executable in a different location, it wouldn't surprise me that that would "fix" the problem of the 64-bit version being configured to run on a different virtual desktop.

This is all guesswork on my part, of course. I have no idea if virtual desktops would work the way I described. I don't have Windows 10 to experiment with.

Last edited by DiapDealer; 06-20-2016 at 10:41 AM.
DiapDealer is online now   Reply With Quote