Facebook Twitter Google +1     Admin

Se muestran los artículos pertenecientes a Febrero de 2009.

Que uso Win 32 bits o Win 64 bits........................

20090205120433-windows-xp-64-bits.jpg

Hola mi publico, esto esta tomado de una pagina y me parece la explicacion mas sencilla para entender este engorroso tema que no nos enseñan en la Universidad ,http://www.laneros.com/archive/index.php/t-95863.html, de todas maneras si alguien quiere corroborar esto puede ir directamente a la pagina de Bill Gates, http://www.microsoft.com/spain/technet/recursos/articulos/2010.aspx, de todas manera instalarlo es igual pero revise los drivers primero y las aplicaciones que soporten 64 bits. La activacion si es un poco engorrosa, busquelo en la red por ahi lo hay ya preactivado y con sp2 incorporado y traducido al idioma de Cervantes.

Bien veamos esto
"Ok,  para empezar los sistemas de 64 bits son el futuro queramos o no los veremos en tods las maquinas, pero claro siempre esta la question, como yo, que no tengo dinero como para tener una pc con 4 gbs de ram para poder recien querer tratar de usar los 64bits, por eso siguen saliendo aplicaciones de 32bits, Expondre mejor en un claro ejemplo de la mejora. La memoria guarda la información en bits, que pueden tener dos valores: 0 o 1, estos bits se agrupan actualmente en grupos de 32, con lo que en binario se puede representar valores de 0 a 4.294.967.295, evidentemente si unimos los bits en grupos de 64 el valor es mucho mayor, llegando de 0 a 18.446.744.073.709.551.615, como queda patente, podemos almacenar muchas más posiciones de memoria con agrupaciones de 64 bitsesto implica aplicaciones mas veloces. pero para poder usar 64bits tenemos como minimo 4gbs de ram en nustras maquinas, ahora con el problemas de drivers nos es tna cierto, claro que existen casos pero todo tiene solucion en este mundo jeje, solo es cuestion de esperar que este sistema madure mas..

Estoy de acuerdo contigo salvo en que como minimo se tenga que usar 4GB, por el contrario 4GB en OS de 32 bit es una limitante por que el tope maximo de reconocimiento es 3.5GB en memoria, salvo un truco de extencion de memoria en el boot.ini , por otro lado en 64bit reconoce esa capacidad sin problema alguno, eso ahce que un OS de 64bit permite utilizar una mayor capacidad de memoria, en mi board por ejemplo se puede reconocer maximo 4 GB en OS de 32bit y 8GB en 64Bit alojadas en 4 slots. Yo he usuado el vista de 64bit con 2gb de ram sin problemas."

05/02/2009 06:55 Victor Manuel Uribe Mantilla #. sin tema No hay comentarios. Comentar.

Safari 4 el navegador mas rapido...............

20090225151338-whatis-elegantbrowser-20090217.png

Safari es un navegador web desarrollado por Apple Inc.. Es el navegador incluido en Mac OS X y recientemente se han desarrollado versiones ejecutables para Microsoft Windows. El código utilizado para renderizar páginas web está basado en el motor KHTML, creado para el proyecto KDE para su navegador Konqueror. Como resultado de esto, el motor interno de Safari es software libre y es liberado bajo los términos de la licencia GPL. Las mejoras al código de KHTML por parte de Apple son incorporadas al código de KDE.

Lo instale en mi maquina y realmente es asombrosa la velocidad para mostra el contenido web, probe las paginas con java y realmente trabajan super rapido, no he encontrado hasta ningun bug, ademas instala los comlementos de IE para ciertas cosas como el reproductor de windows en internet y otras cosas. 

Vale la pena probarlo es genial por su velocidad 

25/02/2009 10:13 Victor Manuel Uribe Mantilla #. sin tema No hay comentarios. Comentar.

Dolor de cabeza al formatear por errores de windows.... quitese ese problema

 

Aunque se ve largo (por las imagenes), este artículo es muy facil de seguir y completar.

Crear las particiones en el disco, formatear, reinstalar Windows, reinstalar controladores y programas, etc. Estos procesos pueden durar horas. Con todos los programas y herramientas cuales yo utilizo, admito que duro días en este proceso de reinstalar un Windows limpio, rápido y saludable. Después de varios meses de usar Windows, es posible que este se sienta mas lento, lleno de errores en el registro, y con muchos disparates instalados. Se siente bien reinstalarlo para volver a sentir la velocidad. Antes yo formateaba y reinstalaba cada mes, pero ya lo hago como 1 vez cada 5 meses, quizas menos, 

