Ever heard of Feng Yuan? Questions about his SysCall Program,...
-
First off, be advised,...I am a newbie at C++ programming and have a very simplistic notion of the complexity of the Windows System. I am reading a book by Feng Yuan, "Windows Graphics Programming" 2002, in which he supplies a humongeous amount of hard intel on the Windows Graphics Engine and related DLL components. His book mainly describes the GDI API and is targeted at the Windows 2000 version. Anyway,... He supplies a number of diagnostic and demo programs with source code as examples for annoying persons like me, and I'm curious if any of you are familiar with this. Specifically, there is a program towards the beginning of the book, called SysCall, which displays an output window with a comprehensive listing of all of over 600 Systems Calls that can be made from user processes to kernel mode address space (not even really sure what that is). Many of these calls appear to be a kernel version of the same calls that a programmer would use in writing a Win32 application. I'm wondering several things. Why would this information be useful from a program design standpoint? And, how could this program be altered to work correctly on older versions of Windows (my system runs Windows 98)? The code in the book is copyrighted, but, I'm sure I could list enough of it to give you an idea of what the program entails. By the way, the book is great,...and way beyond my current comprehension of Windows graphics programming.
-
First off, be advised,...I am a newbie at C++ programming and have a very simplistic notion of the complexity of the Windows System. I am reading a book by Feng Yuan, "Windows Graphics Programming" 2002, in which he supplies a humongeous amount of hard intel on the Windows Graphics Engine and related DLL components. His book mainly describes the GDI API and is targeted at the Windows 2000 version. Anyway,... He supplies a number of diagnostic and demo programs with source code as examples for annoying persons like me, and I'm curious if any of you are familiar with this. Specifically, there is a program towards the beginning of the book, called SysCall, which displays an output window with a comprehensive listing of all of over 600 Systems Calls that can be made from user processes to kernel mode address space (not even really sure what that is). Many of these calls appear to be a kernel version of the same calls that a programmer would use in writing a Win32 application. I'm wondering several things. Why would this information be useful from a program design standpoint? And, how could this program be altered to work correctly on older versions of Windows (my system runs Windows 98)? The code in the book is copyrighted, but, I'm sure I could list enough of it to give you an idea of what the program entails. By the way, the book is great,...and way beyond my current comprehension of Windows graphics programming.
To modify the program to work with older Windows may not be possible, it depends on what API's he is calling, and if they have a W98 equivelant. Yes, it's without a doubt the best book on GDI by a large margin. Too bad that he hasn't done one on GDI+. Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002
It'd probably be fairly easy to make a bot that'd post random stupid VB questions, and nobody would probably ever notice - benjymous - 21-Jan-2003 -
First off, be advised,...I am a newbie at C++ programming and have a very simplistic notion of the complexity of the Windows System. I am reading a book by Feng Yuan, "Windows Graphics Programming" 2002, in which he supplies a humongeous amount of hard intel on the Windows Graphics Engine and related DLL components. His book mainly describes the GDI API and is targeted at the Windows 2000 version. Anyway,... He supplies a number of diagnostic and demo programs with source code as examples for annoying persons like me, and I'm curious if any of you are familiar with this. Specifically, there is a program towards the beginning of the book, called SysCall, which displays an output window with a comprehensive listing of all of over 600 Systems Calls that can be made from user processes to kernel mode address space (not even really sure what that is). Many of these calls appear to be a kernel version of the same calls that a programmer would use in writing a Win32 application. I'm wondering several things. Why would this information be useful from a program design standpoint? And, how could this program be altered to work correctly on older versions of Windows (my system runs Windows 98)? The code in the book is copyrighted, but, I'm sure I could list enough of it to give you an idea of what the program entails. By the way, the book is great,...and way beyond my current comprehension of Windows graphics programming.
Nebulous Person wrote: listing of all of over 600 Systems Calls that can be made from user processes to kernel mode address space (not even really sure what that is). Here you displayed this book isn't for you. If you don't even know what it is, stick to Win32. When Win32 limits you, then, maybe, these calls might be of use. Why would this information be useful from a program design standpoint? It wouldn't, and thereby the question is wrong. The Correct question would be "Is this information of use from a program design standpoint?" and the answer is: no, at least not now for you. Read, and understand, the sourcecode at sysinternals (former winternals) first. how could this program be altered to work correctly on older versions of Windows How the heck would we know without neither seeing the code, nor knowing what it really does? Since you yourself don't even know what the program does (or at least not how it's done), is this question even relevant? If you want to use a function call available from later OSes in an older OS (that doesn't implement this call itself), you'd have to write that code yourself like any good hacker.
-
Nebulous Person wrote: listing of all of over 600 Systems Calls that can be made from user processes to kernel mode address space (not even really sure what that is). Here you displayed this book isn't for you. If you don't even know what it is, stick to Win32. When Win32 limits you, then, maybe, these calls might be of use. Why would this information be useful from a program design standpoint? It wouldn't, and thereby the question is wrong. The Correct question would be "Is this information of use from a program design standpoint?" and the answer is: no, at least not now for you. Read, and understand, the sourcecode at sysinternals (former winternals) first. how could this program be altered to work correctly on older versions of Windows How the heck would we know without neither seeing the code, nor knowing what it really does? Since you yourself don't even know what the program does (or at least not how it's done), is this question even relevant? If you want to use a function call available from later OSes in an older OS (that doesn't implement this call itself), you'd have to write that code yourself like any good hacker.
Thanks for the response.