Warning 2 warning C4996: 'scanf': This function or variable may be unsafe. Consider using scanf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. (there are 6 of this)
That's because you're using scanf, which is a C standard library function. A few years ago, Mikrosoft went krazy and created "secure" versions of a lot of the string handling functions amongst other things. That's what the "_s" in scanf_s stands for - "secure". The warning is to get you to use the scanf_s instead of scanf.
If you're sure of yourself, follow the suggestion and use the flag _CRT_SECURE_NO_WARNINGS when compiling to get rid of the warnings.
I've come up against this particular thing recently, while trying to port code from a Windoze programmer using VS, to Linux and VxWorks. These "_s" functions are all over the place. No doubt they're very safe, and if you don't care about portability (and why should you), then by all means use them.
Carefully check the VS documentation though, these functions tend to add an extra argument, and sometimes there's a posix version of the function that matches the types and number of arguments but not their order.
When posting code, please enclose it in code tags. Highlight the code and click the "<>" button on the right of the edit window.
If you can get past the scanf(), the bug in your code is this: while(input== '1','2','3','4','5')
which is equivalent to while ('5') which is always true. Look up the comma operator if you don't understand why. Do this instead: while (input >= '1' && input <= '5')