Article View: comp.windows.ms.programmer
Article #436Re: Trouble using INT's from Windows-program
From: Jim Beveridge
Date: Wed, 15 Apr 1992 19:29
Date: Wed, 15 Apr 1992 19:29
26 lines
1370 bytes
1370 bytes
In article <4764@krafla.rhi.hi.is>, indridi@rhi.hi.is (Indridi Bjornsson) writes: > A friend of mine is writing some kind of communication > program in windows. The driver is called TES and is > located at INT 14. The services TES provides are A0 through A8. > He is using Borland C++ 3.0. > > Most of the services work, just by using int86x() inside > the program, but when he tries to send a string, TES doesn't > seem to get the right one, just some garbage. > The problem is that the string is stored in extended memory, which a real mode program (which int86x calls) is unable to look at. You have to have this string copied to an area of memory that is located below 640k. Windows does this automatically for you for interrupts that it understands. Obviously, it doesn't understand this interrupt. There are functions in the SDK for getting and using memory below 640k, I just don't remember them off the top of my head. Hope this helps. Jim
Technical Details
Message-ID:
<1992Apr15.192954.17831@newmedia.uucp>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!rpi!bu.edu!wang!newmedia!jimReferences:
<4764@krafla.rhi.hi.is>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!rpi!bu.edu!wang!newmedia!jim From: jim@newmedia.uucp (Jim Beveridge) Newsgroups: comp.windows.ms.programmer Subject: Re: Trouble using INT's from Windows-program Message-ID: <1992Apr15.192954.17831@newmedia.uucp> Date: 15 Apr 92 19:29:54 GMT References: <4764@krafla.rhi.hi.is> Organization: New Media Graphics Lines: 26