I have tentatively swapped in 7600 on a number of project trees that were
building with 7100. Nothing negative to report thus far. It all just built
and so far runs on the drivers I have tested.
As promised, the RTM WDF CoInstaller did indeed upgrade the 7100 RC KMDF
bits without fuss (just a reboot of course).
Smooth sailing thus far.
Dave Cattley
So your experience was nothing like mine. I uninstalled the WDK 7100 and then installed the 7600 version. It completely screwed my doc explorer help system. It did that also before but this time it was unrepairable by reinstalling the help. I uninstalled the whole new WDK hoping to repeat the whole installation process but this time it completely messed up for good. I suppose one picture says more than 1000 words:
http://www.resplendence.com/images/WdkInstall.jpg
When this finished, it assumed to be still installed. There is no way to either uninstall or reinstall the WDK other than reinstall the OS from scratch on my dev machine or probably spend hours hacking away in the registry. Well anyway, thanks MS for not keeping this thing portable!
//Daniel
“David R. Cattley” wrote in message news:xxxxx@ntdev…
I have tentatively swapped in 7600 on a number of project trees that were building with 7100. Nothing negative to report thus far. It all just built and so far runs on the drivers I have tested.
As promised, the RTM WDF CoInstaller did indeed upgrade the 7100 RC KMDF bits without fuss (just a reboot of course).
Smooth sailing thus far.
Dave Cattley
Well I found the first new problem with 7600. It is in OACR, in the
previous revisions the command OACR stop would stop the service and
eliminate the tray table icon, now OACR stop turns the ICON to red
indicating an error, while the service sits there still leaking memory like
before. You now have to go over to the tray table icon manually and select
stop to shut things down.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“David R. Cattley” wrote in message news:xxxxx@ntdev…
>I have tentatively swapped in 7600 on a number of project trees that were
> building with 7100. Nothing negative to report thus far. It all just
> built
> and so far runs on the drivers I have tested.
>
>
>
> As promised, the RTM WDF CoInstaller did indeed upgrade the 7100 RC KMDF
> bits without fuss (just a reboot of course).
>
>
>
> Smooth sailing thus far.
>
>
>
> Dave Cattley
>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4314 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4314 (20090807)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Ok, so not all roses here either:
As I *always* do I install the new WDK first and verify side-by-side that
projects build. I also manually ?windiff? the entire kit since nothing like
it in the documentation comes close to telling you what has changed.
After I am happy with the state of affairs, I will remove the previous kit.
This is standard ?make before break? system management.
Well, last time I did this with a WDK kit the ?break? (uninstall of older
kit after new kit installed) failed with some incredibly stupid nonsense and
I had to remove the new kit, find the .ISO for the old kit, run the setup
from the .ISO to remove the old kit, re-install the new kit. I am pretty
sure I bitched loudly about this goofiness to the WDK team.
For those about to consider a side-by-side install of the RTM WDK with the
RC WDK I can only report that MSFT has worked hard to maintain the previous
state of affairs. I once again have the rather silly, cryptic, and
completely stupid message from the KitInstaller
KitSetup is unable to validate that this software kit was produced by
Microsoft Copr. Due to digital signature verification error(s).
Additional information:
Unable to verify that the specified file was signed by Microsoft Corp.
Kit content filename: C:\Program Files\Common Files\Microsoft
KitSetup\Setup Versions\201.104.808.2200\KitSetup.exe
Logfile: C:\DOCUMEN~1\dcattley\LOCALS~1\Temp\WDK-KitSetup.log
[Kitsetup version 201.104.808.2200 error code 0x00c caught during
initialization of runtime routines. The KitSetup process will now exit.]
And of course, the Authenticode signature on the module is indeed from MSFT
(signed 13-Jul-09 at 10:27:35PM) and the certificate chain does validate
through the “Microsoft Code Signing PCA” and “Microsoft Root Certificate
Authority” signatures. So who knows what sort of issue this thing has with
itself.
Now, the RC and RTM kits both have *different* KitVersionUuid values. The
kits are *explicitly* attributed to support side by side.
From SKOM_1-kit-identification.xml for RC WDK
TRUEguration>
{515B5358-5757-5459-605A-5B635E5E5F60}
7
0
0
7100
7100.0.winmain_win7rc
Apr 21, 2009 17:00
090421
1700
7100.0.0
FALSE
From SKOM_1-kit-identification.xml for RTM WDK
TRUEguration>
{676E6B70-5659-5459-5B5F-6063635E5F61}
7
0
0
7600
7600.16385.win7_rtm
Jul 13, 2009 12:55
090713
1255
7600.16385.0
FALSE
So let me guess, only side-by-side installation is supported, right? Not
‘uninstall’?
And yes, I did read the release notes and no, they don’t say that installing
the RTM kit first requires removing any previous beta or RC kit.
This is why people liked XCOPY. Even in the hands of rookies, it was hard
to screw up as an installer. And DEL is a very useful uninstaller.
Dave Cattley
(as if my post before was anything other)
I realize the way of the world now. Since I have been tenaciously hanging
on to my XP build environment because, miracle of miracles, it works, and
because Vista seems like a rather silly thing to do to myself for the
environment that I need to have work, I now realize the following:
This ‘feature’ of the kit (to screw up) is probably only tied to users of
XP. It is a grand design to convince me to format my hard-disk and install
Win7. The KitSetup team is doing their part to reduce the barriers for
Winy7 adoption by XP users by making it a foregone conclusion that they all
will have to reformat their systems and start over thus eliminating the
barrier of having no upgrade path from XP to Winy7.
Now the grand design is apparent to me. Pass the purple coolaid. When doe
the comet arrive?
Actually, much worse than I thought. Even though I did OACR stop, the tray
table stuff is coming back So the OACR stop command is totally broken.
Well at least I have the beta version still to develop with, I guess I will
only use the release version when I have to ship something.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“Don Burn” wrote in message news:xxxxx@ntdev…
> Well I found the first new problem with 7600. It is in OACR, in the
> previous revisions the command OACR stop would stop the service and
> eliminate the tray table icon, now OACR stop turns the ICON to red
> indicating an error, while the service sits there still leaking memory
> like before. You now have to go over to the tray table icon manually and
> select stop to shut things down.
>
>
> –
> Don Burn (MVP, Windows DKD)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
>
> “David R. Cattley” wrote in message
> news:xxxxx@ntdev…
>>I have tentatively swapped in 7600 on a number of project trees that were
>> building with 7100. Nothing negative to report thus far. It all just
>> built
>> and so far runs on the drivers I have tested.
>>
>>
>>
>> As promised, the RTM WDF CoInstaller did indeed upgrade the 7100 RC KMDF
>> bits without fuss (just a reboot of course).
>>
>>
>>
>> Smooth sailing thus far.
>>
>>
>>
>> Dave Cattley
>>
>>
>>
>>
>> Information from ESET NOD32 Antivirus, version of virus
>> signature database 4314 (20090807)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4314 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4315 (20090807)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
xxxxx@resplendence.com wrote:
So your experience was nothing like mine. I uninstalled the WDK 7100
and then installed the 7600 version.
And that appears to be the only successful order for those operations.
I installed 7600, did some diffs, then tried to uninstall 7100, but the
uninstall failed. It looked like the 7600 install plopped its
uninstaller over the top of the 7100 uninstaller.
Fortunately, “rmdir /s” is still available.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
David R. Cattley wrote:
…
For those about to consider a side-by-side install of the RTM WDK with the
RC WDK I can only report that MSFT has worked hard to maintain the previous
state of affairs. I once again have the rather silly, cryptic, and
completely stupid message from the KitInstaller
> KitSetup is unable to validate that this software kit was produced by
> Microsoft Copr. Due to digital signature verification error(s).
>
> Additional information:
>
> Unable to verify that the specified file was signed by Microsoft Corp.
> Kit content filename: C:\Program Files\Common Files\Microsoft
> KitSetup\Setup Versions\201.104.808.2200\KitSetup.exe
>
> Logfile: C:\DOCUMEN~1\dcattley\LOCALS~1\Temp\WDK-KitSetup.log
>
> [Kitsetup version 201.104.808.2200 error code 0x00c caught during
> initialization of runtime routines. The KitSetup process will now exit.]
>
Yep, that’s exactly what I saw. I thought the reference to the log file
was interesting; I delete those hundreds of log files as soon as I know
the installation is successful, so the referenced file did not actually
exist. I sincerely hope the uninstall doesn’t require them.
Now, the RC and RTM kits both have *different* KitVersionUuid values. The kits are *explicitly* attributed to support side by side.
Did you notice how suspicious the GUIDs are?
From SKOM_1-kit-identification.xml for RC WDK
{515B5358-5757-5459-605A-5B635E5E5F60}
…
From SKOM_1-kit-identification.xml for RTM WDK
{676E6B70-5659-5459-5B5F-6063635E5F61}
They look like ASCII strings, but they’re not intelligible. If the
version field of the UUIDs is right, those are supposed to be SHA-1
UUIDs, but those other bytes are from such a narrow range (51 to 70) as
to make that incredibly unlikely. I’m curious to know how they were
created.
(Note: this is not important. Merely interesting.)
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Did you notice how suspicious the GUIDs are?
Curious. None the less, they need to be unique only within the scope of
world of KitSetup. I think they are free to allocate using whatever
technique they wish. Moreover, these are only a ‘version’ UID subjugated
below the product UID. Which, also, is something only KitSetup cares
about.
I just wish it all worked 
Cheers,
Dave Cattley
Does it mean “no_oacr” doesn’t work? I still haven’t installed 7600 and
my last kit installed is 7202.
BTW, I have 5 WDK beta kits installed at once and no problem. Never
tried to uninstall some, thought. I guess I’ll just delete whole
subtrees.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, August 07, 2009 4:46 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] WDK 7600: So far, so good.Actually, much worse than I thought. Even though I did OACR
stop, the tray
table stuff is coming back So the OACR stop command is
totally broken.
Well at least I have the beta version still to develop with,
I guess I will
only use the release version when I have to ship something.–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr“Don Burn” wrote in message news:xxxxx@ntdev…
> > Well I found the first new problem with 7600. It is in
> OACR, in the
> > previous revisions the command OACR stop would stop the service and
> > eliminate the tray table icon, now OACR stop turns the ICON to red
> > indicating an error, while the service sits there still
> leaking memory
> > like before. You now have to go over to the tray table
> icon manually and
> > select stop to shut things down.
> >
> >
> > –
> > Don Burn (MVP, Windows DKD)
> > Windows Filesystem and Driver Consulting
> > Website: http://www.windrvr.com
> > Blog: http://msmvps.com/blogs/WinDrvr
> >
> >
> >
> > “David R. Cattley” wrote in message
> > news:xxxxx@ntdev…
> >>I have tentatively swapped in 7600 on a number of project
> trees that were
> >> building with 7100. Nothing negative to report thus far.
> It all just
> >> built
> >> and so far runs on the drivers I have tested.
> >>
> >>
> >>
> >> As promised, the RTM WDF CoInstaller did indeed upgrade
> the 7100 RC KMDF
> >> bits without fuss (just a reboot of course).
> >>
> >>
> >>
> >> Smooth sailing thus far.
> >>
> >>
> >>
> >> Dave Cattley
> >>
> >>
> >>
> >>
> >> Information from ESET NOD32 Antivirus, version of virus
> >> signature database 4314 (20090807)
> >>
> >> The message was checked by ESET NOD32 Antivirus.
> >>
> >> http://www.eset.com
> >>
> >>
> >
> >
> >
> > Information from ESET NOD32 Antivirus, version of virus
> > signature database 4314 (20090807)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> >
> >
> >
> > Information from ESET NOD32 Antivirus, version of virus
> > signature database 4315 (20090807)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
>
>
>
> Information from ESET NOD32 Antivirus, version of
> virus signature database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> —
> 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
>
Since I use the build environments off the start menu, I have not tried
this. Nor have I tried the ini file in the WDK directory, since I detest
changing anything in the build tools directory. In fact most firms I have
worked for or consulted for that produce good code have the policy change
the build tools and be fired for cause before you close the editor.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
Does it mean “no_oacr” doesn’t work? I still haven’t installed 7600 and
my last kit installed is 7202.
BTW, I have 5 WDK beta kits installed at once and no problem. Never
tried to uninstall some, thought. I guess I’ll just delete whole
subtrees.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Friday, August 07, 2009 4:46 PM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] WDK 7600: So far, so good.
>
> Actually, much worse than I thought. Even though I did OACR
> stop, the tray
> table stuff is coming back So the OACR stop command is
> totally broken.
> Well at least I have the beta version still to develop with,
> I guess I will
> only use the release version when I have to ship something.
>
>
> –
> Don Burn (MVP, Windows DKD)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
> “Don Burn” wrote in message news:xxxxx@ntdev…
> > Well I found the first new problem with 7600. It is in
> OACR, in the
> > previous revisions the command OACR stop would stop the service and
> > eliminate the tray table icon, now OACR stop turns the ICON to red
> > indicating an error, while the service sits there still
> leaking memory
> > like before. You now have to go over to the tray table
> icon manually and
> > select stop to shut things down.
> >
> >
> > –
> > Don Burn (MVP, Windows DKD)
> > Windows Filesystem and Driver Consulting
> > Website: http://www.windrvr.com
> > Blog: http://msmvps.com/blogs/WinDrvr
> >
> >
> >
> > “David R. Cattley” wrote in message
> > news:xxxxx@ntdev…
> >>I have tentatively swapped in 7600 on a number of project
> trees that were
> >> building with 7100. Nothing negative to report thus far.
> It all just
> >> built
> >> and so far runs on the drivers I have tested.
> >>
> >>
> >>
> >> As promised, the RTM WDF CoInstaller did indeed upgrade
> the 7100 RC KMDF
> >> bits without fuss (just a reboot of course).
> >>
> >>
> >>
> >> Smooth sailing thus far.
> >>
> >>
> >>
> >> Dave Cattley
> >>
> >>
> >>
> >>
> >> Information from ESET NOD32 Antivirus, version of virus
> >> signature database 4314 (20090807)
> >>
> >> The message was checked by ESET NOD32 Antivirus.
> >>
> >> http://www.eset.com
> >>
> >>
> >
> >
> >
> > Information from ESET NOD32 Antivirus, version of virus
> > signature database 4314 (20090807)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> >
> >
> >
> > Information from ESET NOD32 Antivirus, version of virus
> > signature database 4315 (20090807)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
>
>
>
> Information from ESET NOD32 Antivirus, version of
> virus signature database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> —
> 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
>
Information from ESET NOD32 Antivirus, version of virus signature
database 4315 (20090807)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Information from ESET NOD32 Antivirus, version of virus signature database 4315 (20090807)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Do you see changing start menu icon or clone it under new name with
added parameter as build tools change? If so (strange…) you can run
setenv.bat with appropriate parameters from command line. Or write a
small batch. Much easier than to muck with OARC.
I can’t imagine going through 6 levels of menu (just counted 
to start
build environment. If I ever use icons for this purpose, I’d copy
necessary ones to the desktop and adjust parameters appropriately. Now I
have batch files to be called from my editor for this purpose.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, August 07, 2009 7:36 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] WDK 7600: So far, so good.Since I use the build environments off the start menu, I have
not tried
this. Nor have I tried the ini file in the WDK directory,
since I detest
changing anything in the build tools directory. In fact most
firms I have
worked for or consulted for that produce good code have the
policy change
the build tools and be fired for cause before you close the editor.–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr“Michal Vodicka” wrote in message
> news:xxxxx@ntdev…
> Does it mean “no_oacr” doesn’t work? I still haven’t
> installed 7600 and
> my last kit installed is 7202.
>
> BTW, I have 5 WDK beta kits installed at once and no problem. Never
> tried to uninstall some, thought. I guess I’ll just delete whole
> subtrees.
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> > Sent: Friday, August 07, 2009 4:46 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] WDK 7600: So far, so good.
> >
> > Actually, much worse than I thought. Even though I did OACR
> > stop, the tray
> > table stuff is coming back So the OACR stop command is
> > totally broken.
> > Well at least I have the beta version still to develop with,
> > I guess I will
> > only use the release version when I have to ship something.
> >
> >
> > –
> > Don Burn (MVP, Windows DKD)
> > Windows Filesystem and Driver Consulting
> > Website: http://www.windrvr.com
> > Blog: http://msmvps.com/blogs/WinDrvr
> >
> >
> > “Don Burn” wrote in message news:xxxxx@ntdev…
> > > Well I found the first new problem with 7600. It is in
> > OACR, in the
> > > previous revisions the command OACR stop would stop the
> service and
> > > eliminate the tray table icon, now OACR stop turns the ICON to red
> > > indicating an error, while the service sits there still
> > leaking memory
> > > like before. You now have to go over to the tray table
> > icon manually and
> > > select stop to shut things down.
> > >
> > >
> > > –
> > > Don Burn (MVP, Windows DKD)
> > > Windows Filesystem and Driver Consulting
> > > Website: http://www.windrvr.com
> > > Blog: http://msmvps.com/blogs/WinDrvr
> > >
> > >
> > >
> > > “David R. Cattley” wrote in message
> > > news:xxxxx@ntdev…
> > >>I have tentatively swapped in 7600 on a number of project
> > trees that were
> > >> building with 7100. Nothing negative to report thus far.
> > It all just
> > >> built
> > >> and so far runs on the drivers I have tested.
> > >>
> > >>
> > >>
> > >> As promised, the RTM WDF CoInstaller did indeed upgrade
> > the 7100 RC KMDF
> > >> bits without fuss (just a reboot of course).
> > >>
> > >>
> > >>
> > >> Smooth sailing thus far.
> > >>
> > >>
> > >>
> > >> Dave Cattley
> > >>
> > >>
> > >>
> > >>
> > >> Information from ESET NOD32 Antivirus,
> version of virus
> > >> signature database 4314 (20090807)
> > >>
> > >> The message was checked by ESET NOD32 Antivirus.
> > >>
> > >> http://www.eset.com
> > >>
> > >>
> > >
> > >
> > >
> > > Information from ESET NOD32 Antivirus, version of virus
> > > signature database 4314 (20090807)
> > >
> > > The message was checked by ESET NOD32 Antivirus.
> > >
> > > http://www.eset.com
> > >
> > >
> > >
> > >
> > >
> > >
> > > Information from ESET NOD32 Antivirus, version of virus
> > > signature database 4315 (20090807)
> > >
> > > The message was checked by ESET NOD32 Antivirus.
> > >
> > > http://www.eset.com
> > >
> > >
> > >
> >
> >
> >
> > Information from ESET NOD32 Antivirus, version of
> > virus signature database 4315 (20090807)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> >
> >
> > —
> > 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
> >
>
>
> Information from ESET NOD32 Antivirus, version of
> virus signature
> database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> Information from ESET NOD32 Antivirus, version of
> virus signature database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> —
> 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 gave up on the raw setenv since they started changing it for every rev of
the WDK/DDK. I have 6 versions of the tools on my development machine to
match my clients. Trying to remember the setenv options for each forget it.
Cloning the start menu stuff would be a change, where again “Oh I’m using
the Win7 WDK, gotta do something special” is not something I want where I
commonly have more than one environment in use during any given day.
I found I could tolerate starting things up, and when the damm obnoxious
OACR Monitor poped up, saying OACR STOP in the command window. Also, in
talking to folks in the static tools team this was their recommended
approach. So it really sucks that Microsoft broke the recommended way in
the final release.
I know you can argue to take a different approach, but build environments
are like C coding, there are things fixed and constrained such as the “C
language” or the build tools, and there are things that are at developers
preference such as “formatting …” or how you use the tools.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
Do you see changing start menu icon or clone it under new name with
added parameter as build tools change? If so (strange…) you can run
setenv.bat with appropriate parameters from command line. Or write a
small batch. Much easier than to muck with OARC.
I can’t imagine going through 6 levels of menu (just counted to start
build environment. If I ever use icons for this purpose, I’d copy
necessary ones to the desktop and adjust parameters appropriately. Now I
have batch files to be called from my editor for this purpose.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Friday, August 07, 2009 7:36 PM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] WDK 7600: So far, so good.
>
> Since I use the build environments off the start menu, I have
> not tried
> this. Nor have I tried the ini file in the WDK directory,
> since I detest
> changing anything in the build tools directory. In fact most
> firms I have
> worked for or consulted for that produce good code have the
> policy change
> the build tools and be fired for cause before you close the editor.
>
>
> –
> Don Burn (MVP, Windows DKD)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
> “Michal Vodicka” wrote in message
> news:xxxxx@ntdev…
> Does it mean “no_oacr” doesn’t work? I still haven’t
> installed 7600 and
> my last kit installed is 7202.
>
> BTW, I have 5 WDK beta kits installed at once and no problem. Never
> tried to uninstall some, thought. I guess I’ll just delete whole
> subtrees.
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> > Sent: Friday, August 07, 2009 4:46 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] WDK 7600: So far, so good.
> >
> > Actually, much worse than I thought. Even though I did OACR
> > stop, the tray
> > table stuff is coming back So the OACR stop command is
> > totally broken.
> > Well at least I have the beta version still to develop with,
> > I guess I will
> > only use the release version when I have to ship something.
> >
> >
> > –
> > Don Burn (MVP, Windows DKD)
> > Windows Filesystem and Driver Consulting
> > Website: http://www.windrvr.com
> > Blog: http://msmvps.com/blogs/WinDrvr
> >
> >
> > “Don Burn” wrote in message news:xxxxx@ntdev…
> > > Well I found the first new problem with 7600. It is in
> > OACR, in the
> > > previous revisions the command OACR stop would stop the
> service and
> > > eliminate the tray table icon, now OACR stop turns the ICON to red
> > > indicating an error, while the service sits there still
> > leaking memory
> > > like before. You now have to go over to the tray table
> > icon manually and
> > > select stop to shut things down.
> > >
> > >
> > > –
> > > Don Burn (MVP, Windows DKD)
> > > Windows Filesystem and Driver Consulting
> > > Website: http://www.windrvr.com
> > > Blog: http://msmvps.com/blogs/WinDrvr
> > >
> > >
> > >
> > > “David R. Cattley” wrote in message
> > > news:xxxxx@ntdev…
> > >>I have tentatively swapped in 7600 on a number of project
> > trees that were
> > >> building with 7100. Nothing negative to report thus far.
> > It all just
> > >> built
> > >> and so far runs on the drivers I have tested.
> > >>
> > >>
> > >>
> > >> As promised, the RTM WDF CoInstaller did indeed upgrade
> > the 7100 RC KMDF
> > >> bits without fuss (just a reboot of course).
> > >>
> > >>
> > >>
> > >> Smooth sailing thus far.
> > >>
> > >>
> > >>
> > >> Dave Cattley
> > >>
> > >>
> > >>
> > >>
> > >> Information from ESET NOD32 Antivirus,
> version of virus
> > >> signature database 4314 (20090807)
> > >>
> > >> The message was checked by ESET NOD32 Antivirus.
> > >>
> > >> http://www.eset.com
> > >>
> > >>
> > >
> > >
> > >
> > > Information from ESET NOD32 Antivirus, version of virus
> > > signature database 4314 (20090807)
> > >
> > > The message was checked by ESET NOD32 Antivirus.
> > >
> > > http://www.eset.com
> > >
> > >
> > >
> > >
> > >
> > >
> > > Information from ESET NOD32 Antivirus, version of virus
> > > signature database 4315 (20090807)
> > >
> > > The message was checked by ESET NOD32 Antivirus.
> > >
> > > http://www.eset.com
> > >
> > >
> > >
> >
> >
> >
> > Information from ESET NOD32 Antivirus, version of
> > virus signature database 4315 (20090807)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> >
> >
> > —
> > 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
> >
>
>
> Information from ESET NOD32 Antivirus, version of
> virus signature
> database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> Information from ESET NOD32 Antivirus, version of
> virus signature database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> —
> 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
>
Information from ESET NOD32 Antivirus, version of virus signature
database 4315 (20090807)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Information from ESET NOD32 Antivirus, version of virus signature database 4315 (20090807)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
I quite understand developers’ preferences…
I have setenv parameters changes handled inside my batch with simpler
set of parameters. It is a pain, sometimes. Especially amd64 -> x64
change was great.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, August 07, 2009 8:00 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] WDK 7600: So far, so good.I gave up on the raw setenv since they started changing it
for every rev of
the WDK/DDK. I have 6 versions of the tools on my
development machine to
match my clients. Trying to remember the setenv options for
each forget it.
Cloning the start menu stuff would be a change, where again
“Oh I’m using
the Win7 WDK, gotta do something special” is not something I
want where I
commonly have more than one environment in use during any given day.I found I could tolerate starting things up, and when the
damm obnoxious
OACR Monitor poped up, saying OACR STOP in the command
window. Also, in
talking to folks in the static tools team this was their recommended
approach. So it really sucks that Microsoft broke the
recommended way in
the final release.I know you can argue to take a different approach, but build
environments
are like C coding, there are things fixed and constrained
such as the “C
language” or the build tools, and there are things that are
at developers
preference such as “formatting …” or how you use the tools.–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr“Michal Vodicka” wrote in message
> news:xxxxx@ntdev…
> Do you see changing start menu icon or clone it under new name with
> added parameter as build tools change? If so (strange…) you can run
> setenv.bat with appropriate parameters from command line. Or write a
> small batch. Much easier than to muck with OARC.
>
> I can’t imagine going through 6 levels of menu (just counted
>
> build environment. If I ever use icons for this purpose, I’d copy
> necessary ones to the desktop and adjust parameters
> appropriately. Now I
> have batch files to be called from my editor for this purpose.
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> > Sent: Friday, August 07, 2009 7:36 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] WDK 7600: So far, so good.
> >
> > Since I use the build environments off the start menu, I have
> > not tried
> > this. Nor have I tried the ini file in the WDK directory,
> > since I detest
> > changing anything in the build tools directory. In fact most
> > firms I have
> > worked for or consulted for that produce good code have the
> > policy change
> > the build tools and be fired for cause before you close the editor.
> >
> >
> > –
> > Don Burn (MVP, Windows DKD)
> > Windows Filesystem and Driver Consulting
> > Website: http://www.windrvr.com
> > Blog: http://msmvps.com/blogs/WinDrvr
> >
> >
> > “Michal Vodicka” wrote in message
> > news:xxxxx@ntdev…
> > Does it mean “no_oacr” doesn’t work? I still haven’t
> > installed 7600 and
> > my last kit installed is 7202.
> >
> > BTW, I have 5 WDK beta kits installed at once and no problem. Never
> > tried to uninstall some, thought. I guess I’ll just delete whole
> > subtrees.
> >
> > Best regards,
> >
> > Michal Vodicka
> > UPEK, Inc.
> > [xxxxx@upek.com, http://www.upek.com]
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> > > Sent: Friday, August 07, 2009 4:46 PM
> > > To: Windows System Software Devs Interest List
> > > Subject: Re:[ntdev] WDK 7600: So far, so good.
> > >
> > > Actually, much worse than I thought. Even though I did OACR
> > > stop, the tray
> > > table stuff is coming back So the OACR stop command is
> > > totally broken.
> > > Well at least I have the beta version still to develop with,
> > > I guess I will
> > > only use the release version when I have to ship something.
> > >
> > >
> > > –
> > > Don Burn (MVP, Windows DKD)
> > > Windows Filesystem and Driver Consulting
> > > Website: http://www.windrvr.com
> > > Blog: http://msmvps.com/blogs/WinDrvr
> > >
> > >
> > > “Don Burn” wrote in message news:xxxxx@ntdev…
> > > > Well I found the first new problem with 7600. It is in
> > > OACR, in the
> > > > previous revisions the command OACR stop would stop the
> > service and
> > > > eliminate the tray table icon, now OACR stop turns the
> ICON to red
> > > > indicating an error, while the service sits there still
> > > leaking memory
> > > > like before. You now have to go over to the tray table
> > > icon manually and
> > > > select stop to shut things down.
> > > >
> > > >
> > > > –
> > > > Don Burn (MVP, Windows DKD)
> > > > Windows Filesystem and Driver Consulting
> > > > Website: http://www.windrvr.com
> > > > Blog: http://msmvps.com/blogs/WinDrvr
> > > >
> > > >
> > > >
> > > > “David R. Cattley” wrote in message
> > > > news:xxxxx@ntdev…
> > > >>I have tentatively swapped in 7600 on a number of project
> > > trees that were
> > > >> building with 7100. Nothing negative to report thus far.
> > > It all just
> > > >> built
> > > >> and so far runs on the drivers I have tested.
> > > >>
> > > >>
> > > >>
> > > >> As promised, the RTM WDF CoInstaller did indeed upgrade
> > > the 7100 RC KMDF
> > > >> bits without fuss (just a reboot of course).
> > > >>
> > > >>
> > > >>
> > > >> Smooth sailing thus far.
> > > >>
> > > >>
> > > >>
> > > >> Dave Cattley
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> Information from ESET NOD32 Antivirus,
> > version of virus
> > > >> signature database 4314 (20090807)
> > > >>
> > > >> The message was checked by ESET NOD32 Antivirus.
> > > >>
> > > >> http://www.eset.com
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > > Information from ESET NOD32 Antivirus,
> version of virus
> > > > signature database 4314 (20090807)
> > > >
> > > > The message was checked by ESET NOD32 Antivirus.
> > > >
> > > > http://www.eset.com
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Information from ESET NOD32 Antivirus,
> version of virus
> > > > signature database 4315 (20090807)
> > > >
> > > > The message was checked by ESET NOD32 Antivirus.
> > > >
> > > > http://www.eset.com
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > Information from ESET NOD32 Antivirus, version of
> > > virus signature database 4315 (20090807)
> > >
> > > The message was checked by ESET NOD32 Antivirus.
> > >
> > > http://www.eset.com
> > >
> > >
> > >
> > >
> > >
> > > —
> > > 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
> > >
> >
> >
> > Information from ESET NOD32 Antivirus, version of
> > virus signature
> > database 4315 (20090807)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> >
> >
> > Information from ESET NOD32 Antivirus, version of
> > virus signature database 4315 (20090807)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> >
> >
> > —
> > 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
> >
>
>
> Information from ESET NOD32 Antivirus, version of
> virus signature
> database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> Information from ESET NOD32 Antivirus, version of
> virus signature database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> —
> 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
>
Michal Vodicka wrote:
Does it mean “no_oacr” doesn’t work? I still haven’t installed 7600 and
my last kit installed is 7202.
Yes, no_oacr works in 7600. Or, given the sense of your question, “no,
no_oacr still works in 7600.”
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
I should have also mentioned that the INI file change documented in the WDK
for all beta’s did not disable the monitor is just caused it to sit there in
the tool tray and did not obnoxiously popup. It did obnoxiously take cpu
time and leak memory, until one used OACR STOP to shut it off completely.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“Don Burn” wrote in message news:xxxxx@ntdev…
>I gave up on the raw setenv since they started changing it for every rev of
>the WDK/DDK. I have 6 versions of the tools on my development machine to
>match my clients. Trying to remember the setenv options for each forget
>it. Cloning the start menu stuff would be a change, where again “Oh I’m
>using the Win7 WDK, gotta do something special” is not something I want
>where I commonly have more than one environment in use during any given
>day.
>
> I found I could tolerate starting things up, and when the damm obnoxious
> OACR Monitor poped up, saying OACR STOP in the command window. Also, in
> talking to folks in the static tools team this was their recommended
> approach. So it really sucks that Microsoft broke the recommended way in
> the final release.
>
> I know you can argue to take a different approach, but build environments
> are like C coding, there are things fixed and constrained such as the “C
> language” or the build tools, and there are things that are at developers
> preference such as “formatting …” or how you use the tools.
>
>
> –
> Don Burn (MVP, Windows DKD)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
> “Michal Vodicka” wrote in message
> news:xxxxx@ntdev…
> Do you see changing start menu icon or clone it under new name with
> added parameter as build tools change? If so (strange…) you can run
> setenv.bat with appropriate parameters from command line. Or write a
> small batch. Much easier than to muck with OARC.
>
> I can’t imagine going through 6 levels of menu (just counted to start
> build environment. If I ever use icons for this purpose, I’d copy
> necessary ones to the desktop and adjust parameters appropriately. Now I
> have batch files to be called from my editor for this purpose.
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
>
>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
>> Sent: Friday, August 07, 2009 7:36 PM
>> To: Windows System Software Devs Interest List
>> Subject: Re:[ntdev] WDK 7600: So far, so good.
>>
>> Since I use the build environments off the start menu, I have
>> not tried
>> this. Nor have I tried the ini file in the WDK directory,
>> since I detest
>> changing anything in the build tools directory. In fact most
>> firms I have
>> worked for or consulted for that produce good code have the
>> policy change
>> the build tools and be fired for cause before you close the editor.
>>
>>
>> –
>> Don Burn (MVP, Windows DKD)
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>>
>>
>> “Michal Vodicka” wrote in message
>> news:xxxxx@ntdev…
>> Does it mean “no_oacr” doesn’t work? I still haven’t
>> installed 7600 and
>> my last kit installed is 7202.
>>
>> BTW, I have 5 WDK beta kits installed at once and no problem. Never
>> tried to uninstall some, thought. I guess I’ll just delete whole
>> subtrees.
>>
>> Best regards,
>>
>> Michal Vodicka
>> UPEK, Inc.
>> [xxxxx@upek.com, http://www.upek.com]
>>
>> > -----Original Message-----
>> > From: xxxxx@lists.osr.com
>> > [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
>> > Sent: Friday, August 07, 2009 4:46 PM
>> > To: Windows System Software Devs Interest List
>> > Subject: Re:[ntdev] WDK 7600: So far, so good.
>> >
>> > Actually, much worse than I thought. Even though I did OACR
>> > stop, the tray
>> > table stuff is coming back So the OACR stop command is
>> > totally broken.
>> > Well at least I have the beta version still to develop with,
>> > I guess I will
>> > only use the release version when I have to ship something.
>> >
>> >
>> > –
>> > Don Burn (MVP, Windows DKD)
>> > Windows Filesystem and Driver Consulting
>> > Website: http://www.windrvr.com
>> > Blog: http://msmvps.com/blogs/WinDrvr
>> >
>> >
>> > “Don Burn” wrote in message news:xxxxx@ntdev…
>> > > Well I found the first new problem with 7600. It is in
>> > OACR, in the
>> > > previous revisions the command OACR stop would stop the
>> service and
>> > > eliminate the tray table icon, now OACR stop turns the ICON to red
>> > > indicating an error, while the service sits there still
>> > leaking memory
>> > > like before. You now have to go over to the tray table
>> > icon manually and
>> > > select stop to shut things down.
>> > >
>> > >
>> > > –
>> > > Don Burn (MVP, Windows DKD)
>> > > Windows Filesystem and Driver Consulting
>> > > Website: http://www.windrvr.com
>> > > Blog: http://msmvps.com/blogs/WinDrvr
>> > >
>> > >
>> > >
>> > > “David R. Cattley” wrote in message
>> > > news:xxxxx@ntdev…
>> > >>I have tentatively swapped in 7600 on a number of project
>> > trees that were
>> > >> building with 7100. Nothing negative to report thus far.
>> > It all just
>> > >> built
>> > >> and so far runs on the drivers I have tested.
>> > >>
>> > >>
>> > >>
>> > >> As promised, the RTM WDF CoInstaller did indeed upgrade
>> > the 7100 RC KMDF
>> > >> bits without fuss (just a reboot of course).
>> > >>
>> > >>
>> > >>
>> > >> Smooth sailing thus far.
>> > >>
>> > >>
>> > >>
>> > >> Dave Cattley
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> Information from ESET NOD32 Antivirus,
>> version of virus
>> > >> signature database 4314 (20090807)
>> > >>
>> > >> The message was checked by ESET NOD32 Antivirus.
>> > >>
>> > >> http://www.eset.com
>> > >>
>> > >>
>> > >
>> > >
>> > >
>> > > Information from ESET NOD32 Antivirus, version of virus
>> > > signature database 4314 (20090807)
>> > >
>> > > The message was checked by ESET NOD32 Antivirus.
>> > >
>> > > http://www.eset.com
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > Information from ESET NOD32 Antivirus, version of virus
>> > > signature database 4315 (20090807)
>> > >
>> > > The message was checked by ESET NOD32 Antivirus.
>> > >
>> > > http://www.eset.com
>> > >
>> > >
>> > >
>> >
>> >
>> >
>> > Information from ESET NOD32 Antivirus, version of
>> > virus signature database 4315 (20090807)
>> >
>> > The message was checked by ESET NOD32 Antivirus.
>> >
>> > http://www.eset.com
>> >
>> >
>> >
>> >
>> >
>> > —
>> > 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
>> >
>>
>>
>> Information from ESET NOD32 Antivirus, version of
>> virus signature
>> database 4315 (20090807)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>> Information from ESET NOD32 Antivirus, version of
>> virus signature database 4315 (20090807)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>> —
>> 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
>>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4315 (20090807)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4315 (20090807)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
“David R. Cattley” wrote in message news:xxxxx@ntdev…
> …
> I just wish it all worked
>
So… xcopy install rocks.
No mess with existing windbg or docum. explorer, no guesswork where it will
land
and what it would clobber. Works on XP x64 too - at least, the xcopy part
of it
Regards,
–pa
“Pavel A.” wrote in message news:xxxxx@ntdev…
> So… xcopy install rocks.
> No mess with existing windbg or docum. explorer, no guesswork where it
> will land
> and what it would clobber. Works on XP x64 too - at least, the xcopy part
> of it
>
That’s not very simple if all you have is 244 msi and cab files. But it’s
worth remembering that msi files can be extracted by executing msiexec /a
//Daniel
Daniel, I believe that your problem is due to not having whatever version of .NET that KitSetup.exe ‘bootstraps’ installed. At least, that fixed it for me when I had this problem with the 6801 & 7000 wdks.
Also, when I had the DExplorer issue, it also crushed my VS & Office installations in exactly the same way - didn’t work, couldn’t uninstall, couldn’t reinstall. I hope that this hasn’t happened to you as well.
mm
In fact most firms I have worked for or consulted for that produce good code have the policy change
the build tools and be fired for cause before you close the editor.
Are you saying that that includes creating your own shortcuts?
mm