I finally got around to trying to install 6.4.7.2 and discovered it appears
that it does not allow you to install it seperately than a previous version.
Microsoft this is not a wise idea, I DETEST 6.3.17.0 and was hoping for
something better, but now it appears I have to blow away 6.2.13.1 the last
version that I find works resonably just to try the new one! Any
suggestions on how to get around this crap?
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
As far as I know, if you use the installer, it has always required that you
uninstall the last version. Maybe there was a time long long ago when that
wasn’t the case, but it has been the case for a long time.
To get around it, rename your old install directory to something else, go to
add/remove programs and uninstall the old one, then install the new one.
Then you can rename your old directory back to whatever it was before. As a
matter of practice you might want to always install it to some directory
like “C:\dbg” and then rename it immediately to “C:\dbg.6.4.7.2”. Then when
new versions come out, you don’t have to worry that uninstall will remove
your last debugger installation.
Another way to get around it is to install the files onto one machine, copy
the raw directory from any machine to any machine (e.g. some archival
location – where you can net use to a share and see the directory). Once
you have the tools in a central location, net use to the machine and xcopy
them (xcopy /s /v /h *.* or xcopy /s /v /h
\server\share\subdir*.* ) to any other machine. You do not
need to use the installer at all to use the debugging tools. You can have
as many different copies of the debugging tools in side by side directories
as you want.
----Original Message Follows----
From: “Don Burn”
Reply-To: “Kernel Debugging Interest List”
To: “Kernel Debugging Interest List”
Subject: [windbg] 6.4.7.2
Date: Mon, 7 Feb 2005 13:09:16 -0500
I finally got around to trying to install 6.4.7.2 and discovered it appears
that it does not allow you to install it seperately than a previous version.
Microsoft this is not a wise idea, I DETEST 6.3.17.0 and was hoping for
something better, but now it appears I have to blow away 6.2.13.1 the last
version that I find works resonably just to try the new one! Any
suggestions on how to get around this crap?
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
—
You are currently subscribed to windbg as: xxxxx@msn.com
To unsubscribe send a blank email to xxxxx@lists.osr.com