Installing WDK on different drive from C:

NTDEV
1

Is there some reason why the installation program for the new WDK
doesn’t allow the user to select an installation root on a drive other
than C:? I understand why you want a single root for all Windows Kits.
But why does that single root have to be on C:? The framework is
present to edit the Kit root; however, the option currently is greyed out.

2

The kit root is shared amongst all of the windows 8 kits (wdk, sdk, adk, whck, etc). once the kit root is set by the first kit, you can’t change it. If you install VS 2012 first, it installs the win8 sdk and sets the root. If not set, you can install anywhere

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of George M. Garner Jr.
Sent: Tuesday, June 5, 2012 3:13 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Installing WDK on different drive from C:

Is there some reason why the installation program for the new WDK doesn’t allow the user to select an installation root on a drive other than C:? I understand why you want a single root for all Windows Kits.
But why does that single root have to be on C:? The framework is present to edit the Kit root; however, the option currently is greyed out.

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

3

Doron,

The kit root is shared amongst all of the windows 8 kits (wdk, sdk,
> adk, whck, etc).

I know that. However, I installed VS 2012 with the Win8 SDK and all of
the other kits on D:. What I am asking is why the wdk won’t let me
install it in the same location as all of the other “kits.” I did, btw.
a completely fresh install of EVERYTHING for this, new OS in new VM with
fresh install of VS 2010 and all of the released sdk’s and wdks. The OS
is on c:. All of the kits but one is installed on d:. Why does the w8
wdk need to be installed on c:?

Regards,

George.

4

Which kit is the “but one” in your statement below? How did you get the but one into a different root? All of the w8 kit installers are the same code, so all should behave the same wrt to install directory

d

debt from my phone

From: George M. Garner Jr.
Sent: 6/5/2012 4:53 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Installing WDK on different drive from C:

Doron,

The kit root is shared amongst all of the windows 8 kits (wdk, sdk,
> adk, whck, etc).

I know that. However, I installed VS 2012 with the Win8 SDK and all of
the other kits on D:. What I am asking is why the wdk won’t let me
install it in the same location as all of the other “kits.” I did, btw.
a completely fresh install of EVERYTHING for this, new OS in new VM with
fresh install of VS 2010 and all of the released sdk’s and wdks. The OS
is on c:. All of the kits but one is installed on d:. Why does the w8
wdk need to be installed on c:?

Regards,

George.

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

5

This kind of nonsense is typical; everyone at Microsoft has effectively an
unlimited C: drive, and therefore no one else in the world has any
limitations based on drive size or working methods.

The alternate explanation is that we must be protected, and we ourselves
are not capable of making responsible decisions. Witness VS, which fails
to operate correctly if your working drive is on a network server. The
rationale was that using the server over 100Mbit lines was too slow, and
all us poor users should be prevented from making decisions that are Bad
For Us. So now, you have to duplicate your development structure on your
local disk, which is silly. I pointed out that it is nearly impossible to
buy a new system with a network slower than 1Gbit, that, as a single
developer, I don’t have problems with multiple developers overwriting each
other’s builds, and I do not wish to be denied the use of my 4TB network
drive.

Also, when I was traveling, for data security purposes all files were kept
on a flash drive, which I carried in my pocket, so if my laptop was
stolen, no confidential information would be compromised. I was told this
should not be supported, because flash drives are slow and have limited
lifetimes. I pointed out that it was my choice to deal with potentially
slower builds and device costs (at $12 for 4GB, I’m supposed to CARE???),
not theirs to demand that I cripple my reliability and data security
because some youngster thinks using other drives might be a Bad Thing.

There is a horrid fascination with C:, which I attribute to lack of
experience among the programmers and their supervisors. This seems to get
only worse as the experienced people move up or retire.
joe

Is there some reason why the installation program for the new WDK
doesn’t allow the user to select an installation root on a drive other
than C:? I understand why you want a single root for all Windows Kits.
But why does that single root have to be on C:? The framework is
present to edit the Kit root; however, the option currently is greyed out.

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

6

There is no disposition to c:. There is a default to %program files %. If you want program files to point somewhere else, right click on it in explorer and redirect it somewhere else. If you want to boot off usb flash, use windows to go.

