View Single Post
Old 06-23-2017, 07:17 AM   #24
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,529
Karma: 8075744
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by kovidgoyal View Post
Seems to be something in windows 10 home -- unfortunately I only have windows 10 pro. I'm surprised though, as I would not think that basic functionality of launching processes would be different between home and pro.
I have Win10 Home and I can make it fail. Unfortunately I can't find a way to figure out what is going on. What I know:
  • If I start while running from source, restart works.
  • If I start using only the binary, restart in debug mode works.
  • If I start using only the binary, restart fails.
In all cases I am starting calibre from a DOS shell. The underlying binary is 3.1.1. In the first and third experiments I am using the built-in restart command, added to calibre's menu. In the two cases where it works, I see a spinning "wait" mouse cursor for a second or two, then nothing for a second or two, then calibre restarts. In the case where it doesn't work, that "wait" mouse cursor is up for around 1/4 second and nothing further happens.

@Kovid: I am happy to run any experiments you suggest. I don't have a C/C++ development environment installed.
chaley is offline   Reply With Quote