WDK7 help broke all my documentation

Just installed WDK 7100 and when I click the help icon, I get: “Microsoft
Document Explorer cannot be shown because the specified help collection
‘ms-help://MS.W7SDK.1033’ is invalid.” Worse, it broke ALL the other
documentation on my machine, including Platform SDK and help for other
products I had installed that make use of document exploder. There was a
link before for a CHM file a while ago so I can at least get that back. Is
it still available ?

//Daniel

http://www.microsoft.com/whdc/DevTools/WDK/WDKdocs.mspx

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@resplendence.com
Sent: 19. kv?tna 2009 13:13
To: Windows System Software Devs Interest List
Subject: [ntdev] WDK7 help broke all my documentation

Just installed WDK 7100 and when I click the help icon, I get: “Microsoft
Document Explorer cannot be shown because the specified help collection
‘ms-help://MS.W7SDK.1033’ is invalid.” Worse, it broke ALL the other
documentation on my machine, including Platform SDK and help for other
products I had installed that make use of document exploder. There was a
link before for a CHM file a while ago so I can at least get that back. Is
it still available ?

//Daniel


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

I’m using x64 vista for my dev box, installed the wdk 7100, and it went
quite smoothly. None is broken, tried to build the network folder of the
src. Everything so far so good. I also about 4 variations of 6000 wdk
installed and they are okay too.

Well, as if I’ve to sign something !
Prokash Sinha
http://prokash.squarespace.com
Success has many fathers, but failure is an orphan.

----- Original Message -----
From:
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Tuesday, May 19, 2009 4:12 AM
Subject: [ntdev] WDK7 help broke all my documentation

> Just installed WDK 7100 and when I click the help icon, I get: “Microsoft
> Document Explorer cannot be shown because the specified help collection
> ‘ms-help://MS.W7SDK.1033’ is invalid.” Worse, it broke ALL the other
> documentation on my machine, including Platform SDK and help for other
> products I had installed that make use of document exploder. There was a
> link before for a CHM file a while ago so I can at least get that back. Is
> it still available ?
>
> //Daniel
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

Try repairing document explorer in add/remove programs. Was this an upgrade from a prev win7 build / released OS or a clean install?

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: xxxxx@resplendence.com
Sent: Tuesday, May 19, 2009 4:13 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDK7 help broke all my documentation

Just installed WDK 7100 and when I click the help icon, I get: “Microsoft
Document Explorer cannot be shown because the specified help collection
‘ms-help://MS.W7SDK.1033’ is invalid.” Worse, it broke ALL the other
documentation on my machine, including Platform SDK and help for other
products I had installed that make use of document exploder. There was a
link before for a CHM file a while ago so I can at least get that back. Is
it still available ?

//Daniel


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

This happened to me when I installed the 7000 WDK beta (or maybe it was the 6801). Actually, in my case, it broke a lot more than that - Office, VS, et. c.

I can’t recall for certain, but I believe that the problem was due the KitSetup doing something to .NET that nothing else appreciated. I can’t say that I’d recommend this as necessarily safe, but I was able to fix the problem by first installing the latest version of .NET, followed by the WDK.

Good luck,

mm

I forgot - obviously, it won’t fix your other DExplorer issues, but as far as the WDK goes, if you haven’t already, I’d recommend getting the ‘jumbo chm’ form of the wdk docs from the link that Petr mentioned. It’s paradise, really.

Good luck,

mm

wrote in message news:xxxxx@ntdev…
> This happened to me when I installed the 7000 WDK beta (or maybe it was
> the 6801). Actually, in my case, it broke a lot more than that - Office,
> VS, et. c.

There is a workaround…
The WDK seems to work just fine after xcopy install.
Run the kit setup on a clean [virtual] machine, then copy the unpacked dir
to your \winddk.
And the batch file below can go instead of start menu shortcuts…

Regards,
– pa

--------- cut here --------
:: Replacement for buld env shortcuts WDK 6000-7100
:: Opens interactive cmd window for WDK build.
:: This is not intended to run from Visual Studio etc.

@echo off

: SET THIS TO YOUR WDK PATH
set BASEDIR=%SystemDrive%\winDDK\7100.0.0
if NOT exist %BASEDIR%\bin\setenv.bat (@echo ERROR: bad WDK path! & goto
:ERR )

:: *** Choose where to CD initially. Set the desired path here, or CD later.
:- set _a_workdir=%~dp0
set _a_workdir=%cd%

:: Prompt for target OS and checked/free:

:RTEQ
@ECHO What do you want to build today?
@ECHO 1=WXP 2=WNET 3=WLH 4=Win7 5=WNET/x64 6=WLH/x64 7=Win7/x64
SET /P _a_n=Target OS?
if %_a_n% LEQ 7 goto :RTE%_a_n%
goto :RTEQ

:RTE0
set _a_targetenv=W2K
goto :RTEN