Gracias a la clonación, he reducido este proceso de varios días intensivos de instalar programas, actualizar Windows, desfragmentar etc, a solo 10 minutos. Aquí en este artículo les enseño como lo hago. No se limiten a los consejos de este artículo. Yo uso una herramienta en particular, pero ustedes pueden descubrir otras, 

 

Que necesitas

- Quemador de CD o DVD.

- Hiren’s Boot CD, o discos de rescate de Acronis TrueImage, conocidos como Bootable Rescue Media. Estos te permiten restaurar la imagen sin tener Windows instalado. Usas estos CDs para iniciar la computadora a la interfaz de Acronis TrueImage. Hiren’s Boot CD incluye una copia de Acronis TrueImage, debajo del menú Disk Clone Tools.

- Dos discos duros, o un disco con dos particiones, o CDs y DVDs en blanco o virgenes. Se recomienda NTFS y no FAT32 ya que FAT32 no puede almacenar archivos más grandes de 4 GB, pero hay un truco, como leerán mas abajo. Como Acronis TrueImage comprime la imagen, es posible siempre crear imágenes cuales ocupan menos de 4 GB, especialmente si usas Windows 9x (Windows 95, 98, 98 SE y ME) cuales no ocupan mucho espacio en el disco. Si usas Windows 9x es obligado usar FAT32 ya que estos no pueden leer particiones NTFS.

Antes de crear la imagen

Recuerda que vas a crear una imagen de un Windows limpio, saludable, veloz y con todo lo que necesitas instalado y actualizado. Mi recomendación es asegurar lo siguiente antes de crear la imagen. 
- Instala Windows y todas las actualizaciones (Media Player, Windows updates, etc.)

- Instala todos los controladores (Chipset, sonido, video, Red, etc.)

- Activa Windows si es necesario 
- Instala todos tus programas favoritos (Office, MSN Live, Antivirus, Photoshop, etc.)

- Ejecuta todos los programas cuales más usas. Esto causa a que Windows cree el archivo prefetch del programa. Este archivo crea información sobre el programa, y ayuda a ejecutarlo mas rápido la próxima vez.

- Limpia el sistema operativo y optimízalo. Elimina archivos innecesarios, chequea Agregar/Quitar programas y asegura eliminar lo que no sea necesario, escanea en busca de viruses y spyware. Este paso es crítico porque te ayuda a reducir el tamaño de la imagen. 

- Desfragmenta el disco o la partición.

Crea la imagen del disco o partición

Inicia la computadora con el disco de rescate de Acronis TrueImage, o inicia con Hiren’s Boot CD y ejecuta Acronis TrueImage. Si estas en Windows, también puedes crear la imagen, pero prefiero el método de no usar Windows porque no tenemos que instalar Acronis TrueImage cual ocupara espacio en el disco. 

TrueImage es fácil de usar y tiene dos opciones básicas. Create o Crear, y Restore o Restaurar. Los nombres lo dicen todo, como queremos crear la imagen, elegimos Create Image.

Después de hacer clic en Create Image, llegamos a la sección donde elegimos cual partición vamos a clonar. En este ejemplo tenemos dos particiones. Estas son particiones de muestra, y la información se puede ver diferente en sus computadoras. Quiero crear una imagen de la partición LETHE_ONLINE. La elijo y hago clic en Next.

Ahora elegimos donde queremos guardar la imagen y le damos un nombre. En este ejemplo guardo la imagen en la partición D: con nombre Imagen_LeThe. Hacemos click en Next.

En esta ventana elegimos Create the full backup image archive. Esto indica que vamos a crear la imagen del disco entero. Append changes incrementally…indica que ya tenemos una imagen, y vamos a actualizarla o hacerle cambios. TrueImage detecta este cambio y nos ahorra el tiempo de volver a crear una imagen entera. Hacemos clic en Next.

Ahora especificamos el tamaño de la imagen. En Automatic la imagen será del tamaño de la capacidad ocupada en el disco. Por ejemplo, si todos los programas incluyendo Windows ocupan 4.6 GB, entonces este será el tamaño de la imagen y puede ser menos después de elegir la compresión en la siguiente ventana.

En Fixed Size, puedes especificar el tamaño de la imagen. Si esta va a ser de 4.6 GB y especificas los tamaños de 2 GB, se van a crear 3 imágenes, dos de 2 GB y otra de 600 MB. Estos es conveniente, ya que evitas archivos más grandes de 4 GB, cual elimina el problema con particiones FAT32, y también puedes quemar estos archivos a CDs o DVDs para poder restaurar la imagen. Nota: Si quieres restaurar la imagen desde CDs tienes que especificar tamaños de 699 MB, quizás menos.

