"//./root/CIMV2" por el error 0x80041003

 "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" en el espacio de nombres "//./root/CIMV2" por el error 0x80041003
http://support.microsoft.com/default.aspx?scid=kb;en-US;2545227

CAUSE: This originated in the Windows 7 SP1 DVD/ISO creation process. There was an issue in the creation process that caused a WMI registration to remain in the DVD/ISO. Since the registration is designed to work only during the DVD/ISO creation process, it fails to run on a live system and causes these events. These events are not indicative of any issue in the system and can be safely ignored. If however you want to prevent these events from getting generated and want to remove this specific WMI registration manually, please follow the steps mentioned in this article for running the workaround script.
Se trata por tanto de un error "rutinario" que se puede ignorar, de todas formas en la página hay una herramienta Fix-It para que no se produzca más.
http://answers.microsoft.com/en-us/protect/forum/mse-protect_start/session-microsoft-security-essentials-oobe-stopped/387c21ed-75db-47e3-9baf-687f6c66f0eb?auth=1
In windows 7:
If you havent already resolved the issue, you will need to navigate to:
C:/program data/microsoft/microsoft security essentials/support/   -   then locate the file: "MSSEOOBE.etl" and simply delete it.
Once you restart the computer, MSE will recreate it, and that should resolve the issue. It worked for me at least.

DD-WRT - reset web GUI password

http://solvecomputerissues.ideacity.ro/2010/05/dd-wrt-reset-web-gui-password-and-also.html

DD-WRT - reset web GUI password and also http username

Suppose you want to change the password for your dd-wrt router. The simple way of doing this is via the web interface (web gui). There you have 3 fields:

• Router username
• Router password
• Re-enter to confirm

If you think that by leaving the username field untouched and only changing the password would leave you with the username (the web gui username) unchanged, you're totally wrong! Doing this also changes the username to a value that seems to be specific to every installation.. not so good, because you will not be able to logon. At least not via the web gui.

What's to be done then?

Well.. if you're lucky enough and have either telnet or ssh enabled on the router, you can get a shell on the router and fix it. See the next steps for how you can do that. If neither telnet nor ssh are enabled, I'm not aware of another way to get into the router without resetting it to defaults.

For login via telnet or ssh you will use 'root' as the username and the new password that you have just changed.

The username used for web gui authentication is kept in nvram under http_username parameter. You can check this by issuing:

nvram show

#nvram get http_username

Now, you can easily reset the username back to admin by issuing:
nvram set http_username $1$5pQBM5KU$L4pN31lcOJls.1.mVIOKb.
The gibberish string above is the equivalent for 'admin'. Make sure you copy the entire string, including the dollar sign from the begining and the dot at the end.

Now you'll be able to login via the web gui with 'admin' as the username and your new password.

And don't forget to also fill-in in the username next time you wish to change only your password on the dd-wrt router :-)

This behaviour is true for Firmware: DD-WRT v24-sp2

----------------
to change the web UI password:
nvram set http_password $1$5pQBM5KU$L4pN31lcOJls.1.mVIOKb.
would reset password to admin.

----------------

For firmware DD-WRT v24-sp2 (08/07/10) mini, the nvram variable is http_passwd. At least it was on my build!

===================
http://www.putty.org/

http://irvingprog.wordpress.com/2010/09/21/conectar-a-servidor-ssh-desde-windows/

===================

http://www.adslzone.net/postt205028.html

Haz un reset posterior al router, lo habitual es que dependiendo de la versión que hayas instalado al escribir 192.168.1.1 el user sea root y al pass: admin pero en las últimas versiones de dd-wrt lo primero que aparece es una ventana para que entres tu password primero (entra el password que quieras, después lo repites y ya entras)

===================

Howto revive a bricked WAP54G
Read the page:
http://www.sorgonet.com/network/wap54gbricked/
Short-circuit the pins shown, and used tftp2.exe .
My advise is to roll-back to the original Linksys firmware for WAP54G, than dd-wrt. But if you also like dd-wrt, you will revive your WAP54G with this tutorial. My information works for any of these firmwares.
If you have problem during tftp the original firmware, like freezing: restart you pc and modem and upload to the modem (via tftp) another file: A photo .jpg around 65kb. The .jpg will erase the nvram.
Restart again the tftp, and this time upload the original firmware.
Sounds strange, but it works!
This is how i revived my WAP54G, after having exactly the same problem

Recuperación de smartphone robado

http://bitelia.com/2013/05/recuperar-tu-telefono-robado?utm_source=dlvr.it&utm_medium=twitter
Los teléfonos inteligentes o smartphones son muy populares, por lo que a su vez se convierten en un bien codiciado por ladrones y demás amigos de lo ajeno. Lo mejor que puedes hacer es tener siempre vigilado tu teléfono iPhone y Android, pero para prevenir futuros robos o pérdidas, te recomendamos que instales una aplicación para recuperar tu teléfono robado. Aprovechando que los celulares inteligentes están siempre conectados a la red, con estas aplicaciones sabrás dónde se encuentran y tal vez incluso podrás pillar in fraganti a quien te lo haya sustraído.

El objetivo de estas aplicaciones es decirte dónde está el teléfono en ese momento. Para ello utiliza el GPS del dispositivo o, en su defecto, la conexión WiFi. No indicará la posición al 100% pero sí se acercará lo suficiente para que la policía se encargue de recuperarlo. Además, algunas de estas apps pueden activar la cámara del teléfono para hacer una foto y así saber quién te lo robó o dónde está. Otra función interesante es la de borrar los datos del dispositivo para evitar que acceda a ellos quien no debe.

Buscar mi iPhone - Find my iPhone (iOS)

Esta aplicación ha sido creada por la propia Apple para sus dispositivos iPhone. Buscar mi iPhone es muy fácil de usar y permite, entre otras cosas, localizar el dispositivo gracias al GPS que integra el teléfono, reproducir un sonido para ahuyentar al ladrón, mostrar un mensaje en pantalla, bloquearlo para que nadie pueda usarlo e incluso borrar los datos para evitar que los vea quien no debe, todo ello directamente desde el navegador web o desde otro dispositivo iOS o Mac usando tu Apple ID.

Prey (iOS y Android)

Esta herramienta es de las más completas que hay para recuperar tu teléfono robado, además de tu ordenador con Windows, Mac o Linux. Prey se instala fácilmente, creas una cuenta de usuario y listo. Tanto en su versión Android como iPhone, te dirá dónde se encuentra, con ayuda del GPS o del WiFi, alertará con un sonido, hará una fotografía para que tengas una prueba contra el ladrón e incluso te dará la opción de borrar los datos del terminal a distancia. Para hacer todo esto tan sólo tendrás que entrar a su página web e iniciar sesión.

Where’s My Droid (Android)

¿Dónde está mi Android? Where’s My Droid te lo dice. Como en los casos mencionados, esta app te avisa de dónde se encuentra el dispositivo, bloquea la posibilidad de instalar o desinstalar aplicaciones y limita el uso del teléfono Android a ciertas persona de una lista concreta.

Lookout (iOS y Android)

Ya hemos hablado de esta aplicación en el pasado. Cuenta con funciones básicas y gratuitas además de otras de pago en la versión Android, que puedes probar durante dos semanas y luego hacerte con ellas por 2.99$ al mes (2,3€). En realidad, Lookout ofrece tres funciones: proteger contra virus, hacer copias de seguridad y, por último, decirte dónde está tu móvil si te lo roban. En concreto, te envía un mensaje de correo electrónico con su posición y una fotografía. Además, Puedes bloquearlo a distancia para que nadie lo pueda utilizar.

Navizon (iOS)

Usando la conexión móvil y el WiFi de tu iPhone, Navizon te indica dónde se encuentra este dispositivo. Su funcionamiento sirve tanto para zonas a cielo abierto como para el interior de edificios, siempre y cuando la zona esté bien conectada a través de redes inalámbricas de comunicación (2G, 3G, WiFi...).

Android Lost (Android)

Con esta aplicación podrás recuperar tu teléfono robado, bloquearlo, borrar el contenido de la tarjeta SD, enviar mensajes SMS y alertas e incluso realizar una fotografía con las cámaras delantera y trasera de tu dispositivo Android. Android Lost incluso graba el sonido que capture el teléfono y permite restaurar la configuración de fábrica al reiniciar. Toda una batería de acciones para que quien te robe no pueda usar tu Android ni acceder a tus datos.
Otro programa interesante para recuperar tu teléfono robado Android o iPhone es TheftSpy, disponible para Android. En cualquier caso, quien debe hacerse cargo de recuperar tu celular es la autoridad competente, pero con estas aplicaciones les podrás ayudar a traerlo de vuelta lo antes posible.

DD-WRT -Scheduled reboot

