Re: When CString doesn't work
- From: "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx>
- Date: Tue, 7 Jun 2005 08:55:37 -0700
It's worth noting that DDK documentation has been GREATLY improved between
Windows 2000 DDK and XP (and even better in Win2003 DDK).
Windows 95 VxD environment is horrible to work with.
"Daniel James" <wastebasket@xxxxxxxxxxxxxxxx> wrote in message
news:VA.00000ba4.08b7e981@xxxxxxxxxxxxxxxxxxx
>
> It's a bit unfair to single out unix for that criticism: I've seen
> enough patchy, incomprehensible, and just plain incorrect
> documentation from Microsoft in my time, too. Documentation for
> writing device drivers -- unless you wanted to make only very small
> changes to standard drivers supplied by Microsoft themselves ("the
> code is the documentation") -- is the worst of all.
>
> It's been a while since I did any serious driver work on Windows (a
> Win95/98 VxD that took over hard disk encryption from an In13
> redirector was the last big one) but I don't suppose the situation has
> changed much.
>
.
- References:
- When CString doesn't work
- From: Lilith
- Re: When CString doesn't work
- From: Joseph M . Newcomer
- Re: When CString doesn't work
- From: Lilith
- Re: When CString doesn't work
- From: Mark Randall
- Re: When CString doesn't work
- From: Joseph M . Newcomer
- Re: When CString doesn't work
- From: Daniel James
- Re: When CString doesn't work
- From: Joseph M . Newcomer
- Re: When CString doesn't work
- From: Daniel James
- Re: When CString doesn't work
- From: Joseph M . Newcomer
- Re: When CString doesn't work
- From: Daniel James
- When CString doesn't work
- Prev by Date: Re: What is the difference between CEdit and CRichEdit control?
- Next by Date: Re: cstringList.Remove method
- Previous by thread: Re: When CString doesn't work
- Next by thread: Re: When CString doesn't work
- Index(es):
Relevant Pages
|
