I am considering installing these older tools on a Windows 8 laptop.
Goal is to occasionally build and debug drivers for XP as well as Vista+
targets as hyper-v guests on the laptop.
I notice that installation requirements for these tools still don’t mention
Windows 8 as a supported OS.
Anyone know of blocking issues in setting a machine up this way?
I will be adding Visual Studio 2012 and WDK 8 add-on eventually as well.
Thomas F. Divine
Both should work and install on w8.
d
Bent from my phone
From: Thomas F. Divinemailto:xxxxx
Sent: ?7/?14/?2013 2:28 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] Install and Use of Visual Studio 2010 and WDK 7.1.0 on Windows 8 Host
I am considering installing these older tools on a Windows 8 laptop.
Goal is to occasionally build and debug drivers for XP as well as Vista+
targets as hyper-v guests on the laptop.
I notice that installation requirements for these tools still don’t mention
Windows 8 as a supported OS.
Anyone know of blocking issues in setting a machine up this way?
I will be adding Visual Studio 2012 and WDK 8 add-on eventually as well.
Thomas F. Divine
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
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</mailto:xxxxx></mailto:xxxxx>
In principle, VS 2010 should run. But whether or not it contains the
right support for the most recent drivers is unliely.
I presume that the laptop is not a terribly important machine. If you are
testing a driver, you can expect that after any test, your machine is
unbootable and/or the file system is destroyed.
What is shocking is that this is the second time today I have had to point
out the obvious, that the development machine instance must not be the
testing machine instance (note that a VM running on the machine counts as
a different instance.) It is very scary that newbies seem to think that it
makes sense, under any conditions, to debug a driver on an instance of a
machine whose integrity matters.
joe
I am considering installing these older tools on a Windows 8 laptop.
Goal is to occasionally build and debug drivers for XP as well as Vista+
targets as hyper-v guests on the laptop.I notice that installation requirements for these tools still don’t
mention
Windows 8 as a supported OS.Anyone know of blocking issues in setting a machine up this way?
I will be adding Visual Studio 2012 and WDK 8 add-on eventually as well.
Thomas F. Divine
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminarsTo unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Mr. Newcomer,
I am an experienced driver developer. Not a dumbass newbie.
In this configuration the Windows host supports the driver build
environment. The host runs ONLY Microsoft software. No third-party drivers -
not even my own. NEVER.
The laptop runs any one of several virtualization machines. In this case I
will be using Microsoft Hyper-V - although I run VMWare Workstation on other
similar Windows 7 -based systems.
The target driver runs in a VM guest. Debugging is from the Windows host to
the target VM machine via named pipe.
This is proven to be an excellent development environment for the type of
drivers that I work with. Mostly filter drivers that do not touch hardware.
I appreciate most of your comments and learn from your insight.
However, in this case I am offended.
(Not that it matters one iota.)
Your obedient servant,
Thomas F. Divine
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@flounder.com
Sent: Sunday, July 14, 2013 8:05 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Install and Use of Visual Studio 2010 and WDK 7.1.0 on
Windows 8 Host
In principle, VS 2010 should run. But whether or not it contains the right
support for the most recent drivers is unliely.
I presume that the laptop is not a terribly important machine. If you are
testing a driver, you can expect that after any test, your machine is
unbootable and/or the file system is destroyed.
What is shocking is that this is the second time today I have had to point
out the obvious, that the development machine instance must not be the
testing machine instance (note that a VM running on the machine counts as a
different instance.) It is very scary that newbies seem to think that it
makes sense, under any conditions, to debug a driver on an instance of a
machine whose integrity matters.
joe
I am considering installing these older tools on a Windows 8 laptop.
Goal is to occasionally build and debug drivers for XP as well as
Vista+ targets as hyper-v guests on the laptop.I notice that installation requirements for these tools still don’t
mention Windows 8 as a supported OS.Anyone know of blocking issues in setting a machine up this way?
I will be adding Visual Studio 2012 and WDK 8 add-on eventually as well.
Thomas F. Divine
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminarsTo unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
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
“Thomas F. Divine” wrote in message news:xxxxx@ntdev…
Anyone know of blocking issues in setting a machine up this way?
Technically, no. I’ve been running Windows 8 on my dev box since RTM and
have had zero issues with this set up (though I went back to VMWare after
trying Hyper-V for a short period, interface didn’t work as well for my
usage).
The ONE major annoyance is the build environment links on the Start screen.
The 7.1 WDK shortcuts use the hierarchical structure of the Start Menu to
differentiate the command shortcuts. So, something like:
Windows XP
->x86 Checked
->x86 Free
Windows Server 2003
->x86 Checked
->x86 Free
->x64 Checked
->x64 Free
Windows Vista
->x86 Checked
->x86 Free
->x64 Checked
->x64 Free
Windows 7
->x86 Checked
->x86 Free
->x64 Checked
->x64 Free
Of course, the Start screen on Win8 provides a flat view. So, what you can
end up with is four tiles labeled “x86 Checked”, four tiles labeled “x86
Free”, etc. Then the only way that I can see to differentiate them is to
click on them and see what the title of the resulting command window is.
VERY annoying for someone like myself who insists on building everything
from the command line. I personally resolved it by keeping representative
build environments pinned to the Start screen (one x86, one x64) and keeping
a link to the full folder of shortcuts
(C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Windows Driver
Kits\WDK 7600.16385.1\Build Environments) in a convenient location.
-scott
OSR
“Thomas F. Divine” wrote in message news:xxxxx@ntdev…
I am considering installing these older tools on a Windows 8 laptop.
Goal is to occasionally build and debug drivers for XP as well as Vista+
targets as hyper-v guests on the laptop.
I notice that installation requirements for these tools still don’t mention
Windows 8 as a supported OS.
Anyone know of blocking issues in setting a machine up this way?
I will be adding Visual Studio 2012 and WDK 8 add-on eventually as well.
Thomas F. Divine
I have run both environments (VS10 and VS12) on win8 in a development
organization production environment, however there is no need for VS10 if
you are just building drivers, unless you don’t want to upgrade to VS12.
VS12 will build win7 WDK drivers using the legacy mechanisms just fine and
gives you a path forward.
In other words I would suggest moving forward to VS12.
Mark Roddy
On Sun, Jul 14, 2013 at 10:19 PM, Thomas F. Divine wrote:
> Mr. Newcomer,
>
> I am an experienced driver developer. Not a dumbass newbie.
>
> In this configuration the Windows host supports the driver build
> environment. The host runs ONLY Microsoft software. No third-party drivers
> -
> not even my own. NEVER.
>
> The laptop runs any one of several virtualization machines. In this case I
> will be using Microsoft Hyper-V - although I run VMWare Workstation on
> other
> similar Windows 7 -based systems.
>
> The target driver runs in a VM guest. Debugging is from the Windows host to
> the target VM machine via named pipe.
>
> This is proven to be an excellent development environment for the type of
> drivers that I work with. Mostly filter drivers that do not touch hardware.
>
> I appreciate most of your comments and learn from your insight.
>
> However, in this case I am offended.
>
> (Not that it matters one iota.)
>
> Your obedient servant,
>
> Thomas F. Divine
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@flounder.com
> Sent: Sunday, July 14, 2013 8:05 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Install and Use of Visual Studio 2010 and WDK 7.1.0 on
> Windows 8 Host
>
> In principle, VS 2010 should run. But whether or not it contains the right
> support for the most recent drivers is unliely.
>
> I presume that the laptop is not a terribly important machine. If you are
> testing a driver, you can expect that after any test, your machine is
> unbootable and/or the file system is destroyed.
>
> What is shocking is that this is the second time today I have had to point
> out the obvious, that the development machine instance must not be the
> testing machine instance (note that a VM running on the machine counts as a
> different instance.) It is very scary that newbies seem to think that it
> makes sense, under any conditions, to debug a driver on an instance of a
> machine whose integrity matters.
> joe
>
> > I am considering installing these older tools on a Windows 8 laptop.
> >
> > Goal is to occasionally build and debug drivers for XP as well as
> > Vista+ targets as hyper-v guests on the laptop.
> >
> > I notice that installation requirements for these tools still don’t
> > mention Windows 8 as a supported OS.
> >
> > Anyone know of blocking issues in setting a machine up this way?
> >
> > I will be adding Visual Studio 2012 and WDK 8 add-on eventually as well.
> >
> > Thomas F. Divine
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
> >
> > OSR is HIRING!! See http://www.osr.com/careers
> >
> > 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
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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, Scott. That is helpful.
My original inquiry was prompted after making my initial setup on this new
machine. Seemed to be OK, but as final Windows Updates tricked in one
(KB2811660) “got stuck”; always failed and repair wouldn’t fix it.
In past these sorts of errors are sometimes related to out of order
installation of older tools, etc. Hence my question. I wanted a complete and
clean install of OS and tools before I started using it.
Rebuilt a second time - this time disabling the “free” Norton AV before
re-installing Windows 8 from OEM recovery partition. Can’t actually “blame”
Norton, but the second install of OS and tools ended up problem free.
Warm regards,
Thomas
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Scott Noone
Sent: Monday, July 15, 2013 10:11 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Install and Use of Visual Studio 2010 and WDK 7.1.0 on
Windows 8 Host
“Thomas F. Divine” wrote in message news:xxxxx@ntdev…
Anyone know of blocking issues in setting a machine up this way?
Technically, no. I’ve been running Windows 8 on my dev box since RTM and
have had zero issues with this set up (though I went back to VMWare after
trying Hyper-V for a short period, interface didn’t work as well for my
usage).
The ONE major annoyance is the build environment links on the Start screen.
The 7.1 WDK shortcuts use the hierarchical structure of the Start Menu to
differentiate the command shortcuts. So, something like:
Windows XP
->x86 Checked
->x86 Free
Windows Server 2003
->x86 Checked
->x86 Free
->x64 Checked
->x64 Free
Windows Vista
->x86 Checked
->x86 Free
->x64 Checked
->x64 Free
Windows 7
->x86 Checked
->x86 Free
->x64 Checked
->x64 Free
Of course, the Start screen on Win8 provides a flat view. So, what you can
end up with is four tiles labeled “x86 Checked”, four tiles labeled “x86
Free”, etc. Then the only way that I can see to differentiate them is to
click on them and see what the title of the resulting command window is.
VERY annoying for someone like myself who insists on building everything
from the command line. I personally resolved it by keeping representative
build environments pinned to the Start screen (one x86, one x64) and keeping
a link to the full folder of shortcuts
(C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Windows Driver
Kits\WDK 7600.16385.1\Build Environments) in a convenient location.
-scott
OSR
“Thomas F. Divine” wrote in message news:xxxxx@ntdev…
I am considering installing these older tools on a Windows 8 laptop.
Goal is to occasionally build and debug drivers for XP as well as Vista+
targets as hyper-v guests on the laptop.
I notice that installation requirements for these tools still don’t mention
Windows 8 as a supported OS.
Anyone know of blocking issues in setting a machine up this way?
I will be adding Visual Studio 2012 and WDK 8 add-on eventually as well.
Thomas F. Divine
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
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
Yep, I am “moving forward”, but have customers who use VS10 and WDK7 only.
Their products require support for Windows XP/Server 2003 as well.
In my case I need “path backward” as well as “path forward”. Hence the dual
setup.
(At least I can drop VS08.)
Thomas “Old Geezer” Divine
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Monday, July 15, 2013 10:44 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Install and Use of Visual Studio 2010 and WDK 7.1.0 on
Windows 8 Host
I have run both environments (VS10 and VS12) on win8 in a development
organization production environment, however there is no need for VS10 if
you are just building drivers, unless you don’t want to upgrade to VS12.
VS12 will build win7 WDK drivers using the legacy mechanisms just fine and
gives you a path forward.
In other words I would suggest moving forward to VS12.
Mark Roddy
On Sun, Jul 14, 2013 at 10:19 PM, Thomas F. Divine mailto:xxxxx > wrote:
Mr. Newcomer,
I am an experienced driver developer. Not a dumbass newbie.
In this configuration the Windows host supports the driver build
environment. The host runs ONLY Microsoft software. No third-party drivers -
not even my own. NEVER.
The laptop runs any one of several virtualization machines. In this case I
will be using Microsoft Hyper-V - although I run VMWare Workstation on other
similar Windows 7 -based systems.
The target driver runs in a VM guest. Debugging is from the Windows host to
the target VM machine via named pipe.
This is proven to be an excellent development environment for the type of
drivers that I work with. Mostly filter drivers that do not touch hardware.
I appreciate most of your comments and learn from your insight.
However, in this case I am offended.
(Not that it matters one iota.)
Your obedient servant,
Thomas F. Divine
-----Original Message-----
From: xxxxx@lists.osr.com
mailto:xxxxx
[mailto:xxxxx@lists.osr.com
mailto:xxxxx] On Behalf Of
xxxxx@flounder.com mailto:xxxxx
Sent: Sunday, July 14, 2013 8:05 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Install and Use of Visual Studio 2010 and WDK 7.1.0 on
Windows 8 Host
In principle, VS 2010 should run. But whether or not it contains the right
support for the most recent drivers is unliely.
I presume that the laptop is not a terribly important machine. If you are
testing a driver, you can expect that after any test, your machine is
unbootable and/or the file system is destroyed.
What is shocking is that this is the second time today I have had to point
out the obvious, that the development machine instance must not be the
testing machine instance (note that a VM running on the machine counts as a
different instance.) It is very scary that newbies seem to think that it
makes sense, under any conditions, to debug a driver on an instance of a
machine whose integrity matters.
joe
> I am considering installing these older tools on a Windows 8 laptop.
>
> Goal is to occasionally build and debug drivers for XP as well as
> Vista+ targets as hyper-v guests on the laptop.
>
> I notice that installation requirements for these tools still don’t
> mention Windows 8 as a supported OS.
>
> Anyone know of blocking issues in setting a machine up this way?
>
> I will be adding Visual Studio 2012 and WDK 8 add-on eventually as well.
>
> Thomas F. Divine
>
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
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
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
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 Visit the list at:
http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See
http://www.osr.com/careers 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</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>
On 15-Jul-2013 17:10, Scott Noone wrote:
…
The ONE major annoyance is the build environment links on the Start
screen. The 7.1 WDK shortcuts use the hierarchical structure of the
Start Menu to differentiate the command shortcuts. So, something like:Windows XP
->x86 Checked
->x86 Free
Windows Server 2003
->x86 Checked
->x86 Free
->x64 Checked
->x64 Free
Windows Vista
->x86 Checked
->x86 Free
->x64 Checked
->x64 Free
Windows 7
->x86 Checked
->x86 Free
->x64 Checked
->x64 FreeOf course, the Start screen on Win8 provides a flat view. So, what you
can end up with is four tiles labeled “x86 Checked”, four tiles labeled
“x86 Free”, etc.
You can recreate these shortcuts, where you like them, and name how you
like, with a simple script:
-------- shortcuts.vbs ----
Set Shell = CreateObject(“WScript.Shell”)
Set Fso = CreateObject(“Scripting.FileSystemObject”)
Set Env = Shell.Environment(“Process”)
CmdPath = Env(“windir”)+“\System32\cmd.exe”
DestPath = Shell.CurrentDirectory
WdkPath = Env(“SystemDrive”)+“\winddk\7.1.0”
OacrOpt = “”
if Fso.FolderExists( WdkPath & “\bin\x86\OACR”) then
OacrOpt = " no_oacr"
end if
’ WXP FRE
Set link = Shell.CreateShortcut(DestPath & “\WinXP_free.lnk”)
link.TargetPath = CmdPath
link.Arguments = “/k”+WdkPath+“\bin\setenv.bat " _
+WdkPath+”\ "+“fre WXP”+OacrOpt
link.Description = "WXP FRE "+WdkPath
link.IconLocation = “%windir%\system32\moricons.dll,4”
link.Save()
’ WXP CHK
Set link = Shell.CreateShortcut(DestPath & “\WinXP_chk.lnk”)
link.TargetPath = CmdPath
link.Arguments = “/k”+WdkPath+"\bin\setenv.bat “+WdkPath+”\ " _
+“CHK WXP”+OacrOpt
link.Description = "WXP CHK "+WdkPath
link.IconLocation = “%windir%\system32\moricons.dll,2”
link.Save()
’ … and so on
Regards,
– pa
Pavel A. wrote:
On 15-Jul-2013 17:10, Scott Noone wrote:
> Of course, the Start screen on Win8 provides a flat view. So, what you
> can end up with is four tiles labeled “x86 Checked”, four tiles labeled
> “x86 Free”, etc.
You can recreate these shortcuts, where you like them, and name how you
like, with a simple script:
I wrote a Python script that presents a wx dialog with set of radio box
lists (which WDK version [I have 5 installed], which target OS, which
target CPU, checked/free), and launches the appropriate command shell
for me. One icon.
I’ve heard people say that someday I won’t hate the Duplo block tiles.
I’m not seeing it so far.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
On 15-Jul-2013 23:57, Tim Roberts wrote:
I wrote a Python script that presents a wx dialog with set of radio box
lists (which WDK version [I have 5 installed], which target OS, which
target CPU, checked/free), and launches the appropriate command shell
for me. One icon.
Here’s a batch file like that
I’ve heard people say that someday I won’t hate the Duplo block tiles.
I’m not seeing it so far.
Have you figured how to create voice commands?
“Siri, write me a driver”? 
– pa