http://www.dd-wrt.com/wiki/index.php/Scheduled_reboot
Scheduled reboot is often used to give the routers a little clearing now and then to keep its performance at its peak. It can also be used in combination with uPnP with the setting "clear ports at startup" enabled to give the benefits of uPnP without the drawbacks of gaps in your security (for long periods of time anyway).
I find that using a scheduled reboot often gives a brilliant transfer and receive rate for wireless which makes a huge difference when in client mode. The higher to the maximum transfer and receive (whilst assuming no other wireless clients are heavily using it such as downloading) I can receive extremely low ping between my primary router and secondary router - around 1-2 ms average with a distance of around 50 metres set in the ACK timer.
Not working as intended
On DD-WRT v24-sp2 (06/14/11) Build 17201 - I have found that in client mode, scheduled reboot does not work or more so, it only does it for the first time set, despite it being put as "every day." To fix this I used code which a moderator passed onto me and hopefully it works for you too.

1. Go to DD-WRT configuration page
2. Disable scheduled reboot in Administration - Keep Alive
3. Administration - Commands
4. Input

echo "startservice run_rc_shutdown; /sbin/reboot" > /tmp/restart_router
chmod a+x /tmp/restart_router
echo "55 5 * * * root /tmp/restart_router" > /tmp/cron.d/restartrouter

1. Save startup
2. You can edit this at any time
3. I would also recommend giving your router a reboot just to be sure. Administration - Management should be good enough

The above configuration will then restart every day at 5:55am assuming you have set the NTP correctly. You may also find it useful to find out more information on CRON

Editor's note: I have no idea how to fix the numbers whilst giving the code box.

Basic and Dynamic Disks

msdn.microsoft.com/en-us/library/windows/desktop/aa363785%28v
Before partitioning a drive or getting information about the partition layout of a drive, you must first understand the features and limitations of basic and dynamic disk storage types. For the purposes of this topic, the term volume is used to refer to the concept of a disk partition formatted with a valid file system, most commonly NTFS, that is used by the Windows operating system to store files. A volume has a Win32 path name, can be enumerated by the FindFirstVolume and FindNextVolume functions, and usually has a drive letter assigned to it, such as C:. For more information about volumes and file systems, see File Systems.
In this topic:

• Basic Disks
• Dynamic Disks
• Partition Styles
  • Master Boot Record
  • GUID Partition Table
• Detecting the Type of Disk
• Related topics

There are two types of disks when referring to storage types in this context: basic disks and dynamic disks. Note that the storage types discussed here are not the same as physical disks or partition styles, which are related but separate concepts. For example, referring to a basic disk does not imply a particular partition style—the partition style used for the disk under discussion would also need to be specified. For a simplified description of how a basic disk storage type relates to a physical hard disk, see Disk Devices and Partitions.
Basic Disks
Basic disks are the storage types most often used with Windows. The term basic disk refers to a disk that contains partitions, such as primary partitions and logical drives, and these in turn are usually formatted with a file system to become a volume for file storage. Basic disks provide a simple storage solution that can accommodate a useful array of changing storage requirement scenarios. Basic disks also support clustered disks, Institute of Electrical and Electronics Engineers (IEEE) 1394 disks, and universal serial bus (USB) removable drives. For backward compatibility, basic disks usually use the same Master Boot Record (MBR) partition style as the disks used by the Microsoft MS-DOS operating system and all versions of Windows but can also support GUID Partition Table (GPT) partitions on systems that support it. For more information about MBR and GPT partition styles, see the Partition Styles section.
You can add more space to existing primary partitions and logical drives by extending them into adjacent, contiguous unallocated space on the same disk. To extend a basic volume, it must be formatted with the NTFS file system. You can extend a logical drive within contiguous free space in the extended partition that contains it. If you extend a logical drive beyond the free space available in the extended partition, the extended partition grows to contain the logical drive as long as the extended partition is followed by contiguous unallocated space. For more information, see How Basic Disks and Volumes Work.
The following operations can be performed only on basic disks:

• Create and delete primary and extended partitions.
• Create and delete logical drives within an extended partition.
• Format a partition and mark it as active.

Dynamic Disks
Dynamic disks provide features that basic disks do not, such as the ability to create volumes that span multiple disks (spanned and striped volumes) and the ability to create fault-tolerant volumes (mirrored and RAID-5 volumes). Like basic disks, dynamic disks can use the MBR or GPT partition styles on systems that support both. All volumes on dynamic disks are known as dynamic volumes. Dynamic disks offer greater flexibility for volume management because they use a database to track information about dynamic volumes on the disk and about other dynamic disks in the computer. Because each dynamic disk in a computer stores a replica of the dynamic disk database, for example, a corrupted dynamic disk database can repair one dynamic disk by using the database on another dynamic disk. The location of the database is determined by the partition style of the disk. On MBR partitions, the database is contained in the last 1 megabyte (MB) of the disk. On GPT partitions, the database is contained in a 1-MB reserved (hidden) partition.
Dynamic disks are a separate form of volume management that allows volumes to have noncontiguous extents on one or more physical disks. Dynamic disks and volumes rely on the Logical Disk Manager (LDM) and Virtual Disk Service (VDS) and their associated features. These features enable you to perform tasks such as converting basic disks into dynamic disks, and creating fault-tolerant volumes. To encourage the use of dynamic disks, multi-partition volume support was removed from basic disks, and is now exclusively supported on dynamic disks.
The following operations can be performed only on dynamic disks:

• Create and delete simple, spanned, striped, mirrored, and RAID-5 volumes.
• Extend a simple or spanned volume.
• Remove a mirror from a mirrored volume or break the mirrored volume into two volumes.
• Repair mirrored or RAID-5 volumes.
• Reactivate a missing or offline disk.

Another difference between basic and dynamic disks is that dynamic disk volumes can be composed of a set of noncontiguous extents on one or multiple physical disks. By contrast, a volume on a basic disk consists of one set of contiguous extents on a single disk. Because of the location and size of the disk space needed by the LDM database, Windows cannot convert a basic disk to a dynamic disk unless there is at least 1 MB of unused space on the disk.
Regardless of whether the dynamic disks on a system use the MBR or GPT partition style, you can create up to 2,000 dynamic volumes on a system, although the recommended number of dynamic volumes is 32 or less. For details and other considerations about using dynamic disks and volumes, see Dynamic disks and volumes.
For more features of and usage scenarios for dynamic disks, see What Are Dynamic Disks and Volumes?.
The operations common to basic and dynamic disks are the following:

• Support both MBR and GPT partition styles.
• Check disk properties, such as capacity, available free space, and current status.
• View partition properties, such as offset, length, type, and if the partition can be used as the system volume at boot.
• View volume properties, such as size, drive-letter assignment, label, type, Win32 path name, partition type, and file system.
• Establish drive-letter assignments for disk volumes or partitions, and for CD-ROM devices.
• Convert a basic disk to a dynamic disk, or a dynamic disk to a basic disk.

Unless specified otherwise, Windows initially partitions a drive as a basic disk by default. You must explicitly convert a basic disk to a dynamic disk. However, there are disk space considerations that must be accounted for before you attempt to do this. For more information, see How To Convert to Basic and Dynamic Disks in Windows XP Professional.
Partition Styles
Partition styles, also sometimes called partition schemes, is a term that refers to the particular underlying structure of the disk layout and how the partitioning is actually arranged, what the capabilities are, and also what the limitations are. To boot Windows, the BIOS implementations in x86-based and x64-based computers require a basic disk that must contain at least one master boot record (MBR) partition marked as active where information about the Windows operating system (but not necessarily the entire operating system installation) and where information about the partitions on the disk are stored. This information is placed in separate places, and these two places may be located in separate partitions or in a single partition. All other physical disk storage can be set up as various combinations of the two available partition styles, described in the following sections. For more information about other system types, see the TechNet topic on partition styles.
Dynamic disks follow slightly different usage scenarios, as previously outlined, and the way they utilize the two partition styles is affected by that usage. Because dynamic disks are not generally used to contain system boot volumes, this discussion is simplified to exclude special-case scenarios. For more detailed information about partition data block layouts, and basic or dynamic disk usage scenarios related to partition styles, see How Basic Disks and Volumes Work and How Dynamic Disks and Volumes Work.
Master Boot Record
All x86-based and x64-based computers running Windows can use the partition style known as master boot record (MBR). The MBR partition style contains a partition table that describes where the partitions are located on the disk. Because MBR is the only partition style available on x86-based computers prior to Windows Server 2003 with Service Pack 1 (SP1), you do not need to choose this style. It is used automatically.
You can create up to four partitions on a basic disk using the MBR partition scheme: either four primary partitions, or three primary and one extended. The extended partition can contain one or more logical drives. The following figure illustrates an example layout of three primary partitions and one extended partition on a basic disk using MBR. The extended partition contains four extended logical drives within it. The extended partition may or may not be located at the end of the disk, but it is always a single contiguous space for logical drives 1-n.

