Microsoft KB Archive/287430

= You receive a &quot;Win.com not found, unable to load Windows&quot; error message after you install SQL Server 2000 Desktop Engine =

Article ID: 287430

Article Last Modified on 1/26/2005

-

APPLIES TO

 Microsoft Access 2002 Standard Edition, when used with:  Microsoft Windows 98 Standard Edition

 Microsoft Windows 98 Second Edition

 Microsoft Windows Millennium Edition 

-

<div class="notice_section">

This article was previously published under Q287430

<div class="notice_section">

Moderate: Requires basic macro, coding, and interoperability skills.

This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).

<div class="symptoms_section">

SYMPTOMS
When you start a Microsoft Windows 98 or a Microsoft Windows Millennium (Me) computer after you have installed the Microsoft SQL Server 2000 Desktop Engine from the Microsoft Office XP CD1, you see the Windows splash screen, and then you are return to an MS-DOS prompt with the following error:

Cannot find WIN.COM, unable to continue loading Windows

NOTE: In some cases, you will be able to boot into Windows; however, some of your programs may report errors. Applications that typically use path statements in the Autoexec.bat file are those developed for MS-DOS and most virus protection applications.

<div class="cause_section">

CAUSE
The SQL Server 2000 Desktop Engine Setup program adds the following text to the SET PATH statement in the Autoexec.bat file:

SET PATH=&quot;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\&quot;

If Windows or another program relies on the SET PATH statement in Autoexec.bat to locate files, the modification made by the SQL Server 2000 Desktop Engine Setup will cause errors.

<div class="resolution_section">

RESOLUTION
Edit the Autoexec.bat file to include the required paths. If you do not know the required path statements for your applications, you can check the documentation for the applications or, in most cases, you can reinstall the applications. You can also check for the existence of backup Autoexec.bat files by using Windows Explorer to browse to the root of drive C. Look for files that start with Autoexec, and open them with Notepad. Look for the line that starts &quot;Path=&quot; or &quot;SET PATH=&quot; (without quotation marks).

If you cannot boot into Windows, you will be booted to a command prompt. Follow these steps to edit the Autoexec.bat file from the MS-DOS command prompt.

<ol> At the C:\ prompt, type cd Windows\Command and then press ENTER.</li> Type edit c:\autoexec.bat, and then press ENTER. This opens the Autoexec.bat file in a text editor.</li> Modify the SET PATH line to include the required paths for your applications. For Windows and the SQL Server 2000 Desktop Engine, use the following statement:

SET PATH=&quot;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Windows\;C:\Windows\Command\&quot;

</li> Save and then close the Autoexec.bat file. If you do not have mouse support, you can press the ALT key to get to the menus. Then, use the ARROW keys to navigate the menus.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

MORE INFORMATION
When you try to start a program from the Run box without specifying a path, Windows searches the current folder for the executable file for the program. For example, click Run on the Start menu, and then type Notepad.exe. If Windows does not find the file in the current folder, it will search the folders specified in the path statement. For more information about this subject, search Windows Help on the search word &quot;path.&quot;

Additional query words: pra path msde 2000 msde2000

Keywords: kberrmsg kbnofix kbprb kbclientserver KB287430

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.