Running off a share assumes a state free app. Vs is not state free, nor is pretty much any msi installed app with external dependencies

d

debt from my phone

From: xxxxx@flounder.com
Sent: 6/5/2012 6:30 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installing WDK on different drive from C:

This kind of nonsense is typical; everyone at Microsoft has effectively an
unlimited C: drive, and therefore no one else in the world has any
limitations based on drive size or working methods.

The alternate explanation is that we must be protected, and we ourselves
are not capable of making responsible decisions. Witness VS, which fails
to operate correctly if your working drive is on a network server. The
rationale was that using the server over 100Mbit lines was too slow, and
all us poor users should be prevented from making decisions that are Bad
For Us. So now, you have to duplicate your development structure on your
local disk, which is silly. I pointed out that it is nearly impossible to
buy a new system with a network slower than 1Gbit, that, as a single
developer, I don’t have problems with multiple developers overwriting each
other’s builds, and I do not wish to be denied the use of my 4TB network
drive.

Also, when I was traveling, for data security purposes all files were kept
on a flash drive, which I carried in my pocket, so if my laptop was
stolen, no confidential information would be compromised. I was told this
should not be supported, because flash drives are slow and have limited
lifetimes. I pointed out that it was my choice to deal with potentially
slower builds and device costs (at $12 for 4GB, I’m supposed to CARE???),
not theirs to demand that I cripple my reliability and data security
because some youngster thinks using other drives might be a Bad Thing.

There is a horrid fascination with C:, which I attribute to lack of
experience among the programmers and their supervisors. This seems to get
only worse as the experienced people move up or retire.
joe

Is there some reason why the installation program for the new WDK
doesn’t allow the user to select an installation root on a drive other
than C:? I understand why you want a single root for all Windows Kits.
But why does that single root have to be on C:? The framework is
present to edit the Kit root; however, the option currently is greyed out.

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

7

Note that I am not running VS from my shared drive, I am BUILDING to the
shared drive, where the source and output directories are on the share.
What will happen is that I eventually get an error “Insufficient resources
to perform the operation” (at least that is what is reported) from VS when
it tries to write the .pch file. How a system with 8GB main memory, 140GB
hard drive, 4TB shared drive can “run out of resources” puzzles me. I
cannot think of any reason other than driver bugs and application bugs
that could cause this.
joe

There is no disposition to c:. There is a default to %program files %. If
you want program files to point somewhere else, right click on it in
explorer and redirect it somewhere else. If you want to boot off usb
flash, use windows to go.

Running off a share assumes a state free app. Vs is not state free, nor is
pretty much any msi installed app with external dependencies

d

debt from my phone

From: xxxxx@flounder.com
Sent: 6/5/2012 6:30 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installing WDK on different drive from C:

This kind of nonsense is typical; everyone at Microsoft has effectively an
unlimited C: drive, and therefore no one else in the world has any
limitations based on drive size or working methods.

The alternate explanation is that we must be protected, and we ourselves
are not capable of making responsible decisions. Witness VS, which fails
to operate correctly if your working drive is on a network server. The
rationale was that using the server over 100Mbit lines was too slow, and
all us poor users should be prevented from making decisions that are Bad
For Us. So now, you have to duplicate your development structure on your
local disk, which is silly. I pointed out that it is nearly impossible to
buy a new system with a network slower than 1Gbit, that, as a single
developer, I don’t have problems with multiple developers overwriting each
other’s builds, and I do not wish to be denied the use of my 4TB network
drive.

Also, when I was traveling, for data security purposes all files were kept
on a flash drive, which I carried in my pocket, so if my laptop was
stolen, no confidential information would be compromised. I was told this
should not be supported, because flash drives are slow and have limited
lifetimes. I pointed out that it was my choice to deal with potentially
slower builds and device costs (at $12 for 4GB, I’m supposed to CARE???),
not theirs to demand that I cripple my reliability and data security
because some youngster thinks using other drives might be a Bad Thing.

There is a horrid fascination with C:, which I attribute to lack of
experience among the programmers and their supervisors. This seems to get
only worse as the experienced people move up or retire.
joe