Each partition, whether primary or extended, can be formatted to be a Windows volume, with a one-to-one correlation of volume-to-partition. In other words, a single partition cannot contain more than a single volume. In this example, there would be a total of seven volumes available to Windows for file storage. An unformatted partition is not available for file storage in Windows.
The dynamic disk MBR layout looks very similar to the basic disk MBR layout, except that only one primary partition is allowed (referred to as the LDM partition), no extended partitioning is allowed, and there is a hidden partition at the end of the disk for the LDM database. For more information on the LDM, see the Dynamic Disks section.
GUID Partition Table
Systems running Windows Server 2003 with SP1 and later can use a partition style known as the globally unique identifier (GUID) partition table (GPT) in addition to the MBR partition style. A basic disk using the GPT partition style can have up to 128 primary partitions, while dynamic disks will have a single LDM partition as with MBR partitioning. Because basic disks using GPT partitioning do not limit you to four partitions, you do not need to create extended partitions or logical drives.
The GPT partition style also has the following properties:

• Allows partitions larger than 2 terabytes.
• Added reliability from replication and cyclic redundancy check (CRC) protection of the partition table.
• Support for additional partition type GUIDs defined by original equipment manufacturers (OEMs), independent software vendors (ISVs), and other operating systems.

The GPT partitioning layout for a basic disk is illustrated in the following figure.

The protective MBR area exists on a GPT partition layout for backward compatibility with disk management utilities that operate on MBR. The GPT header defines the range of logical block addresses that are usable by partition entries. The GPT header also defines its location on the disk, its GUID, and a 32-bit cyclic redundancy check (CRC32) checksum that is used to verify the integrity of the GPT header. Each GUID partition entry begins with a partition type GUID. The 16-byte partition type GUID, which is similar to a System ID in the partition table of an MBR disk, identifies the type of data that the partition contains and identifies how the partition is used, for example if it is a basic disk or a dynamic disk. Note that each GUID partition entry has a backup copy.
Dynamic disk GPT partition layouts looks similar to this basic disk example, but as stated previously have only one LDM partition entry rather than 1-n primary partitions as allowed on basic disks. There is also a hidden LDM database partition with a corresponding GUID partition entry for it. For more information on the LDM, see the Dynamic Disks section.

Detecting the Type of Disk

There is no specific function to programmatically detect the type of disk a particular file or directory is located on. There is an indirect method.
First, call GetVolumePathName. Then, call CreateFile to open the volume using the path. Next, use IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS with the volume handle to obtain the disk number and use the disk number to construct the disk path, such as "\\?\PhysicalDriveX". Finally, use IOCTL_DISK_GET_DRIVE_LAYOUT_EX to obtain the partition list, and check the PartitionType for each entry in the partition list.
Related topics

About Volume Management

Basic Disks and Volumes Technical Reference

Dynamic Disks and Volumes Technical Reference

Basic Storage Versus Dynamic Storage in Windows XP

VPN Client for Windows

https://www.shrew.net/software
https://www.shrew.net/static/help-2.1.x/vpnhelp.htm

1. Introduction
2. Features and Compatibility
3. System Requirements
4. Known Issues
5. IPsec Overview
6. Using the VPN Client

Windows Platforms

---

The Shrew Soft VPN Client for Windows is an IPsec Remote Access VPN Client for Windows 2000, XP, Vista and Windows 7/8 operating systems ( i386 and x64 versions ). It was originally developed to provide secure communications between mobile Windows hosts and open source VPN gateways that utilize standards compliant software such as ipsec-tools, OpenSWAN, FreeSWAN, StrongSWAN, isakmpd. It now offers many of the advanced features only found in expensive commercial software and provides compatibility for VPN appliances produced by vendors such as Cisco, Juniper, Checkpoint, Fortinet, Netgear, Linksys, Zywall and many others.

Product Editions

---

The Shrew Soft VPN Client for Windows is available in two different editions, Standard and Professional. The Standard version provides a robust feature set that allows the user to connect to a wide range of open source and commercial gateways. It contains no trial period limits, nag screens or unrelated software bundles. It is simply free for both personal and commercial use.
https://breakwall.net/2012/10/shrew-soft-vpn-client-reverts-back-to-version-2-1-7/

Samsung Kies

http://www.samsung.com/us/kies/
GT-I5500
http://www.filehorse.com/download-samsung-kies/ (66MB)

Samsung Kies german

Samsung Kies spanish

Samsung Kies portuguese

http://en.kioskea.net/download/download-16195-samsung-kies
Download
Free version (140 MB)

Key Features

• Data backup: this application allows its users to create backup of data. In fact, it is copying data files physically to a removable storage device so that the data can be stored in another location to better protect them and recover them if needed.
• File exchange: by using Samsung Kies, users can exchange some multimedia files between the Windows or Mac PC and a Samsung mobile device. This can be extremely practical if you want to copy some mobile files from your computer.
• Synchronization: it syncs contacts with those of Google, Yahoo or Outlook. For that, you can create your own favorite music playlist and Sync them with your mobile. Apart from that, Samsung Kies also lets you synchronize photos, music and videos. There is a link to the Samsung Apps store where you will discover numbers of tools for your mobile.
• Update notification: when connected, the application notifies its users automatically of new firmware version. You can improve your version with a newer one easily.
• Multimedia management: also having a feature of multimedia management, its users can display images as thumbnails, playback of audio files, manage photo albums, visualize video, creating slide shows, etc.

all about videos with subtitles

http://www.jaybob.org/jaybob_02_2010_002.htm
How to watch movies with subtitles
mini how-to guide:
1. watch this video:

2. download GOOD video player:

• Open Subtitles MKV Player (download exact subtitles on request – the most easy way)
• Kantaris Media Player (Tip: Kantaris Media Player)
• ALLPlayer (Introducing All Player)
• MPC – Media Player Classic (Download it) – Download subtitles using MPC – guide
• VLC – VideoLAN (Download it)
• GOM Player (Download it)
• KM Player (Download it)
• MPlayer (Download it)
• SMPlayer (Download it)
• BS PLayer (Download it)
• Zoom Player (Download it)
• Video players list – pick up your favourite

And that’s all. As you can see, it is really easy, everything you have to do is rename subtitle file according movie file. So if you have “movie.avi” your subtitles must be located in same directory and renamed to “movie.srt”. Now open movie in your favourite video player and enjoy!
Tip: if you like to watch movie with 2 subtitles (switch them in video player), let’s say english and dutch, you just have to rename subtitle files like:

• movie.en.srt
• movie.nl.srt

Of course there exists millions ways how to watch subtitles, but this how-to is for begginers.
UPDATE: Many users are asking how they can add subtitles to DVD and watch in standalone DVD player – here is the link for the best software -  in this area (I am not only promoting something what I didn’t try, I was absolutely happy with this software) – try it here. They support every common format of subtitles, and also sub/idx files…Here is really nice guide for beginners.
 http://www.subtitleseeker.com/
http://subscene.com/subtitles/
opensubtitles.org
http://forum.gleitz.info/showthread.php?25804-AVI-mit-SRT-brennen
VobSub 2.23 besteht aus mehreren Teilen:
a) Der VobSub-Untertitel-Ripper, der aus DVDs die Untertitel herausholt und im VobSub-Format (*.sub+*.idx) auf Platte schreibt. Da du eine *.srt-Datei hast, ist der für dich hier nicht wichtig...

b) Ein Filter für VirtualDub und AviSynth, der Untertitel zum Weiterbearbeiten in das Video einblenden kann, wenn es über die VfW-Schnittstelle geöffnet wird. Für dich zum Abspielen weniger interessant...
c) Der DirectShow-Filter "DirectVobSub", der Untertitel in Videos einblendet, wenn sie in einem (mehr oder weniger beliebigen) Media-Player abgespielt werden. Der ist für dich interessant, wenn du den MS-WMP verwendest: Du musst nur bei "Start > Programme > VobSub > DirectVobSub Configure" entweder bei "Main" die srt-Datei direkt lädst, oder bei "Paths" eventuell das Verzeichnis hinzufügst, wo die *.srt-Datei drin liegt.
Aber anstatt des DirectVobSub-Filters kann man auch Media-Player verwenden, die selber Untertitel laden können, und dafür keine DirectShow-Filter benötigen. Zum Beispiel: BSplayer, Media Player Classic, VideoLan Client, ... - nur nicht der MS-WMP. Korrekt konfigurieren muss man die allerdings auch erst mal, und wenn's nur das Häkchen ist, dass er überhaupt Untertitel anzeigen soll, wenn er welche findet...
Eine der wichtigsten Voraussetzungen dafür, dass der Filter oder Player erkennt, dass die Untertitel zum Film gehören, ist jedoch, dass beide den gleichen Dateinamen haben. Beispiel:
Toller_Film.avi
Toller_Film.german.srt
Toller_Film.english.srt
http://www.urusoft.net/products.php?cat=sw&lang=1
Subtitle Workshop is the most complete, efficient and convenient freeware subtitle editing tool. It supports all the subtitle formats you need and has all the features you would want from a subtitle editing program. Subtitle Workshop makes subtitle creating/editing/converting tasks almost a pleasure, the amicable and intuitive interface mixes easy to access menus & must have features with advanced functions and a remarkable speed and stability, drastically reducing subtitle editing time. It includes spell check function and an advanced video preview feature which will ease the task even more. The best choice for the beginner, expert or the fansubber. Have a try, and you'll forget the rest!
==================
 http://forum.gleitz.info/showthread.php?26035-Untertitel-in-Avi-einbinden
