Article ID: 134389
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
This article was previously published under Q134389
SYMPTOMS
When you attempt to upgrade an exiting Windows NT installation to Windows NT 3.5 or 3.51, an error may appear stating that Windows NT Setup could not find an existing version of Windows NT. You can only exit Setup or install Windows NT into a new directory.
CAUSE
This problem occurs because Setup looks for SCSI instead of MULTI in the BOOT.INI file.
Setup fails to find standard Windows NT 3.1 installations that have SCSI in the BOOT.INI file, and fails to find Windows NT 3.5 installations where you have changed the MULTI references to SCSI in the BOOT.INI file.
WORKAROUND
To work around this problem, add a extra line in the BOOT.INI file that points to the install to be upgraded. Use MULTI instead of SCSI.
STATUS
Microsoft has confirmed this to be a problem in Windows NT versions 3.5 and 3.51 We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Additional query words: prodnt
Keywords: KB134389