En este ejemplo, como tengo suficiente espacio, elijo Automatic. Hacemos clic en Next.


Ahora elegimos el nivel de compresión. En esta ventana tienes que fijarte en dos cosas importantes cuales están resaltadas. Una es el tamaño de la imagen, y lo otro es el tiempo para crearla. En este ejemplo apenas tengo archivos en la partición, por eso se ve una imagen de 3.494 MB, creada en 1 minuto. En realidad, normalmente la imagen esta entre 2 a 6 GB y se crea entre 5 a 15 minutos dependiendo de la velocidad de tu computadora. Yo normalmente elijo High, ya que esta opción comprime el archivo suficiente y se crea en el mismo tiempo que compresión Normal. Pero todo depende de la imagen, si tu prefieres velocidad y no te importa la capacidad, puedes elegir None. Pero si espacio en tu disco es critico, puedes elegir Maximum. Hacemos clic en Next.

En la siguiente ventana puedes digitar una clave cual protegerá a la imagen. Esto no es necesario, pero siempre existe el peligro que alguien tenga acceso a la imagen, cual puede ser explorada. Haz clic en Next.

Ahora puedes digitar comentarios sobre la imagen. Esto puede ser importante si no recuerdas cual es la imagen. Si creas muchas imágenes, al restaurarlas, es importante tener los mismos dispositivos instalados. Si has cambiado algún dispositivo es posible que recibas una pantalla azul u otro error. Hacemos clic en Next.

Ahora finalizamos el proceso haciendo clic en Proceed, y se creara la imagen.

Restaurando la Imagen

Volvemos a la interfaz de TrueImage, pero esta vez del menú elegimos Restore o Restaurar y buscamos la imagen cual deseamos restaurar. La elegimos, y hacemos clic en Next.

Es posible que se te pida verificar la imagen (Do you wish to verify the Image). Este paso es opcional y lo que hace es verificar la integridad de la imagen, ósea asegurar que no este corrupta, antes de restaurarla. Es recomendado. Haz clic next hasta llegar a la imagen debajo, aquí eliges cual partición quieres restaurar.

En la siguiente ventana eliges a donde quieres restaurar la partición. Elegimos la partición C:, en este ejemplo conocida como LETHE_ONLINE. Hacemos clic en Next.

Ahora elegimos el tipo de partición. Si estas restaurando la partición de arranque con Windows, entonces quieres elegir Active. Como experimento he probado Primary y me ha funcionado bien. A veces esta seleccionado por ti.

Las siguientes ventanas nos ofrecen otras opciones cuales son opcionales. Como en este ejemplo solo queremos restaurar nuestra imagen, podemos hacer clic en Next hasta llegar a la ventana final, donde punchamos Proceed para restaurar la imagen. Despues reiniciamos y entramos a Windows limpio, nuevo y saludable.

Restaurando a otro disco

Como guardamos la imagen en DVDs, CDs y posiblemente en otro disco duro, ¿Qué pasa si se nos daña el disco o cambiamos el disco de donde creamos la imagen? Todos los otros dispositivos deben permanecer idénticos, pero el disco duro si se puede cambiar. Podemos restaurar la imagen pero a veces se puede producir un problema, donde después de restaurar la imagen y reiniciar, al iniciar Windows nos sale el error: Memoria Virtual Limitada o Limited Virtual Memory. Este problema se describe aquí: http://support.microsoft.com/kb/812448/es

Para mi la solución fue iniciar con un disco de inicio de Windows 98, y en DOS digitar FDISK /MBR.

Articulos Relacionados

Crea tu propio método de Recovery para tu computadora (Punchas una tecla antes de iniciar Windows para entrar a una particion de Recovery o Restauracion).

 

28/02/2009 07:31 Victor Manuel Uribe Mantilla #. sin tema No hay comentarios. Comentar.

Una pantalla azul .....llamen a los bomberos se me jodio mi computadora... que hago

20090228125247-unmountable-boot-volume.jpg

Esta en ingles pero es facil de entender, busca cual es el error que te da y le das al enlace y vas directamente a microsoft para encontrar la solucion. Dale es sumamente sencillo lo mas arrecho es la pantalla azul.

hen Windows XP detects a problem from which it cannot recover, it displays Stop messages. These are text-mode error messages that report information about the condition.

Stop messages, sometimes referred to as blue screens (BSoD), contain specific information that can help you diagnose and possibly resolve the problem detected by the Windows kernel.

This list describes these messages and helps you understand and interpret them.

