Forum Replies Created
-
Posts
-
I’m getting the same thing, windows 7 x86. Not sure if I heard a mount sound, but it just won’t go – no drive letter appears. I thought it might be a UAC problem but I have UAC turned completely off.
call C:WINDDK7600.16385.0binsetenv.bat C:WINDDK7600.16385.0 chk win7
cd /d c:UsersAdminDesktopDriverslegacyDrvlegacyDrv
buildI ran the above in explorer and it resulted in a successful build of x86 version (not x64)
I ran the same above script from the visual studio 2008 cmd window and it also resulted in a successful build of the x86 versionThen I modified the above to line: (added x64 parameter)
call C:WINDDK7600.16385.0binsetenv.bat C:WINDDK7600.16385.0 chk win7 x64Re-Ran the scripts and the result was successful build of (x86 version). It ignored my x64 flag. So I closed all my command windows and restarted them again running the script and it resulted in a successful build of the x64 version!!!
So I launch visual studio (created a brand new driver project) tried to build x64 version and failed. Same output as before. Try to compile x86 version and it was fine.
Any help would be great. I would really like to be able to build both the x86 and x64 from within visual studio.
Command Lines Creating temporary file “C:UsersAdminAppDataLocalTempBAT00000122883468.bat” with contents
[
@echo offcall C:WINDDK7600.16385.0binsetenv.bat C:WINDDK7600.16385.0 chk win7
cd /d c:UsersAdminDesktopDriverslegacyDrvlegacyDrv
from the error log should there be an x64 flag in that command?
Make sure that you can ping the VM from the host. I had to setup the host-to-VM networking stuff so that the VM could communicate with the host. Make sure firewalls are off or have the right ports open, in the VM the make sure the visuallDDK app is running as admin.
Hope this helps a little
Build Log
Build started:Project: legacyDrv, Configuration: Debug|x64
Command Lines Creating temporary file “C:UsersAdminAppDataLocalTempBAT00000122883468.bat” with contents
[
@echo offcall C:WINDDK7600.16385.0binsetenv.bat C:WINDDK7600.16385.0 chk win7
cd /d c:UsersAdminDesktopDriverslegacyDrvlegacyDrv
build
if errorlevel 1 goto VCReportError
goto VCEnd
:VCReportError
echo Project : error PRJ0019: A tool returned an error code from “Performing Makefile project actions”
exit 1
:VCEnd
]
Creating command line “C:UsersAdminAppDataLocalTempBAT00000122883468.bat”Output Window Performing Makefile project actions
OACR monitor running already
path contains nonexistant c:program filesmicrosoft visual studio 9.0common7toolsbin, removing
path contains nonexistant c:program filesmicrosoft sdkswindowsv6.0alibwin64, removing
BUILD: Compile and Link for x86
BUILD: Loading c:winddk7600.16385.0build.dat…
BUILD: Computing Include file dependencies:
BUILD: Start time: Wed Jan 06 15:05:59 2010
BUILD: Examining c:usersadmindesktopdriverslegacydrvlegacydrv directory for files to compile.
c:usersadmindesktopdriverslegacydrvlegacydrv
Invalidating OACR warning log for ‘root:x86chk’
BUILD: Saving c:winddk7600.16385.0build.dat…
BUILD: Compiling and Linking c:usersadmindesktopdriverslegacydrvlegacydrv directory
Configuring OACR for ‘root:x86chk’ –
BUILD: Finish time: Wed Jan 06 15:06:01 2010
BUILD: Done
0 files compiled – 2 WarningsSolved some of my problems.
I was forgetting to launch the launchvisualddk.exe program inside the VM. This is key. The app is set to automatically run but b/c of UAC and win7 security it was not running.
Some tips that worked for me. Turn off UAC, make sure your user account is an Admin account, I even set the Window 7 VM to auto login.
One annoying thing I would still like to figure out is:
When I start the VM it gets to the “load windows” logo screen and freeze (until i run vmmon, start the debugger and hit F5 (go)). Then I have to close windbg and start up visual studio. Any way around this?Another interesting observation:
So I took my driver project (the one created by visualDDK), and openned up a x64 wdk command window, and ran build, and the project built just fine with no problems, but building from visual studio does not work for me still (for x64)? Any ideas?
Do i need to do anything in visual studio besides change the configuration manager to be x64 (from win32)
I just reloaded my machine, win7 x86, with visual studio 2008 (sp1), windbg (newest version), and wdk 7100, and visualddk 1.4.
I create a new driver project ( the x64 support checkbox is checked). I build the project with the Win32 configuration and builds fine. I change the configuration in visual studio to be x64 and the project will not build. I will try to post the messages later.
Other observations: Does visualddk support WDF (ie KMDF or UMDF)? Also when creating a WDM project the tool creates the .inf file and the .inf file references the .cat file but the physical .cat file is not automatically created. I have to create that by hand.
Hi, I almost installed WinCDEmu but I stopped after the installer rebooted my computer for the testing….so now on my backround it says “Test Mode” on each corner. How do i get rid of that? I would appreciate the help ty.
Ordinarily I would agree and would use flac, wavpack, ape or some other lossless format but I just don’t like to double handle… the reason why I have iso format audio cds is because I automatically create backups for my cds for when I take them into my car or to listen to at work, I don’t like damaging my originals.
Its still a great little application that some people might find handy but at the end of the day it would be nice for this thing to be a complete virtual drive package and stand toe to toe with the other apps that can achieve this sorts of things.Can’t wait a single day to test it (really, I need this for yesterday). Some beta/alpha/development/preview version out there?
I get this same problem with audio cd’s in iso format that have been created using Imgburn… odd this application would be fantastic and quite honestly its the only reason why I use Alcohol120%.
On another note would it be possible to add support for bin files.
I’ve just noticed that on other machines, the forward slash is missing. Not sure what’s going on here, but it seems to be present in only *some* systems… or only my system?!
Bit of a mystery, I assume therefore that I’m in the minority with the forward slash before ‘default’ but if any body else has this problem I guess you can just remove the forward slash!
Sorry for wasting your time if my forward slash was unique 😳
kev
