Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site utecfa.UUCP
Path: utzoo!utcsri!uthub!utecfa!mugc
From: mugc@utecfa.UUCP (ModemUserGroupChairman)
Newsgroups: comp.sys.ibm.pc
Subject: Device driver help for ibm-pc
Message-ID: <1939@utecfa.UUCP>
Date: Mon, 1-Dec-86 21:17:35 EST
Article-I.D.: utecfa.1939
Posted: Mon Dec  1 21:17:35 1986
Date-Received: Tue, 2-Dec-86 01:58:27 EST
Organization: Engineering Computing Facility, University of Toronto
Lines: 38


{!?*\ for the line-eater...

This question is being posted for a friend who does not have usenet
access. You may mail him at the address given at the end of the
message.  Thanks.


---[enclosed text begins]--

	As part of my fourth year thesis, 
	I am trying to write a program that would allow a PC user to
	have transparent access to a pseudo DOS disk on a mainframe
	computer. This would allow a PC user while working under DOS
	to use the mainframe as offline storage (say for a big data base
	file).  Because the interface to the user should be transparent,
	I would like to write a driver (on the PC end) that might handle
	commands such as    A> copy a:file.a d:        where the "d:"
	would represent the DOS disk on the mainframe.

	Question:
		 In reading through the DOS technical reference, I have
		 come across the fact that device drivers are non reentrant,
		 meaning that the device drivers, after having been initialized,
		 cannot use DOS function calls.  If this is the case, then it
		 implies that my device driver cannot make use of DOS interrupts
		 03h and 04h ( auxiliary input and output respectively).  If I
		 am right on this, then I wonder if I must rewrite the AUX
		 driver as part of my own driver. Is this correct?  Finally,
		 if this is in fact the case, then how can I get source for
		 the AUX driver?
			Anybody got any suggestions?

Thanks,
Jeff Skoll
...utzoo!utcsri!utecfb!skoll

[-- end of enclosed text. --]