Copyrights @ Journal 2014 - Designed By Templateism - SEO Plugin by MyBloggerLab

Monday, December 30, 2002

Paul Bausch:
As Bertrand Russell said, "There are two motives for reading a book: one, that you enjoy it; the other, that you can boast about it

Paul is the co-writer for "We Blog" the book I blogged on Aug 23,2002. Paul is a curious book reader seems and has a good taste also. Being a frequent reader of his book list now a days.

Saturday, December 28, 2002


Actually I donn give a damn to India-Pakistan war, the war is between two different politicians or two different theories of life, but never between people. I was always curious about the Pakistani people their way of thinking and also about what they think about the Indian. I am proud to be an Indian but still feel they are the brothers. May be step brothers who can always stop and come down to a solution good for both. I pray for the day to come soon.
Adnan Arif, a student from Pakistan has got a beautiful mind along with his site design. Some fascinating graphics can be added points on the same but Adnan do still write only on the middle east countries? You seems like sponsorer for blogsnob too.

Friday, December 27, 2002

Removing the Blog code now !!! bye bye | Blog Code : B2 d++ t k++ s+ u f++ i+ o+ x e- l c+
It had been sitting on my web site for a long time and now it is making little more space in header. I don't like that. Reading a few new User Interface designs making it difficult for me to keep it there. So lets place it in a blog and say good bye.
cover Windows NT Device Driver Development
by Peter Viscarola, W. Anthony Mason
Sample Pages
Paperback: 684 pages
Publisher: New Riders Publishing; ISBN: 1578700582; 1st edition (November 10, 1998)
The book is of the level that you can start from scratch. The slef experiences are described which are more important. By making a wonderful book calls the no Errata needs. A comprehensive index also plays part for reader to feel satisfied.
Windows NT Device Driver Development is the definitive and comprehensive technical reference for software engineers, systems programmers, and any engineer who needs to understand Windows NT systems internals. You will learn: vital information about the internal design and architecture of the Windows NT operating system; Critical information on the implementation of standard Windwows NT kernel mode drivers; Key information on the workings of Windows NT I/O Manager, including how I/O requests are described and passed among drivers; and detailed technical information on interrupt management and synchronization issues.
From the Back Cover
Windows NT Device Driver Development is the definitive and comprehensive technical reference for software engineers, systems programmers, and any engineer who needs to understand Windows NT systems internals. You will learn: vital information about the internal design and architecture of the Windows NT operating system; Critical information on the implementation of standard Windwows NT kernel mode drivers; Key information on the workings of Windows NT I/O Manager, including how I/O requests are described and passed among drivers; and detailed technical information on interrupt management and synchronization issues.
Authors
Peter G. Viscarola is a founder of, and Consulting Partner at, Open Systems Resources (OSR), the world-renowned consulting firm specializing in Windows NT systems internals. During more than 20 years in the computer industry, including more than 10 years as an independent consultant, Peter has developed device drivers and protocol implementations under a wide array of operating systems. Since the release of Windows NT, Peter has designed or developed more than three dozen Windows NT drivers, including drivers for almost every type of programmed I/O and DMA device imaginable. Recent Windows NT driver projects include development of high-speed drivers for ATM[r], ISDN, and Frame Relay devices, as well as design of special Kernel mode drivers for a number of unique situations.
W. Anthony Mason is an Open Systems Resources Consulting Partner with experience in a wide array of system software disciplines during the past 16 years. Tony is also an internationally recognized expert in file systems technologies. Among his recent projects has been the design and development of several Windows NT installable file system drivers, including both physical media file systems and networked distributed file systems.

My Device Driver are also have some experiences from this book.
**BOOKS**

Tuesday, December 17, 2002

But where Microsoft fails us, entrepreneurs step in.

Idealab founder Bill Gross is behind Find.com, a new company that makes a utility that does just what I and, I suspect, millions of other people are looking for. Find.com keeps a running index of your e-mail and returns your search results as you type in each letter of the search query -- you see the results list get shorter and shorter in real time. The product searches your text files the same way.

Rajesh Jain also wants to use the similar facility for searching his emails and the pages too I guess. Changing the email location for the thick server would enable the usage I guess. I guess the company projected for profit in 2003. I do not hope much from this IDEALAB kid. Bill Gross need to use the same search engine to search for money from it.

Thursday, December 12, 2002

Talking more about the Kernel Mode and User Mode drivers
The differences, I will continue to read and write about. These Kernel Mode Drivers continue to work as a part of Windows Executive and the provide inherent support to Windows Operating System Level Kernel mode functionality such as I/O, PnP, Processes, Threads, Security and memory and so on ..
Some Kernel mode drivers can be the WDM drivers. They Conform to the needs of Windows Driver Model, I mean they support the PnP Architecture and also the powr management. Important hint is these WDM drivers support the source on most Windows platform but they are not binary compatible. My understanding is they need to be recompiled once on the specific DDK.
Based on the fuctionality the Kernel mode drivers can be distingushed beteween three major categories.
1) Highest level drivers
2) Intermidiate level drivers
3)Lowest level drivers.

