Path: utzoo!utgpu!attcan!uunet!pyrdc!pyrnj!rutgers!netnews.upenn.edu!eniac.seas.upenn.edu!ranjit
From: ranjit@eniac.seas.upenn.edu (Ranjit Bhatnagar)
Newsgroups: comp.sys.amiga.tech
Subject: Finding DOS Handler Message Ports
Message-ID: <5459@netnews.upenn.edu>
Date: 5 Oct 88 06:28:06 GMT
Sender: news@netnews.upenn.edu
Reply-To: ranjit@eniac.seas.upenn.edu.UUCP (Ranjit Bhatnagar)
Organization: University of Pennsylvania
Lines: 23

Alright, suppose I were writing a DOS handler which would filter
packets given to it and pass them on to other handlers.  How can I,
given a filename, figure out the handler corresponding to it without
actually making any attempt to access the file (or device) in question?

The cheap solution is "don't do that.  Use high-level DOS commands
such as Open(filename,...) in your handler, and let DOS sort it out."
But that just doesn't sound cool.  I'm hoping there's a function I
can call, or a table that I can look in without violating system
privacy, that maps names to handlers.

Door prize to the first person to guess what I want this handler
to do.  (By the way: nearly all my understanding of how
handlers works comes from Matt Dillon's example ramdisk.  Thanks,
Matt!)

	- Ranjit



			  She watch channel ZERO!?
she watched  she watched  she watched  she watched  she watched  she watched  
"Trespassers w"   ranjit@eniac.seas.upenn.edu	mailrus!eecae!netnews!eniac!...