Cannot Dual-Boot DBCS and SBCS Versions of Windows 95

 Last reviewed: August 19, 1997
Article ID: Q172860
The information in this article applies to:
  • Microsoft Windows 95

SUMMARY

Microsoft does not support dual-booting double-byte character set (DBCS) and single-byte character set (SBCS) versions of Windows 95. DBCS versions of Windows 95 include the Chinese and Japanese versions.

MORE INFORMATION

Dual-booting DBCS and SBCS versions of Windows 95 can cause the following problems:

  • File names that contain DBCS characters are unreadable when you boot the SBCS version of Windows 95.
  • Using disk tools that are not designed to work with DBCS files could damage the file allocation table (FAT) and cause data loss.
  • You may not be able to delete files whose names contain DBCS characters when you boot the SBCS version of Windows 95. If you remove the DBCS version of Windows 95 and then want to remove such files, you may have to reinstall the DBCS version of Windows 95 to delete the files.
  • Both versions of Windows 95 attempt to use the same Program Files folder. Therefore, the default items in the Program Files folder created by the first installed version of Windows 95 are overwritten by the second installed version.

Additional query words: 95
Keywords : win95 kbenv
Version : WINDOWS:95
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.