This list is NOT exhaustive or meant to resolve EVERY error.

This list of messages is a guide to individual messages and their possible causes and resolutions... Having a basic understanding of these error messages enables you to communicate with your technical support professional more effectively too.

With all these Stop messages, you can pretty much assume someone else has encountered the problem before you. That is why tying in the error message into www.google.com , posting a notice for help on a relevant newsgroup and entering the stop code into the "Microsoft Knowledge Base" can yield help just when you need it!

Here is the (long) list:

Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL

The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.

Possible Resolutions:

  • A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
     
  • A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.
     
  • If you encounter a Stop 0xA message while upgrading to Windows XPl, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.

Microsoft KB articles:

 Troubleshooting a Stop 0x0000000A Error in Windows XP
STOP 0x0000000A Error Message When You Change from AC Power to DC Power
STOP 0x0000000A Error Message When You Fast Switch Between UsersSTOP 0x0000000A Irql_Not_Less_or... During Windows XP UpgradeSTOP 0x0000000A "Fatal System Error" on HP5100C ScanJetSTOP 0x0000000A A Computer may Hang during heavy load with an Ericsson HIS ModemSTOP 0x0000000A Windows XP restarts when you try to shut down your computerSTOP 0x0000000A Computer automatically restarts after upgrade to XP

 

Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED

The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors in that they can be due to invalid memory and access violations. This default Windows XP error handler typically intercepts these problems if error-handling routines are not present in the code itself.

Possible Resolutions:

  • Stop 0x1E messages typically occur after installing faulty drivers or system services, or they can indicate hardware problems, such as memory and IRQ conflicts. If a Stop message lists a driver by name, disable, remove, or roll it back to correct the problem. If disabling or removing applications and drivers resolves the issue, contact the hardware manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.
     
  • If the Stop message mentions the file Win32k.sys, the source of the error might be a third-party "remote control" program. If such software is installed, you might be able to disable it by starting the system in safe mode. If not, use Recovery Console to manually delete the system service file that is causing the problem.
     
  • Problems can result from system firmware incompatibilities. Many Advanced Configuration and Power Interface (ACPI) issues can be resolved by updating to the latest firmware.
     
  • Other possible causes include insufficient disk space while installing applications or performing certain functions that require more memory. You can free up space by deleting unneeded files. Use Disk Cleanup to increase available disk space. From Recovery Console, remove temporary files (those with .tmp file extensions), Internet cache files, application backup files, and .tmp files generated by Chkdsk.exe or Autochk.exe. You can also choose to install additional applications to another hard disk with more free space or move data files, paging files, and so on.
     
  • The problem might be due to a memory leak caused by an application or service that is not releasing memory correctly. Poolmon (Poolmon.exe) helps you to isolate the components that are causing kernel memory leaks. For more information about troubleshooting memory leaks, see Microsoft Knowledgebase articles Q177415, "How to Use Poolmon to Troubleshoot Kernel Mode Memory Leaks," and Q298102, "Finding Pool Tags Used by Third Party Files Without Using the Debugger." 

Microsoft KB articles:

STOP 0x0000001E Error Message During Windows SetupSTOP 0X0000001E in Protcls.sys When You Undock a Toshiba TecraSTOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED Error Message from Aspi32.sys

 

Stop 0x00000024 or NTFS_FILE_SYSTEM

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.

Possible Resolutions:

  • Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system’s ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.
  • Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows XP. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.

    To test hard disk or volume integrity

    Method 1:

    1. In the Run dialog box, in the Open box type:

      cmd

    2. Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:

      chkdsk drive: /f

    Method 2:

    1. Double-click My Computer, and then select the hard disk you want to check.
    2. On the File menu, click Properties.
    3. Click the Tools tab.
    4. In the Error-checking box, click Check Now.
    5. In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.

    If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.

    If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!

  • Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel. 

Microsoft KB articles:

Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages
STOP 0x23 (or STOP 0x24) When restarting PC after installing PC-Magic Encrypted Magic Folders

 

Stop 0x0000002E or DATA_BUS_ERROR

The Stop 0x2E message indicates a system memory parity error. The cause is typically failed or defective RAM (including motherboard, Level 2 cache, or video memory), incompatible or mismatched memory hardware, or when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (does not map to a physical address). A Stop 0x2E message can also indicate hard disk damage caused by viruses or other problems.

Possible Resolutions:

  • Stop 0x2E is typically due to defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
     
  • Stop 0x2E messages can also occur after installing faulty drivers or system services. If a file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
     
  • Hard disk corruption can also cause this Stop message.
     
  • The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.

 

Stop 0x0000003F or NO_MORE_SYSTEM_PTES

The Stop 0x3F message indicates one or more of the following problems:

  • The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions.
  • A faulty device driver is not managing memory properly.
  • An application, such as a backup program, is improperly allocating large amounts of kernel memory.

Possible Resolutions:

  • Stop 0x3F messages can occur after installing faulty drivers or system services. If a file name is given, you need to disable, remove, or roll back that driver. Disable the service or application and confirm that this resolves the error. If so, contact the hardware manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
  • The system might not actually be out of PTEs, but a contiguous memory block of sufficient size is not available to satisfy a driver or application request. Check for the availability of updated driver or application files and consult the hardware or program documentation for minimum system requirements.
  • Another cause is excessive demands for system PTE by applications. This situation is more common in server environments. Windows XP Professional provides a registry entry, SystemPages, that you can use to increase the number of PTEs allocated.

    Caution

    • Do not edit the registry unless you have no alternative. The registry editor bypasses standard safeguards, allowing settings that can damage your system, or even require you to reinstall Windows. If you must edit the registry, back it up first... 

    To increase the number of PTEs allocated in the registry

    1. In the Run dialog box, and in the Open box, type: regedit
    2. In the registry editor, navigate to the subkey HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl
      Session ManagerMemory Management.
    3. Double-click on PagedPoolSize and SystemPages to view the value for each entry.
    4. If PagedPoolSize is not zero, assign a value of 0.
    5. If SystemPages is not zero, assign a value of 40000 for systems with 128 MB (or less) of memory, or 110000 for systems with 128 MB to 256 MB of memory. For systems with more memory, do not increase the SystemPages value above 110000 without contacting Microsoft technical support.
    6. Click OK, and then close the registry editor.
    7. Restart your computer.

 

Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.

Possible Resolutions:

  • If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.
  • Stop 0x50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.

Microsoft KB articles:

 STOP 0x00000050 PrtSeqRd deferencing null device objectSTOP 0x50 Error starting Windows after connecting a scanner

 

Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR

The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.

Possible Resolutions:

  • Stop 0x77 messages can be caused by bad sectors in the virtual memory paging file or a disk controller error. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, which is an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.
  • Another cause of Stop 0x77 messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
  • The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
  • Problems that cause Stop 0x77 messages can also cause Stop 0x7A messages. For more information about Stop 0x7A messages, see "Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR" later in this list.

Microsoft KB articles:

Troubleshooting Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR

 

Stop 0x00000079 or MISMATCHED_HAL

The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. This error most often occurs when ACPI firmware settings are changed. For example, you might install Windows XP on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also result when mismatched single and multi-processor configuration files are copied to the system.

Possible Resolutions:

  • A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the system. This error also occurs when using mismatched files, such as copying a multiprocessor HAL on to a system using a single-processor kernel (or vice versa). The kernel and HAL files for single-processor and multiprocessor systems are stored on the Windows XP Professional operating system CD using two different file names. For example, the single and multi-processor versions of the kernel, named Ntoskrnl.exe and Ntkrnlmp.exe respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your system as Ntoskrnl.exe. In Recovery Console, you can use the Copy command to copy the correct HAL or kernel files from the CD to the appropriate folder on the hard disk.
  • If you experience Stop 0x79 messages after changing firmware settings, restore the original settings used during Windows XP Professional Setup.

    Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware, you can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Somex86-based provide the option to toggle ACPI functionality. To disable or re-enable ACPI, you must change firmware settings and reinstall Windows XP. Because of the numerous registry and system file changes required, you must run Setup again (an upgrade installation does not work).

 

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR

The Stop 0x7A message indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.

Frequently, the cause of this error can be determined from the second parameter, the I/O status code. Some common status codes are:

  • 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
  • 0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors) on the hard disk.
  • 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.
  • 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
  • 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, or defective disk cabling, or two devices attempting to use the same resources.

Possible Resolutions:

  • Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk controller error, virus infection, or memory hardware problems. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix.
  • Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
  • Check the hardware manufacturer’s Web site for updates to disk adapter firmware or drivers that improve compatibility. Verify that your disks and controller support the same set of advanced features, such as higher transfer rates. If necessary, select a slower transfer rate if an update is not yet available. Consult your hardware or device documentation for more information.

    Important

    • You can install disk controller drivers not present on the Windows XP Professional operating system CD by responding to the following prompt shortly after starting Setup:
    • Press F6 if you need to install a third party SCSI or RAID driver.
    • Press F6, and when prompted, provide the appropriate storage controller driver (ATA or SCSI) supplied by the manufacturer.

     

  • The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
  • Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For more information about Stop 0x77 messages, see "Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR" earlier in this list.

 

Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE

The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.

The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:

  • Disks or storage controllers that are failing, defective, or improperly configured.
  • Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.

Possible Resolutions:

  • During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.
  • Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.
  • Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer’s documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer’s instructions when installing drivers. Periodically check for driver and firmware updates.
  • Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.
  • Problems that cause 0x7B errors might also cause Stop 0xED errors. For more information about 0xED Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" later in this list.

Microsoft KB articles:

Troubleshooting STOP 0x0000007B or 0x4,0,0,0 ErrorSTOP 0x0000007B Error After You Move the Windows XP System Disk to Another ComputerSTOP 0x0000007B Error Message When You Restart ComputerSTOP 0x0000007B Caused by Missing [SysprepMassStorage] Section on Windows XP sysprep ImagesSTOP 0x0000007B Error Occurs When You Press F6 to Load Drivers During Unattended Windows Setup

 

Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP

The Stop 0x7F message indicates that one of three types of problems occurred in kernel-mode:

  • A condition that the kernel is not allowed to have or intercept (also known as a bound trap).
  • Software problems.
  • Hardware failures.

Possible Resolutions:

  • Stop 0x7F messages are typically due to defective, malfunctioning, or failed memory hardware. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.
  • Running the CPU beyond the rated specification, known as "overclocking," can cause Stop 0x7F or other error messages due to heat buildup. When diagnosing problems on overclocked systems, first restore all clock and bus speed settings to the manufacturer recommended values to determine if this resolves the issues.
  • The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
  • Stop 0x7F messages can occur after installing incompatible applications, drivers, or system services. Contact the software manufacturer about possible Windows XP specific updates. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.

Microsoft KB articles:

STOP 0x0000007F Errors - General CausesSTOP 0x0000007F Computer Turns Off During Text-Mode Setup if it is too hotSTOP 0x0000007F During Setup on Hewlet Packard Pavilion 7840

 

Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE

The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.

Possible Resolutions:

  • Stop 0x9F messages can occur after installing faulty applications or drivers or system services. If a file is listed by name and you can associate it with an application, uninstall the application. For drivers, disable, remove, or roll back that driver to to determine if this resolves the error. If it does, contact the hardware manufacturer for a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
  • For information about troubleshooting standby and hibernate mode issues, see KB article Q266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000." 

Microsoft KB articles:

Troubleshooting a Stop 0x9F Error in Windows XPSTOP 0X0000009F Computer hangs at shutdown or "Cannot find enough resources"

 

Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY

The Stop 0xBE message indicates that a driver attempted to write to read-only memory.

Possible Resolutions:

  • A Stop 0xBE message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Microsoft KB articles: STOP 0xBE Qwestdex Dex Toolbar not totally compatible with Windows XP

 

Stop 0xC2 or BAD_POOL_CALLER

The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:

  • By allocating a memory pool size of zero bytes.
  • By allocating a memory pool that does not exist.
  • By attempting to free a memory pool that is already free.
  • By allocating or freeing a memory pool at an IRQL that was too high.

This Stop message is typically due to a faulty driver or software.

Possible Resolutions:

  • A Stop 0xC2 messages might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
  • A Stop 0xC2 messages might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.
  • If you encounter a Stop 0xC2 message while upgrading to Windows XP, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP, contact the hardware manufacturer to obtain compatible updates.

Microsoft KB articles:

How to Debug Stop 0xC2 or Stop 0x000000C2 Error Messages
STOP 0x000000c2 Computer with ATI FURY MAXX hangs after upgrade to Windows XP STOP 0x000000c2 After you install IomegaWareSTOP 0xC2 Bad_Pool_Caller When you upgrade from Windows 2000

 

Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT
_CANCELLING_PENDING_OPERATIONS

This Stop messages indicates that a driver failed to cancel pending operations before exiting.

Possible Resolutions:

  • Stop 0xCE messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

Microsoft KB articles:

STOP 0x000000CE in Dxapi.sys Error on Blue ScreenSTOP 0x000000CE When you stop SFU 2.0 NFS Client Service on Windows-XP Based Computer

 

Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL

The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.

Possible Resolutions:

  • Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Microsoft KB articles: STOP 0x000000D1 Error Message When You Turn Your Computer OffSTOP 0xD1 Error Message When You Start Windows XPSTOP 0xD1 Second Mylex AcceleRAID SCSI Controller Causes Error MessageSTOP 0x000000D1 WRQ AtGuard Program causes error message in Windows XP

 

Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER

A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.