SRT in eine AVI einbinden.
STEP.BY.STEP
----------------
Du musst nur bei "Start > Programme > VobSub > DirectVobSub Configure" entweder bei "Main" die srt-Datei direkt lädst, oder bei "Paths" eventuell das Verzeichnis hinzufügst, wo die *.srt-Datei drin liegt.
-----------------
Du brauchst folgende Software:
AviSynth 2.5.6
VSFilter
Jetzt erstellst du eine Textdatei mit folgendem Inhalt:

Code:

 LoadPlugin("absoluter Pfad zur Datei\VSFilter.dll")
AVISource("absoluter Pfad zur Datei\film.avi")
TextSub("absoluter Pfad zur Datei\subtitle.srt")

und speicherst sie als blabla.avs ab.
Diese AVS-Datei kannst du jetzt z.B. mit TMPEGEnc öffnen und encoden. Du musst sie vorher natürlich anpassen (Pfade).
Eventuell musst du noch resizen und schwarze Ränder hinzufügen, aber das sind mpeg1/2-spezifische Probleme, dazu findest du bestimmt genug im Forum. Auf jeden Fall kannst du resizen (z.B. lanczosresize()) und Ränder hinzufügen (AddBorders()) alles mit AviSynth machen. Falls du nicht verstehst was AviSynth macht, lies mal das hier.

Epson Printer Hacks

http://www.ssclg.com/epsone.shtml
Supported printer models >>>

An I/O operation initiated by the Registry failed unrecoverably.

The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.
http://windowsitpro.com/windows-server/troubleshooting-infamous-event-id-333-errors
==================================
Troubleshooting the Infamous Event ID 333 Errors
Executive Summary:
Event ID 333 errors are some of the most difficult Windows System event log errors to troubleshoot. Learn how to diagnose and resolve event ID 333 errors more quickly, using Microsoft’s Performance Monitor, poolmon.exe, and dureg.exe tools and troubleshooting tips from a Microsoft support professional
Event ID 333 Symptoms
Event ID 333’s description is An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, write out, or flush, one of the files that contain the system’s image of the Registry. This means that the image of the registry held in memory could not be written to disk. Windows uses what’s called the lazy writer to periodically write modified pages of memory to disk. When the lazy writer fails, an event ID 333 is recorded in the System event log.
The symptoms that might accompany the event ID 333 errors include these:

• Server hangs: Your server may completely stop responding to keyboard or mouse movements and appears completely locked up, requiring a hard reboot.
• Server sluggishness: The server is extremely slow to respond at the console, and processing information is significantly delayed.
• Delayed Terminal Services connections: Users trying to log on to a terminal server could experience slow or delayed logons. Once they log on, they may be able to work without a slow experience; however, the logon takes several minutes instead of a few seconds.

Generally, event ID 333 can be classified into three categories:

• Memory resource depletion: At the time the lazy writer attempted to write the modified pages in cache to disk, there weren’t enough resources to complete the operation. Often this type of problem is accompanied by either an event ID 2020 or 2019.
• Disk was too busy or inaccessible: Sometimes a busy disk might not respond quickly enough to handle the lazy writer’s request to commit modified pages of memory to disk.
• Registry bloat: The registry suddenly grows in size, which makes it increasingly difficult for the lazy writer to commit the changes to disk, commonly occurring on terminal servers.

Especially frustrating is how the events continue to flood the System event log (many times per minute) until the server is rebooted. All it takes is one time for the lazy writer to fail for the event flooding to begin. Although the condition that caused the lazy writer to fail might have been brief (such as a short spike in memory usage), event ID 333 continues to be logged even during normal memory utilization. The event is still logged because the system recognizes that a failure to sync the registry has occurred and the registry version contained in memory is out of sync with the version on disk. As a result, the number and frequency of event ID 333 messages isn’t a good indicator of the problem’s severity. By default the lazy writer tries to flush to disk every five seconds.
Event ID 333 Troubleshooting Tools
When troubleshooting event ID 333 errors, first you must determine which general category the error falls into. Also it’s useful to check the System event log for any other event IDs that accompany the 333 error, such as event ID 2020, which indicates a lack of paged pool memory, or event ID 2019, which indicates a leak in nonpaged pool memory.
These tools can assist in further diagnosing event ID 333 messages:

• Performance Monitor: The counters to track are the system, memory, disk, and process objects.
  • Memory object: Look for a rise in nonpaged or paged memory.
  • Process object: Look for continuous rises in a process’s handles just prior to the event ID 333’s being logged.
  • System object: The %Registry Quota In Use counter can be useful in displaying how much of the allowed registry quota is being utilized. The higher the percentage, the more likely that the problem is related to a growing registry.
  • Physical disk: Look for increases in the Avg Disk Queue Length counter, which tracks the average number of read and write requests to the selected disk. If this counter spikes during the problem, start investigating the filter drivers (i.e., antivirus or backup software) on your system.
• Poolmon.exe: This tool, which is included in the Windows Debugging Tools, is used to track kernel pool memory usage by pool-allocation tag name. Using poolmon.exe can halve your troubleshooting time by enabling you to find the tag that’s leaking memory.
• Dureg.exe: This tool lets you view the size of the entire registry per hive. Dureg.exe is great for finding which registry hive is consuming the most space, which helps to determine what software might be causing the problem.

Case 1: Finding a Memory-Leaking Driver
I recently worked on an issue where the customer’s Windows 2003 SP2 server completely hung. Accompanying the event ID 333 was also event 2019, The server was unable to allocate from the system nonpaged pool because the pool was empty. The addition of the 2019 error told me that this was a resource-depletion issue, so the next step was to determine which driver was leaking. As Figure 1 shows, the output that poolmon.exe captured helped to pinpoint which tag allocated the highest amount of memory.
Figure 1: Poolmon.exe output indicating a leaking tag

To help in quickly identifying the leaky tag, use the -b switch, which will sort the output based on byte usage for each tag. The tag at the top of the output is the tag that has consumed the most amount of memory (in bytes).
Our next step was to use the built-in Windows Findstr utility to find the driver associated with the NTID tag, by running this command:
C:\>findstr /m /s "NTID" *.sys The /m switch tells Findstr to list only the filename in the output, and the /s switch searches in only the current folder and its subfolders. The Findstr output yielded the driver C:\WINDOWS\SYSTEM32\DRIVERS\CPQTEAM.SYS.
Armed with the pool-allocation tag and name of the driver leaking memory, our final step was to do a simple search on "NTID CPQTEAM". In the search results, we found a link to HP's tech forum that discussed a memory leak associated with a specific version of the Cpqteam.sys driver.
Case 2: Tracking Heavy Registry Usage
Not all event ID 333 errors are a result of a resource problem, however. It’s possible to have event ID 333 errors and be unable to correlate them with any resource depletion. One such issue I worked on occurred on a Terminal Services server on which event ID 333 was flooding the System event log. Using Performance Monitor, we noticed that the counter %Registry Quota In Use was greater than 98 (i.e., the system was using more than 98 percent of the allowed system quota for registry size). Knowing that the system was heavily utilizing the registry, we took another look at the Application event log entries during the problem period and found an event ID 1517, which Figure 2 shows.
Figure 2: Event ID 1517

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: ComputerName
Description:
Windows saved user User_Name registry while an application
or service was still using the registry during log off. The memory
used by the user’s registry has not been freed. The registry will
be unloaded when it is no longer in use.

Event 1517 indicates that the registry isn’t being freed when users log off. Our Performance Monitor counter %Registry Quota in Use correlates this information. We searched Microsoft Help and Support for “1517” and “registry” and found an article at support.microsoft.com/kb/944984 that fixed our problem.
Dureg.exe is another utility that’s becoming increasingly popular to use for troubleshooting event ID 333 errors. Dureg.exe output needs to be collected once before users experience a problem and again during the problem period to determine whether the registry is becoming bloated. The first run of dureg.exe (before the problem) would look like this:

C:\>dureg.exe /a
Size of HKEY_CLASSES_ROOT : 11627272
Size of HKEY_USERS : 56739224
Size of HKEY_LOCAL_MACHINE : 47719408
Total Registry data size: 115985904

The second time you’d run dureg.exe would be when the slow logon and event ID 333 problems are occurring, like this:

C:\>dureg.exe /a
Size of HKEY_CLASSES_ROOT : 11879338
Size of HKEY_USERS : 335257592
Size of HKEY_LOCAL_MACHINE : 46006166
Total Registry data size: 392142994

Notice the large change in the HKEY_USERS key, from 56MB to 334MB. Although this size discrepancy doesn’t necessarily resolve the problem, the information provides a valuable starting point for tech support that can drastically reduce the time needed to resolve the problem.
For this particular example, you’d want to run regedit and navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software. Then look for duplicate registry keys associated a particular application because the values of this key are copied to a user’s profile (HKEY_USERS) when the user logs on to a terminal server. An application might be flooding the Software key with values that end up bloating the registry and causing the Event ID 333 errors. Merely deleting any duplicate values under the HKEY_USERS key would be inadequate because the next time the user logged on, all those duplicate keys would be copied from the Software key to the HKEY_USERS key, and the problem would continue.
Faster Problem-Solving
Although troubleshooting Event ID 333 errors can be tricky, you’ve now learned ways to make the process easier. With help from Performance Monitor, poolmon.exe, and dureg.exe, you can more easily spot causes of Event ID 333 problems and use that information to resolve such problems faster.
See also, "Collecting and Analyzing Event and System Logs."
====================================
http://blogs.technet.com/b/yongrhee/archive/2009/10/14/how-to-troubleshoot-event-id-333-in-windows-server-2003.aspx
how to troubleshoot “Event ID 333” on Windows Server 2003.
My team has written a blog regarding this issue:
Troubleshooting Event ID 333 Errors
http://blogs.technet.com/askperf/archive/2007/10/30/troubleshooting-event-id-333-errors.aspx
and
Michael Morales has written a nice article for Windows IT Pro about this issue.
Troubleshooting the Infamous Event ID 333 Errors
http://windowsitpro.com/Articles/ArticleID/101059/pg/1/1.html
SYMPTOMS
Event Type: Error
Event Source: Application Popup
Event Category: None
Event ID: 333
Computer: computer name
Description: An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.
Troubleshooting:
------------------
I wanted to bring to you this new item to your arsenal of tools to get to the bottom of this issue.
1)  You want to make sure to have the following kernel hotfix or a newer version is installed:
970054 Many events with ID 333 are added to the System log on a Windows Server 2003-based computer
http://support.microsoft.com/kb/970054
Updates Ntoskrnl.exe 5.2.3790.4497
2)  You want to setup the tools for gathering data for memory issues as described in:
http://blogs.technet.com/yongrhee/archive/2009/10/14/how-to-troubleshoot-the-use-of-paged-pool-kernel-memory-event-id-2020-in-windows-server-2003.aspx

=========================================
http://serverfault.com/questions/56121/an-i-o-operation-initiated-by-the-registry-failed-unrecoverably

I added the column "handles count" to the processes view. One process permanently keeps creating handles (SNMP). Performance Wizard shows, SNMP had over 2 Million handles before our last server crash.

It's definitely a handle leak. The eventlog entry is merely the result of system resource depletion. The question is which process is leaking handles? I recommend using perfmon to trace various system wide resources counters, so when the system crashed again, you've enough data to find out the root cause.
The following counters maybe helpful: Object, Memory, Process\Snmp
BTW: in your case, the culprit is obviously the snmp process

==================================

Windows cannot impersonate the user

(Insufficient system resources exist to complete the requested service. ) 
server become inaccessible (no access to shares, Home Server Console, or RDP), although I could still ping the machine.
http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/1961f079-2092-4ccb-9e70-8d8fb22f8393
1.Click Start, click Run, type regedit, and then click OK.
.Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
3.On the Edit menu, point to New, and then click DWORD Value.
4.In the New Value #1 box, type PoolUsageMaximum, and then press ENTER.
5.Right-click PoolUsageMaximum, and then click Modify.
6.In the Value data box, type 60, click Decimal, and then click OK.
7.If the PagedPoolSize registry entry exists, go to step 8. If the PagedPoolSize registry entry does not exist, create it.
To do this, follow these steps:
•On the Edit menu, point to New, and then click DWORD Value.
•In the New Value #1 box, type PagedPoolSize, and then press ENTER.
8.Right-click PagedPoolSize, and then click Modify.
9.In the Value data box, type ffffffff, and then click OK.
10.Exit Registry Editor, and then restart the computer.

fakeRAID linux

https://wiki.archlinux.org/index.php/Installing_with_Fake_RAID
The purpose of this guide is to enable use of a RAID set created by the on-board BIOS RAID controller and thereby allow dual-booting of Linux and Windows from partitions inside the RAID set using GRUB. When using so-called "fake RAID" or "host RAID", the disc sets are reached from

1 What is "fake RAID" 2 History 3 Supported hardware 4 Backup 5 Outline 6 Preparation 6.1 Configure RAID sets 7 Boot the installer 8 Load dmraid 9 Perform traditional installation 9.1 Partition the RAID set 9.2 Mounting the filesystem 9.3 Install and configure Arch 10 install bootloader 10.1 Use GRUB2 10.2 Use GRUB Legacy (Deprecated) 11 Troubleshooting 11.1 Booting with degraded array 11.2 Error: Unable to determine major/minor number of root device 11.3 dmraid mirror fails to activate

What is "fake RAID"
From Wikipedia:

Operating system-based RAID doesn't always protect the boot process and is generally impractical on desktop versions of Windows. Hardware RAID controllers are expensive and proprietary. To fill this gap, cheap "RAID controllers" were introduced that do not contain a RAID controller chip, but simply a standard disk controller chip with special firmware and drivers. During early stage boot-up, the RAID is implemented by the firmware. When a protected-mode operating system kernel such as Linux or a modern version of Microsoft Windows is loaded, the drivers take over.

These controllers are described by their manufacturers as RAID controllers, and it is rarely made clear to purchasers that the burden of RAID processing is borne by the host computer's central processing unit -- not the RAID controller itself -- thus introducing the aforementioned CPU overhead which hardware controllers do not suffer from. Firmware controllers often can only use certain types of hard drives in their RAID arrays (e.g. SATA for Intel Matrix RAID, as there is neither SCSI nor PATA support in modern Intel ICH southbridges; however, motherboard makers implement RAID controllers outside of the southbridge on some motherboards). Before their introduction, a "RAID controller" implied that the controller did the processing, and the new type has become known in technically knowledgeable circles as "fake RAID" even though the RAID itself is implemented correctly. Adaptec calls them "host RAID".wikipedia:RAID

See Wikipedia:RAID or FakeRaidHowto @ Community Ubuntu Documentation for more information.
Despite the terminology, "fake RAID" via dmraid is a robust software RAID implementation that offers a solid system to mirror or stripe data across multiple disks with negligible overhead for any modern system. dmraid is comparable to mdraid (pure Linux software RAID) with the added benefit of being able to completely rebuild a drive after a failure before the system is ever booted.
History
In Linux 2.4, the ATARAID kernel framework provided support for fake RAID (software RAID assisted by the BIOS). For Linux 2.6 the device-mapper framework can, among other nice things like LVM and EVMS, do the same kind of work as ATARAID in 2.4. Whilst the new code handling the RAID I/O still runs in the kernel, device-mapper is generally configured by a userspace application. It was clear that when using the device-mapper for RAID, detection would go to userspace.
Heinz Maulshagen created the dmraid tool to detect RAID sets and create mappings for them. The controllers supported are (mostly cheap) fake RAID IDE/SATA controllers which contain BIOS functions. Common examples include: Promise FastTrak controllers; HighPoint HPT37x; Intel Matrix RAID; Silicon Image Medley; and NVIDIA nForce.
Information on supported hardware
RAID/Onboard @ Gentoo Linux Wiki

Backup

Warning: Backup all data before playing with RAID. What you do with your hardware is only your own fault. Data on RAID stripes is highly vulnerable to disc failures. Create regular backups or consider using mirror sets. Consider yourself warned!

Outline

• Preparation
• Boot the installer
• Load dmraid
• Perform traditional installation
• Install GRUB

Preparation

• Open up any needed guides (e.g. Beginners' Guide, Official Arch Linux Install Guide) on another machine. If you do not have access to another machine, print it out.
• Download the latest Arch Linux install image.
• Backup all important files since everything on the target partitions will be destroyed.

Configure RAID sets

Warning: If your drives are not already configured as RAID and Windows is already installed, switching to "RAID" may cause Windows to BSOD during boot.[1]

• Enter your BIOS setup and enable the RAID controller.
  • The BIOS may contain an option to configure SATA drives as "IDE", "AHCI", or "RAID"; ensure "RAID" is selected.
• Save and exit the BIOS setup. During boot, enter the RAID setup utility.
  • The RAID utility is usually either accessible via the boot menu (often F8, F10 or CTRL+I) or whilst the RAID controller is initializing.
• Use the RAID setup utility to create preferred stripe/mirror sets.

Tip: See your motherboard documentation for details. The exact procedure may vary.

Boot the installer

See Official Arch Linux Install Guide#Pre-Installation for details.

Load dmraid

Load device-mapper and find RAID sets:

# modprobe dm_mod
# dmraid -ay
# ls -la /dev/mapper/

Warning: Command "dmraid -ay" could fail after boot to Arch linux Release: 2011.08.19 as image file with initial ramdisk environment does not support dmraid. You could use an older Release: 2010.05. Note that you must correct your kernel name and initrd name in grubs menu.lst after installing as these releases use different naming

Example output:

/dev/mapper/control            

- data-blogger-escaped-a="" data-blogger-escaped-by="" data-blogger-escaped-controller="" data-blogger-escaped-created="" data-blogger-escaped-dev="" data-blogger-escaped-device-mapper="" data-blogger-escaped-first="" data-blogger-escaped-functioning="" data-blogger-escaped-if="" data-blogger-escaped-image="" data-blogger-escaped-is="" data-blogger-escaped-likely="" data-blogger-escaped-mapper="" data-blogger-escaped-on="" data-blogger-escaped-partition="" data-blogger-escaped-pre="" data-blogger-escaped-present="" data-blogger-escaped-raid="" data-blogger-escaped-sata="" data-blogger-escaped-set="" data-blogger-escaped-sil_aiageicechah1="" data-blogger-escaped-sil_aiageicechah="" data-blogger-escaped-silicon="" data-blogger-escaped-this=""
If there is only one file (/dev/mapper/control), check if your controller chipset module is loaded with lsmod.
 If it is, then dmraid does not support this controller or there are no RAID sets on the system (check RAID BIOS setup again). If correct, then you may be forced to use software RAID (this means no dual-booted RAID system on this controller).
If your chipset module is NOT loaded, load it now. For example:
# modprobe sata_sil

See /lib/modules/`uname -r`/kernel/drivers/ata/ for available drivers.
To test the RAID sets:
# dmraid -tay


 Perform traditional installation 
Switch to tty2 and start the installer:
# /arch/setup


 Partition the RAID set 

Under Prepare Hard Drive choose Manually partition hard drives since the Auto-prepare option will not find your RAID sets.
Choose OTHER and type in your RAID set's full path (e.g. /dev/mapper/sil_aiageicechah). Switch back to tty1 to check your spelling.
Create the proper partitions the normal way.


 Tip: This
 would be a good time to install the "other" OS if planning to 
dual-boot. If installing Windows XP to "C:" then all partitions before 
the Windows partition should be changed to type [1B] (hidden FAT32) to 
hide them during the Windows installation. When this is done, change 
them back to type [83] (Linux). Of course, a reboot unfortunately 
requires some of the above steps to be repeated.

  Mounting the filesystem 
If -- and this is probably the case -- you do not find your newly created partitions under Manually configure block devices, filesystems and mountpoints:

Switch back to tty1.


Deactivate all device-mapper nodes:


# dmsetup remove_all

Reactivate the newly-created RAID nodes:

# dmraid -ay
# ls -la /dev/mapper

Switch to tty2, re-enter the Manually configure block devices, filesystems and mountpoints menu and the partitions should be available.


 Warning: NEVER delete a partition in cfdisk to create 2 partitions with dmraid after Manually configure block devices, filesystems and mountpoints have been set.

(really screws with dmraid metadata and existing partitions are worthless)

Solution: delete the array from the bios and re-create to force creation under a new /dev/mapper ID, reinstall/repartition.

  Install and configure Arch 

 Tip: Utilize
 three consoles: the setup GUI to configure the system, a chroot to 
install GRUB, and finally a cfdisk reference since RAID sets have weird 
names.


 tty1: chroot and grub-install
 tty2: /arch/setup

 tty3: cfdisk for a reference in spelling, partition table and geometry of the RAID set

Leave programs running and switch to when needed.
Re-activate the installer (tty2) and proceed as normal with the following exceptions:

Select Packages
Ensure dmraid is marked for installation
Configure System



Add dm_mod to the MODULES line in mkinitcpio.conf. If using a mirrored (RAID 1) array, additionally add dm_mirror

Add chipset_module_driver to the MODULES line if necessary

Add dmraid to the HOOKS line in mkinitcpio.conf; preferably after sata but before filesystem




  install bootloader 

  Use GRUB2 
Please read GRUB2 for more information about configuring GRUB2. Currently, the latest version of grub-bios does not compatiable with fake-raid. If you got an error like this when you run grub-install:
 $ grub-install /dev/mapper/sil_aiageicechah
 Path `/boot/grub` is not readable by GRUB on boot. Installation is impossible. Aborting.

You could try an old version of grub. You could find old version package of grub at ARM Search. Read Downgrade for more information.
1. download an old version package for grub
  i686:
   http://arm.konnichi.com/extra/os/i686/grub2-bios-1:1.99-6-i686.pkg.tar.xz
   http://arm.konnichi.com/extra/os/i686/grub2-common-1:1.99-6-i686.pkg.tar.xz
  x86_64:
   http://arm.konnichi.com/extra/os/x86_64/grub2-bios-1:1.99-6-x86_64.pkg.tar.xz
   http://arm.konnichi.com/extra/os/x86_64/grub2-common-1:1.99-6-x86_64.pkg.tar.xz
  You could verify these packages by the .sig file if you take care.
2. install these old version packages by using "pacman -U *.pkg.tar.xz"
3. (Optional) Install os-prober if you have other OS like windows.
4. $ grub-install /dev/mapper/sil_aiageicechah
5. $ grub-mkconfig -o /boot/grub/grub.cfg
6. (Optional) put grub2-bios, grub2-common in /etc/pacman.conf's IgnorePkg array, if you don't want pacman upgrade it.
That's all, grub-mkconfig will generate the configure 
automatically. You could edit /etc/default/grub to modify the configure 
(timeout, color, etc) before grub-mkconfig.

  Use GRUB Legacy (Deprecated) 

 Warning: You can normally specify default saved instead of a number in menu.lst so that the default entry is the entry saved with the command savedefault. If you are using dmraid do not use savedefault or your array will de-sync and will not let you boot your system.
Please read GRUB Legacy for more information about configuring GRUB Legacy. 

 Note: For an unknown reason, the default menu.lst will likely be incorrectly populated when installing via fake RAID. Double-check the root lines (e.g. root (hd0,0)).
Additionally, if you did not create a separate /boot partition, ensure the kernel/initrd paths are correct (e.g. /boot/vmlinuz-linux and /boot/initramfs-linux.img instead of /vmlinuz-linux and /initramfs-linux.img.
For example, if you created logical partitions (creating the equivalent of sda5, sda6, sda7, etc.) that were mapped as:
  /dev/mapper     |    Linux    GRUB Partition
                  |  Partition      Number
nvidia_fffadgic   |
nvidia_fffadgic5  |    /              4
nvidia_fffadgic6  |    /boot          5
nvidia_fffadgic7  |    /home          6

The correct root designation would be (hd0,5) in this example.

 Note: If
 you use more than one set of dmraid arrays or multiple Linux 
distributions installed on different dmraid arrays (for example 2 disks 
in nvidia_fdaacfde and 2 disks in nvidia_fffadgic and you are installing
 to the second dmraid array (nvidia_fffadgic)), you will need designate 
the second array's /boot
 partition as the GRUB root. In the example above, if nvidia_fffadgic 
was the second dmraid array you were installing to, your root 
designation would be root (hd1,5).
After saving the configuration file, the GRUB installer will FAIL. However it will still copy files to /boot. DO NOT GIVE UP AND REBOOT -- just follow the directions below:

Switch to tty1 and chroot into our installed system:

# mount -o bind /dev /mnt/dev
# mount -t proc none /mnt/proc
# mount -t sysfs none /mnt/sys
# chroot /mnt /bin/bash

Switch to tty3 and look up the geometry of the RAID set. 
In order for cfdisk to find the array and provide the proper C H S 
information, you may need to start cfdisk providing your raid set as the
 first argument. (i.e. cfdisk /dev/mapper/nvidia_fffadgic):

The number of Cylinders, Heads and Sectors on the RAID set should be written at the top of the screen inside cfdisk. Note: cfdisk shows the information in H S C order, but grub requires you to enter the geometry information in C H S order.



Example: 18079 255 63 for a RAID stripe of two 74GB Raptor discs.
Example: 38914 255 63 for a RAID stripe of two 160GB laptop discs.


GRUB will fail to properly read the drives; the geometry command must be used to manually direct GRUB:

Switch to tty1, the chrooted environment.

Install GRUB on /dev/mapper/raidSet:



# dmsetup mknodes
# grub --device-map=/dev/null
grub> device (hd0) /dev/mapper/raidSet
grub> geometry (hd0) C H S

Exchange C H S above with the proper numbers (be aware: they are not entered in the same order as they are read from cfdisk).
If geometry is entered properly, GRUB will list partitions found on this RAID set. You can confirm that grub is using the correct geometry and verify the proper grub root device to boot from by using the grub find command. If you have created a separate boot partition, then search for /grub/stage1 with find. If you have no separate boot partition, then search /boot/grub/stage1 with find. Examples:
grub> find /grub/stage1       # use when you have a separate boot partition
grub> find /boot/grub/stage1  # use when you have no separate boot partition

Grub will report the proper device to designate as the grub root 
below (i.e.  (hd0,0), (hd0,4), etc...) Then, continue to install the bootloader into the Master Boot Record, changing "hd0" to "hd1" if required.
grub> root (hd0,0)
grub> setup (hd0)
grub> quit


 Note: With dmraid >= 1.0.0.rc15-8, partitions are labeled "raidSetp1, raidSetp2, etc. instead of raidSet1, raidSet2, etc. If the setup command fails with "error 22: No such partition", temporary symlinks must be created.[2]
The problem is that GRUB still uses an older detection algorithm, and is looking for /dev/mapper/raidSet1 instead of /dev/mapper/raidSetp1.


The solution is to create a symlink from /dev/mapper/raidSetp1 to /dev/mapper/raidSet1 (changing the partition number as needed). The simplest way to accomplish this is to:
# cd /dev/mapper
# for i in raidSetp*; do ln -s $i ${i/p/}; done

Lastly, if you have multiple dmraid devices with multiple sets of arrays set up (say: nvidia_fdaacfde and nvidia_fffadgic), then create the /boot/grub/device.map file to help GRUB retain its sanity when working with the arrays. All the file does is map the dmraid device to a traditional hd#. Using these dmraid devices, your device.map file will look like this:
(hd0) /dev/mapper/nvidia_fdaacfde
(hd1) /dev/mapper/nvidia_fffadgic

And now you are finished with the installation!
# reboot


  Troubleshooting 

Booting with degraded array 
One drawback of the fake RAID approach on GNU/Linux is that dmraid is
 currently unable to handle degraded arrays, and will refuse to 
activate. In this scenario, one must resolve the problem from within 
another OS (e.g. Windows) or via the BIOS/chipset RAID utility. 


Alternatively, if using a mirrored (RAID 1) array, users may 
temporarily bypass dmraid during the boot process and boot from a single
 drive:

 Edit the kernel line from the GRUB menu

Remove references to dmraid devices (e.g. change /dev/mapper/raidSet1 to /dev/sda1)
Append disablehooks=dmraid to prevent a kernel panic when dmraid discovers the degraded array


 Boot the system



Error: Unable to determine major/minor number of root device 
If you experience a boot failure after kernel update where the boot process is unable to determine major/minor number of root device, this might just be a timing problem (i.e. dmraid -ay might be called before /dev/sd* is fully set up and detected). This can effect both the normal and LTS kernel images. Booting the 'Fallback' kernel image should work. 
The error will look something like this:
Activating dmraid arrays...
no block devices found
Waiting 10 seconds for device /dev/mapper/nvidia_baaccajap5
Root device '/dev/mapper/nvidia_baaccajap5' doesn't exist attempting to create it.
Error: Unable to determine major/minor number of root device '/dev/mapper/nvidia_baaccajap5'

To work around this problem:

 boot the Fallback kernel

 insert the 'sleep' hook in the HOOKS line of /etc/mkinitcpio.conf after the 'udev' hook like this:



HOOKS="base udev sleep autodetect pata scsi sata dmraid filesystems"


 rebuild the kernel image and reboot




  dmraid mirror fails to activate 
Does everything above work correctly the first time, but then when you reboot dmraid cannot find the array?
This is because Linux software raid (mdadm) has already attempted to mount the fakeraid array during system init and left it in an umountable state. To prevent mdadm from running, move the udev rule that is responsible out of the way:
# cd /lib/udev/rules.d
# mkdir disabled
# mv 64-md-raid.rules disabled/
# reboot

============================ 
============================
HOWTO: Linux Software Raid using mdadm
1) Introduction:
Recently I went out and bought myself a second hard drive with the purpose of setting myself up a performance raid (raid0). It took me days and a lot of messing about to get sorted, but once I figured out what I was doing I realised that it's actually relatively simple, so I've written this guide to share my experiences 
 I went for raid0, because I'm not too worried about loosing data, but if you wanted to set up a raid 1, raid 5 or any other raid type then a lot of the information here would still apply.
2) 'Fake' raid vs Software raid:
When I bought my motherboard, (The ASRock ConRoeXFire-eSATA2), one of the big selling points was an on board raid, however some research revealed that rather than being a true hardware raid controller, this was in fact more than likely what is know as 'fake' raid. I think wikipedia explains it quite well: http://en.wikipedia.org/wiki/Redunda...ependent_disks