:RTE1
set _a_targetenv=WXP
goto :RTEN
:RTE2
set _a_targetenv=WNET
goto :RTEN
:RTE3
set _a_targetenv=WLH
goto :RTEN
:RTE4
set _a_targetenv=WIN7
:RTE5
set _a_targetenv=WNET x64
goto :RTEN
:RTE6
set _a_targetenv=WLH x64
goto :RTEN
:RTE7
set _a_targetenv=WIN7 x64
goto :RTEN
:RTEN

:CF0
SET /P _a_n=Checked(1) or Free(2)?
if %_a_n% LEQ 2 goto :CF%_a_n%
goto :CF0
:CF1
set _a_chkfre=chk
goto :CFN
:CF2
set _a_chkfre=fre
:CFN

:: Reset PATH to default.
PATH %windir%\system32;%windir%;%windir%\system32\wbem;
:: VS2005+ can set this. Affects the WDK compiler too, so remove it.
set VS_UNICODE_OUTPUT=

set _a_no_oacr=
:: Comment out the next line if you want OACR:
if exist %BASEDIR%\bin\x86\OACR set _a_no_oacr=NO_OACR

: Save username, setenvbat clobbers it. I use it in privatebuild version
string
set _a_username=%USERNAME%

call %BASEDIR%\bin\setenv.bat %BASEDIR%\ %_a_chkfre% %_a_targetenv%
%_a_no_oacr%

if NOT “%_a_workdir%” == “” cd /d %_a_workdir%

if NOT “%_a_username%” == “” set USERNAME=%_a_username%

:: TODO add here your env. tweaks

:: Now spawn another cmd for interactive box:
@%comspec% /k @echo Ok, now run build.
exit /B

:ERR
pause Hit enter to continue…
goto :EOF
------ cut here-------

Thanks, Pavel.

That is what I did temporarily, but I thought someone mentioned something about oacr breaking this type of installation.

mm

Thanks for the response, I got it fixed. This was a clean install of the WDK
on a clean install of Win7 RC.

//Daniel

“Doron Holan” wrote in message
news:xxxxx@ntdev…
> Try repairing document explorer in add/remove programs. Was this an
> upgrade from a prev win7 build / released OS or a clean install?
>
> d
>
> Sent from my phone with no t9, all spilling mistakes are not intentional.
>
> -----Original Message-----
> From: xxxxx@resplendence.com
> Sent: Tuesday, May 19, 2009 4:13 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] WDK7 help broke all my documentation
>
>
> Just installed WDK 7100 and when I click the help icon, I get: “Microsoft
> Document Explorer cannot be shown because the specified help collection
> ‘ms-help://MS.W7SDK.1033’ is invalid.” Worse, it broke ALL the other
> documentation on my machine, including Platform SDK and help for other
> products I had installed that make use of document exploder. There was a
> link before for a CHM file a while ago so I can at least get that back. Is
> it still available ?
>
> //Daniel
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>

xxxxx@evitechnology.com wrote:

Thanks, Pavel.

That is what I did temporarily, but I thought someone mentioned something about oacr breaking this type of installation.

OACR breaking? no, it works just fine for me with “xcopy install”.

Regards,
– pa

What was the fix?

d

Sent from my phone with no t9, all spilling mistakes are not intentional.

-----Original Message-----
From: xxxxx@resplendence.com
Sent: Wednesday, May 20, 2009 1:36 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] WDK7 help broke all my documentation

Thanks for the response, I got it fixed. This was a clean install of the WDK
on a clean install of Win7 RC.

//Daniel

“Doron Holan” wrote in message
news:xxxxx@ntdev…
> Try repairing document explorer in add/remove programs. Was this an
> upgrade from a prev win7 build / released OS or a clean install?
>
> d
>
> Sent from my phone with no t9, all spilling mistakes are not intentional.
>
> -----Original Message-----
> From: xxxxx@resplendence.com
> Sent: Tuesday, May 19, 2009 4:13 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] WDK7 help broke all my documentation
>
>
> Just installed WDK 7100 and when I click the help icon, I get: “Microsoft
> Document Explorer cannot be shown because the specified help collection
> ‘ms-help://MS.W7SDK.1033’ is invalid.” Worse, it broke ALL the other
> documentation on my machine, including Platform SDK and help for other
> products I had installed that make use of document exploder. There was a
> link before for a CHM file a while ago so I can at least get that back. Is
> it still available ?
>
> //Daniel
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Thanks for this information. That was one of my concerns about the
usability of the WIN7 WDK in production build systems - that it can be
copied into a sandbox without loss of functionality.

Mark Roddy

On Wed, May 20, 2009 at 6:47 AM, Pavel A. wrote:
> xxxxx@evitechnology.com wrote:
>>
>> Thanks, Pavel.
>> That is what I did temporarily, but I thought someone mentioned something
>> about oacr breaking this type of installation.
>
> OACR breaking? no, it works just fine for me with “xcopy install”.
>
> Regards,
> – pa
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>