Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Thursday, June 30, 2011

OpenDNS.org

OpenDNS: Un DNS rápido y útil
Siguiente »

Resumen

Cada vez que ingresamos el nombre de una página web en la barra de direcciones (http://tux-y-cia.blogspot.com), el PC consulta a un servidor DNS para avriguar la dirección IP de la página.
Por lo general, utilizamos los servidores DNS de nuestro proveedor de acceso a Internet, pero podemos utilizar otros servidores DNS.
OpenDNS nos permite utilizar (gratuitamente) sus servidores DNS en lugar de los de nuestro proveedor de acceso a Internet.
Ventajas
Es más rápido y posee funciones de protección (anti-phishing y otros).
Características:
  • Generalmente más rápido que nuestro proveedor de acceso a Internet (estos poseen enormes servidores, con un caché DNS importante)
  • Más fiable (OpenDNS es muy fiable y sus servidores tienen una disponibilidad del 100%)
  • Autocorrección de pequeños errores al teclear (google.cmo → google.com)
  • Proposición automática (Motor de búsqueda) si el dominio no existe.
  • Protección anti-phishing (OpenDNS está conectado directamente a PhishTank.com)
  • El servicio es gratuito
  • No hay necesidad de instalar ningún programa (sólo la dirección del DNS por configurar)
  • Cuando queremos podemos dejar de utilizar OpenDNS.
La mayoría de usuarios de OpenDNS han constatado una mejora del rendimiento, en particular el de los navegadores.
Ejemplo de como bloquea OpenDNS una página de phishing: En lugar de la página fraudulenta aparece una página de advertencia:



Simplemente utiliza los servidores DNS siguientes:
208.67.222.222
208.67.220.220 
-----------------------------------------
OpenDNS no es:
  • OpenDNS no es un filtro web: El no filtra el contenido de las páginas web.
  • OpenDNS no es un filtro URL: El no filtra las URL, bloquea únicamente los dominios y sub-dominios y no examina el resto de la URL.
  • OpenDNS no es un antivirus/antimalware: El no bloqueará la descarga de virus y troyanos.
  • OpenDNS no mejora el bitrate de tu conexión: únicamente acelera las peticiones DNS.
  • OpenDNS no mejora el ping: El solamente acelera las peticiones DNS.

Error HTTP 400 Bad request

[Solicitud incorrecta]
Fuente Introducción
El servidor web (que corre el sitio web) cree que el flujo de datos enviado por el cliente (por ejemplo, su navegador web o nuestro robot CheckUpDown) estaba malformado", es decir, no respetaba completamente el protocolo HTTP. Por lo tanto, el servidor web no pudo entender y procesar la solicitud.
Casi siempre significa una mala programación del sistema cliente o del servidor web.
Errores 400 en el ciclo HTTP
Cualquier cliente (por ejemplo, su navegador web o nuestro robot CheckUpDown) sigue el siguiente ciclo:
  • Obtiene una dirección IP del nombre IP del sitio (la URL del sitio sin el encabezado "http://"). Esta búsqueda (la conversión del nombre IP a dirección IP) es provista por los servidores de nombre de dominio (DNS).
  • Abre una conexión de socket IP hacia esa dirección IP.
  • Escribe un flujo de datos HTTP a través de ese socket.
  • Recibe un flujo de datos HTTP en respuesta desde el servidor web. Este flujo de datos contiene códigos de estado cuyos valores son determinados por el protocolo HTTP. Analiza este flujo de datos en busca de códigos de estado y otra información útil.
Este error ocurre en el paso final mencionado arriba cuando cliente recibe un código de estado HTTP que reconoce como "400".
Arreglo de errores 400 - General
Existe un problema de nivel bajo en el cliente o servidor Web o en ambos. El 95% de las veces esto se debe a un problema en el sistema cliente, o sea, que hay algún elemento inestable en el ordenador en el que está utilizando el navegador Web.
  • ¿Su ordenador es seguro? Si su ordenador no está correctamente protegido, entonces pueden tener lugar múltiples problemas, incluyendo errores de código HTTP 400. Si utiliza Windows, manténgase al día con las actualizaciones automáticas de seguridad de Microsoft y considere además realizar una limpieza de registros. Siempre disponga de la protección de un buen antivirus y anti espías. Invierta en un cortafuegos de hardware si puede permitírselo. Utilice su sentido común al navegar por la web, bloquee las ventanas emergentes y evite ir a sitios malos. Si la seguridad de su ordenador está en peligro, el tráfico web desde su ordenador hacia la Internet puede estar corrupto por programas malignos (programas de espías, virus, etc.) que se están ejecutando en su ordenador de forma secreta. Esto es algo difícil de detectar por el usuario.
  • ¿Ha instalado programas desde el Internet? Algunas webs de redes sociales y sitios de juegos le piden que descargue y ejecute programas en su ordenador para poder interactuar con otras personas de forma directa a través de Internet (sin utilizar su navegador Web). Estos programas, tanto si contienen defectos de programación o han sido creados con propósitos criminales, pueden corromper todo el tráfico HTTP desde su ordenador. Y deshacerse de los mismos puede resultar complicado. En el peor de los casos, deberá reinstalar su sistema operativo nuevamente (posiblemente con la consiguiente pérdida de datos personales en su ordenador si no dispone de una copia de seguridad).
  • ¿Qué tan estable es su conexión a Internet? Si ha cambiado de proveedor de Internet recientemente o su proveedor de Internet es muy lento o poco fiable, el tráfico web desde su ordenador hacia cualquier sitio de Internet puede estar corrupto. La razón de la inestabilidad puede deberse a que su proveedor de Internet haya reconfigurado parte de la instalación (por ej., introducción de nuevos servidores proxys o caché). Una señal posible de que hay problemas es si no puede navegar fácilmente por la página web de su proveedor de internet. También puede intentar comprobando que la página web que esté visitando en ese momento sea la que Usted crea que es. Por ejemplo, esto puede deberse a un problema del sistema de nombres de dominio (servidor DNS). Esto puede comprobarse empleando un test de ping. El problema con el serivdor DNS puede ser causado por su proveedor de internet o puede encontrarse en su propio sistema, por ej., en un archivo huésped.
  • ¿Se repite el mismo error en más de una página web? Si se repite el mismo error en varias paginas web, esto indica que el problema está en su ordenador, no en todas esas páginas.
  • ¿Se repite el mismo error en más de un navegador web? Si cuenta con dos o más navegadores web instalados en su ordenador y el comportamiento al utilizar cada uno es diferente (un navegador web da un error HTTP 400 al visitar un sitio y otro navegador web no da el error 400 al visitar el mismo sitio) entonces puede tratarse de que uno de sus navegadores puede estar defectuoso. Intente buscar una actualización o parche de seguridad para el navegador con problemas. Si ha cambiado cualquier opción de configuración recientemente en el navegador con problemas, intente revertir el cambio para ver si esa es la causa.
  • ¿Recibe el código de error al visitar páginas web reconocidas? Si tiene el problema al visitar alguna página pequeña, visite algunas de las páginas web reconocidas como Amazon, Ebay, Google, Microsoft y Yahoo. Si el problema sólo ocurre cuando visita páginas pequeñas, esto indica que el problema se da con esos sitios solamente o con el tráfico desde su ordenador hacia estos sitios.
  • ¿Recibe el código de error al visitar páginas web simples? Si tiene el problema al visitar direcciones URL largas y complicadas (como por ej. http://www.xxx.com?PHPrequest=643&value=dres&cookies=No) pero no le sucede al visitar direcciones URL más cortas y simples dentro del mismo sitio ( como ser http://www.xxx.com), esto puede indicar un problema en el servidor web del sitio que está intentando visitar. Aunque no se trata de evidencia concluyente, es un buen punto de comienzo. Consulte a los propietarios de la página web y descríbales el problema.
    Podrá tratarse por ejemplo de un problema con los métodos POST (al enviar y recibir información hacia y desde la página web) pero no con los métodos GET (al recibir únicamente información desde la página web).
  • ¿Tiene una problema de caché? Intente limpiar sus cookies, el caché de su navegador y su historia de navegación en el navegador. Desactive o elimine cualquier método de caché de terceros o programas de aceleramiento de la web que haya instalado. Intente reiniciar su ordenador y/o el cortafuegos o enrutador o módem que utilice para conectarse a internet. Esto puede que no resuelva el problema, pero al menos eliminará cualquier problema debido a viejas configuraciones en su ordenador.
  • ¿Qué cambios se han realizado desde que empezó a tener el problema HTTP 400? En términos generales, piense en lo que ha cambiado en su ordenador desde que empezó a ver el problema por primera vez. Esto puede cubrir cualquiera de los elementos antes mencionados. Vaya dando pasos hacia atrás y compruebe si al deshacer estos cambios se produce alguna modificación.
Hay multitud de elementos que puede comprobar en su propio ordenador. Si consulta con los propietarios de la página web que le da el error HTTP 400 y éstos le responden "Tenemos multitud de usuarios que no tienen su mismo problema - por eso debe tratarse de algún problema en su ordenador", la mayoría de las veces tienen razón - y no es de esperar que estén interesados en solucionar los problemas de su ordenador. Aunque si ellos saben que existe un problema en su página web, deberían decírselo y decirle cuándo esperan solucionar el problema.
error-de-htpp-400-bad-request

Saturday, June 25, 2011

OSX recovery

About Disk Drill
A Mac data recovery software designed natively for Mac OS: easily recover deleted files on Mac from external or internal hard drives, memory cards, etc. CleverFiles Mac Data Recovery also protects data by introducing Recovery Vault to ensure guaranteed Mac data recovery from HFS/HFS+/FAT file systems. It handles Mac data recovery from any, even formatted or raw, media.

CleverFiles Mac recovery software finds any data if it wasn’t overwritten and supports any file system by offering Deep & Quick Scan data recovery methods right on your Mac. So if your hard drive was damaged, or you accidentally deleted your favorite photos, music, videos and other data, no worries about data loss. Disk Drill will recover deleted files on Mac from your disk, camera, memory card, etc. And it’s absolutely free now! More than that Disk Drill features Recovery Vault technology, which helps you protect your files and prevent data loss in future. Many more features.
mac-osx/disk-drill-1-3
http://www.applesfera.com/aplicaciones/disk-drill-recuperador-de-datos-a-fondo

Friday, June 17, 2011

amd phenom 8450 triple core update

amd phenom(tm) 8450e triple-core processor driver – DOWNLOAD 

$MFTMirr does not match $MFT (record 0)

Source
 BY 

Sometimes, when you are executing a file transfer between your computer hard drive and an external drive and your computer shutdown for some reason (in my case, no battery/ac power) it’s pretty common to get some errors on external drives that uses NTFS as they file system.

The most common message is:

Error mounting: mount exited with exit code 13: $MFTMirr does not match $MFT (record 0).

Failed to mount ‘/dev/sdb3′: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it’s a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the ‘dmraid’ documentation
for more details.
One workaround for this issue is to do as the message says, boot on Windows and try to use the 
awesome
 NTFS tool that Windows offer. But a perfect solution for a Linux users is to use the ntfsprogs utility.
ntfsprogs is a suite of NTFS utilities based around a shared library. The tools are available for free and come with full source code.
  • mkntfs: Create an NTFS volume on a partition
  • ntfscat: Print a file on the standard output
  • ntfsclone: Efficiently backup/restore a volume at the sector level
  • ntfscluster: Given a cluster, or sector, find the file
  • ntfsfix: Forces Windows to check NTFS at boot time
  • ntfsinfo: Dump a file’s attributes, completely
  • ntfslabel: Display or set a volume’s label
  • ntfslib: Move all the common code into a shared library
  • ntfsls: List directory contents
  • ntfsresize: Resize an NTFS volume
  • ntfsundelete: Find files that have been deleted and recover them
  • ntfswipe: Write zeros over the unused parts of the disk
  • ntfsdefrag: Defragment files, directories and the MFT
  • ntfsck: Perform consistancy checks on a volume
  • nttools: Command-line tools to view/change an offline NTFS volume, e.g. ntfscp, ntfsgrep, ntfstouch, ntfsrm, ntfsrmdir, ntfsmkdir
  • ntfsdiskedit: Walk the tree of NTFS ondisk structures (and alter them)
Be careful with these utilities, they might damage the filesystem, or your hard disk !
With ntfsprogs installed (sudo apt-get install ntfsprogs) you should execute the following commands in a terminal:
sudo ntfsfix /dev/partitionName
After this command you should expect the following output:
~$ sudo ntfsfix /dev/sdb3
Mounting volume... FAILEDAttempting to correct errors...Processing $MFT and $MFTMirr...Reading $MFT... OKReading $MFTMirr... OKComparing $MFTMirr to $MFT... FAILEDCorrecting differences in $MFTMirr record 0...OKProcessing of $MFT and $MFTMirr completed successfully.Setting required flags on partition... OKGoing to empty the journal ($LogFile)... OKNTFS volume version is 3.1.NTFS partition /dev/sdb3 was processed successfully.
After this step you should be able to access your external drive partition as usual, mount or use nautilus to access your files.
Source:  http://gnuwin32.sourceforge.net/packages/ntfsprogs.htm


How to recover files off a crashed hard drive


One universal true about computers is this: the hard drive will fail. It is not a matter of if, but a matter of when. In an ideal world, every computer user would make regular, full backups of their system. Unfortunately, that isn’t the case, and far too often computer users find themselves with a crashed hard drive.
If your hard drive has crashed and you’re unable to boot into the system to retrieve your files, you’ll have to take a different, more involved approach. This tutorial will show you how to recover files off of a crashed hard drive.
These instructions assume that the hard drive is crashed but not physically damaged. You can use these instruction with both Mac OS X and Windows. You will need a second computer with Internet access and a DVD burner, a blank CD, and the crashed system should have an optical drive.
Step 1
Download a Linux distro that offers a LiveCD, or that can be run from a CD or pen drive. Small-file size options are Puppy Linux and Damn Small Linux. However, I recommend downloading Ubuntu, simply because mounting a drive is effortless with it and does not require the Terminal.
Step 2
Burn the downloaded ISO file to a blank CD using Nero or any other burning software.
Step 3
Insert the CD into your crashed system and restart the computer. At BIOS, enter setup by pressing the designated key for your system – for most computers, it’s F12 or ESC.
Once in BIOS, select Boot Sequence and highlight CD/DVD Drive. Press the ‘U’ button to move the option above the internal hard drive, then save and exit BIOS.
The computer will restart and the Ubuntu logo will be displayed along with a menu of options. Choose ‘Try Ubuntu….’ This will start Ubuntu, running it from your CD drive. Don’t worry, it won’t affect your hard drive in any way.
Step 4
After Ubuntu has loaded, look in the upper left corner. Choose Places. Towards the bottom of the menu, you will see a picture of a hard drive – it will say something like ’0.0GB Drive’, displaying the capacity of your internal hard drive. Click to mount.
Step 5
Plug in your external hard drive or flash drive. Navigate to Places and choose the new drive you just plugged in to mount it.
Step 6
The internal hard drive and external media are now mounted. Look on the desktop for the hard drives. Click them to open.
In the windows that appear, you can choose Documents and Settings and copy the data files to your external drive, or you can simply copy the entire internal drive to the external drive and sort it out later.
Step 7
Once finished, shut the machine down and remove the CD when instructed.
You can now reload your system as normal.
http://www.ubuntu-es.org/?q=node/124721

Tuesday, June 14, 2011

nForce 630a and fakeRAID

MCP78 630a+7050 or nForce630a
All nVidia forums

Source
Windows XP
7025/630a

None of them do support nForce 630a chipsets. The needed DeviceID's are missing.
Those are the official drivers from NV for their mediashield raid setup.
They were extracted from the installs for both those chipsets.
And for your info, the mediashield drivers are NOT universal for all recent (since nforce3) chipsets, I included both just in case (have now taken apart nearly all the chipset drivers from NV and the raid drivers are NOT all the same). The latest official nForce SATA and RAID drivers, which natively should support nForce 630a chipsets (needed DeviceID's are present), are v10.3.0.46 and part of NVIDIA's 15.25 sets.
I suggest to try these special 32bit nForce SATARAID drivers.
You can download them from here
=============================
Source
Windows 7 drivers
The problem is the 630a is actually 2 different chip-sets, there is the 630a SLI that is a stand alone chip-set for use with a video card and there is the 630a that is used with integrated chip-sets (7050, 7150, 7025, etc).
Yours is the latter of course, these drivers should work.
nvidia.com..nforce_vista_win7_64bit_15.49 (210 MB)
But they don't work with nForce 630a chipsets, although NVIDIA's download pages do officially offer this 15.49 set for them.
The latest officil NVIDIA nForce chipset driver set, which does support nForce 630a chipsets, are the 15.25 sets for Vista, which contain the nForce IDE drivers v10.3.0.46.
----------------
It's installer won't install even Ethernet driver (nor manually trying it via devmgmt.msc).
Affected platform: MCP78 630a+7050
Affected OS: WinXP, Vista, Windows 7.
Affected OS editions: all x32 and x64 editions.
At least 15.25 driver will install Ethernet in Winxp 32bit, although there was no SATA driver around for Vista/Win7 either x32 nor X64.
---------------
You are right: The nForce chipset driver sets, which are officially offered by NVIDIA for nForce 630a chipset users at this site, do not work with nForce 630a chipsets, because the needed DeviceID's are missing within the INF files of the drivers.
Nevertheless here are some corrections:
1. NVIDIA's "officially presented" nForce driver sets for nForce 630a chipsets are v15.45 (for Windows XP 32/64bit) and v15.49 (for Vista and Win7 32/64bit). None of these sets are compatible with nForce 630a chipsets.
2. The latest nForce chipset driver sets, which do work with nForce 630a chipsets, are v15.25 (for XP, Vista and Win7 32/64bit).
3. nForce 630a chipsets belong to the MCP67 series.
At least 15.25 driver will install Ethernet in Winxp 32bit, although there was no SATA driver around for Vista/Win7 either x32 nor X64.
The nForce chipset driver sets 15.25 do contain a NVIDIA nForce SATA driver (it's v10.3.0.46), which will work with nForce 630a chipset systems, but only if the SATA Controllers have been set to AHCI or RAID mode. Users, who want or have to run their SATA ports in IDE mode, can only use Microsoft's generic IDE driver named PCIIDE.SYS.

==============================
==============================
Integration of NVIDIA's nForce RAID and AHCI drivers 
Thanks, Fernando!!
The problem:
None of the Pre-Vista Windows Operating Systems do support the S-ATA Controller features RAID ("Redundant Array of Independent Disks") and AHCI ("Advanced Host Controller Interface"). Unless the suitable nForce Sata/PataRAID or AHCI drivers are separately presented by the user, the OS installation fails, because the OS Setup doesn't find the related RAID/AHCI drives and their partitions.
The traditional method to provide the needed drivers by F6/floppy has some severe disadvantages:
  • A floppy drive is needed, but not available at many actual desktop computers and notebooks.
  • Floppy disks are the worst data storage media regarding the file integrity. Bad floppy disks are the main reason for corrupted driver files.
  • The F6/floppy method doesn't work at all with some "LEGACY mode" nForce RAID systems. Even if the user loads the correct nForce drivers and the RAID is detected by Windows Setup, the OS installation may end with a BSOD and endless reboot loops.
The better alternative is the integration of the needed textmode drivers into a bootable OS CD. Only this way the user can be sure to succeed with the installation of the OS onto an nForce RAID or AHCI system. Nevertheless the developers of the driver integration method had to solve the above specified problem (see point 3). Until 2005 the correct installation of the nForce S-ATA/P-ATA Controllers and drivers needed addtional manual work of the user. They only succeeded after having created special folders and edited some SIF and/or OEM files.

The solution:
The safest and easiest way to get the problematic nForce textmode drivers properly installed is to integrate them by using a tool like nLite. All actual versions of nLite (Since v1.0 Final) have incorporated a special method, which guarantees the successful OS installation onto any nForce RAID or AHCI system (if the user observes some rules layed down below). The replacement of the correct nForce Controllers and drivers by the "wrong" MS IDE ones will be prevented by the built-in suppression of the MS IDE drivers during the hardware detection part of the OS installation.
Advantages:
- fully automatic method (without creating new directories or editing SIF or OEM files)
- support of not digitally signed textmode drivers
- without restriction of any kind during the use of nLite

Who needs to load/integrate which nForce IDE driver subfolder?
You can get NVIDIA nForce chipset deskop computers and laptops with the following variations:
  • non-RAID/AHCI nForce systems (RAID/AHCI not supported or disabled):
    Users with such system don't have to load/integrate any nForce IDE drivers.
  • nForce RAID systems (SataRAID or PataRAID):
    NForce Users with enabled RAID settings within the BIOS need to load/integrate the LEGACY (for NF2-4 chipsets) or the SATARAID subfolder of the suitable nForce chipset driverpack as TEXTMODE driver. Users with an old "LEGACY mode" nForce RAID system, who want to integrate the SATARAID subfolder, additionally have to integrate the SATA_IDE subfolder as PnP driver to prevent a BSOD at the end of the OS installation.
  • nForce AHCI systems (S-ATA Controllers set to AHCI mode):
    The actual nForce chipsets (MCP65 and up) do support the enhanced features (NCQ etc.) of the new S-ATA standard AHCI. If the NVIDIA nForce S-ATA Controllers are set to "AHCI mode" (instead of "IDE mode") within the BIOS, users have to load/integrate the suitable SATA_IDE subfolder as TEXTMODE driver. Only the new generation of nForce S-ATA drivers named "NVGTS" do support the AHCI features and can be integrated as textmode driver. Suitable SATA_IDE subfolders contain a TXTSETUP.OEM file.
Here is the way how to do it:

Integration of NVIDIA's nForce RAID and AHCI drivers
by using nLite


Guide for Windows XP and Windows Server 2003 (32/64bit)



A. Integration of the nForce RAID drivers
(if the OS will be installed onto any RAID partition)


Short form guide
(for hasty users, who want a quick result)

If you want to create a bootable OS CD, which will detect your RAID and be successfully installed onto it, you should do the following:
  • Get the actual nLite version from here and install it (.NET Framework 2.0 or equivalent is needed).
  • Download and unzip one of the following already prepared drivers (the choice depends on the OS, which shall be installed, and the nForce chipset of the destination desktop/laptop):
    a. Windows XP or Windows Server 2003 (32bit)
    b. Windows XP x64 or Windows Server 2003 x64:
  • Create a folder named "nLiteCD" (or similar) somewhere and copy the whole content of the original OS CD into it.
  • Start nLite > point to the content of the just created folder as source > hit the buttons "Drivers" and "Bootable ISO".
  • When the task "Drivers" comes > hit "Insert" > choose "Single driver" > point to the prepared SATARAID resp. LEGACY driver folder.
  • Click onto any of the shown INF files > a popup window will come up.
  • Both shown "required" NVIDIA products should be highlighted (already done by nLite) > hit "OK".
  • Only needed for some NF4-5 RAID systems after the integration of the SATARAID drivers: integrate additionally the SATA_IDE folder as PnP driver.
  • Let nLite burn the Image directly onto an empty CD ("General" > "Mode" > "Direct Burn").
  • Boot off the created CD, choose the destination partition, do a quick NTFS formatting and install the OS.
  • Have fun!


Detailed RAID drivers integration guide
(for users, who want the best possible results or who ran into problems)

Important Requirements:

You only will succeed with the integration of the nForce Pata/SataRaid drivers, if you have
  • a correctly created nForce RAID array (shown as "healthy" and set as bootable, for further information look here)
  • an up-to-date mainboard and nVRaid BIOS (= MediaShield IDE ROM), which is part of the mainboard BIOS. Actual nVRaid drivers may need a Raid Bios v4.81 (NF3) resp. v5.60 (NF4) or higher.
  • a stable system (proper RAM modules and stable BIOS settings)
  • an original (=untouched) OS CD as source (don't use or reuse a source, which has already been processed by nLite!)
  • a proper working IDE-connected CD or DVD drive (a S-ATA connected optical drive should not be connected with an nForce S-ATA Controller which are set to RAID or AHCI mode)
  • an enabled ACPI power management (within BIOS, don't disable it by nLite settings).
Tips:
  • You can see the nVRaid BIOS (=MediaShield) version of your system on the second boot screen. If you can't get a Raid BIOS version v. 4.81 or higher after having flashed the latest mainboard BIOS, you might get problems with the integration of the latest nForce Pata/SataRaid drivers.
  • The successful integration of the nForce Pata/SataRaid drivers into a bootable OS CD requires the presence of the latest available Service Pack (SP) of the used OS. If your OS CD does not contain any or the last SP, you should integrate the latest SP as first step, when you are going to create your nLited CD with integrated nForce Sata/PataRaid drivers.
  • XP 32bit (x86) only: If possible don't slipstream SP3 into an XP SP1 or SP2 CD. In this case it's better to take an original ("Gold"/RTM) OS CD without any SP as source for slipstreaming SP3 and the nForce Raid drivers. Otherwise you may get problems during the installation of the nLited CD.
  • It is a good idea to unplug all unnecessary external hardware devices during the installation of the OS with integrated nVRaid drivers.
  • If you have any hard disk drive outside your RAID array or a plugged-in USB stick, you may get the problem, that the MS Setup routine tries to install the master boot record (MBR) onto that non-RAID device, although you have set the RAID array as first bootable hard disk drive within BIOS. The only sure way to prevent this is to unplug these non-RAID devices during the installation of the OS. After the successful installation they can be reconnected without any problems.



1. Preparation and driver choice

If you are not already running the latest version of nLite, you should download it here and install it (.NET Framework 2.0 or equivalent is needed).

The next step is the preparation of the nForce textmode driver for the later integration. The choice of the "best suitable" nForce IDE driver version and subfolder mainly depends on the nForce chipset details, the RAID configuration (SataRAID or PataRAID) and maybe on the nVRaid BIOS version of the destination desktop/laptop.
NVIDIA is offering for all nForce chipsets complete driverpacks with included nForce SataRAID drivers. You will find them, if you go here, choose "nForce" (NF5 and up) or "LEGACY" (NF1-4) as "Product Type" and then choose your special nForce chipset and the OS you are going to install. Unfortunately NVIDIA's official nForce driverpacks are not always the best choice for nForce RAID users. Either they do not work at all (example: NF4 RAID), they are outdated (example: NF2-3 RAID) or they don't provide the best possible performance (valid for nearly all NF chipsets).

Since January 2008 I am offering alternative nForce drivers and driverpacks, which are actual, but maybe better than NVIDIA's official ones (for details you may look here). The used drivers themselves (=SYS files) were developed and released by NVIDIA, but for unknown reasons the manufacturer didn't add the HardwareID's of all supported nForce IDE devices. That is why I customized the associated INF/OEM files to make them compatible with as many nForce chipsets as possible. This modification doesn't touch the driver's function and the loss of Microsoft's digital signature (WHQL) has no impact on the driver's installation (thanks to nLite's built-in textmode driver integration method).

For the later integration I recommend to prepare the following actual and approved nForce textmode drivers, which are optimized for being used with nForce RAID systems:

a. Windows XP or Windows Server 2003 (32bit)
  • for nForce2/3/4 SataRAID and nForce2/3/4/5 PataRAID systems:
    >32bit nForce LEGACY drivers v6.99 mod by Fernando (download link)<
    This LEGACY textmode driver package contains the newest non-AHCI capable nForce IDE drivers v6.99 dated 14th May 2007. Since I have added all needed HardwareID's, this package will support all "LEGACY Mode" nForce2-5 RAID systems ("LEGACY Mode" means, that the NVIDIA nForce RAID Controllers of the mainboard do support Pata- and Sata-RAID simultaneously).
  • for nForce 430/410 (MCP51), nForce 590/570/550/680i/650i/780i/750i (MCP55) and nForce 430/405/400 (MCP61) SataRAID systems:
    >32bit nForce IDE drivers v9.99.09 mod by Fernando (download link)<
    Within the small package you will find the nForce IDE drivers v9.99.09 dated 01/17/2008, which have been customized by me to make them compatible with all NF4-7 chipsets. These drivers will give your nForce RAID system the best possible performance. Usually only the SATARAID driver folder will be needed for the later integration, but some users with a LEGACY Mode nForce RAID system may have to integrate both included driver subfolders (SATARAID as textmode and SATA_IDE as PnP driver).
  • for nForce 560/520 (MCP65) and nForce 630a (MCP67) SataRAID systems:
    >32bit nForce SATARAID drivers v10.3.0.46 WHQL (download link)<
    These are NVIDIA's latest nForce IDE drivers, which do fully support MCP65 and MCP67 chipsets.
  • for all other nForce SataRAID systems:
    >32bit nForce SATARAID drivers v11.1.0.43 WHQL (download link)<
    These are NVIDIA's latest WHQL certified nForce IDE drivers v11.1.0.43 dated 04/09/2010. I recommend to use these new drivers for users with a SataRAID system and an MCP73-79 chipset mainboard. Users with an MCP51, MCP55 or MCP61 chipset mainboard may take them too, but I am not sure, that they will get a better performance than with the modified nForce SATARAID drivers v9.99.09.


b. Windows XP x64 or Windows Server 2003 x64
  • for nForce3 250/nForce4 SataRAID and PataRAID systems:
    >64bit nForce LEGACY drivers v6.99 mod by Fernando (download link)<
    The package contains the newest natively 64bit nForce IDE drivers, which have been customized by me to make them usable with all "LEGACY Mode" nForce RAID systems from nForce3 up. Even MCP51, MCP55 and MCP61 PataRAID systems are supported by them.
  • for nForce 430/410 (MCP51), nForce 590/570/550/680i/650i/780i/750i (MCP55) and nForce 430/405/400 (MCP61) SataRAID systems:
    >64bit nForce IDE drivers v9.99.09 mod by Fernando (download link)<
    Within the package you will find the nForce IDE drivers v9.99.09 dated 01/17/2008, which have been customized by me to make them compatible with all NF4-7 chipsets. These drivers will give your nForce RAID system the best possible performance. Usually only the SATARAID driver folder will be needed for the later integration, but some users with a LEGACY Mode nForce RAID system may need both included driver subfolders (SATARAID as textmode and SATA_IDE as PnP driver).
  • for nForce 560/520 (MCP65) and nForce 630a (MCP67) SataRAID systems:
    >64bit nForce SATARAID drivers v10.3.0.46 WHQL (download link)<
    These are NVIDIA's latest nForce IDE drivers, which do fully support MCP65 and MCP67 chipsets.
  • for all other nForce SataRAID systems:
    >64bit nForce SATARAID drivers v11.1.0.43 WHQL (download link)<
    These are NVIDIA's latest WHQL certified nForce IDE drivers v11.1.0.43 dated 04/09/2010. I recommend to use these new drivers for users with a SataRAID system and an MCP73-79 chipset mainboard. Users with an MCP51, MCP55 or MCP61 chipset mainboard may take them too, but I am not sure, that they will get a better performance than with the modified nForce SATARAID drivers v9.99.09.

After having downloaded the suitable driverpack and unzipped it with a tool like WinRAR or 7-Zip everything is prepared for the later integration procedure.



2. Processing with nLite:

This is what you should do, before you start nLite:
  • Create a new folder somewhere on any available hard disk drive and name it as you like (for example "nLiteCD") .
  • Copy the whole content of the original OS CD into the just created folder. Don't use or reuse any already nLited or modded source.
  • Check, if you have already running the latest nLite version. If not, download and install it.
Now you can begin with the nLite processing:
  • Start nLite.
  • Choose your language > hit "Next"
  • Hit the "Browse" button, find the path to your just created folder "nLiteCD" (or similar) > click onto the folder name. Now you can see the OS details inclusive the eventually already integrated Service Pack version > hit "Next".
  • Don't import or enable any presets > hit "Next".
  • Now you will get the Task Selection page.
    You can enable all offered tasks (not recommended for newbees), but you have to enable the tasks "Integrate Drivers" and "Create Bootable ISO".
    Recommendations:
    • You should additionally choose the task "Integrate Service Pack", if the OS SP version is not actual.
    • Don't enable any other tasks, unless you are already familiar with nLite and nearly sure, that the nLite CD will work with your system (the more you are adding, tweaking or removing, the more difficult is the search for the reason, if the OS installion should fail).
    > hit "Next"
  • When you get the "Drivers Integration" page > hit "Insert" > choose the "Single driver" option > point to the prepared SATARAID or LEGACY folder with the suitable nForce Sata/PataRAID drivers > hit onto any of the shown INF files (=files with the suffix ".inf").
  • Now you will get the following popup window:
    Attached File  Textmode_Driver_Popup_nLite.jpg (34.99K)
    Number of downloads: 1151
    Both listed "required" NVIDIA products ("NVIDIA RAID CLASS DRIVER" and "NVIDIA nForce Storage Controller") have to be enabled. Usually nLite has already highlighted both of them and set the integration mode to "TEXTMODE" (if not, you should do it manually) > hit "OK"
    Important: Users with an NF3-5 chipset RAID system, who had just integrated the SATARAID folder, may need to additionally integrate the content of the SATA_IDE subfolder of the same driverpack as PnP driver to get the OS properly installed.
    If you have integrated all needed nForce Sata/PataRAID drivers > hit "Next"
  • Let nLite start its processing > hit "Yes"
  • After the successful nLite processing > hit "Next"
  • As last step you will get the "Create Bootable ISO" page. Within the "General" section you can choose the "Mode".
    You have the options "Direct Burn" (burns the image directly onto an empty CD/DVD), "Burn Image" or "Create Image" (default setting).
    If you don't want, that nLite burns the Image itself, you should let nLite create the ISO file by hitting the "Make ISO" button.
    After having chosen the storage place and -if applicable - a special name for the ISO file > hit "Store".
  • At this point nLite has finished its work.

If nLite hasn't already burnt the Image onto a CD, you have to burn the stored ISO file as bootable Image by using a burning tool.
You will get the best results with Nero Burning ROM, when you choose the options "Recorder" (on top task bar) > "Create Image...." > point to the ISO file nLite has created > hit "Burn".
Tip: Burn at no more than 8x(DVD) or 24x(CD) and choose the "Verify" option of Nero to avoid any burning errors!

At the end you will have a bootable 32bit or 64bit Windows OS CD with integrated NVIDIA Sata/PataRaid drivers - no F6 and no floppy will be necessary.


Tips for the Installation of the OS:
  • Make sure that your BIOS settings are ok. You will only be able to install the OS by booting off your nLited CD, when the CD-ROM device with your nLited CD is set as first bootable device.
  • Before you begin with the installation of the OS by using your nLited CD, make sure that there is no floppy within your floppy drive, no USB stick within any USB port and no Memory Card within your Card Reader.
  • If you are using more than 2 GB of RAM, it is a good idea to remove 1-2 sticks during the OS installation (otherwise you may get a lot of errors during the OS Setup). Once the OS is up, they can be reinserted.
  • Don't hit F6 and don't insert a driver floppy if you install an OS by using a CD with integrated nForce SataRaid drivers!
Good luck!



B. Integration of the nForce AHCI drivers
(only valid for AHCI supporting nForce mainboards with enabled AHCI)

Actual nForce chipsets (MCP65 and up) do support the advanced S-ATA-Features (z.B. NCQ) of the AHCI standard. Users of such systems usually have the BIOS option to set the nForce S-ATA Controllers to "AHCI Mode" instead of the "IDE Mode" (which doesn't require any separate textmode drivers). If AHCI is enabled, Windows Setup will not detect the S-ATA hdd('s) unless the needed AHCI drivers will be loaded (F6) or have been integrated into the OS CD.

If you try to get Windows XP or Server 2003 (32/64bit) installed onto a non-RAID nForce chipset system and should realize, that Windows Setup doesn't find any hard drive, the following procedure will be successful for nearly all users:
  • get the actual version of nLite from here and install it (.NET Framework 2.0 required)
  • depending on your nForce chipset and the OS you are going to install, download and unzip one of the following drivers:
  • create a folder named "nLiteCD" or similar and copy the whole content of the OS CD into that folder
  • start nLite > point to the just created "nLiteCD" folder as source
  • choose the tasks "Integrate Drivers" and "Create Bootable ISO"
  • when the "Driver Integration" task comes up > hit "Insert" > choose "Single driver" > point to the prepared SATA_IDE subfolder
  • check any of the shown INF files
  • now you see the following popup window:
    Attached File  nForce_AHCI_driver_popup_with_nLite.jpg (36.02K)
    Number of downloads: 432
    let the "NVIDIA nForce Storage Controller (required)" enabled > hit "OK"
  • let nLite burn the Image directly onto an empty CD/DVD
  • boot of the just created CD > choose the destination partition > do a quick NTFS formatting > install the OS
  • have fun!


C. Most common problems during the OS installation

If you have followed my guide until this point, you can be rather optimistic, that you will get the OS perfectly installed onto your nForce RAID or AHCI system, but the success is not guaranteed.
These are the most common mistakes/errors, which will cause a failure of the OS installation:
  • The prepared CD doesn't boot. ("Hit any key to boot off CD/DVD" message is missing).
    Reason: Either you haven't set the correct boot device order within the BIOS or you didn't burn the ISO file correctly.
    Solution: The CD/DVDROM device has to be set as 1st bootable device and the ISO file has to be burnt as bootable Image (see above).
  • Windows Setup doesn't detect the RAID or the SATA drives, which were set to "AHCI Mode".
    Reason: You obviously didn't integrate the "suitable" textmode drivers or didn't choose the needed Controllers during the integration procedure.
    Solution: Check the exact chipset name of your mainboard, the BIOS settings and the sort of the S-ATA Controllers, where your hdd's are connected (example: you can't get Silicon Image S-ATA Controllers working with nForce drivers and vice versa).
    After having found the "correct" textmode drivers you have to restart the integration procedure from scratch (don't reuse the nLited source again!).
  • You get a message like "The file NVxxx.SYS is corrupt."
    Reason: You obviously mixed the 32/64bit textmode driver version or you didn't use a clean source.
    Solution: Start the nLite processing again from scratch with a clean source and integrate the correct 32/64bit textmode driver version. XP, W2k and W2k3 can only be installed by using 32bit textmode drivers, whereas the 64bit Operating Systems (XP x64/W2k3 x64) need 64bit drivers.
    You get an error message like "Cannot find file NVxxx.SYS".
    Reason: You either didn't integrate the textmode driver or you tried to additionally load it by F6/floppy method.
    Solution: Don't hit F6 when prompted, if you have integrated the textmode driver.
  • The OS installation fails at last reboot with a short BSOD and endless reboots.
    Reason: You either didn't choose the correct driver integration method or your optical drive is connected to a S-ATA port, which is set to RAID or AHCI.
    Solution:Connect the optical drive to a non-RAID/non-AHCI S-ATA port or take an IDE connected CD/DVDROM drive for the OS installation.

Aside from the previously mentioned problems there are some other sources of error:
  • not correctly configurated RAID or wrong BIOS settings regarding RAID/AHCI
  • wrong BIOS settings regarding the "HARD DISK BOOT PRIORITY" (solution: the RAID/AHCI drive has to be set as first bootable hard disk)
  • presence of additional hdd's outside the RAID/AHCI device (solution: disconnect all non-RAID/non-AHCI hdd's during the OS installation)
  • plugged-in USB sticks, floppys, memory cards etc. (solution: unplug them all before you start with the OS installation)
  • faulty RAM sticks, overclocking or > 3 GB of RAM (solution: check the RAM with Memtest, no OC'ing, removal of RAM sticks during the OS installation)
  • hardware malfunction (broken or not really connected S-ATA cables, poor PSU etc.)


D. After the successful OS installation

Once the OS is up, you should install the complete "suitable" nForce chipset driver set. The best suitable driverpack is that one, which contains the same version of nForce IDE drivers as the integrated ones (v6.99, v9.99.09 or 11.1.0.33, if you had followed my advices).
Here are the download links to the related complete nForce chipset driver packs:

a. XP/W2k3 (32bit)
b. XP/W2k3 (64bit)That's all - I hope, that you will succeed with the integration of the drivers and with the installation of the OS onto your nForce RAID or AHCI system.

Good luck!
Fernando


Important notice:
This guide contains a lot of links to drivers, which have been modified by me to make them usable for nForce chipset users. As you certainly understand, I cannot overtake any warranty for the function and the quality of the drivers. You may use them nevertheless, but at own risk.




Annex I

MediaShield/Raidtool installation guide

The easiest way to get the Raidtool installed is by running the SETUP.EXE of the associated nForce chipset driver package, but by doing this all nForce IDE drivers of the package will be installed too (and maybe replace the better and currently working ones).
In these cases you have to use another way to get full access to the MediaShield/RAID software (NVIDIA Control Panel) after having completed the OS installation.
Here is the guide for the manual installation of the nForce Raidtool (on the basis of a post from nForcersHQ forums member TheMaxx32000):
  • Run your just installed OS.
  • Create a new folder named "RAIDTOOL" somewhere within your currently running OS partition (for example within the directory "\Program Files")
  • Search for the RAIDTOOL folder of the actual 32bit/64bit XP/W2k/W2k3 nForce chipset driver package
  • Extract the RAIDTOOL.cab into the just created RAIDTOOL folder of your OS partition
  • Open the RAIDTOOL folder with the extracted files
  • Doubleclick the REGRAID.BAT (you will find it in older Raidtools) or REGRAIDSEDONA.BAT (actual file name of the Sedona type Raidtool) to register the Raidtool Services
  • Run the NVRAIDMAN.EXE (normal MediaShield) or NVCPLUI.EXE (Sedona type NVIDIA Control Panel)
Now you will see the MediaShield Control Panel. It should also appear as NVIDIA Control Panel within the Vista Control Panel, but if it doesn't, try to install nTune on top.
For further information about the abilities of the NVIDIA MediaShield software you should open the MediaShield help file (as .chm or .pdf), which you will find within the extracted raidtool files.
Suggestion: You should create shortcuts to the .EXE files of the RAIDTOOL folder and put them into your Startmenu folder. This way you will get an easy access to all services of the MediaShield/Raidtool.


Annex II

Tips for users with a SATA RAID array outside the OS partition[/u]
Here are some advices for such users:
  • Users with an nForce Sata-RAID array, who are going to install any OS onto an IDE or non-AHCI S-ATA drive, which is outside the RAID, should not integrate any nForce SataRaid drivers. They will be able to get the OS installed without any problems.
  • Once the OS is up, you should run the installer of the suitable nForce chipset driver package. After the reboot, the RAID array normally will be detected by the OS.
  • If the OS should not show the RAID device and their partitions, you should do the following:[list]
  • Open the Device Manager and check, if you see the "NVIDIA nForce RAID Controller" within the "SCSI and RAID Controllers" section. If not, you haven't enabled the NVIDIA RAID Controllers within the BIOS.
  • If you see the "NVIDIA nForce RAID Controller", you have to open the "IDE ATA/ATAPI Controllers" section and look for the "Standard Dual Channel PCI IDE Controllers", where your RAIDed SATA hdd's are connected to.
  • Right click onto these Controllers and do a driver software "update" until you see the compatible devices.
  • Choose the "NVIDIA nForce Serial ATA Controllers", if they are shown as compatible.
  • After the reboot your OS will see and will be able to work with the datas of the RAID array.

Mobile Net Switch

Source
Do you connect to more than one network?
Mobile Net Switch is the network switcher for Windows 7, Vista and XP. It enables you to easily use your computer on more than one network or location.
Mobile Net Switch allows you to automatically switch network related settings on the fly based on location profiles. With the click of a single button you can set Drive mappings, Internet connection settings, Printer settings, IP settings, Wi-Fi settings and much more!
Features
Mobile Net Switch is a network switch utility, also called a netswitcher, multinetwork manager or network connection manager and enables you to create multiple network profiles.
The program has been designed to allow you to switch between several network profiles instantly, without needing to restart your computer. It also incorporates a professional yet easy to use interface and even allows you to enable none-admin users to configure network settings without technical knowledge. It's the best network connection program. Switch network profiles instantly.
Download the fully functional and non-expiring version here

SYSTEM_SERVICE_EXCEPTION error

0x000003b stop error
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+9e
fffff880`0452cfee 41

Usar Test SW
Source
"memory corruption"
So what you can do is try to update or uninstall video and RAID drivers.
Google them to find out what they are and their importance:
Foremost upgrade the video driver
Download memtestx86 and run it for several hours (preferably overnight)
run a system file check to verify and repair your system files
Run execute... or in Vista or Seven type cmd --in search results right click on the application and run as admin
SFC /SCANNOW

If you are overclocking STOP it!
If you have a RAID upgrade the driver
Update your video card driver from NVIDIA's website and chipset drivers from motherboard manufacturer's website.
Also, visit the maker of your ram module's website for the correct Vdimm and timings specific to yours. Then adjust the bios accordingly.
Apparently there seem to be a lot of issues with the i7 and hyperthreading?
Turn it off ;-)) and try
Update the BIOS
Source
I just got a new build running Vista x64, got an eVGA GTX 260 Core 216 with it. But every time I install the video drivers, after restarting, I get a BSOD every time before the logon screen usually appears. The BSOD says "SYSTEM SERVICE EXCEPTION", 0x000003b.
I can restart in safe mode and roll back the drivers so I can login normally. But every time I install an nVidia driver (tried quite a number of different versions, including the one on the CD that the card came with), it BSODs exactly the same way.
I've searched the net quite a bit without finding a solution. It seems only a few people are having the same problem, none of which found a solution. It's a bit hard to search for since the "System Service Exception" error doesn't really point anywhere too specific.
Drivers to be updated

adp94xx.sys  Sat Dec 06 05:24:42 2008 
arc.sys      Fri May 25 02:57:55 2007
iirsp.sys    Wed Dec 14 03:17:54 2005
lsi_fc.sys   Wed Dec 10 04:16:09 2008
nfrd960.sys  Wed Jun 07 02:41:48 2006
SiSRaid2.sys Wed Sep 24 23:58:20 2008

BlueScreenView

View BSOD (blue screen) crash information stored in dump files

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.

Mersenne.org
Any modern personal computer with Windows, Mac OS X, Linux, or FreeBSD can contribute. The How it Works page answers many questions you may have before downloading the software. You must also agree to the GIMPS free software license.
Unix and non-x86 users should check out Ernst Mayer's Mlucas page and the Glucas page for guidance as to which code is best for their platform.
Some software has been written for Nvidia GPUs. Visit the Mersenne GPU Computing Forum for more information.