1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Drive C is using MS-DOS compatibility mode file system.

Discussion in 'Earlier Versions of Windows' started by unoIT, Nov 20, 2000.

Thread Status:
Not open for further replies.
Advertisement
  1. unoIT

    unoIT Thread Starter

    Joined:
    Jul 13, 2000
    Messages:
    46
    A couple of weeks ago I replaced my motherboard. I only kept my original hard drive and processor. Everything has seemed to work okay. However, I noticed when I went to SYSTEM PROPERTIES/PERFORMANCE/ :

    File System: Some drives are using MS-DOS compatibility
    Virtual Memory: MS-DOS compat. mode

    Also, in the window below it:
    "Compat. mode paging reduces overall sys performance."
    "Drive C is using MS-DOS compat. mode file system."

    Does anyone know why it says this? how to change it?

    -unoIT

    ------------------
     
  2. brianF

    brianF

    Joined:
    Dec 2, 1999
    Messages:
    12,041
    This should cover it, rather lengthy, I copied it from ms.

    MS-DOS Compatibility Mode and Hard Drives

    June 1998

    This month's tip is meant to help
    unlock some of the mystery behind
    MS-DOS Compatibility Mode with
    hard drives. Generally, hard drives do
    not cause MS-DOS Compatibility
    mode, but because Windows indicates a
    drive is in compatibility mode,
    it appears as if the drive is at fault.

    The following describes causes of
    compatibility mode and the
    step-by-step methods that resolve
    the issue. Most of this information
    comes from Microsoft's
    KnowledgeBase and should help you identify and
    resolve the specific problem.

    MS-DOS Compatibility mode may be
    caused by any of the following
    reasons:

    An "unsafe" device driver,
    memory-resident program, or virus
    hooked the INT21h or INT13h
    chain before Windows 95/98 loaded.
    The hard disk controller in
    your computer was not detected by
    Windows 95/98.
    The hard disk controller was
    removed from the current
    configuration in Device
    Manager.
    There is a resource conflict
    between the hard disk controller and
    another hardware device.
    The Windows 95/98
    protected-mode driver is missing or damaged.
    The Windows 95/98 32-bit
    protected-mode disk drivers detected a
    non-standard configuration
    or incompatible hardware.

    To correct the problem, follow
    these steps:

    1.Use the Performance tab in
    System properties to identify which
    drive is using MS-DOS
    Compatibility mode and why.

    Note: Floppy disk drives and
    CD-ROM drives operating in
    MS-DOS Compatibility mode
    cause the Performance tab to display
    the message "Some drives are
    using MS-DOS compatibility" for
    the file system, but this
    article applies only to troubleshooting hard
    disks operating in MS-DOS
    Compatibility mode.
    a.If the driver name
    listed as causing MS-DOS Compatibility
    mode is MBRINT13.SYS,
    your computer may be infected
    with a boot-sector
    virus that must be removed,

    - or -

    you are running
    real-mode geometry translation software
    (for an IDE hard disk
    with more than 1024 cylinders) that is
    not compatible with
    Windows 95/98 protected-mode disk
    drivers. Data Lifeguard
    Tools' EZ BIOS, the translation
    software used by
    Western Digital to support large drives, is
    compatible with Windows
    95/98 and does not cause any
    compatibility mode
    issues. EZ-Drive and Disk Manager
    (6.03d version),
    translation software previously used by
    Western Digital, are
    also compatible with Windows 95/98.

    b.If a driver in your
    CONFIG.SYS file is listed, contact the
    driver's manufacturer
    to determine whether there is a
    version of the driver
    that allows protected-mode access in
    Windows 95/98.

    If no driver is listed on
    the Performance tab, continue with Step 2.

    2.Check that the hard disk
    controller is listed in Device Manager. If it
    is not listed, install it
    with the Add New Hardware Wizard. If the
    Wizard does not detect the
    controller, run the Wizard again but do
    not let the Wizard detect
    the hardware in your computer. Instead,
    select the controller from
    the hardware list. If the controller is not
    listed, contact the
    manufacturer of the hard disk controller to
    determine whether there is a
    Windows 95/98 protected-mode disk
    driver or a Windows 3.1
    32-bit disk access (FastDisk) driver
    available.

    Note: If the hard disk
    controller is listed in Device Manager but has
    a red X over it, it has been
    removed from the current hardware
    profile. Click Properties
    for the controller in Device Manager and
    then click the check box
    corresponding to the current hardware
    profile under Device Usage.

    3.If the hard disk controller
    is listed in Device Manager but has a
    yellow exclamation point
    over it, there is an IRQ, I/O, DMA, or
    RAM address conflict with
    another device, the protected-mode
    driver is missing or
    damaged, or the "Disable all 32-bit
    protected-mode disk drivers"
    check box is selected in File System
    properties.
    a.Check to make sure that
    the "Disable all 32-bit
    protected-mode disk
    drivers" check box has not been
    selected on the
    Troubleshooting tab in File System
    properties.
    b.Resolve any resource
    (IRQ, I/O, DMA, or RAM address)
    conflicts with other
    devices. Consult the controller's
    documentation for
    information about resource usage and
    changing resource
    usage.
    c.Check to make sure that
    the protected-mode driver is in the
    Windows\SYSTEM\IOSUBSYS
    directory and is loading
    properly. To determine
    which driver is providing 32-bit disk
    access, click
    Properties for the controller in Device
    Manager and click the
    Driver tab to see which driver files
    are associated with the
    controller.

    Restart Windows 95/98
    and press F8 at the "Starting
    Windows 95/98" message.
    Select a Logged
    (/BOOTLOG.TXT) start.
    Examine the just-created
    BOOTLOG.TXT file to
    determine if the driver listed above is
    loading properly.

    If the BOOTLOG.TXT file
    shows an "Init Failure" or "Load
    Failure" message for
    the driver listed above, proceed with
    step D. If the
    BOOTLOG.TXT file shows an
    "INITCOMPLETESUCCESS"
    message for the drive listed
    above, examine the
    IOS.LOG file.

    Windows 95/98 creates
    an IOS.LOG file in the Windows
    directory if any drives
    are using MS-DOS Compatibility
    mode. The first few
    lines of the IOS.LOG file may contain
    information describing
    why the protected-mode disk driver
    failed to load. Please
    have this information available if you
    contact Microsoft
    Product Support Services about this
    problem.

    d.Make sure the
    protected-mode driver is not damaged.

    For all ESDI and IDE
    drives, Windows 95/98 uses
    ESDI_506.PDR in the
    IOSUBSYS directory to provide 32-bit
    disk access. For SCSI
    controllers, Windows 95/98 uses
    SCSIPORT.PDR and a
    "mini-port" (.MPD) driver to provide
    32-bit disk access.

    Manually extract the
    appropriate .PDR or .MPD files from
    the Windows 95/98 disks
    or CD-ROM, or run Setup and
    choose the Verify
    option.

    4.Contact the hard disk
    controller's manufacturer for information
    about Windows 95/98
    compatibility. You may be able to get
    protected-mode, 32-bit disk
    access in Windows 95/98 by using one
    of the following methods:

    Disable any enhanced
    features (such as caching,
    fast or turbo mode,
    reduced data transfer rates, and
    so on) on the
    controller (SCSI, IDE, or ESDI) or
    system BIOS (IDE only).
    Obtain a protected-mode
    Windows 95/98 disk
    driver, or Windows 3.1
    FastDisk driver for the
    controller.

    A real-mode driver is "safe"
    if its functionality does not
    exceed the functionality of
    the corresponding Windows
    95/98 protected-mode driver.
    If a real-mode driver is safe,
    the protected-mode driver
    can take over all I/O operations
    for the corresponding
    device. Otherwise, Windows 95/98
    routes all I/O operations
    through the real-mode driver.

    An example of an unsafe
    driver is a real-mode IDE/ESDI
    driver that uses dynamic
    encryption for security reasons.
    Since Windows 95/98 does not
    provide encryption,
    Windows 95/98 does not allow
    the protected-mode
    IDE/ESDI driver to take over
    the real-mode driver. Any
    real-mode driver with
    functionality on the following list is
    considered unsafe:

    Data compression that
    is not compatible with
    DoubleSpace
    Data encryption
    Disk mirroring
    Bad sector mapping
    Fault tolerance (for
    example, maintenance of ECC
    correction on a
    separate disk)
    Vendor-specific IOCTLs
    Microsoft-defined
    IOCTLs with vendor-extended
    features

    The safe driver list (the
    IOS.INI file) is a Windows
    95/98-maintained list of
    safe drivers. Each entry in the list
    identifies a driver or TSR
    that Windows 95/98 can take over
    with the corresponding
    protected-mode driver. The safe
    driver list includes the
    name of the driver or TSR. This name
    should be the same as the
    name in the CONFIG.SYS or
    AUTOEXEC.BAT file.

    Windows 95/98 does not store
    the version number of the
    driver or TSR in the list,
    so it is the responsibility of the
    vendor to change the name of
    the driver if a future version
    of the driver is enhanced in
    a manner that makes the driver
    unsafe.

    By default, the following
    drivers are considered safe:

    MS-DOS 5.0-compatible
    real-mode block device
    drivers
    INT 13 monitors (hooks
    INT 13 for monitoring INT
    13 I/O but does not
    access the hardware directly or
    modify the I/O buffer)
    INT 13 hooker (hooks
    INT 13 for altering INT 13 I/O
    but does not access the
    hardware directly)
    INT 13 driver (provides
    INT 13 functionality and
    directly accesses the
    hardware)
    ASPI Manager
    (implements ASPI for MS-DOS
    specification)
    CAM Manager (implements
    MS-DOS CAM
    specification)

    Note: If the real-mode
    driver you are using has better
    performance or provides some
    functions that are not be
    present in the Windows 95/98
    protected-mode driver, the
    driver's vendor should
    remove the driver from the safe
    driver list. The system will
    use real mode to access the
    drive. If the real-mode
    driver you are using can be safely
    taken over by protected-mode
    drivers, the driver's vendor
    can add that driver to the
    safe driver list.

    Another symptom of MS-DOS
    Compatibility mode is:

    1.32bit file system access
    and 32bit virtual memory are
    not available.
    2.Device manager displays
    an exclamation point in a
    yellow circle for the
    primary and secondary IDE
    channels.

    Note: Removing and
    reinstalling the hard disk controllers
    does not resolve the
    problem.

    This can occur if your
    computer contains a PCI-IDE hard
    disk controller that employs
    serialization between the two
    IDE channels. The problem
    lies with the protected-mode
    driver for the hardisk
    controller. It was not properly
    initialized when you started
    Windows 95/98. When this
    occurs, a NOIDE entry is
    placed in the registry preventing
    Windows 95/98 from making
    future attempts to initialize the
    protected-mode driver.

    To make Windows 95/98
    reinitialize the protected-mode IDE
    driver, remove the NOIDE
    entry from the following registry
    key:

    HKEY_LOCAL_MACHINE\
    SYSTEM\

    CURRENTCONTROLSET\

    SERVICES\

    VXD\

    IOS\

    Note: Use great care when
    editing the Windows Registry.
    An error in the registry can
    easily stop Windows from
    functioning.

    5.After you update the
    registry, restart Windows 95/98. Windows
    will then attempt to
    initialize the protected-mode driver for the
    controller. If Windows
    encounters no problems, the file system and
    virtual memory will operate
    in 32bit mode
    and Device Manager will
    not display an exclamation
    point in a
    yellow circle for the IDE
    channels.


     
  3. unoIT

    unoIT Thread Starter

    Joined:
    Jul 13, 2000
    Messages:
    46
    Thanks for the info brianF. I'll give it a try and let you know how it turns out. I hope it will speed my system up. It should be running faster since I upgraded to 256k RAM!

    Thanks again!
    -unoIT

    ------------------
     
  4. brianF

    brianF

    Joined:
    Dec 2, 1999
    Messages:
    12,041
    Upgrading ram past 128 really only shows performance improvement if you are running graphics apps, etc. Most other applications and games perform about the same as far as what I have seen.
     
  5. unoIT

    unoIT Thread Starter

    Joined:
    Jul 13, 2000
    Messages:
    46
    I'm an "8 hr a day" AutoCAD user! So believe me, I love the extra RAM!
    Back to the computer problem,...still working on it. I'll let you know the progress.
    -unoIT

    ------------------
     
  6. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/25067

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice