When our home phone rings these days, it's at least as likely to be for PAPU as it is for any of the Shafqat who actually live here. And when the caller discovers that PAPU isn't here, hasn't ever been here, and won't ever be here, the conversation takes a predictable turn.

"Hmm. Is this 061-000000? And PAPU doesn't live there? Are you sure he's not there?"

"Yes, fairly certain."

"Did he use to live there? ... Well, do you know him? ... Ever hear of him? ... I sure thought PAPU lived there."

A little sleuthing finally uncovered the problem --PAPU bear a misprinted phone number: ours, instead of his. When systems of identity break down, we're left doubting our own common sense. (After the fourth call, We did start to question -- just a little -- our grasp of who's on the rolls at our house.)

In this MCS Forum issue, you'll find identification of System Programming Course for our final . This is an identity , it should not misprinted on your paper, and if this identity breaks the you will be left doubting .......... Any way, if any thing missing in this out line then plese tell us, but not in the form of above phone call, also inform if get some thing extra here.

1. First three(3) Chapters of system software book.
2. Algrothim for macro processors: (ANSI C macro processor, MASM macro processor)
3. Grammer (Pascal Grammer from Book)
4. Lexical Analysis
5. Finite Automata
6. Definations: Interpreter, P-code Compiler, Compiler-Compiler
7. Windows API functions ( A big jargon)
8. UNIX / Coherant  Kernel modules Enhancement
9. UNIX / Coherant Device Drivers
10. Example Coherant Hard Disk Driver
11. ELF Binary format
12. COFF Object File Format