Hybrid RAID implementations have become very popular with the introduction of inexpensive RAID controllers, implemented using a standard disk controller and BIOS (software) extensions to provide the RAID functionality. The operating system requires specialized RAID device drivers that present the array as a single block based logical disk. Since these controllers actually do all calculations in software, not hardware, they are often called "fakeraids", and have almost all the disadvantages of both hardware and software RAID.


After realising this, I spent some time trying to get this fake raid to work - the problem is that although the motherboard came with drivers that let windows see my two 250 GB drives as one large 500 GB raid array, Ubuntu just saw the two separate drives and ignored the 'fake' raid completely. There are ways to get this fake raid working under linux, however if you are presented with this situation then my advice to you is to abandon the onboard raid controller and go for software raid instead. I've seen arguments as to why software raid is faster and more flexible, but I think the best reason is that software raid is far easier to set up! 
3) The Basics of Linux Software Raid:
For the basics of raids try looking on Wikipedia again: http://en.wikipedia.org/wiki/Redunda...ependent_disks.
 I don't want to discuss it myself because its been explained many times before by people who are far more qualified to explain it than I am. I will however go over a few things about software raids:
Linux software raid is more flexible than hardware raid or true raid because rather than forming a raid arrays between identical disks, the raid arrays are created between identical partitions. As far as I understand, if you are using hardware raid between (for example) two disks, then you can either create a raid 1 array between those disks, or a raid 0 array. Using software raid however, you could create two sets of identical partitions on the disks, and for a raid 0 array between two of those partitions, and a raid 1 array between the other two. If you wanted to you could probably even create a raid array between two partitions on the same disk! (not that you would want to!)
The process of setting up the a raid array is simple:

Create two identical partitions
Tell
 the software what the name of the new raid array is going to be, what partitions we are going to use, and what type of array we are creating (raid 0, raid 1 etc...)

Once we have created this array, we then format and mount it in a similar way to the way we would format a partition on a physical disk.
4) Which Live CD to use:
You want to download and burn the alternate install Ubuntu cd of your choosing, for example, I used:


Code:
ubuntu-6.10-alternate-amd64.iso

If you boot up the ubuntu desktop live CD and need to access your raid, then you will need to install mdadm if you want to access any software raid arrays:


Code:
sudo apt-get update
sudo apt-get install mdadm

Don't worry too much about this for now - you will only need this if you ever use the Ubuntu desktop cd to fix your installation, the alternate install cd has the mdadm tools installed already.
5) Finally, lets get on with it!
Boot up the installer
Boot up the alternate install CD and run through the text based installation until you reach the partitioner, and select "Partition Manually".
Create the partitions you need for each raid array
You now need to create the partitions which you will (in the next step) turn into software raid arrays. I recommend using the space at the start, or if your disks are identical, the end of your disks. That way once you've set one disk up, you can just enter exactly the same details for the second disk. The partitioner should be straightforward enough to use - when you create a partition which you intend to use in a raid, you need to change the type to "Linux RAID Autodetect".
How you partition your installation is upto you, however there are a few things to bear in mind:

If (like me) you are going for a performance raid, then you will need to create a separate /boot partition, otherwise grub wont be able to boot - it doesn't have the drivers needed to access raid 0 arrays. It sounds simple, but it took me so long to figure out.
If, on the other hand, you are doing a server installation (for example) using raid 1 / 5 and the goal is reliability, then you probably want the computer to be able to boot up even if one of the disks is down. In this situation you need to do something different with the /boot partition again. I'm not sure how it works myself, as I've never used raid 1, but you can find some more information in the links at the end of this guide. Perhaps I'll have a play around and add this to the guide later on, for completeness sake.
If you are looking for performance, then there isn't a whole load of point creating a raid array for swap space. The kernel can manage multiple swap spaces by itself (we will come onto that later).
Again,
 if you are looking for reliability however, then you may want to build a raid partition for your swap space, to prevent crashes should one of your drives fail. Again, look for more information in the links at the end.

