I upgraded my 6.1 system to 6.2.
Using the boot disk, It booted then asked me for mouse type (intimouse
serial) and video montor.
Then the next screen I saw was enter admin password and new user.
Foolishly I pressed next, next hoping to get to the main choice screen to
choose Upgrade. Even when it said "now writing data to your hard disk" I
pressed return (I didn't think it would do anything serious without showing
the "main" selection screen). I was wrong, and it overwrote my 6.1 system.
In intalling it again, the installer had autochosen, the defaults for
"Install Worstation", "loose data" screen. Without showing any of the
screens and left me at the enter root password screen.
The back button is enabled, so it is possible to go back - BUT....
this is definately not how I expected the install to work.
Currently I am rebuilding my system, from all those backups I should have
Unfortunately, the IntelliMouse protocol requires a mouse reset to properly
work. When you select different mouse protocols in the mouse configuration
screen, we tell the X server to switch to use the new protocol. There seems to
be a problem when switching to IMPS or IntelliMouse. The X server sends data to
the mouse to get it to switch modes, but this data is echoed and interpreted as
I ran into this problem on PS/2 IntelliMouse and fixed it before we shipped
6.2. I saw the behavior on the serial IntelliMouse, made some changs, and had
it working, but it seems that there was a regression before we shipped.
To prevent this from happening in the future, I've modified the installer to
never switch to IntelliMouse protocols.
Apologies for you loss of data. Protecting our customer's data is our #1
concern here. This is why we've expanded the warning text on the "about to
install" screen, "this is the last point at which you can abort the installation
I'll make sure this won't happen again.
Created attachment 192 [details]
patch applied to never move to IntelliMouse protocol
*** This bug has been marked as a duplicate of 10456 ***
*** Bug 10456 has been marked as a duplicate of this bug. ***