[Saman]

Hmm, I thought it may be also over network, and what is needed IP adress

[Saman]

But I want debug on a second machine and IP adress at Target machine field is adress of the second machine,so how I must set Debug launch dialog for debugging on a second machine?

[Saman]

Sorry, I dont know how to add a picture at the message body so the screenshots are at attachments 🙁

[Saman]

Unfortunatelly I get the same error, if I use VS Build system. :-((((((((((((((((((((
It is possible lookup, which file system cannot find?I lookup at Vs logfile but i don’t see any error.
Which files use VisualDDk debug at startup?
I can enter whatever at field Target machine or Driver path at target machine but always I get VisualDDk error:……

[Saman]

.SYS file is created.
I am sorry but I don’t know, where I find VS Build System.
And one basic question.Which files and where must be the files for source and target machine for successfull debuging the driver.I mean, that on target machine can be only .sys file at shared folder.Or I am not right.

[Saman]

Sorry, one more tine

Build started: Project: VddK, Configuration: Debug Win32

Build started 30.5.2011 22:46:00.
Build:
OACR monitor running already
path contains nonexistant c:program filesmicrosoft visual studio 10.0common7toolsbin, removing
path contains nonexistant c:windowssyswow64, removing
path contains nonexistant c:usersmirekdocumentsrad studio8.0bpl, removing
BUILD: Compile and Link for x86

BUILD: Loading c:winddkbuild.dat…

BUILD: Computing Include file dependencies:

BUILD: Start time: Mon May 30 22:46:02 2011
BUILD: Examining c:msvisprojectsvddkvddk directory for files to compile.

c:msvisprojectsvddkvddk

Auto-cleaning queue for ‘root:x86chk’ (2 of 2 file(s) removed)
Invalidating OACR warning log for ‘root:x86chk’
BUILD: Saving c:winddkbuild.dat…

BUILD: Compiling and Linking c:msvisprojectsvddkvddk directory

Configuring OACR for ‘root:x86chk’ –
Compiling – stdafx.cpp
Compiling – vddk.cpp
Compiling – generating code…
Linking Executable – objchk_win7_x86i386vddk.sys
BUILD: Finish time: Mon May 30 22:46:07 2011
BUILD: Done

4 files compiled – 3 Warnings – 98 LPS

1 executable built

Build succeeded.

Time Elapsed 00:00:07.71
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

[Saman]

Build started: Project: VddK, Configuration: Debug Win32

Build started 30.5.2011 21:49:41.
Build:
path contains nonexistant c:program filesmicrosoft visual studio 10.0common7toolsbin, removing
path contains nonexistant c:windowssyswow64, removing
path contains nonexistant c:usersmirekdocumentsrad studio8.0bpl, removing
BUILD: Compile and Link for x86

BUILD: Loading c:winddkbuild.dat…

BUILD: Computing Include file dependencies:

OACR monitor running already
BUILD: Start time: Mon May 30 21:49:42 2011
BUILD: Examining c:msvisprojectsvddkvddk directory for files to compile.

c:msvisprojectsvddkvddk

Invalidating OACR warning log for ‘root:x86chk’
BUILD: Saving c:winddkbuild.dat…

BUILD: Compiling and Linking c:msvisprojectsvddkvddk directory

BUILD: Finish time: Mon May 30 21:49:43 2011
BUILD: Done

0 files compiled – 3 Warnings

Configuring OACR for ‘root:x86chk’ –

Build succeeded.

Time Elapsed 00:00:02.73
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

[Saman]

The project was created without any error.The driver I create with File->New->Project->VisualDDkWiz.I try it at Visual 2010 and 2008 and problem is under both VS.

[Saman]

Yes,
first I try the driver, which is created with VisualDDk wizard.

[Saman]

Problem is solved. I had installed only Visual C++.If I had install a C# so VisualDDk Debug menu was (is) visible.

[Author]

Posts