I was unpleasantly surprised when I installed the new windbg and it wiped
out all of the old installations. In the past I found it bad that you
overwrote the last install, but removing the rest without warning is very
poor design. Some of us believe in testing WinDBG extenisons on the
various versions of the debugger, this install policy just makes this
harder, decreasing quality for everyone.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
This is definitely not intentional behavior. We use side-by-side
installs every day and I haven’t heard of any problems. I just tried
two installs back-to-back to different directories and the first install
was not deleted.
Were you using the regular GUI installer? Any non-default options?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, February 02, 2006 4:48 PM
To: Kernel Debugging Interest List
Subject: [windbg] Really bad install
I was unpleasantly surprised when I installed the new windbg and it
wiped out all of the old installations. In the past I found it bad that
you overwrote the last install, but removing the rest without warning is
very
poor design. Some of us believe in testing WinDBG extenisons on the
various versions of the debugger, this install policy just makes this
harder, decreasing quality for everyone.
–
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@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Regular GUI installer, no change in the options. It came up and asked me if
I wanted to upgrade and showed grey the directory with the latest version of
WinDBG. I choose the default (non-custom) upgrade, and the first idea I was
having a problem is when the installer started showing it was deleting items
from the directory with the older version of WinDBG on my system.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
This is definitely not intentional behavior. We use side-by-side
installs every day and I haven’t heard of any problems. I just tried
two installs back-to-back to different directories and the first install
was not deleted.
Were you using the regular GUI installer? Any non-default options?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, February 02, 2006 4:48 PM
To: Kernel Debugging Interest List
Subject: [windbg] Really bad install
I was unpleasantly surprised when I installed the new windbg and it
wiped out all of the old installations. In the past I found it bad that
you overwrote the last install, but removing the rest without warning is
very
poor design. Some of us believe in testing WinDBG extenisons on the
various versions of the debugger, this install policy just makes this
harder, decreasing quality for everyone.
–
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@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Don’t know if it helps but the version I was installing over was 6.5.3.7 the
version I expected to keep was 6.2.13.1
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Don Burn” wrote in message news:xxxxx@windbg…
> Regular GUI installer, no change in the options. It came up and asked me
> if I wanted to upgrade and showed grey the directory with the latest
> version of WinDBG. I choose the default (non-custom) upgrade, and the
> first idea I was having a problem is when the installer started showing it
> was deleting items from the directory with the older version of WinDBG on
> my system.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> “Drew Bliss” wrote in message
> news:xxxxx@windbg…
> This is definitely not intentional behavior. We use side-by-side
> installs every day and I haven’t heard of any problems. I just tried
> two installs back-to-back to different directories and the first install
> was not deleted.
>
> Were you using the regular GUI installer? Any non-default options?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Thursday, February 02, 2006 4:48 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Really bad install
>
> I was unpleasantly surprised when I installed the new windbg and it
> wiped out all of the old installations. In the past I found it bad that
> you overwrote the last install, but removing the rest without warning is
> very
> poor design. Some of us believe in testing WinDBG extenisons on the
> various versions of the debugger, this install policy just makes this
> harder, decreasing quality for everyone.
>
>
> –
> 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@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
I believe that in an upgrade it is expected that the old binaries are
replaced with the new ones. I don’t think this behavior has changed.
I’ll check with the people that do the debugger setup.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, February 02, 2006 5:17 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Don’t know if it helps but the version I was installing over was 6.5.3.7
the version I expected to keep was 6.2.13.1
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Don Burn” wrote in message news:xxxxx@windbg…
> Regular GUI installer, no change in the options. It came up and asked
me
> if I wanted to upgrade and showed grey the directory with the latest
> version of WinDBG. I choose the default (non-custom) upgrade, and the
> first idea I was having a problem is when the installer started
showing it
> was deleting items from the directory with the older version of WinDBG
on
> my system.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> “Drew Bliss” wrote in message
> news:xxxxx@windbg…
> This is definitely not intentional behavior. We use side-by-side
> installs every day and I haven’t heard of any problems. I just tried
> two installs back-to-back to different directories and the first
install
> was not deleted.
>
> Were you using the regular GUI installer? Any non-default options?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Thursday, February 02, 2006 4:48 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Really bad install
>
> I was unpleasantly surprised when I installed the new windbg and it
> wiped out all of the old installations. In the past I found it bad
that
> you overwrote the last install, but removing the rest without warning
is
> very
> poor design. Some of us believe in testing WinDBG extenisons on the
> various versions of the debugger, this install policy just makes this
> harder, decreasing quality for everyone.
>
>
> –
> 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@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
The setup expert said that the upgrade behavior is normal. For
side-by-side installs he recommended simply copying or renaming old
install directories before installing the new version.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, February 02, 2006 5:17 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Don’t know if it helps but the version I was installing over was 6.5.3.7
the version I expected to keep was 6.2.13.1
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Don Burn” wrote in message news:xxxxx@windbg…
> Regular GUI installer, no change in the options. It came up and asked
me
> if I wanted to upgrade and showed grey the directory with the latest
> version of WinDBG. I choose the default (non-custom) upgrade, and the
> first idea I was having a problem is when the installer started
showing it
> was deleting items from the directory with the older version of WinDBG
on
> my system.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> “Drew Bliss” wrote in message
> news:xxxxx@windbg…
> This is definitely not intentional behavior. We use side-by-side
> installs every day and I haven’t heard of any problems. I just tried
> two installs back-to-back to different directories and the first
install
> was not deleted.
>
> Were you using the regular GUI installer? Any non-default options?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Thursday, February 02, 2006 4:48 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Really bad install
>
> I was unpleasantly surprised when I installed the new windbg and it
> wiped out all of the old installations. In the past I found it bad
that
> you overwrote the last install, but removing the rest without warning
is
> very
> poor design. Some of us believe in testing WinDBG extenisons on the
> various versions of the debugger, this install policy just makes this
> harder, decreasing quality for everyone.
>
>
> –
> 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@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Drew,
First in the past IIRC, the upgrade overwrote the last version
installed, it did not blow away the other versions. Second, I was lectured
several years ago, that copy/rename technique was absolutely wrong and that
no bug report would be accepted this way for WinDbg, this was by Andre when
he still was the guru. If this is now the blessed behavior can you document
this!
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The setup expert said that the upgrade behavior is normal. For
side-by-side installs he recommended simply copying or renaming old
install directories before installing the new version.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, February 02, 2006 5:17 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Don’t know if it helps but the version I was installing over was 6.5.3.7
the version I expected to keep was 6.2.13.1
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Don Burn” wrote in message news:xxxxx@windbg…
> Regular GUI installer, no change in the options. It came up and asked
me
> if I wanted to upgrade and showed grey the directory with the latest
> version of WinDBG. I choose the default (non-custom) upgrade, and the
> first idea I was having a problem is when the installer started
showing it
> was deleting items from the directory with the older version of WinDBG
on
> my system.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> “Drew Bliss” wrote in message
> news:xxxxx@windbg…
> This is definitely not intentional behavior. We use side-by-side
> installs every day and I haven’t heard of any problems. I just tried
> two installs back-to-back to different directories and the first
install
> was not deleted.
>
> Were you using the regular GUI installer? Any non-default options?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Thursday, February 02, 2006 4:48 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Really bad install
>
> I was unpleasantly surprised when I installed the new windbg and it
> wiped out all of the old installations. In the past I found it bad
that
> you overwrote the last install, but removing the rest without warning
is
> very
> poor design. Some of us believe in testing WinDBG extenisons on the
> various versions of the debugger, this install policy just makes this
> harder, decreasing quality for everyone.
>
>
> –
> 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@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
We don’t know of any way for our installer to remove anything more than
the upgrade directory. I haven’t seen any behavior like this in my
testing. I’m at a loss for what might have happened there.
Zero (file-copy-only) install is an officially supported thing, I
believe we’ve exchanged mail about that in the past.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 4:37 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Drew,
First in the past IIRC, the upgrade overwrote the last version
installed, it did not blow away the other versions. Second, I was
lectured
several years ago, that copy/rename technique was absolutely wrong and
that no bug report would be accepted this way for WinDbg, this was by
Andre when he still was the guru. If this is now the blessed behavior
can you document this!
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The setup expert said that the upgrade behavior is normal. For
side-by-side installs he recommended simply copying or renaming old
install directories before installing the new version.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, February 02, 2006 5:17 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Don’t know if it helps but the version I was installing over was 6.5.3.7
the version I expected to keep was 6.2.13.1
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Don Burn” wrote in message news:xxxxx@windbg…
> Regular GUI installer, no change in the options. It came up and asked
me
> if I wanted to upgrade and showed grey the directory with the latest
> version of WinDBG. I choose the default (non-custom) upgrade, and the
> first idea I was having a problem is when the installer started
showing it
> was deleting items from the directory with the older version of WinDBG
on
> my system.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> “Drew Bliss” wrote in message
> news:xxxxx@windbg…
> This is definitely not intentional behavior. We use side-by-side
> installs every day and I haven’t heard of any problems. I just tried
> two installs back-to-back to different directories and the first
install
> was not deleted.
>
> Were you using the regular GUI installer? Any non-default options?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Thursday, February 02, 2006 4:48 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Really bad install
>
> I was unpleasantly surprised when I installed the new windbg and it
> wiped out all of the old installations. In the past I found it bad
that
> you overwrote the last install, but removing the rest without warning
is
> very
> poor design. Some of us believe in testing WinDBG extenisons on the
> various versions of the debugger, this install policy just makes this
> harder, decreasing quality for everyone.
>
>
> –
> 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@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I can try to reproduce this, is there anything that will help diagnose the
problem if I can reproduce the problem?
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
We don’t know of any way for our installer to remove anything more than
the upgrade directory. I haven’t seen any behavior like this in my
testing. I’m at a loss for what might have happened there.
Zero (file-copy-only) install is an officially supported thing, I
believe we’ve exchanged mail about that in the past.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 4:37 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Drew,
First in the past IIRC, the upgrade overwrote the last version
installed, it did not blow away the other versions. Second, I was
lectured
several years ago, that copy/rename technique was absolutely wrong and
that no bug report would be accepted this way for WinDbg, this was by
Andre when he still was the guru. If this is now the blessed behavior
can you document this!
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The setup expert said that the upgrade behavior is normal. For
side-by-side installs he recommended simply copying or renaming old
install directories before installing the new version.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, February 02, 2006 5:17 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Don’t know if it helps but the version I was installing over was 6.5.3.7
the version I expected to keep was 6.2.13.1
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Don Burn” wrote in message news:xxxxx@windbg…
> Regular GUI installer, no change in the options. It came up and asked
me
> if I wanted to upgrade and showed grey the directory with the latest
> version of WinDBG. I choose the default (non-custom) upgrade, and the
> first idea I was having a problem is when the installer started
showing it
> was deleting items from the directory with the older version of WinDBG
on
> my system.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> “Drew Bliss” wrote in message
> news:xxxxx@windbg…
> This is definitely not intentional behavior. We use side-by-side
> installs every day and I haven’t heard of any problems. I just tried
> two installs back-to-back to different directories and the first
install
> was not deleted.
>
> Were you using the regular GUI installer? Any non-default options?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Thursday, February 02, 2006 4:48 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Really bad install
>
> I was unpleasantly surprised when I installed the new windbg and it
> wiped out all of the old installations. In the past I found it bad
that
> you overwrote the last install, but removing the rest without warning
is
> very
> poor design. Some of us believe in testing WinDBG extenisons on the
> various versions of the debugger, this install policy just makes this
> harder, decreasing quality for everyone.
>
>
> –
> 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@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I think just a set of specific repro steps would be sufficient.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 10:50 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
I can try to reproduce this, is there anything that will help diagnose
the problem if I can reproduce the problem?
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
We don’t know of any way for our installer to remove anything more than
the upgrade directory. I haven’t seen any behavior like this in my
testing. I’m at a loss for what might have happened there.
Zero (file-copy-only) install is an officially supported thing, I
believe we’ve exchanged mail about that in the past.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 4:37 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Drew,
First in the past IIRC, the upgrade overwrote the last version
installed, it did not blow away the other versions. Second, I was
lectured
several years ago, that copy/rename technique was absolutely wrong and
that no bug report would be accepted this way for WinDbg, this was by
Andre when he still was the guru. If this is now the blessed behavior
can you document this!
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The setup expert said that the upgrade behavior is normal. For
side-by-side installs he recommended simply copying or renaming old
install directories before installing the new version.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, February 02, 2006 5:17 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
Don’t know if it helps but the version I was installing over was 6.5.3.7
the version I expected to keep was 6.2.13.1
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Don Burn” wrote in message news:xxxxx@windbg…
> Regular GUI installer, no change in the options. It came up and asked
me
> if I wanted to upgrade and showed grey the directory with the latest
> version of WinDBG. I choose the default (non-custom) upgrade, and the
> first idea I was having a problem is when the installer started
showing it
> was deleting items from the directory with the older version of WinDBG
on
> my system.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> “Drew Bliss” wrote in message
> news:xxxxx@windbg…
> This is definitely not intentional behavior. We use side-by-side
> installs every day and I haven’t heard of any problems. I just tried
> two installs back-to-back to different directories and the first
install
> was not deleted.
>
> Were you using the regular GUI installer? Any non-default options?
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
> Sent: Thursday, February 02, 2006 4:48 PM
> To: Kernel Debugging Interest List
> Subject: [windbg] Really bad install
>
> I was unpleasantly surprised when I installed the new windbg and it
> wiped out all of the old installations. In the past I found it bad
that
> you overwrote the last install, but removing the rest without warning
is
> very
> poor design. Some of us believe in testing WinDBG extenisons on the
> various versions of the debugger, this install policy just makes this
> harder, decreasing quality for everyone.
>
>
> –
> 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@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I have now reproduced the problem twice with the following steps:
- On a clean system create a directory named WinDbg
- Run the install of 6.5.3.7
- Choose a custom install and a place the debugger in WinDbg\current
- Add installing all the SDK from the custom installation.
- Complete the installation
- Run the install of 6.2.13.1
- Choose a custom install and a place the debugger in WinDbg\6_2_13_1
- Add installing all the SDK from the custom installation.
- Complete the installation
- Run the install of 6.6.03.5
- Choose either the custom or the full update
- Complete the installation
- Check the WinDbg\6_2_13_1 directory it will be empty
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
I think just a set of specific repro steps would be sufficient.
The MSI support in the OS only tracks the last installed package. In
this case you have:
Install 6.5.3 - now latest.
Install 6.2.13 - no upgrade since there’s a newer package, now latest.
Install 6.5.3 - upgrade since latest package is 6.2.13, now latest.
The upgrade of the 6.2.13 install to 6.5.3 is the normal
upgrade-in-place. Did your original 6.5.3 from step #1 get wiped out?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 11:57 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
I have now reproduced the problem twice with the following steps:
- On a clean system create a directory named WinDbg 2. Run the
install of 6.5.3.7 3. Choose a custom install and a place the debugger
in WinDbg\current 4. Add installing all the SDK from the custom
installation.
- Complete the installation
- Run the install of 6.2.13.1
- Choose a custom install and a place the debugger in WinDbg\6_2_13_1
- Add installing all the SDK from the custom installation.
- Complete the installation
- Run the install of 6.6.03.5
- Choose either the custom or the full update 12. Complete the
installation 13. Check the WinDbg\6_2_13_1 directory it will be empty
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
I think just a set of specific repro steps would be sufficient.
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
6.5.3 is upgraded (which is what I would expect since its directory appears
in the upgrade dialog). 6.2.13 is left with an empty directory with no
files in it. Also, checking the “Add Remove Programs” control panel, one of
the two versions which was previously there is now removed.
Since the installer has been over-writing the latest install, the solution
to this has been to install the debugger packages in reverse order, i.e
latest to earliest. It has been a while since I did it, but I have been
using the current directory and letting it get overwritten, so I only have
to reinstall the previous package. Now it looks like everytime I wish to
cleanly install a new version, I need to install all versions, if I want to
keep things clean and be able to use “Add Remove Programs”
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The MSI support in the OS only tracks the last installed package. In
this case you have:
Install 6.5.3 - now latest.
Install 6.2.13 - no upgrade since there’s a newer package, now latest.
Install 6.5.3 - upgrade since latest package is 6.2.13, now latest.
The upgrade of the 6.2.13 install to 6.5.3 is the normal
upgrade-in-place. Did your original 6.5.3 from step #1 get wiped out?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 11:57 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
I have now reproduced the problem twice with the following steps:
1. On a clean system create a directory named WinDbg 2. Run the
install of 6.5.3.7 3. Choose a custom install and a place the debugger
in WinDbg\current 4. Add installing all the SDK from the custom
installation.
5. Complete the installation
6. Run the install of 6.2.13.1
7. Choose a custom install and a place the debugger in WinDbg\6_2_13_1
8. Add installing all the SDK from the custom installation.
9. Complete the installation
10. Run the install of 6.6.03.5
11. Choose either the custom or the full update 12. Complete the
installation 13. Check the WinDbg\6_2_13_1 directory it will be empty
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
I think just a set of specific repro steps would be sufficient.
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I can repro this. I have no idea what’s happening but it doesn’t seem
right. I’ll pass this on to our setup guys.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 1:21 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
6.5.3 is upgraded (which is what I would expect since its directory
appears in the upgrade dialog). 6.2.13 is left with an empty directory
with no files in it. Also, checking the “Add Remove Programs” control
panel, one of the two versions which was previously there is now
removed.
Since the installer has been over-writing the latest install, the
solution to this has been to install the debugger packages in reverse
order, i.e latest to earliest. It has been a while since I did it, but
I have been using the current directory and letting it get overwritten,
so I only have to reinstall the previous package. Now it looks like
everytime I wish to cleanly install a new version, I need to install all
versions, if I want to keep things clean and be able to use “Add Remove
Programs”
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The MSI support in the OS only tracks the last installed package. In
this case you have:
Install 6.5.3 - now latest.
Install 6.2.13 - no upgrade since there’s a newer package, now latest.
Install 6.5.3 - upgrade since latest package is 6.2.13, now latest.
The upgrade of the 6.2.13 install to 6.5.3 is the normal
upgrade-in-place. Did your original 6.5.3 from step #1 get wiped out?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 11:57 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
I have now reproduced the problem twice with the following steps:
1. On a clean system create a directory named WinDbg 2. Run the
install of 6.5.3.7 3. Choose a custom install and a place the debugger
in WinDbg\current 4. Add installing all the SDK from the custom
installation.
5. Complete the installation
6. Run the install of 6.2.13.1
7. Choose a custom install and a place the debugger in WinDbg\6_2_13_1
8. Add installing all the SDK from the custom installation.
9. Complete the installation
10. Run the install of 6.6.03.5
11. Choose either the custom or the full update 12. Complete the
installation 13. Check the WinDbg\6_2_13_1 directory it will be empty
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
I think just a set of specific repro steps would be sufficient.
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Drew,
I will be the first to say it is an annoyance not a critical bug. If
the setup guys do go in there, I will ask again to consider having a “New
Install” versus “Upgrade” option. The reasons I have multiple debug tools
around are:
-
I alway try the newest beta, but it is a beta so in case of a bug I
want to revert without loss of time.
-
I will not ship a piece of software without exercising it in all
the environments it it going to run in where possible. For WinDBG, that
means an extension for a customer should at least be minimally exercised in
all the major versions still available.
The current approach to install makes both of the above hard to do and
acts differently than many other Microsoft installs.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
I can repro this. I have no idea what’s happening but it doesn’t seem
right. I’ll pass this on to our setup guys.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 1:21 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
6.5.3 is upgraded (which is what I would expect since its directory
appears in the upgrade dialog). 6.2.13 is left with an empty directory
with no files in it. Also, checking the “Add Remove Programs” control
panel, one of the two versions which was previously there is now
removed.
Since the installer has been over-writing the latest install, the
solution to this has been to install the debugger packages in reverse
order, i.e latest to earliest. It has been a while since I did it, but
I have been using the current directory and letting it get overwritten,
so I only have to reinstall the previous package. Now it looks like
everytime I wish to cleanly install a new version, I need to install all
versions, if I want to keep things clean and be able to use “Add Remove
Programs”
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
The MSI support in the OS only tracks the last installed package. In
this case you have:
Install 6.5.3 - now latest.
Install 6.2.13 - no upgrade since there’s a newer package, now latest.
Install 6.5.3 - upgrade since latest package is 6.2.13, now latest.
The upgrade of the 6.2.13 install to 6.5.3 is the normal
upgrade-in-place. Did your original 6.5.3 from step #1 get wiped out?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Friday, February 03, 2006 11:57 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Really bad install
I have now reproduced the problem twice with the following steps:
1. On a clean system create a directory named WinDbg 2. Run the
install of 6.5.3.7 3. Choose a custom install and a place the debugger
in WinDbg\current 4. Add installing all the SDK from the custom
installation.
5. Complete the installation
6. Run the install of 6.2.13.1
7. Choose a custom install and a place the debugger in WinDbg\6_2_13_1
8. Add installing all the SDK from the custom installation.
9. Complete the installation
10. Run the install of 6.6.03.5
11. Choose either the custom or the full update 12. Complete the
installation 13. Check the WinDbg\6_2_13_1 directory it will be empty
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting Remove StopSpam from
the email to reply
“Drew Bliss” wrote in message
news:xxxxx@windbg…
I think just a set of specific repro steps would be sufficient.
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com