Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!decwrl!mcnc!rutgers!zodiac!nanda
From: nanda@zodiac.rutgers.edu
Newsgroups: comp.windows.ms
Subject: INTERFACE over DOS
Message-ID: <341.27848276@zodiac.rutgers.edu>
Date: 4 Jan 91 13:26:13 GMT
Organization: Rutgers University - Computing Services
Lines: 52


 HI, I ran into the following problem. Any body out there who knows what's
 going on please HELP!!
 Please mail all replys to sarao@winlab.rutgers.edu
THANKS.....


 I'm developing an application layer interface to a resident
device driver for a scanner in MS windows version 3.0 environment.
When I try to use windows API "DOS3Call" (or int21) with appropriate
register settings to read an interrupt vector (ah=35h,al=0xa1) the expected
value is not returned in es:bx.  When I try debugging using CVW, I get
es=06xx and bx=0xa1.  The dump of es:bx is F4's.

Is there a possibility of re-allocation of interrupt vectors in windows?
Please help me out as I'm stuck.


ps: I need to read the vector to get a id-string to confirm that the driver
is loaded.



	I'm trying to read the interrupt vector using Windows
	DOS3Call () with AH=0x35 and AL=0xA1. The expected
	value is not returned in ES:BX. Is it because the CPU
	is in protected mode.
	The environment is as follows:
	Hardware : PC386 with 8 MB RAM
	Running MS-WIndows on DOS 3.3
	CONFIG.SYS: .
				.
				PANASONI.SYS
				.

    AUTOEXEC.BAT: ....
				  MEISCAN.COM   ....


   All this effort is in developing a Window interface driver
   on top of DOS "installable device driver" supplied with
   the Scanner.

   







..