Ke386CallBios()
in [Device Drivers]
|
From: Dean Ramsier on 28 Jun 2005 16:23 I've got a situation where I'm being told to make an Int15 bios call from a driver. I know it's no longer supported, highly discouraged etc, but I'm still being pushed into it. Based on some newsgroup posts, it looks like Ke386CallBios() is what I need. However, I don't have any idea on how to call it (obviously no documentation for an undocumented function). Any suggestions? -- Dean
From: Gary G. Little on 28 Jun 2005 16:42 What is it that you want to do? There may be a better way than the way you "think" is the only way. Some of us have been around the block MANY times and know that there may very well be a better way if we know what you are trying to do. The personal opinion of Gary G. Little "Dean Ramsier" wrote: > I've got a situation where I'm being told to make an Int15 bios call from a > driver. I know it's no longer supported, highly discouraged etc, but I'm > still being pushed into it. Based on some newsgroup posts, it looks like > Ke386CallBios() is what I need. However, I don't have any idea on how to > call it (obviously no documentation for an undocumented function). > > Any suggestions? > > -- > Dean > > >
From: Don Burn on 28 Jun 2005 16:43 What are you trying to do with INT 15? There is likely to be a better way to do it. Let the group know what you need. -- Don Burn (MVP, Windows DDK) Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from the email to reply "Dean Ramsier" <ramsiernospam(a)nospam.com> wrote in message news:ON4QG9BfFHA.3852(a)TK2MSFTNGP10.phx.gbl... > I've got a situation where I'm being told to make an Int15 bios call from > a > driver. I know it's no longer supported, highly discouraged etc, but I'm > still being pushed into it. Based on some newsgroup posts, it looks like > Ke386CallBios() is what I need. However, I don't have any idea on how to > call it (obviously no documentation for an undocumented function). > > Any suggestions? > > -- > Dean > >
From: Dean Ramsier on 28 Jun 2005 17:23 In this case, there is watchdog handling that is being done by an SMI interrupt. Unfortunately, there is GPIO that also has to be accessed using the same set of IO ports. Both can't be allowed to occur at the same time, and they want to keep the watchdog in the SMI. So, the BIOS is doing all access to these IO ports, and serving as the mutex to prevent conflicts. My experience in XP drivers is limited, so I'm sure there are plenty of other mechanisms I don't about. They can't be too complex though :) -- Dean "Don Burn" <burn(a)stopspam.acm.org> wrote in message news:IDiwe.175$Si3.165(a)fe06.lga... > What are you trying to do with INT 15? There is likely to be a better way > to do it. Let the group know what you need. > > > -- > Don Burn (MVP, Windows DDK) > Windows 2k/XP/2k3 Filesystem and Driver Consulting > Remove StopSpam from the email to reply > > > > "Dean Ramsier" <ramsiernospam(a)nospam.com> wrote in message > news:ON4QG9BfFHA.3852(a)TK2MSFTNGP10.phx.gbl... > > I've got a situation where I'm being told to make an Int15 bios call from > > a > > driver. I know it's no longer supported, highly discouraged etc, but I'm > > still being pushed into it. Based on some newsgroup posts, it looks like > > Ke386CallBios() is what I need. However, I don't have any idea on how to > > call it (obviously no documentation for an undocumented function). > > > > Any suggestions? > > > > -- > > Dean > > > > > >
|
Pages: 1 Prev: DrvQueryFontTree fails with Splwow64.exe Next: SysHook and STATUS_ACCESS_VIOLATION |