Newsgroup: it.comp.os.win.win9x
Titolo: Paging....

Ciao a tutti,
qualcuno saprebbe spiegarmi come mai da qualche giorno a questa parte il mio
Pc con s.o.Windows 95 parte in modalità provvisoria e nella voce prestazioni
dentro la finestra sistema,mi dà questo messaggio?
"Il Paging in modalita' compatibile riduce le prestazioni".
Grazie a chi mi risponderà.


Devi vedere in gestione periferiche cosa e' accaduto,
hai sicuramente un conflitto, vedrai qualche simbolo colorato,
tipo esclamativo, non ricordo come e' il w95.
Nel caso reinstalli le periferiche malate.
-- 
extrabug

 ha scritto nel messaggio
news:9e2snh$n7or$1...@ID-47808.news.dfncis.de...


 nessun conflitto.....
Puoi vedere i conflitti anche con MicrosoftSystemInformation,
ed usare le utility in Strumenti.
Start/Programmi/Accessori/M$sysInfo
P.S.: potresti quotare? ;-)
--
Saluti
¯massimo_ ......cercante lavoro.
(my From alterate) No close by Usenet.

 "Il Paging in modalita' compatibile riduce le prestazioni".
MS KB: Article ID: Q130179
      Troubleshooting MS-DOS Compatibility Mode on Hard Disks
----------------------------------------------------------------------------
----
The information in this article applies to:
  a.. Microsoft Windows 95
  b.. Microsoft Windows 98
  c.. Microsoft Windows 98 Second Edition
  d.. Microsoft Windows Millennium Edition
----------------------------------------------------------------------------
----
SYMPTOMS
The Performance tab in System properties shows that one or more of the hard
disks in your computer is using MS-DOS Compatibility mode. MS-DOS
compatibility mode may be in use either for the file system or for virtual
memory. You may receive the following message:
  Compatibility Mode Paging reduces overall system performance
CAUSE
MS-DOS Compatibility mode may be in use for any of the following reasons:
  a.. An "unsafe" device driver, memory-resident program, or virus hooked
the INT21h or INT13h chain before Windows is loaded.
  b.. The hard disk controller in your computer was not detected by Windows.
  c.. The hard disk controller was removed from the current configuration in
Device Manager.
  d.. There is a resource conflict between the hard disk controller and
another hardware device.
  e.. The Windows protected-mode driver is missing or damaged.
  f.. The Windows 32-bit protected-mode disk drivers detected an
unsupportable configuration or incompatible hardware.
  g.. You are running Windows Millennium Edition (Me) and have used Drive
Copy 2.0 by Powerquest to copy the contents of one hard disk to another hard
disk.
RESOLUTION
To correct the behavior, follow these steps:
  1.. If you used Drive Image 2.0 by Powerquest, contact Powerquest for a
version of the software that is compatible with Windows Me.
  2.. 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.
  For additional information about troubleshooting floppy disk drives, click
the article number below to view the article in the Microsoft Knowledge
Base:
    Q131690 Troubleshooting Floppy Disk Drive Problems in Windows
    1.. If the driver name listed as causing MS-DOS Compatibility mode is
Mbrint13.sys, your computer may be infected with a boot-sector virus, 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
protected-mode disk drivers.
    For additional information about real-mode geometry translation software
that is compatible with Windows protected-mode disk drivers, click the
article number below to view the article in the Microsoft Knowledge Base:
      Q126855 Windows Support for Large IDE Hard Disks
    Disk Manager 6.03 is supported in protected mode on hard disks on the
primary IDE channel and when DriveSpace disk compression is not installed.
For drives on the secondary IDE channel, Disk Manager 7.0 or later is
required. When using the DriveSpace compression software that is included
with Microsoft Windows and Microsoft Plus!, Disk Manager 7.04 or later must
be used.
    For additional information, click the article number below to view the
article in the Microsoft Knowledge Base:
      Q126855 Windows Support for Large IDE Hard Disks
    For additional information about detecting and removing boot-sector
viruses, click the article number below to view the article in the Microsoft
Knowledge Base:
      Q82923 Methods to Detect a Boot-Sector Virus
      Q129972 Description of Computer Viruses
      Q49500 List of Antivirus Software Vendors
    b. If a driver that is listed in the Config.sys file is named, contact
the driver's manufacturer to determine whether there is a version of the
driver that enables protected-mode access in Windows.
    If no driver is listed on the Performance tab, continue with Step 2.
  3.. Check to make sure 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 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 that corresponds to the current hardware profile under Device Usage.
  4.. 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 absent or
damaged, or the "Disable all 32-bit protected-mode disk drivers" check box
is selected in File System properties.
    1.. 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. To access this tab, double-click System in Control Panel,
click the Performance tab, and then click File System.
    2.. 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.
    3.. 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.
    NOTE: If you are using an IDE, EIDE, or ESDI hard disk controller, the