Possible Resolutions:

  • Stop 0xD1 messages can occur after installing faulty drivers (especially video drivers) or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
Microsoft KB articles: STOP 0x000000EA ErrMsg Running Video-Intensive ProgramsSTOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER

 

Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME

The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error might also occur during an upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling. In some cases, your system might appear to work normally after you restart.

Possible Resolutions:

  • If using higher throughput ATA disks and controllers, those capable of data transfer rates above 33.3 megabytes per second, replace the standard 40-pin cable with an 80-pin cable. Using an 80-pin cable is optional for transfer rates up to and including 33.3 megabytes per second, but is mandatory for higher transfer rates. The additional grounded pins are required to avoid data loss.
  • Some firmware enables you to force higher transfer rates even when you are using the incorrect cable type. Your firmware might issue a warning but allow the startup process to proceed. Restore the default firmware setting for ATA cable detection.
  • Problems that cause 0xED errors might also cause Stop 0x7B errors. For more information about 0x7B Stop messages, see "Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE" earlier in this appendix.

Microsoft KB articles:

STOP 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is MountedSTOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME Error Message

 

Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.

Possible Resolutions:

  • You can use Driver Rollback or System Restore from safe mode, to restore a previous driver. You can also use Windows XP Professional recovery features such as the Last Known Good Configuration startup option, Backup, or Automated System Recovery to restore a previous working configuration. After restoring from backup media, you might need to reapply service packs or hotfixes, depending on when the backups were made.
  • If the Stop message names the specific file, try replacing it manually with a fresh copy from the Windows XP Professional operating system CD using safe mode or Recovery Console. For systems using the FAT16 or FAT32 file system, you have the option of using a Windows 98 or Windows Millennium Edition Emergency Boot Disk to access the hard disk.

    If the original file from the operating system CD has a file name that ends with an underscore (_) character, you cannot use the file until it is uncompressed. The Recovery Console’s Copy command is ideal for copying compressed files because it detects and expands them. If you do not specify a destination file name, you must rename the expanded file with the correct extension before using it. From safe mode or Recovery Console, you can use the Expand command to uncompress and copy a file to a destination location. In Recovery Console, the expanded file is given the correct name after being copied to the destination location. For more information about the Copy or Expand commands, see Windows XP Help and Support Centre.

Microsoft KB articles:

STOP C0000221 Unknown Hard Error
STOP 0xc000026C or Stop 0xc0000221 Unable to Load Device Driver Error Occurs When You Start Windows XP

 


28/02/2009 07:46 Victor Manuel Uribe Mantilla #. sin tema No hay comentarios. Comentar.

Te esta molestando el svchost.exe y te apaga el equipo u otras vainas....

Me refiero a un reinicio sin aviso, no como el Blaster o el Sasser cuales te reinician la computadora en un minuto después de causarte un problema con Svchost.exe o lsass.exe.  Este reinicio ocurre segundos después de iniciar Windows XP, de repente, sin aviso se reinicia el equipo. Normalmente, esto se debe a una falla en uno de tus dispositivos, pero Windows XP esta configurado para reiniciar la computadora automáticamente y no presentarte un error.

Presentar un error en vez de reiniciar

En vez de reiniciar, podemos hacer que Windows XP te presente una pantalla azúl con información del problema. Para esto, haz clic derecho sobre Mi PC o My Computer, del menú eliges propiedades. Ahora fijate en esta imagen:

Si no logras llegar a esta ventana entrando a Windows normalmente, trata entrando a modo a prueba de fallos (modo seguro), o Safe Mode. Para esto, presiona F8 varias veces al terminarse de ver la pantalla del BIOS y antes de empezar a cargar Windows XP.

Fíjate en la imagen hasta llegar a la segunda ventana. En la primera, eliges opciones avanzadas. En la segunda ventana desactivas Reiniciar automáticamente o restart automatically, como ves en la imagen, haz clic en OK o Aceptar para guardar los cambios.

Si se te presenta la pantalla azul, puede ser que tengas un problema con un de tus dispositivos, podemos hacer varias cosas para tratar de determinar la causa del problema.

Encontrando el problema

Desde Windows 95, la pantalla azul indica que Windows ha fallado de una manera irrecuperable y se ha terminado la sesión. Ahora tienes que reiniciar tu computadora o apagarla. Esta pantalla puede indicar muchas cosas así como un sector dañado en el disco duro, varios bytes dañados en la memoria, incompatibilidad con un controlador de un dispositivo, problemas con el archivo de paginación o un problema con la tarjeta madre. La pantalla azul presenta un mensaje en especifico cual nos puede ayudar a determinar el problema. Esta pagina:http://www.updatexp.com/stop-messages.html contiene una lista explicando cada error, asi como IRQL_NOT_LESS_OR_EQUAL o KMODE_EXCEPTION_NOT_HANDLED. Si con tus propios experimentos has determinado que la causa se debe a un fallo en uno de los dispositivos, puedes probarlos individualmente, 

