I don't know anything about windows, so I can only offer some style points. Sorry, this is not going to help in any way towards your goal, but hopefully you might learn a couple things that might be useful.
My main comment is that you could do with splitting the whole thing into more functions, will make it easier to read & understand.
The input_value function is very long. Where is the call to input_value? Where is the definition of gotoxy?
The normal way of presenting code, is to have the declaration of functions, then main(), then the definition of functions. This way we don't have to scroll through all the code to get to main.
Your indenting makes it hard to read the code, there are various styles. I put the opening brace at the end of the line after the if or while for etc. Others put it on the following line, immediately below (that is the same column number as) the if, for, while etc. The closing brace is probably more important, it needs to be in the same column as the opening if, for etc, so that one can see where the block ends. Indenting is important too, a lot of people set a tab to be 4 spaces. I put braces around one liners, as you have done, to save myself when I add code in the future.Like this:
1 2 3 4 5
|
for (i = 0; i < 9; i++){
for (j = 0; j < 9; j++){
output[i][j] = input[i][j];
}
}
|
or this:
1 2 3 4 5 6 7
|
for (i = 0; i < 9; i++)
{
for (j = 0; j < 9; j++)
{
output[i][j] = input[i][j];
}
}
|
This is a matter of style, choose one you like (there are others also) & stick to it.
Also comments, are good always. It is good practice to put them with variable declarations, and at the start of functions. Your current code makes it hard to see the start / end of functions.
Hope this helps a little bit.