In the last issue of the NT Insider on page 13 there is an
article mentioning the DDI ‘DbgPrompt’. Scanning through the
entire ‘inc’ tree of the 3790 DDK i could not find a declaration
of this DDI, although it can be found in the list of exported
functions of ‘ntoskrnl.exe’.
Where can i find more information about ‘DbgPrompt’?
I use the following for a function prototype:
extern VOID DbgPrompt(char *prompt, char *buf, unsigned long buflen);
where prompt in the string to display, buf is the buffer to recieve the
WinDBG input, and bulen is the length of the buffer. You will get a null
terminated input string (unless you input more than the buffer length).
Use this function only when you have a debugger connected.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
wrote in message news:xxxxx@ntdev…
> In the last issue of the NT Insider on page 13 there is an
> article mentioning the DDI ‘DbgPrompt’. Scanning through the
> entire ‘inc’ tree of the 3790 DDK i could not find a declaration
> of this DDI, although it can be found in the list of exported
> functions of ‘ntoskrnl.exe’.
>
> Where can i find more information about ‘DbgPrompt’?
>
>
>
>
Those guys at OSR seem to be working with a different OS 
In their sample code they use it like this:
ULONG Port;
DbgPrompt(“\nPort to use: %x”, &Port);
“Don Burn” schrieb im Newsbeitrag news:xxxxx@ntdev…
>I use the following for a function prototype:
>
> extern VOID DbgPrompt(char *prompt, char *buf, unsigned long buflen);
>
> where prompt in the string to display, buf is the buffer to recieve the
> WinDBG input, and bulen is the length of the buffer. You will get a null
> terminated input string (unless you input more than the buffer length).
>
> Use this function only when you have a debugger connected.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> wrote in message news:xxxxx@ntdev…
>> In the last issue of the NT Insider on page 13 there is an
>> article mentioning the DDI ‘DbgPrompt’. Scanning through the
>> entire ‘inc’ tree of the 3790 DDK i could not find a declaration
>> of this DDI, although it can be found in the list of exported
>> functions of ‘ntoskrnl.exe’.
>>
>> Where can i find more information about ‘DbgPrompt’?
>>
>>
>>
>>
>
>
>
Actually doing some checking it should be:
extern ULONG DbgPrompt(char *prompt, char *buf, unsigned long buflen);
where it returns the number of characters it put in the buffer. Have to ask
OSR about the missing parameter.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“poltrone” wrote in message news:xxxxx@ntdev…
> Those guys at OSR seem to be working with a different OS
>
> In their sample code they use it like this:
>
> ULONG Port;
> DbgPrompt(“\nPort to use: %x”, &Port);
>
>
> “Don Burn” schrieb im Newsbeitrag news:xxxxx@ntdev…
> >I use the following for a function prototype:
> >
> > extern VOID DbgPrompt(char *prompt, char *buf, unsigned long buflen);
> >
> > where prompt in the string to display, buf is the buffer to recieve the
> > WinDBG input, and bulen is the length of the buffer. You will get a
null
> > terminated input string (unless you input more than the buffer length).
> >
> > Use this function only when you have a debugger connected.
> >
> >
> > –
> > Don Burn (MVP, Windows DDK)
> > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > Remove StopSpam from the email to reply
> >
> > wrote in message news:xxxxx@ntdev…
> >> In the last issue of the NT Insider on page 13 there is an
> >> article mentioning the DDI ‘DbgPrompt’. Scanning through the
> >> entire ‘inc’ tree of the 3790 DDK i could not find a declaration
> >> of this DDI, although it can be found in the list of exported
> >> functions of ‘ntoskrnl.exe’.
> >>
> >> Where can i find more information about ‘DbgPrompt’?
> >>
> >>
> >>
> >>
> >
> >
> >
>
>
>
Don Burn wrote:
where it returns the number of characters it put in the buffer. Have to ask
OSR about the missing parameter.
Missing parameter = sloppy techical review of article. We’ll get it
fixed on the web.
Sorry,
Peter
OSR