This diagram will make the ideas more clear.
The Highest level drivers can be examplified as file system drivers (FSDs) such as NT, FAT or CDFS driver. They are system supplied. (If you want you can try the expensive Installable file System Kit from Microsoft.) These type of drivers have a very high level of dependency on one or more lower level(other two types) drivers. Lets say at least the PnP Hardware bus driver.

Monday, December 09, 2002

Vande Mataram
Vande Matarm is running the top one now.....

Sunday, December 08, 2002

See what I found... The Constitution of India (Sanvidhan u see)..
I didn't try to find who launched it but has all 395 articles and sorted by the parts... cool.
Check out here
Kernel Mode and User Mode
The User mode drivers are allowed to use the Win32(r) API described by the Windows SDK where as the Win32 subsystem internally calls the exported driver and operating system kernel routines. The difference is vast just to understand and describe in few lines here. Lets try best, but better get the DDK installed to see the right one. The kernel mode drivers can use most of the routines exported by the Windows Operating System, these exported routines support the I/O, configuration, Plug and Play, power management, memory management, and numerous other operating system features. This is a very standard way of describing the way the Device Drivers are taught but definitely reading this will not suffice to introduce you to it.
These two types differ in everything. The difference starts by the definition of DriverEntry routine. Every WDM driver has a entry point and this is used by the operating system to understand where to start the execution. Let me put it in other terms like this routine is called first when driver is loaded in the memory of the system. This routine describes the start of execution of the driver.
The type of driver to be used or written is totally depends on the support provided by the Operating system. In vague language I can say, you may have to write a user mode device driver when the Operating system has the support means the Win32 subsyem has the capability to provide the routines, otherwise you dont have an option go for the Kernel mode driver and then all I can say is Best of luck...
the other major difference is also the interrupts used by the same but lets leave something for tomorrow.

Wednesday, December 04, 2002

Mahendra Agarwal is Concerned...

Mahendra has lotsa questions on corruptions but has it not been known to anybody. the questions and their explainations are very simple like WHO IS THE MOST CORRUPT INDIAN OF ALL? - Laloo Prasada Yadav. Do they carry any meaning or they are just from the reports.
We all know, must be having a concesus for the slowed speed of national development is the side product of the corruption in India. Still the blame is passed from one place to other for the reason saying they are the culprits.
In my opinion, when the one bread or roti is to be split in more than one person, the corruption starts. The fight for the shared resource which may be the food, shelter or anything we may guess gets into the corruption in order to have a pleasant looking end. The bribe is just the token to bypass the line for the resource. Apply this anywhere, a builder bribing the Govt officer for getting the contract out of the normal bidding process.
Bottomline, it is not the corruption that is bad, bad is the mentality and its founder named merciless and ever growing POPULATION...

Tuesday, December 03, 2002

Oops!!! It's December already... I need to start finishing off my resolutions I made last december.
How to Write a Windows XP Driver
MSDN is a vast resource of information indeed. Still I feel, it is half way for the DDK. In case of DDK and XP drivers more you explore more it gets confusing. this attempt is for making the related resources right at the single contact page. To begin with a person needs at least a suitable machine where he can install and play around with the system. If you are having a good working system, please understand that it is no more be useful. You keep all your restore CDs close by may be you will have to reinstall the operating system itself. I am very sure for atleast 30% times the WinXP System Restore will not work at all.
While reading and searching more, I find the same SDLC (Systems Developement Life Cycle) getting repeated for Driver development also at a very vague level. 1) Requirements : Understand the Device needs and the Operating System Level Concepts. 2) Design : Decide at earlier stage, what you want an how you want. 3) Build-Test-Debug : The Key to better driver and avoiding the Win fame BSD (Blue Screen of Death). 4) Package it: Gift-wrap is needed for proper distribution. Support is indeed not needed... offcourse I am kidding, but being developer I never liked to support. Check out more from horse's mouth.
Disabling Device Driver Update Wizard
In this most user friendly, Windows family, the automatic driver update wizard is considered as the most useful resource for the all those who do not want to tweak with the Driver Database of the machine. This wizard gets to nerves when the Device driver tweaker comes to play. Change the Windows registry settings so this is wizard is disabled and Windows Update to locate updated drivers for hardware in Device Manager is stopped instantly.
Registry Settings
User Key: [HKEY_CURRENT_USER\Software\Microsoft\WindowsCurrentVersion\Policies\Explorer] Value Name: NoDevMgrUpdate Data Type: REG_DWORD (DWORD Value) Value Data: (0 = default, 1 = remove update)
Be careful and this works for Win 98/NT/XP/ME.