I considered this.
I doubt it, otherwise you would not have come up with the queston ;-)
However, Ctrl+O (open-file) isn't hijacked
afaik ctrl-o has no special meaning inside cmd.exe or windows in general. But, for instance i use a special cmd.exe that has all sort of additions such as see through, multiple tabs etc. and there ctrl-o is hijacked (at least when not changed the default keyboard shortcuts).
so I assume that Ctrl+S (save-file) would also not be hijacked.
ctrl-s is stopping output inside a cmd.exe console, which afaik is default behaviour
Is there any way to determine if a key combination is being hijacked?
ctrl break, ctrl-c, ctrl-f1, ctrl-print-screen and a bunch more is hijacked by windows. That is because processed input flag is set on the input handler (i still have to verify this to make 100% sure).
I do not know of an existing list of shortcuts that are in place, but it also depends on your personal windows settings. e.g. you can choose to 'swap' ctrl-f1 for something else.
In any case, any work-around for Ctrl+S?
See the link i posted.
I am currently testing with fpc (but no windows around, so have to search for a machine which can take me a while). Also i have no clue how this would otherwise influence Bart's example code as afaik that depends on processed input.
The other alternative is writing your own (windows console) keyboard driver which does as you want.