Re: How to call bios function in WDM Driver??

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mark Roddy (mroddy_at_nospam.spamt)
Date: 02/10/04


Date: Tue, 10 Feb 2004 07:33:57 -0500

On 10 Feb 2004 00:48:20 -0800, paullee@iei.com.tw (paullee) wrote:

>Hi All
>
>Sorry, I know there are so many people has ready ask this question many times,
>But, I still can't understand how to do it??
>
>I have a simple digit IO device connect to south bridge,
>In dos, I can just call int 15 to access it, for now , I need to access it
>in win 2000, Can any one tell me how to do it??
>
>Does anyone know how to use ke386bioscall function?? what argument it use ??
>Is there any east way to slove this problem??
>
>Any comment is welcome, sample code is the best.
>
>Thanks for your reading^^"""
>
>Best Regards
>
>Paul

You write an NT device driver for it. You do not access the bios in
NT. This ain't no dos.

=====================
Mark Roddy
Windows .NET/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com



Relevant Pages

  • Re: Find out the volume GUID of a drive
    ... > "Mark Roddy" wrote: ... >> Windows 2003/XP/2000 Consulting ... >> Hollis Technology Solutions 603-321-1032 ...
    (microsoft.public.development.device.drivers)
  • Re: IFSKIT for the masses
    ... Mark Roddy DDK MVP ... Windows 2003/XP/2000 Consulting ... Hollis Technology Solutions 603-321-1032 ...
    (microsoft.public.development.device.drivers)
  • Re: checked version of a microsoft driver?
    ... Mark Roddy ... Windows 2003/XP/2000 Consulting ... Hollis Technology Solutions 603-321-1032 ...
    (microsoft.public.development.device.drivers)
  • Re: Kernel/User mode synchronization
    ... Mark Roddy ... Windows 2003/XP/2000 Consulting ... Hollis Technology Solutions 603-321-1032 ...
    (microsoft.public.development.device.drivers)
  • Re: boot start drivers
    ... Mark Roddy DDK MVP ... Windows 2003/XP/2000 Consulting ... Hollis Technology Solutions 603-321-1032 ...
    (microsoft.public.development.device.drivers)