On my two identical 250 GB drives, I created two 1 GB swap partitions, two +150 GB partitions (to become a raid0 array fro my /home space), and two +40 GB partitions (to become a raid 0 array for my root space), all inside an extended partition at the end of my drives. I then also created a small 500 MB partition on the first drive, which would become my /boot space. I left the rest of the space on my drives for ntfs partitions.
Assemble the partitions as raid devices
Once you've created your partitions, select the "Configure software raid" option. The changes to the partition table will be written to the disk, and you will be allowed to create and delete raid devices - to create a raid device, simply select "create", select the type of raid array you want to create, and select the partitions you want to use. 

Remember to check which partition numbers you are going to use in which raid arrays - if you forget, hit  a few times to bring you back to the partition editor screen where you can see whats going on.
Tell the installer how to use the raid devices

Once you are done, hit finish - you will be taken back to the partitioner where you should see some new raid devices listed. Configure these in the same way you would other partitions - set them mounts points, and decide on their filesystem type.
Finish the instalation

Once you are done setting up these raid devices (and swap / boot partitions you decide to keep as non-raid), the installation should run smootly.
6) Configuring Swap Space
I mentioned before that the linux kernel automatically manages multiple swap partitions, meaning you can spread swap partitions across multiple drives for a performance boost without needing to create a raid array. A slight tweak may be needed however; each swap partition has a priority, and if you want the kernel to use both at the same time, you need to set the priority of each swap partition to be the same. First, type


Code:
swapon -s

to see your current swap usage. Mine outputs the following:



Code:
Filename                                Type            Size    Used    Priority
/dev/sda5                               partition       979956  39080   -1
/dev/sdb5                               partition       979956  0       -2

As you can see, the second swap partition isn't being used at the moment, and won't be until the first one is full. I want a performance gain, so I need to fix this by setting the priority of each partition to be the same. Do this in /etc/fstab, by adding pri=1 as an option to each of your swap partitions. My /etc/fstab file now looks like this:



Code:
# /dev/sda5
UUID=551aaf44-5a69-496c-8d1b-28a228489404 pri=1 swap sw 0 0
# /dev/sdb5
UUID=807ff017-a9e7-4d25-9ad7-41fdba374820 pri=1 swap sw 0 0
 7) How to do things manually

As I mentioned earlier, if you ever boot into your instalation with a live cd, you will need to install mdadm to be able to access your raid devices, so its a good idea to at least roughly know how mdadm works. 

http://man-wiki.net/index.php/8:mdadm has some detailed information, but the important options are simply:


Code:


-A, --assemble
 Assemble a pre-existing array that was previously created with --create.
-C, --create
 Create a new array. You only ever need to do this once, if you try to create arrays with partitions that are part of other arrays, mdadm will warn you.
--stop
 Stop an assembled array. The array must be unmounted before this will work.





When using --create, the options are:

Code:
mdadm --create md-device --chunk=X --level=Y --raid-devices=Z devices

-c, --chunk=
    Specify chunk size of kibibytes.  The default is 64.
-l, --level=
    Set  raid  level, options are: linear, raid0, 0, stripe, raid1, 1, mirror, raid4, 4, raid5,  5,  raid6, 6,  multipath,  mp, fautly.
-n, --raid-devices=
    Specify the number of active devices in the array.



 for example:




Code:
mdadm --create /dev/md0 --chunk=4 --level=0 --raid-devices=2 /dev/sda1 /dev/sdb1

will create a raid0 array /dev/md0 formed from /dev/sda1 and /dev/sdb1, with chunk size 4.
When using --assemble, the usage is simply:


Code:
mdadm --assemble md-device component-devices

for example


Code:
mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1

Which will assemble the raid array /dev/md0 from the partitions /dev/sda1 and /dev/sdb1
Alternatively you can use:


Code:
mdadm --assemble --scan

and it will assemble any raid arrays it can detect automatically.
Lastly,


Code:
mdadm --stop /dev/md0

will stop the assembled array md0, so long as its not mounted.
If you wish you can set the partitions up yourself manually using fdisk and mdadm from the command line. Either boot up a desktop live cd and apt-get mdadm as described before, or boot up the alternate installer and hit escape until you see a list of the different stages of instalation - the bottom one should read execute shell - which will drop you at a shell with fdisk, mdadm and mkfs etc... available.
Note that if you ever need to create another raid partition, you create filesystems on them in exactly the same way you would a normal physical partition. For example, to create an ext3 filesystem on /dev/md0 I would use:


Code:
mkfs.ext3 /dev/md0

And to create a swapspace on /dev/sda7 I woud use:



Code:
mkswap /dev/sda7

Lastly, mdadm has a configuration file located at 


Code:
/etc/mdadm/mdadm.conf

this file is usually automatically generated, and mdadm will probably work fine without it anyway. If you're interested then http://man-wiki.net/index.php/5:mdadm.conf has some more information.
And that's pretty much it. As long as you have mdadm available, you can create / assemble raid arrays out of identical partitions. Once you've assembled the array, treat it the same way you would a partition on a physical disk, and you can't really go wrong! 
I hope this has helped someone! At the moment I've omitted certain aspects of dealing with raids with redundancy (like raid 1 and raid 5), such a rebuilding failed arrays, simply because I've never done it before. Again, I may have a play around and add some more information later (for completeness), or if anyone else running a raid 1 wants to contribute, it would be most welcome.
Other links
The Linux Software Raid Howto: 
http://tldp.org/HOWTO/Software-RAID-HOWTO.html
This guide refers to a package "raidtools2" which I couldn't find in the Ubuntu repositories - use mdadm instead, it does the same thing.
Quick HOWTO: Linux Software Raid
http://www.linuxhomenetworking.com/w..._Software_RAID

Using mdadm to manage Linux Software Raid arrays
http://www.linuxdevcenter.com/pub/a/...2/05/RAID.html
Ubuntu Fake Raid HOWTO In the community contributed documentation
https://help.ubuntu.com/community/Fa...ght=%28raid%29
============================ 
https://bugs.launchpad.net/linuxmint/+bug/682315 
dmraid and kpart? 

$ sudo dmraid -a 
y  
$ sudo dmraid -r
$ sudo dmraid -l
To fix this problem fast I added "dmraid -ay" at the bottom of the script so it did the trick for me but somebody should look deeper in to this.
====================== 
http://forums.linuxmint.com/viewtopic.php?f=46&t=105725 
Do you have to use bios raid? Linux raid, mdadm, is recommended.
The problem you are having is probably due to your Grub and/or your OS not having dmraid support. This is because the Installer only does half the job.
Presumably you booted the live CD and installed dmraid, then installed to the raid device and Grub install failed.
At this point you need to chroot into the raid and install dmraid, update initramfsand reconfigure grub.
https://help.ubuntu.com/community/Grub2 ... ing#ChRoot
sudo apt-get install dmraid
sudo update-initramfs -u
sudo dpkg-reconfigure grub-pc
---------------------
How-to install LinuxMint or Ubuntu of softraid / fakeraid the simple way:

Install Linux using the default installer program (let it do the partitioning unless you have specific requirements)
When grub fails at the end of the install select install grub manually
chroot into system installed on raid (fake or soft) https://help.ubuntu.com/community/Grub2/Installing#ChRoot
grub-install on the TOP level partition of the raid
update-grub
Reboot and enjoy linux

======================= 
http://ubuntuforums.org/showthread.php?t=2089865&page=2
The possibility is a partition table irregularity which confuses the installer. Fairly easily fixed, but if your drive was not used in a RAID, lets see if this is so. Close the installer and open a terminal. 
Run this command and post the output:


Code:
sudo fdisk -lu
and then 



Code:
sudo parted -l

I have suggested both as you may have GPT partitions and a UEFI bios. 

----------------------

Is a Intel SRT system. Those tend to be a large hard drive and small SSD to speed Windows up. Each vendor slightly different but the Intel part is the same.
Some delete the SRT and install Linux to the SSD, others turn off  SRT in Windows and have to use the RAID commands to remove RAID settings. 

Then after install they seem to be able to re-implement the SRT, but I do not then think Linux sees Windows.
        Intel Smart Response Technology
http://www.intel.com/p/en_US/support...ts/chpsts/imsm
Intel SRT - Dell XPS
http://ubuntuforums.org/showthread.php?t=2038121
http://ubuntuforums.org/showthread.php?t=2036204
http://ubuntuforums.org/showthread.php?t=2020155
Some info on re-instating 
http://ubuntuforums.org/showthread.php?t=2038121
http://ubuntuforums.org/showthread.php?t=2070491
Disable the RAID, for me it was using the Intel rapid management thingy and telling it to disable the acceleration or the use of the SSD. If you have a different system, just disable the RAID system then install Ubuntu. Once installed you can then re-enable it.

You will need to use the dmraid command prior to running the Ubuntu Installer so that it will be able to see the partitions on the drive because otherwise with the raid metadata in place it will see the drive as part of a raid set and ignore its partitions. 

Try first to remove the dmraid package from Linux.

Code:
sudo apt-get remove dmraid