> Is there some reason why the installation program for the new WDK
> doesn’t allow the user to select an installation root on a drive other
> than C:? I understand why you want a single root for all Windows Kits.
> But why does that single root have to be on C:? The framework is
> present to edit the Kit root; however, the option currently is greyed
> out.
>
> —
> 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

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

8

Run process explorer on your build and see if it fails in the network or file io stack and then report the bug.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@flounder.com
Sent: Tuesday, June 5, 2012 7:58 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Installing WDK on different drive from C:

Note that I am not running VS from my shared drive, I am BUILDING to the shared drive, where the source and output directories are on the share.
What will happen is that I eventually get an error “Insufficient resources to perform the operation” (at least that is what is reported) from VS when it tries to write the .pch file. How a system with 8GB main memory, 140GB hard drive, 4TB shared drive can “run out of resources” puzzles me. I cannot think of any reason other than driver bugs and application bugs that could cause this.
joe

There is no disposition to c:. There is a default to %program files %.
If you want program files to point somewhere else, right click on it
in explorer and redirect it somewhere else. If you want to boot off
usb flash, use windows to go.

Running off a share assumes a state free app. Vs is not state free,
nor is pretty much any msi installed app with external dependencies

d

debt from my phone

From: xxxxx@flounder.com
Sent: 6/5/2012 6:30 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installing WDK on different drive from C:

This kind of nonsense is typical; everyone at Microsoft has
effectively an unlimited C: drive, and therefore no one else in the
world has any limitations based on drive size or working methods.

The alternate explanation is that we must be protected, and we ourselves
are not capable of making responsible decisions. Witness VS, which fails
to operate correctly if your working drive is on a network server.
The rationale was that using the server over 100Mbit lines was too
slow, and all us poor users should be prevented from making decisions
that are Bad For Us. So now, you have to duplicate your development
structure on your local disk, which is silly. I pointed out that it
is nearly impossible to buy a new system with a network slower than
1Gbit, that, as a single developer, I don’t have problems with
multiple developers overwriting each other’s builds, and I do not wish
to be denied the use of my 4TB network drive.

Also, when I was traveling, for data security purposes all files were
kept on a flash drive, which I carried in my pocket, so if my laptop
was stolen, no confidential information would be compromised. I was
told this should not be supported, because flash drives are slow and
have limited lifetimes. I pointed out that it was my choice to deal
with potentially slower builds and device costs (at $12 for 4GB, I’m
supposed to CARE???), not theirs to demand that I cripple my
reliability and data security because some youngster thinks using other drives might be a Bad Thing.

There is a horrid fascination with C:, which I attribute to lack of
experience among the programmers and their supervisors. This seems to
get only worse as the experienced people move up or retire.
joe

> Is there some reason why the installation program for the new WDK
> doesn’t allow the user to select an installation root on a drive
> other than C:? I understand why you want a single root for all Windows Kits.
> But why does that single root have to be on C:? The framework is
> present to edit the Kit root; however, the option currently is greyed
> out.
>
> —
> 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

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

9

You can just copy all the files onto the other disk, and symlink or mount it
to c:\whatever.
In Win8, Explorer nicely shows the synlinks as shortcuts.
That’s the True Unix Way :slight_smile:
– pa

10

On 6/5/2012 8:25 PM, Doron Holan wrote:

Which kit is the “but one” in your statement below? How did you get the
but one into a different root?

w8 wdk.

I installed in the following order to a fresh install of w7x64sp1:

  1. vs2010 -> d:
  2. Windows sdk 7.1 -> d:
  3. Windows wdk 7.1 -> d:
  4. vs2012 -> d:
  5. w8 wdk -> c: (option to change path greyed out).

VS2012 installed some stuff (e.g msbuild) on the c: drive
notwithstanding the installation path which I selected. Perhaps, VS2012
created the Kit path on c: and the w8 wdk followed it without question.
I would have to roll back the vm and do the (lengthy) install process
over to find out. Is there a service key which the wdk uses to locate
the “Kit” installation path? Perhaps I could create that and point it
to d: before undertaking steps 4 and 5.

Regards,

George.

11

Doron,

Perhaps, VS2012
created the Kit path on c: and the w8 wdk followed it without question.

That is indeed what happened! VS2012 installed some “Kits” (e.g.
Silverlight and Metro App dev) to c: notwithstanding the fact that I had
selected d: as the install path. This is a VS bug. I will try manually
setting the kit path to d: and reinstall. We’ll see if VS ignores the
existing kit path.

