Why can Windows not read beyond the 0x1A (EOF) character but Unix can? [duplicate]

Why can Windows not read beyond the 0x1A (EOF) character but Unix can?
[duplicate]

References

Reference NO 1

http://stackoverflow.com/questions/13582804/why-can-windows-not-read-beyond-the-0x1a-eof-character-but-unix-can

Reference NO 2

http://stackoverflow.com/questions/6283632/how-to-know-if-the-next-character-is-eof-in-c

Reference NO 3

http://superuser.com/questions/621199/why-is-sort-exe-truncating-large-output-on-32-bit-windows

Reference NO 4

http://www.perlmonks.org/bare/?node_id=374705

Reference NO 5

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=33&t=36026

Reference NO 6

http://bytes.com/topic/c/answers/215083-eof-novice

Reference NO 7

http://sed.sourceforge.net/sedfaq4.html

Reference NO 8

http://www.dreamincode.net/forums/topic/108057-asii-sub-hex-1a-char-causing-problems/