If I call it from a workitem.
I’m especially in 64 bit vista and 64 bit win7.
thanks,
I’ve always thought HalMakeBeep() is a debugging function. Why do you
want to call HalMakeBeep()?
On Thu, May 20, 2010 at 12:41 AM, wrote:
> If I call it from a workitem.
> I’m especially in 64 bit vista and 64 bit win7.
>
–
Aram Hăvărneanu
Let’s say I use it for debugging. Question is, is it safe and legal?
Well, it’s LEGAL as far as I know. That is, you won’t violate any LAWS by using it 
But it’s CLEARLY NOT a SUPPORTED function… it’s not documented in the WDK or anywhere in MSDN. So, like all such functions, you should use it at your own risk. In general, driver writers are advised to avoid using unsupported and undocumented functions.
Because it’s not supported, it’s subject to change at any time. So that renders it “unsafe” for at least some value of the term.
Peter
OSR
Let me expand on what Peter said. That function is undocumented and
unsupported. Calling it at PASSIVE_LEVEL probably won’t cause your driver
to crash. But it may or may not actually make a beep.
We hook that up when it’s convenient, when the machine is more or less a
“PC.” If the machine isn’t a PC, there’s no meaningful way to make a beep
without commandeering the sound device from within the HAL, if that exists.
So we don’t.
–
Jake Oshins
Hyper-V I/O Architect
Windows Kernel Group
This post implies no warranties and confers no rights.
wrote in message news:xxxxx@ntdev…
> Well, it’s LEGAL as far as I know. That is, you won’t violate any LAWS by
> using it
>
> But it’s CLEARLY NOT a SUPPORTED function… it’s not documented in the
> WDK or anywhere in MSDN. So, like all such functions, you should use it
> at your own risk. In general, driver writers are advised to avoid using
> unsupported and undocumented functions.
>
> Because it’s not supported, it’s subject to change at any time. So that
> renders it “unsafe” for at least some value of the term.
>
> Peter
> OSR
>
>