Regards,

George.

12

Those Kits are not kits built by windows, so the common kit root statement doesn’t apply. Regardless of where you install, some sub components (like msbuild) have their own hard coded roots, usually under %program files% or %program files (x86)%…which you should be able to reconfigure

d

debt from my phone

From: George M. Garner Jr.
Sent: 6/6/2012 9:59 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Installing WDK on different drive from C:

Doron,

Perhaps, VS2012
created the Kit path on c: and the w8 wdk followed it without question.

That is indeed what happened! VS2012 installed some “Kits” (e.g.
Silverlight and Metro App dev) to c: notwithstanding the fact that I had
selected d: as the install path. This is a VS bug. I will try manually
setting the kit path to d: and reinstall. We’ll see if VS ignores the
existing kit path.

Regards,

George.

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

13

Reconfigure how?

Thanks,

mm

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, June 06, 2012 10:23 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Installing WDK on different drive from C:

Those Kits are not kits built by windows, so the common kit root statement
doesn’t apply. Regardless of where you install, some sub components (like
msbuild) have their own hard coded roots, usually under %program files% or
%program files (x86)%…which you should be able to reconfigure

d

debt from my phone

From: George M. Garner Jr.
Sent: 6/6/2012 9:59 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Installing WDK on different drive from C:

Doron,

Perhaps, VS2012
created the Kit path on c: and the w8 wdk followed it without question.

That is indeed what happened! VS2012 installed some “Kits” (e.g.
Silverlight and Metro App dev) to c: notwithstanding the fact that I had
selected d: as the install path. This is a VS bug. I will try manually
setting the kit path to d: and reinstall. We’ll see if VS ignores the
existing kit path.

Regards,

George.

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

14

On 6/6/2012 1:38 PM, Martin O’Brien wrote:

Reconfigure how?

Thanks,

mm

By changing the value of the environment variable, I presume. Not
exactly an ideal solution. However, it does explain why MSBuild has to
go on c: (unless you want to change the value of %program files(x86)%
for everybody).

15

Iirc, right click a change where it points to in the properties page. That, or there is a supported reg value you can muck with.

d

debt from my phone

From: Martin O’Brien
Sent: 6/6/2012 10:38 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Installing WDK on different drive from C:

Reconfigure how?

Thanks,

mm

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, June 06, 2012 10:23 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Installing WDK on different drive from C:

Those Kits are not kits built by windows, so the common kit root statement doesn’t apply. Regardless of where you install, some sub components (like msbuild) have their own hard coded roots, usually under %program files% or %program files (x86)%…which you should be able to reconfigure

d

debt from my phone

From: George M. Garner Jr.
Sent: 6/6/2012 9:59 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Installing WDK on different drive from C:
Doron,

Perhaps, VS2012
created the Kit path on c: and the w8 wdk followed it without question.

That is indeed what happened! VS2012 installed some “Kits” (e.g.
Silverlight and Metro App dev) to c: notwithstanding the fact that I had
selected d: as the install path. This is a VS bug. I will try manually
setting the kit path to d: and reinstall. We’ll see if VS ignores the
existing kit path.

Regards,

George.

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

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

16

That was the only thing I could think of too, but that doesn’t seem like a
workable solution. I mean, surely something else is going to complain.

mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of George M. Garner Jr.
Sent: Wednesday, June 06, 2012 10:43 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Installing WDK on different drive from C:

On 6/6/2012 1:38 PM, Martin O’Brien wrote:

Reconfigure how?

Thanks,

mm

By changing the value of the environment variable, I presume. Not exactly
an ideal solution. However, it does explain why MSBuild has to go on c:
(unless you want to change the value of %program files(x86)% for everybody).

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

17

Ah.

Thanks,

mm

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, June 06, 2012 10:44 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Installing WDK on different drive from C:

Iirc, right click a change where it points to in the properties page. That,
or there is a supported reg value you can muck with.

d

debt from my phone

From: Martin O’Brien
Sent: 6/6/2012 10:38 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Installing WDK on different drive from C:

Reconfigure how?

Thanks,