Driver tab may not be present when you click Properties for the controller
in Device Manager. Unless you are using a third-party driver, Esdi_506.pdr
is the protected-mode driver that is used to provide 32-bit disk access for
these controllers.
    Restart Windows and press F8 at the "Starting Windows xx" message, and
then choose Logged (/Bootlog.txt) start from the Windows Startup Menu.
Examine the just-created Bootlog.txt file to determine if the driver listed
above is loading properly.
    In Windows 98, press and hold the CTRL key until you see the Windows 98
Startup menu, and then choose Logged (/Bootlog.txt).
    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 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 behavior.
    4.. Check for the NOIDE value in the registry under:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\IOS
    The NOIDE value is placed in the registry when the protected-mode driver
for the IDE Controller is not properly initialized.
    For additional information about how to troubleshoot NOIDE, click the
article number below to view the article in the Microsoft Knowledge Base:
      Q151911 MS-DOS Compatibility Mode Problems with PCI IDE Controllers
    5.. Make sure the protected-mode driver is not damaged.
    For all ESDI and IDE drives, Windows uses ESDI_506.PDR in the IOSUBSYS
directory to provide 32-bit disk access. For SCSI controllers, Windows 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
disks or CD-ROM, or run Setup and choose the Verify option.
  5.. Check to see if the Mh32bit.386 driver is being loaded in the
System.ini file. Check for a line that reads "device=mh32bit.386." This
driver is installed by MicroHouse EZ-Drive software, and is not compatible
with the Windows protected-mode disk drivers. This driver is not removed by
Windows Setup.
  6.. Contact the hard disk controller's manufacturer for information about
Windows compatibility. You may be able to get protected-mode, 32-bit disk
access in Windows by using one of the following methods:
    a.. 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).
    b.. Obtain a protected-mode Windows disk driver, or Windows 3.1 FastDisk
driver for the controller.
MORE INFORMATION
A real-mode driver is "safe" if its functionality does not exceed the
functionality of the corresponding Windows 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 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 does not provide
encryption, Windows does not enable 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:
  a.. Data compression that is not compatible with DoubleSpace
  b.. Data encryption
  c.. Disk mirroring
  d.. Bad sector mapping
  e.. Fault tolerance (for example, maintenance of ECC correction on a
separate disk)
  f.. Vendor-specific IOCTLs
  g.. Microsoft-defined IOCTLs with vendor-extended features
The safe driver list (the Ios.ini file) is a Windows-maintained list of safe
drivers. Each entry in the list identifies a driver or TSR that Windows 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 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:
  a.. MS-DOS 5.0-compatible real-mode block device drivers
  b.. 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)
  c.. INT 13 hooker (hooks INT 13 for altering INT 13 I/O but does not
access the hardware directly)
  d.. INT 13 driver (provides INT 13 functionality and directly accesses the
hardware)
  e.. ASPI Manager (implements ASPI for MS-DOS specification)
  f.. 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
protected-mode driver, the driver's vendor should remove the driver from the
safe driver list. The system may 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.
Disk Manager is manufactured by OnTrack Computer Systems, a vendor
independent of Microsoft; we make no warranty, implied or otherwise,
regarding this product's performance or reliability.
EZ-Drive is manufactured by Micro House, a vendor independent of Microsoft;
we make no warranty, implied or otherwise, regarding this product's
performance or reliability.

prestazioni
Controinterrogatorio: cosa hai fatto, qualche giorno fa?
1) Hai installato qualcosa?
2) Hai avuto blocchi strani?
3) Hai eseguito programmi di non sicura fede politica?
4) Hai aggiunto o ripartizionato un disco?
5) Hai aggiunto o sostituito i driver di un cd rom o un masterizzatore?
Per i punti 1,2,3, potresti aver contratto un virus che circolava tempo
fa, che aveva come effetto collaterale proprio quello, oltre ad
impedirti l'accesso ai cd rom (andava in errore tentando di infettarlo,
ed e' piuttosto difficile scrivere su un cdrom)
Per il punto 4: una stramba caratteristica di windows e' prendersela con
l'utente se gli fornisce un disco gia' formattato, in aggiunta a quelli
che ha riconosciuto lui durante l'installazione.
Per risolvere questo problema, occorre rimuvere dal pannello di
controllo i dischi, fare uno spegnimento normale, all'avvio dovrebbe
riconoscere i nuovi dischi, aggiornarne la firma, e il problema sparire.
Per il punto 5: se hai installato qualcosa di questo tipo, controlla in
autoexec e config se non c'e' per caso la chiamata ad un driver cdrom,
se c'e', prova a togliere la riga, riavviare e vedere se il problema
sparisce.
-- 
           |Save our planet!
  Ciao     |Save wildlife;
  roberto  |For your E-MAIL use only recycled Bytes !!
           |roberto poggi  
rpo...@softhome.net