[enry_straker]

I call BS on that attitude.

First, the author was making a generic point. Your contribution is to point out some silly exception.

However, if a 20 year old had the driver's code, he can learn to look at the code of similar driver's or failing that learn to read the code, and run them through a kernel-level debugger. If he doesn't know how to do that, there are resources available on the internet to show him how.

[rahul_rai]

Where do you find a similar iscsi driver code written for windows NT

[enry_straker]

Similar to what?

Here's a link to the open source linux version: http://linux-iscsi.sourceforge.net/

Also check out this site for more info: http://www.open-iscsi.org/

The Windows DDK is a good source of sample driver code. If you are a MSDN subscriber, you would be able to find it as part of your collection ( or available for download online )

Beyond that, i suggest contacting MS tech support.

[rahul_rai]

I know all of this

my point is how do you deal with the pain of supporting code written by someone else years ago?

[enry_straker]

If you knew all this why ask a specific question?

I am really trying hard to take you seriously and not treat you like a troll.

As far as supporting code written by someone else years ago, that's just the nature of programming. If you find it too painful, get out of this industry, find something you truly enjoy and do your best in that area.

Life is too short to be struck doing something you really don't enjoy.