mm

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, June 06, 2012 10:23 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Installing WDK on different drive from C:

Those Kits are not kits built by windows, so the common kit root statement
doesn’t apply. Regardless of where you install, some sub components (like
msbuild) have their own hard coded roots, usually under %program files% or
%program files (x86)%…which you should be able to reconfigure

d

debt from my phone

From: George M. Garner Jr.
Sent: 6/6/2012 9:59 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Installing WDK on different drive from C:

Doron,

Perhaps, VS2012
created the Kit path on c: and the w8 wdk followed it without question.

That is indeed what happened! VS2012 installed some “Kits” (e.g.
Silverlight and Metro App dev) to c: notwithstanding the fact that I had
selected d: as the install path. This is a VS bug. I will try manually
setting the kit path to d: and reinstall. We’ll see if VS ignores the
existing kit path.

Regards,

George.

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

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

18

Moving stuff off of drive C: is critically important to folks who have SSD
boot drives.

Thomas F. Divine

From: “Martin O’Brien”
Sent: Wednesday, June 06, 2012 1:46 PM
To: “Windows System Software Devs Interest List”
Subject: RE: [ntdev] Installing WDK on different drive from C:

> That was the only thing I could think of too, but that doesn’t seem like a
> workable solution. I mean, surely something else is going to complain.
>
>
>
> mm
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of George M. Garner
> Jr.
> Sent: Wednesday, June 06, 2012 10:43 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Installing WDK on different drive from C:
>
> On 6/6/2012 1:38 PM, Martin O’Brien wrote:
>> Reconfigure how?
>>
>> Thanks,
>>
>> mm
>>
>
> By changing the value of the environment variable, I presume. Not exactly
> an ideal solution. However, it does explain why MSBuild has to go on c:
> (unless you want to change the value of %program files(x86)% for
> everybody).
>
>
> —
> 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

19

Outstanding point.

I have this problem myself right now, actually.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Thomas F. Divine
Sent: Wednesday, June 06, 2012 11:13 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installing WDK on different drive from C:

Moving stuff off of drive C: is critically important to folks who have SSD
boot drives.

Thomas F. Divine

From: “Martin O’Brien”
Sent: Wednesday, June 06, 2012 1:46 PM
To: “Windows System Software Devs Interest List”
Subject: RE: [ntdev] Installing WDK on different drive from C:

> That was the only thing I could think of too, but that doesn’t seem
> like a workable solution. I mean, surely something else is going to
complain.
>
>
>
> mm
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of George M.
> Garner Jr.
> Sent: Wednesday, June 06, 2012 10:43 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Installing WDK on different drive from C:
>
> On 6/6/2012 1:38 PM, Martin O’Brien wrote:
>> Reconfigure how?
>>
>> Thanks,
>>
>> mm
>>
>
> By changing the value of the environment variable, I presume. Not
> exactly an ideal solution. However, it does explain why MSBuild has to go
on c:
> (unless you want to change the value of %program files(x86)% for
> everybody).
>
>
> —
> 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

—
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

20

And that is why you should configure program files and the 32 bit version of it to another drive as soon you install windows, not necessarily a problem that VS introduces

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Thomas F. Divine
Sent: Wednesday, June 6, 2012 11:13 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installing WDK on different drive from C:

Moving stuff off of drive C: is critically important to folks who have SSD boot drives.

Thomas F. Divine

From: “Martin O’Brien”
Sent: Wednesday, June 06, 2012 1:46 PM
To: “Windows System Software Devs Interest List”
Subject: RE: [ntdev] Installing WDK on different drive from C:

> That was the only thing I could think of too, but that doesn’t seem
> like a workable solution. I mean, surely something else is going to complain.
>
>
>
> mm
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of George M.
> Garner Jr.
> Sent: Wednesday, June 06, 2012 10:43 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Installing WDK on different drive from C:
>
> On 6/6/2012 1:38 PM, Martin O’Brien wrote:
>> Reconfigure how?
>>
>> Thanks,
>>
>> mm
>>
>
> By changing the value of the environment variable, I presume. Not
> exactly an ideal solution. However, it does explain why MSBuild has to go on c:
> (unless you want to change the value of %program files(x86)% for
> everybody).
>
>
> —
> 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

—
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