28/02/2009 07:56 Victor Manuel Uribe Mantilla #. sin tema No hay comentarios. Comentar.

en mayo del 2002 se dijo esto de los usb.............y hoy siguen dando problemas

20090228140514-images.jpg

En una reciente conferencia de seguridad realizada en Londres, se planteó un tema que actualmente preocupa cada vez más a los expertos.

Actualmente, ni los antivirus ni los cortafuegos proveen una defensa directa contra una nueva vía de ataque para el código maligno: los puertos USB.

Creados para brindar una fácil y rápida conectividad con diversos dispositivos, los puertos USB permiten la rápida conexión de elementos que van desde cámaras digitales a impresoras, pasando por dispositivos de almacenamiento como el Memory Key, aparato con forma de llavero que se convierte automáticamente en un muy útil dispositivo de almacenamiento.

Pero esta interconectividad, también permite no solo el ingreso de virus, gusanos y troyanos, sino el robo de información de nuestras computadoras.

Una simple cámara digital conectada a un puerto USB, tiene hoy día una gran capacidad de almacenamiento, y muchas veces se convierte en una unidad de disco más, desde donde se pueden cargar y descargar imágenes. Esta facilidad habilita también la propagación de virus y otro código dañino hacia nuestra computadora, por el simple hecho de la facilidad de conectar la cámara en forma promiscua a cualquier computadora.

No siempre un antivirus reaccionará ante esta posible forma de propagación, porque además no estamos hablando de código ejecutable normal. Si nos atenemos a las recientes alarmas dadas sobre la posible infección de archivos MP3 por ejemplo, podemos darnos una idea de que es lo que preocupa a los expertos.

Una sencilla cámara digital tiene una gran capacidad de almacenamiento, que podría poner en riesgo toda una red corporativa. No solo al infectar, sino también al poder "robar" información sin que un cortafuegos advirtiera del peligro.

Sobre el tema de los virus, recientemente fue noticia (comentada en nuestro boletín 591), el descubrimiento de un virus que infecta los sectores de booteo, el WYX, en algunos dispositivos Memory Key de IBM, el "llavero" que mencionábamos antes.

La infección se produjo por un error, pero llegó a salir a la venta una partida de ese elemento, antes que fuera dada la voz de alarma. Y si bien en ese caso concreto, el virus, además de sumamente conocido, prácticamente era inofensivo ya que no se puede bootear desde un dispositivo como el mencionado, nada impide la ejecución por error en un ambiente crítico, de código que pueda propagar una infección de consecuencias imprevisibles.

Existen además, diversas herramientas que pueden utilizarse a través de los puertos USB, y que permiten a cualquier usuario ganar privilegios administrativos en una red, al ejecutar una simple aplicación.

Cómo la mayoría de los ataques de seguridad a una compañía provienen, en una proporción realmente alta, de su interior (un empleado disconforme o molesto), la posibilidad de utilizar para alguna clase de ataque, una interconectividad vía USB y sus dispositivos, es realmente preocupante, según otra de las conclusiones aportadas en la reciente conferencia de seguridad realizada en Londres.

En este entorno, utilizar una cámara digital con capacidad de conexión USB, para desatar en forma premeditada un ataque virósico desde adentro de una empresa, tiene una gran probabilidad de éxito, tal como están las cosas al momento actual.

También es cierto que ya existe software que protege a una compañía de ataques internos, e incluso desde puertos USB. Pero muchas empresas que ni siquiera mantienen un control estricto en materia de intercambio de correo electrónico (por ejemplo), lo ignora, o no lo tiene en cuenta en su presupuesto.

Por lo pronto, es conveniente que al menos, empecemos a ser conscientes que la facilidad de conectar cualquier dispositivo a un puerto USB, también abre nuevas puertas a los virus y a nuevos ataques malignos a nuestro PC, para empezar a aplicar al menos, unas mínimas medidas de control, sobre todo en entornos corporativos o

28/02/2009 09:05 Victor Manuel Uribe Mantilla #. sin tema No hay comentarios. Comentar.


Blog creado con Blogia. Esta web utiliza cookies para adaptarse a tus preferencias y analítica web.
Blogia apoya a la Fundación Josep Carreras.

Contrato Coloriuris