Out of boot experience

Windows Welcome music (Windows XP)
C:\Windows\system32\oobe\images\title.wma
...

Hagamos un pequeño viaje al pasado, exactamente a 1994. Por aquellas días, Mark Malamud y Erik Gavriluk, que trabajan en el proyecto de Microsoft con nombre clave Cairo, se ponen en contacto con Brian Eno, el compositor de música electrónica que empezara con Roxy Music, y consiguen que componga los 6 segundos del sonido de inicio del que más tarde sería Windows 95. Brian cuenta en una entrevista concedida al San Francisco Chronicle que la idea le llegó en un momento en que estaba seco de ideas y le pareció realmente divertido y asombroso tratar de componer una pieza musical tan pequeña, que era como fabricar una pequeña joya. Después de medir minuciosamente los microsegundos de la pequeña pieza musical, cuenta Brian que al volver a los temas de 3 minutos le parecían océanos de tiempo. “The Microsoft sound” continuó acompañando el arranque de las versiones siguientes de los sistemas operativos de Redmond, si bien ya no se trataba del tema de Eno… ¡qué poco apego a la tradición!

Brian Eno, en 2006 (Wikipedia)
Quizás lo más singular de toda esta historia es que se cuenta que Brian compuso la pequeña pieza usando su ordenador Apple Machintosh.

Pruebalo, funciona

Hola,
karen_puta@hotmail.com ha decidido enviarte una invitación para probar nuestro servicio totalmente gratuito.

Te permite detectar todos los contactos que te han eliminado de su lista.
De este modo, podrás:
- Fijarte quién te ha eliminado de su lista.
- Limpiar tu MSN de quien no quiere hablarte.
- Recuperar contactos eliminados.
- Ver quién te tiene agregado que no tienes en tu lista.
Pruébalo aquí - CLICK AQUI
¡Te esperamos!

¡Sitio web reportado como falsificación!
Este sitio web en tumsn.net ha sido reportado como una falsificación web y ha sido bloqueada basándose en sus preferencias de seguridad.
Las falsificaciones de webs son diseñadas para intentar engañar al usuario para que revele información personal o financiera imitando fuentes en las que confia.
Introducir cualquier información en esta página web puede resultar en un robo de identidad o en otro tipo de fraude.

Full virtualization on Phenom?

To check if the CPU supports full virtualization use command
#grep vmx /proc/cpuinfo
or look for info with
#cat /proc/cpuinfo

Grub error on SCSI and SATA disks

Source
Grub Error 2 means "Selected disk doesn't exist"
Errors description

Errors Reported by the Stage 1

The general way that the Stage 1 handles errors is to print an error string and then halt. Pressing Ctrl-Alt-Del will reboot.

The following is a comprehensive list of error messages for the Stage 1:

• "Hard Disk Error"

  This error message will occur if the Stage 2 or Stage 1.5 is being read from a hard disk, and the attempt to determine the size and geometry of the hard disk fails.

• "Floppy Error"

  This error message will occur if the Stage 2 or Stage 1.5 is being read from a floppy disk, and the attempt to determine the size and geometry of the floppy disk fails. It's listed as a different error since the probe sequence is different than for hard disks.

• "Read Error"

  This error message will occur if a disk read error happens while trying to read the Stage 2 or Stage 1.5.

• "Geom Error"

  This error message will occur if the location of the Stage 2 or Stage 1.5 is not in the area supported by reading the disk with the BIOS directly. This could occur because the BIOS translated geometry has been changed by the user or the disk is moved to another machine or controller after installation, or GRUB was not installed using itself (if it was, the Stage 2 version of this error would have been seen during that process and it would not have completed the install).

---

Errors Reported by the Stage 1.5

The general way that the Stage 1.5 handles errors is to print an error number in the form "Error: " and then halt. Pressing Ctrl-Alt-Del will reboot.

The error numbers correspond to the Errors Reported by the Stage 2 in the listed sequence.

---

Errors Reported by the Stage 2

The general way that the Stage 2 handles errors is to abort the operation in question, print an error string, then (if possible) either continue based on the fact that an error occurred or wait for the user to deal with the error.

The following is a comprehensive list of error messages for the Stage 2 (error numbers for the Stage 1.5 are listed before the colon in each description):

• 1 : "Selected item won't fit into memory"

  This error is returned if a kernel, module, or raw file load command is either trying to load it's data such that it won't fit into memory or it is simply too big.

• 2 : "Selected disk doesn't exist"

  This error is returned if the device part of a device- or full filename refers to a disk or BIOS device that is not present or not recognized by the BIOS in the system.

• 3 : "Disk read error"

  This error is returned if there is a disk read error when trying to probe or read data from a particular disk.

• 4 : "Disk write error"

  This error is returned if there is a disk write error when trying to write to a particular disk. This would generally only occur during an install of set active partition command.

• 5 : "Disk geometry error"

  This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general).

• 6 : "Attempt to access block outside partition"

  This error is returned if a linear block address is outside of the disk partition. This generally happens because of a corrupt filesystem on the disk or a bug in the code handling it in GRUB (it's a great debugging tool).

• 7 : "Partition table invalid or corrupt"

  This error is returned if the sanity checks on the integrity of the partition table fail. This is a bad sign.

• 8 : "No such partition"

  This error is returned if a partition is requested in the device part of a device- or full filename which isn't on the selected disk.

• 9 : "Bad filename (must be absolute pathname or blocklist)"

  This error is returned if a filename is requested which doesn't fit the syntax/rules listed in the Filesystem Description.

• 10 : "Bad file or directory type"

  This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO.

• 11 : "File not found"

  This error is returned if the specified filename cannot be found, but everything else (like the disk/partition info) is OK.

• 12 : "Cannot mount selected partition"

  This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB.

• 13 : "Inconsistent filesystem structure"

  This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.

• 14 : "Filesystem compatibility error, can\'t read whole file"

  Some of the filesystem reading code in GRUB has limits on the length of the files it can read. This error is returned when the user runs into such a limit.

• 15 : "Error while parsing number"

  This error is returned if GRUB was expecting to read a numbur and encountered bad data.

• 16 : "Device string unrecognizable"

  This error is returned if a device string was expected, and the string encountered didn't fit the syntax/rules listed in the Filesystem Description.

• 17 : "Invalid device requested"

  This error is returned if a device string is recognizable but does not fall under the other device errors.

• 18 : "Invalid or unsupported executable format"

  This error is returned if the kernel image boing loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).

• 19 : "Loading below 1MB is not supported"

  This error is returned if the lowest address in a kernel is below the 1MB boundary. The Linux zImage format is a special case and can be handled since it has a fixed loading address and maximum size.

• 20 : "Unsupported Multiboot features requested"

  This error is returned when the Multiboot features word in the Multiboot header requires a feature that is not recognized. The point of this is that the kernel requires special handling which GRUB is likely unable to provide.

• 21 : "Unknown boot failure"

  This error is returned if the boot attempt did not succeed for reasons which are unknown.

• 22 : "Must load Multiboot kernel before modules"

  This error is returned if the module load command is used before loading a Multiboot kernel. It only makes sense in this case anyway, as GRUB has no idea how to communicate the presence of location of such modules to a non-Multiboot-aware kernel.

• 23 : "Must load Linux kernel before initrd"

  This error is returned if the initrd command is used before loading a Linux kernel. Similar to the above error, it only makes sense in that case anyway.

• 24 : "Cannot boot without kernel loaded"

  This error is returned if GRUB is told to execute the boot sequence without having a kernel to start.

• 25 : "Unrecognized command"

  This error is returned if an unrecognized command is entered into the command-line or in a boot sequence section of a config file and that entry is selected.

• 26 : "Bad or incompatible header on compressed file"

  This error is returned if the file header for a supposedly compressed file is bad.

• 27 : "Bad or corrupt data while decompressing file"

  This error is returned the run-length decompression code gets an internal error. This is usually from a corrupt file.

• 28 : "Bad or corrupt version of stage1/stage2"

  This error is returned if the install command is pointed to incompatible or corrupt versions of the stage1 or stage2. It can't detect corruption in general, but this is a sanity check on the version numbers, which should be correct.

Super Grub Disk

BerliOS.de

We want Linux newbies to restore their new toy, but also help the Linux advanced user make potentially dangerous operations to the MBR in a safe way. Super Grub Disk is also a teaching tool to help you learn more about bootloaders and the booting process. After all, booting is the most important thing your computer does -- without the boot process, you would not have an operating system to use!

NewSID

Source
Von Mark Russinovich und Bryce Cogswell
NewSID herunterladen (68 KB)

NTFS-3g error: Hal.Storage.mount-fixed

org.freedesktop.Hal.Device.PermissionDeniedByPolicy:
org.freedesktop.Hal.Storage.mount-fixed
auth_admin_keep_always <-- (action, result).
Source

Hal is the hardware abstraction layer, which to my knowledge knows no policy by itself. That is usually the domain of "udev". Have a look at
http://www.reactivated.net/writing_udev_rules.html
http://gentoo-wiki.com/HOWTO_Customizing_UDEV
http://linuxcommand.org/man_pages/udev8.html
http://ftp.kernel.org/pub/linux/util...tplug/udev-FAQ
http://www.linuxfromscratch.org/lfs/...er07/udev.html
But maybe, just maybe, it is faster to have a look at your file ".hal-mtab-lock". What does it contain? "cat /etc/mtab" lists the mounted devices as you probably know. Why not renaming that ".hal-mtab-lock" for a test and try to access your DVD-drive...
-------------------------------
Windows-Partitionen einbinden
Bugs in Hal?
mein Fall:/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part2 / ext3 acl,user_xattr 1 1
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part8 /DATEN ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part11 /IMAGES ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part9 /MMEDIA ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part10 /VMs ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part1 /Win2k3 ntfs-3g defaults,users,locale=POSIX 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part3 /WinXP ntfs-3g defaults,locale=POSIX 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part7 /home ext3 acl,user_xattr 1 2
/dev/sdb9 /media/data1 ntfs-3g defaults,locale=POSIX 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part6 swap swap defaults 0 0

/dev/sdb9 wird gemounted ohne Probleme!

VirtualBox installation in OpenSuSE 11.1

Source
Installation of VirtualBox in openSUSE is made easy through the 1-click installation.

Extended n Filesystem Explorer

Explore2fs
Explore2fs is a GUI explorer tool for accessing ext2 and ext3 filesystems. It runs under all versions of Windows and can read almost any ext2 and ext3 filesystem. A beta version of Virtual Volumes is now available. This is a technology preview for Explore2fs 2. Virtual Volumes also has the ability to read ReiserFS and many other filesystems
explore2fs-1.08beta9.zip

Windows x64 [6 en 1] DVD

Download

AMD X2 procesadores & juegos

Source

Localization: MUI and Regional Options

Source (unattended.msfn.org)

The Multilanguage User Interface (MUI) is used for localizing the OS interface elements (menus, dialogs windows, etc). MUI is not available for retail, and distributed among the volume license customers only. Home users cannot download MUI from the Microsoft web site. The only MUI available on the Microsoft web site is MUI for Windows Embedded. It cannot be used with Windows XP. MUI can be installed on the English Windows XP only.
In this section the Russian MUI is discussed, but the procedures can be applied to any other language version of MUI. There is a total of five CDs with several MUI languages per CD. For example, I'm interested in installing Russian language interface only. First of all, I would like to extract Russian MUI from the CD. This task can be accomplished by creating the Administrative Installation Point. All you need to do is to run setup.exe with the /a switch.

X:\muisetup.exe /a

Where X is the CD-ROM letter. Then follow the wizard and "install" (extract to the specified location) the language you need. This is your MUI installation source that can be used for the installation.
There's only one modification left. You need the updated muisetup.exe. If you have SP2 installed, navigate to your %SystemRoot%\mui folder and copy the muisetup.exe file from there to the MUI installation source (confirm overwrite prompt). If you don't have SP2 installed, you can extract muisetup.exe from the SP2 source (I hope you'll figure out how to do it). Once the updated muisetup.exe is placed in the MUI source, you can prepare for the installation.
...

Internet Explorer Enhanced Security

Windows Server 2003 shipped with security locked down by default. Part of this locking down is Internet Explorer Enhanced Security which is an extra layer of protection when surfing the internet using Internet Explorer (more information can be found by going here on a Windows Server 2003 [test] machine). Some people want to uninstall it.

Before we start, understand the way the uninstaller works. You can uninstall the entire Configuration, or just for users, or just for Administrators. The un-installer is set up like this:
Enhanced Security
->For Administrators
->For Users
If you have just random users connecting via Remote Desktop or Terminal Services, you may want to leave the Users configuration installed. This tutorial will be removing all of it.

Disabling IEES Configuration (source of this post)
Disabling Internet Explorer Enhanced Security Configuration

Click Start-- Control Panel -- Add/Remove Programs
Now click Add/Remove Windows Components
Click the check mark next to Internet Explorer Enhanced Security Configuration (to make it unchecked).
If you'd like to only disable it for Administrators or only for Users you can click Details and do so.
NEXT and voilá

Wipe the free space on media

Linux tools
By default, shred will overwrite the whole drive 25 times!
If you have a 100GB disk, that means writing 2500GB of data.
To just do it once, you would type (hda or sda!)
#shred -n 1 /dev/hda1
but bear in mind that this is less secure.
--------------------------------
# cat /dev/urandom > /dev/hda1
Break w/ Ctrl+c
--------------------------------
# dd if=/dev/urandom of=/dev/hda1
if u want zeros:
# dd if=/dev/zero of=/dev/hda1
---------------------------------
You can "delete" the journal with:
tune2fs -O ^has_journal /dev/hdXX
But can you shred the journal?
=======================
Windows XP Professional
The cipher command can be used to wipe the free space on a drive.
Use the /w: switch.
This command would wipe the free space on drive C:
cipher /w:c
==========================
http://www.dban.org/

Why doesn't Linux need defragmenting?

Source THANKS for the excellent explanation!!!

That is a question that crops up with regularity on Linux forums when new users are unable to find the defrag tool on their shiny new desktop. Here's my attempt at giving a simple, non-technical answer as to why some filesystems suffer more from fragmenting than others.

Rather than simply stumble through lots of dry technical explanations, I'm opting to consider that an ASCII picture is worth a thousand words. Here, therefore, is the picture I shall be using to explain the whole thing:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
n  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

This is a representation of a (very small) hard drive, as yet completely empty - Hence all the zeros. The a-z's at the top and the left side of the grid are used to locate each individual byte of data: The top left is aa, top right is za, and bottom left is az. You get the idea, I'm sure. . .
We shall begin with a simple filesystem of a sort that most users are familiar with: One that will need defragmenting occasionally. Such filesystems, which include FAT, remain important to both Windows and Linux users: if only for USB flash drives, FAT is still widely used - unfortunately, it suffers badly from fragmentation.
We add a file to our filesystem, and our hard drive now looks like this:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t a e l e 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  H e l l o , _ w o r l d 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

(Empty rows g-z ommitted for clarity)

To explain what you see: The first four rows of the disk are given over for a "Table of contents", or TOC. This TOC stores the location of every file on the filesystem. In the above example, the TOC contains one file, named "hello.txt", and says that the contents of this file are to be found between ae and le. We look at these locations, and see that the file contents are "Hello, world"
So far so good? Now let's add another file:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t a e l e b y e . t x t m e z
b  e 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  H e l l o , _ w o r l d G o o d b y e , _ w o r l d
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

As you can see, the second file has been added immediately after the first one. The idea here is that if all your files are kept together, then accessing them will be quicker and easier: The slowest part of the hard drive is the stylus, the less it has to move, the quicker your read/write times will be.
The problem this causes can be seen when we decide to edit our first file. Let's say we want to add some exclamation marks so our "Hello" seems more enthusiastic. We now have a problem: There's no room for these exclamation marks on our filesystem: The "bye.txt" file is in the way. We now have only two options, neither is ideal:

1. We delete the file from its original position, and tack the new, bigger file on to the end of the second file.
2. We fragment the file, so that it exists in two places but there are no empty spaces.

To illustrate: Here is approach one

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t a f n f b y e . t x t m e z
b  e 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  0 0 0 0 0 0 0 0 0 0 0 0 G o o d b y e , _ w o r l d
f  H e l l o , _ w o r l d ! ! 0 0 0 0 0 0 0 0 0 0 0 0

And here is approach two:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t a e l e a f b f b y e . t x
b  t m e z e 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  H e l l o , _ w o r l d G o o d b y e , _ w o r l d
f  ! ! 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

This is why FAT filesystems need defragging regularly. All files are placed right next to each other, so any time a file is enlarged, it fragments. And if a file is reduced, it leaves a gap. Soon the hard drive becomes a mass of fragments and gaps, and performance starts to suffer.

And then there is Linux. Which has a different philosophy. Windows filesystems are ideal if you have a single user, accessing files in more-or-less the order they were created in, one after the other. Linux, however, was always intended as a multi-user system: It was gauranteed that you would have more than one user trying to access more than one file at the same time. So a different approach was used. When we create "hello.txt" on a Linux filesystem, it looks like this:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t h n s n 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
n  0 0 0 0 0 0 0 H e l l o , _ w o r l d 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

And then when another file is added:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t h n s n b y e . t x t d u q
b  u 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
n  0 0 0 0 0 0 0 H e l l o , _ w o r l d 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 G o o d b y e , _ w o r l d 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

The cleverness of this approach is that the disk's stylus can sit in the middle, and most files, on average, will be fairly nearby: That's how averages work, after all.

Plus when we add our exclamation marks to this filesystem, observe how much trouble it causes:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t h n u n b y e . t x t d u q
b  u 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
n  0 0 0 0 0 0 0 H e l l o , _ w o r l d ! ! 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 G o o d b y e , _ w o r l d 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

That's right: Absolutely none.

Windows tries to put all files as close to the start of the hard drive as it can, thus it constantly fragments files when they grow larger and there's no free space available.

Linux scatters files all over the disk so there's plenty of free space if the file's size changes. It also re-arranges files on-the-fly, since it has plenty of empty space to shuffle around.
Defragging a Windows filesystem is a more intensive process and not really practical to run during normal use.
Fragmentation thus only becomes an issue on Linux when a disk is so full that there just aren't any gaps a large file can be put into without splitting it up. So long as the disk is less than about 80% full, this is unlikely to happen.
It is also worth knowing that even when an OS says a drive is completely defragmented, due to the nature of hard drive geometry, fragmentation may still be present: A typical hard drive actually has multiple disks, AKA platters, inside it.
Let's say that our example hard drive is actually on two platters, with aa to zm being the first and an to zz the second:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

   a b c d e f g h i j k l m n o p q r s t u v w x y z

n  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

The following file would be considered non-fragmented, because it goes from row m to row n, but this ignores the fact that the stylus will have to move from the very end of the platter to the very beginning in order to read this file.

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t r m e n 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 H e l l o , _ w o

   a b c d e f g h i j k l m n o p q r s t u v w x y z

n  r l d ! ! 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

I hope this has helped you to understand why no defragging software came with your Linux installation. If not, I'm always open to suggestions

You may also be interested in why deleting just isn't enough
---------------------------------
Why does Linux need defragmenting?

PC schaltet beim Herunterfahren nicht ab

Source

Achtung: dieser Tipp funktioniert nicht beim W2K-Server!
Eigentlich sollte der PC unter Windows 2000/XP beim Herunterfahren abschalten, sofern es
sich um ein ATX-Modell handelt. Dies ist aber dann z.B. nicht der Fall, wenn man W2K / XP
absichtlich ohne ACPI installiert. Um das Abschalten dennoch zu erreichen, muss man in
der Systemsteuerung unter "Energieoptionen" auf der Registerkarte "APM" die
"Unterstützung für das Advanced Power Management" aktivieren.
Wenn diese Registerkarte fehlt, muss man im Gerätemanager unter Ansicht / Ausgeblendete Geräte anzeigen aktivieren.
Dann wird in der Geräteliste auch der "Herkömmliche NT-APM Schnittstellenknoten" angezeigt und ist vermutlich deaktiviert.
Also aktivieren, danach wird in den "Energieoptionen" auch die Registerkarte "APM" angezeigt.
---------------------------------
Mehrere Möglichkeiten kommen hier in Betracht:
1. Der PC besitzt kein ATX Netzteil.
2. Der PC wurde ohne ACPI installiert. Hier muss APM (Unterstützung für Advanced Power Management) eingeschaltet werden.
Zu finden unter: Systemsteuerung / Energieoptionen
Dort APM einschalten. Jetzt sollte W2K den Rechner automatisch ausschalten können.
3. Schlüssel: HKEY_LOCAL_MACHINE / Software / Microsoft / WindowsNT / CurrentVersion / Winlogon
Wert: PowerdownAfterShutdown [REG_SZ] auf "1" stellen.
4. Im BIOS-Setup unter Powermanagement die Option soft-off by pwr-bttn (beim AWARD-BIOS) auf Instant-Off stellen.

Globovision & batanga.com

http://radio.batanga.com/sp/linuxusers.asp

The Problem with Multimedia & Linux distros

Source

I love Linux, but why does playing music have to be soo tough?

oldcpu

Global Moderator of openSuSE forums:

Why?? To avoid being sued. Novell is a big fat juicy target for those seeking to make money by suing an operating system supplier for illegal provision of codecs without payment of royalties.
In many cases private users are free to download and install codecs, but its not legal for operating system suppliers to provide the codecs.
Also, from what I have read its not the policy of Novell/SuSE-GmbH to provide proprietary software, drivers, nor codecs (and the MAJORITY of audio formats are in a proprietary format). This is because of the "open" in openSUSE. Note the emphasis on "open". That is because Novell/SuSE-GmbH in openSUSE try harder than most other distribution packagers to provide a distribution that follows the free open source philosophy:
Free Software Philosophy - openSUSE
... which means no automatic playing of most music as such music is stored in proprietary formats. Fortunately there are work arounds and ways to download and install codecs and applications to play such music, BUT its up to the openSUSE community to provide those means. And by "openSUSE community" I mean users like YOU and ME to contribute and find a way to make it easier. If we do not do this, (ie YOU and ME and other's like us), then NO ONE ELSE will.
caf4926 is doing his best in this guide to make this music installation easier for you in a Linux distribution (openSUSE) that places VERY HIGH importance on Free open source software and NO PROPRIETARY software, codecs, applications.
--------------------------------
Useful Terminal Commands & Solutions to Low Resolution Issues
Useful Guides for Ubuntu - Install Anything - Ubuntu:Chronicles

Compiz in KDE4.2

Thanks, Carl!
Compiz in KDE4.2 - Video
OpenSUSE Help - Video Downloads

Here I have uploaded a Video of Managing Packages in Yast - Software Management. Using Filter by Repository and doing Update All, you can choose 'if newer version avail' or 'unconditionally'.
If all Packages are showing with Blue text then the 'if newer ver' option is fine. But if there is a mix of Red and Blue use 'unconditionally'. This method of Package Management is especially helpful in Managing packages in repo's like those in the video - unstable or factory repo's. Or in multi-media situations where everytime you click on a package to update (eg;Amarok) say in Packman you get dependency errors. You can temporarily disable the check box for that and re-enable it before pressing accept. This lets you mark all the updates/upgrades/changes without interference. By the time you finish doing 'update all' in the various repo's - when you check at the end for dependencies, it is usually all OK. Read carefully any errors you do get, it is a bit confusing but it is usually fairly easy to opt your way through it. Or save the the error to file with the expert button.

Yast_Package]Yast Video- Package Management_Archived

Multi-media Subarea (OpenSUSE)

Welcome to the openSUSE Forums multimedia section!
This is our multimedia thread area, where support for multimedia is provided. This is intended to include questions about media applications, codecs (DVD, music, video, pdf) configuration (usage, bugs), etc ...
If you have sound working, but can not play many audio/video formats, it is possible these are proprietary formats that are not supported "after a fresh install" by openSUSE. More information on the openSUSE approach for packaged audio/video support can be found here:
Restricted Formats - openSUSE
OpenSUSE users can have 1st rate multimedia with the appropriate 3rd party applications and codecs installed. Information on installing 3rd party applications/codecs can be found here:
Multimedia - openSUSE-Community
More information for installing 3rd party "restricted formats" on different openSUSE versions can be found here:
Restricted Formats - openSUSE-Community
Note it often makes the above significantly easier if you have setup your repositories per this wiki here:
Repositories - openSUSE-Community
If you have a problem getting your sound card to work, please go here:
SDB:AudioTroubleshooting - openSUSE
If that that does not help you get your basic sound working, please post in this "multimedia" sub-forum, providing in your post the following information:
* provide the URLs (of a summary webpage) that are created by running the two diagnostic scripts noted here:
SDB:AudioTroubleshooting - openSUSE
* in a terminal, or xterm, or konsole, type: uname -a #and post output here
* in a terminal, or xterm, or konsole, type: rpm -qa | grep alsa #and post output here
* in a terminal, or xterm, or konsole, type: cat /etc/modprobe.d/sound #and post output here
* in addition in openSUSE-11.1 run the script /usr/sbin/alsa-info.sh and post here the output URL. Just the URL.

---

openSUSE-community.org/Restricted_Formats

In openSUSE 11.1 all our codec handling will be done using One-Click-Install. This provides a simple wizard to guide you through everything, and you have to install absolutely nothing extra to be good to go!

Restricted Multimedia Formats (MP3, MPEG-4, etc.)
Note: Different copyright and patent laws apply differently depending on what country you are in; if you are unsure about a particular restriction or patent, you might consider applying for legal advice. This site does not offer legal advice. For more information about why some formats/codecs are restricted and why they don't ship out-of-the-box on openSUSE, read Restricted Formats.
To go through a simple wizard guiding you through the installation process of some additional multimedia codecs where necessary, simply click on one of the links below:

If you are using the KDE Desktop Environment 1-click installation codecs-kde.ymp Note: On 32-bit systems there'll be a dialog asking for about architecture change for libxine1 from from i586 to i686, accept that change.

If you are using the KDE Desktop Environment Command line installation Instead of using the 1-click you can install the codecs using a root terminal instead. Simply copy/paste the commands. Add the required software repositories (one line command: zypper... ): zypper addrepo http://ftp.skynet.be/pub/packman/suse/11.1 packman zypper addrepo http://suse.linuxin.dk/repo/11.1 libdvdcss Install the packages (one line command: zypper... ): zypper install ffmpeg flash-player gst-fluendo-mp3 k3b-codecs libdvdcss libxine1-codecs phonon-backend-xine w32codec-all amarok-xine

If you are using the GNOME Desktop Environment: codecs-gnome.ymp

his will enable you to have:

• Flash
• Java
• Latest Amarok (with MP3 Support) for KDE, or Helix-Banshee for GNOME users
• Encrypted DVD (libdvdcss)
• Extra xine codecs, for MPEG-4 etc. (libxine1)
• K3b with MP3 Support (k3b-codecs)
• Win 32 Codecs (w32codec-all)

..as well as the option of installing many more applications (select Customise mode at the screen), including:

• Opera
• VLC
• ..and more

---

TROUBLESHOOTING

Sometimes things are not installed correctly. When that happens, you will find that you cannot play mp3, mp4, wmv using totem. At that point key to making it work correctly may not be so obvious. Here is what I did to get things working after the default install attempt went badly.

The key was to DISABLE all repositories but the packman and libdvdcss repositories... then remove all of the gstreamer packages and totem. Then do the install using the link from http://opensuse-community.org/Restricted_Formats/11.1. After this, re-enable all of repositories that you disabled before and then install totem. At that point everything works.

CARL'S PAGE
openSUSE 11.1_Install Slideshow

Multi-media and Restricted Format Installation

Source
Ben Kevan: Things to do after installing openSUSE 11.0
Multi-media and Restricted Format Installation Guide (openSUSE)

The purpose of this guide is to try and simplify what some have found to be a tricky process. There exist 'OneClick' options for this. Experienced users, at least as far as I am aware, do not use the 'OneClick' method. Keep in mind this was written for openSUSE 11.0 – You will be Working from Yast – Software – Software Management /& Repositories.
Some basic Repositories You Must Have:

1. Oss: Index of /distribution/11.0/repo/oss
2. Non-oss: Index of /distribution/11.0/repo/non-oss
3. Update: Index of /update/11.0

These repositories should be in your repositories list from Installation.
If Not, add them.
Additional Repositories You will need:

1. Packman: http://ftp.gwdg.de/pub/linux/misc/packman/suse/11.0/
2. Videolan VLC: Index of /pub/vlc/SuSE/11.0/

N.B. You will install one package from VLC: libdvdcss – That's it!! Then DISABLE this repo. Install this Package FIRST.
Now we can move on to everything else...
But first you need to know something of the installation process. Using Yast – Software – Software Management you can filter by Repositories and so go to the repository you need to work from. In our case it will be the Packman Repository. Installed Packages have a tick in the check box, Packages with Blue text mean they are updates – Packages showing Red text mean they are roll-backs. In the case of a New Installation it is unlikely that there will be any Red packages. If you see blue packages in the Packman repo – do the following:
- Looking at the menu buttons along the top of the GUI, select 'Package' and in the drop box select 'Update all in this list if Newer version Available'. Now accept.
**In Gnome this option is not available, but there is a work around to get the QT GUI here:
How To Get QT zypper GUI in GNOME YAST
If you receive a dependency error, look to accept the 'Vendor Change' option to resolve it.
For eg: Amarok from a default install of KDE will be a Blue package and will update, but you will need to confirm 'Vendor Change' to Packman. If you can't work out what to do, save the error to file by clicking the 'other' button in the error box. Then paste that info in to a question in the forum.
When Yast finishes it will ask if you want to install more? Select Yes.
Now filter by repository again and go back to Packman.
You now need to mark for installation the following – some of which may auto add to install by dependency as you work through the list.
libavcodec52
libdvdnav4
libdvdplay0
libdvdread4
libffmpeg0
libquicktime0
libxine1
libxine1-codecs
libxvidcore4
smplayer
vlc
w32codec-all
xine-ui
xvidcore
This list is by no means comprehensive and depending on your system and chosen desktop environment, you may need further adjustment. You may also want to use the search box and type realplayer to install this too. It should be noted that FLASHPLAYER is installed by default at install and should just work. If it does not - Post your question/problem in the forum.

Thanks to RedDwarf for this check list:
Check your multimedia problem in ten steps
'oldcpu' has a 'sticky' here:
Multimedia sub-area - openSUSE Forums

ONECLICK's openSUSE 11.0 KDE: http://opensuse-community.org/codecs-kde.ymp GNOME: http://opensuse-community.org/codecs-gnome.ymp

Multi-media and Restricted Format Installation Guide

UPDATED FOR openSuSE 11.1

The purpose of this guide is to try and simplify what some have found to be a tricky process. There exist 'OneClick' options for this. Experienced users, at least as far as I am aware, do not use the 'OneClick' method. Keep in mind this was written for openSUSE 11.0 (NOW UPDATED FOR 11.1) – You will be Working from Yast – Software – Software Management /& Repositories.
Some basic Repositories You Must Have:

1. Oss: http://download.opensuse.org/distribution/11.1/repo/oss/
   
2. Non-oss: http://download.opensuse.org/distribution/11.1/repo/non-oss/
   
3. Update: http://download.opensuse.org/update/11.1/
   

These repositories should be in your repositories list from Installation.
If Not, add them.
Additional Repositories You will need:

1. Packman: Index of /pub/linux/misc/packman/suse/11.1
2. Videolan VLC: http://download.videolan.org/pub/vlc/SuSE/11.1
   

N.B. You will install one package from VLC: libdvdcss – That's it!! Then DISABLE this repo. Install this Package FIRST.
---------------------------------
Now we can move on to everything else:
But first you need to know something of the installation process. Using Yast – Software – Software Management you can filter by Repositories and so go to the repository you need to work from. In our case it will be the Packman Repository. Installed Packages have a tick in the check box, Packages with Blue text mean they are updates – Packages showing Red text mean they are roll-backs. In the case of a New Installation it is unlikely that there will be any Red packages. If you see blue packages in the Packman repo – do the following:
- Looking at the menu buttons along the top of the GUI, select 'Package' and in the drop box select 'Update all in this list if Newer version Available'. Now accept.
**In Gnome this option is not available, but there is a work around to get the QT GUI here:
QT zypper GUI in GNOME YAST
If you receive a dependency error, look to accept the 'Vendor Change' option to resolve it.
For eg: Amarok from a default install of KDE will be a Blue package and will update, but you will need to confirm 'Vendor Change' to Packman. If you can't work out what to do, save the error to file by clicking the 'other' button in the error box. Then paste that info in to a question in the forum.
When Yast finishes it will ask if you want to install more? Select Yes.
Now filter by repository again and go back to Packman.
You now need to mark for installation the following – some of which may auto add to install by dependency as you work through the list.
amarok-packman (if kde or you want this media player) + amarok-xine
libavcodec52
libdvdnav4
libdvdplay0
libdvdread4
libffmpeg0
libquicktime0
libxine1
libxine1-codecs
libxvidcore4
smplayer
vlc
w32codec-all
xine-ui
xvidcore
This list is by no means comprehensive and depending on your system and chosen desktop environment, you may need further adjustment. You may also want to use the search box and type realplayer to install this too. It should be noted that FLASHPLAYER is installed by default at install and should just work. If it does not - Post your question/problem in the forum.
Thanks to RedDwarf for this check list:
Check your multimedia problem in ten steps
'oldcpu' has a 'sticky' here:
Welcome to multimedia sub-area

ONE CLICK OPTION KDE: http://opensuse-community.org/codecs-kde.ymp Gnome: http://opensuse-community.org/codecs-gnome.ymp

__________________

For all other apps:
Search an application & One Click Install openSuSE 11.1 KDE

NTFS access in Linux

Use ntfs-config to allow full access to the NTFS partitions
If errors:
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sdb5': Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.

Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:

mount -t ntfs-3g /dev/sdb5 /media/PAGEFILE_ -o force

Or add the option to the relevant row in the /etc/fstab file:

/dev/sdb5 /media/PAGEFILE_ ntfs-3g force 0 0

Instant Boot & Inteligent Energy Saver

Quelle

Hier gibt es zwei Optionen: zum einen den "fast mode" und zum anderen den "regular mode". Aktiviert man Instant Boot in einem der beiden Modi, so startet der PC beim nächsten Herunterfahren selbstständig neu, bootet abermals und fährt sich dann erst herunter.

Anschließen bootet der PC deutlich schneller, der Vorgang erinnert an ein Aufwachen aus dem Standby-Modus (S3 STR) bzw. Ruhezustand (regular mode). Der Test dieser Funktion ist denkbar simpel - wir booten das System einmal mit aktiviertem Instant Boot und einmal ohne.

Modus	Dauer
Instant Boot (fast mode)	16 s
Instant Boot (regular mode)	21 s
Standby S3 (STR)	15 s
Standby S4 (Ruhezustand)	20s

Die Quintessenz aus unserem Vergleich ist schnell gezogen: zeitlich bringt Instant Boot nichts. Die sogar geringfügig längere Bootzeit ist bedingt durch das automatische Laden des Instant Boot Clients beim Windowsstart - was man nicht vermeiden kann. Liest man sich die Dokumentation zu diesem Feature einmal genau durch und sieht nicht nur das individualistische Video dazu an, eröffnet sich einem auch schnell wieso.

So soll und kann Instant Boot gar nicht schneller als der klassische S3- oder S4-Modus sein. Denn Instant Boot bedient sich exakt dieser Modi. Der einzige Vorteil soll das vermeiden von „accumulated garbage data" sein. Was das genau für überflüssige Daten sein sollen und welche Vorteile deren Vermeidung für den Anwender genau bringten erklärt ASRock leider nicht. Wir konnten in der Praxis keinen Unterschied entdecken.

Intelligent Energy Saver

Intelligent Energy Saver, kurz IES, soll (elektrische) Energie sparen, indem einzelne Phasen der CPU-Versorgung - je nach Bedarf - zu oder abgeschalten werden. Zwar bewirbt ASRock dieses Feature nicht explizit in Zusammenhang mit dem A780GM-LE, allerdings wird es von dem passenden Softwaretool unterstützt. Aktiviert man IES in dem Tool, so wird angezeigt, wie viele Phasen der Versorgung momentan aktiv sind. In unserem Fall waren im Idle zwei Phasen aktiv und unter Last vier Phasen.

In der Übersicht nun die Energieersparnis, gemessen mit der 9350e-CPU:

Modus	IES	normal	delta
Idle	55	57	2 W / 3,5%
Vollast	115	115	0 W / 0%
3 Kerne Last	106	108	2 W / 1,9%
2 Kerne Last	94	99	5 W / 5,6%
1 Kerne Last	79	85	6 W / 7%

Wie zu erwarten, bringt IES nur im Vollast-Modus nichts. Aber ist bereits nur einer von drei Kernen nicht belastet ,macht sich ein Unterschied bemerkbar. Gerade bei der Belastung nur eines CPU-Cores, einer sicher häufigen Alltagssituation, lassen sich immerhin ca. sieben Proeznt Strom einsparen. Somit ist es auf alle Fälle empfehlenswert, dieses Feature auch zu verwenden.

AMD Phenom-ene: X3 vs. X4

Quelle

Inhaltsverzeichnis

• 1 – Test AMD Phenom X3 8750, 8650 und 8450
• 2 – Phenom X3 mit drei Kernen
• 3 – Modellübersicht aller Phenom X4 und X3
• 4 – Verlustleistung
• 5 – Verlustleistungsmessung: Phenom X3 nur XX Watt
• 6 – AMD Overdrive Tool
• 7 – Preise: Phenom X3 8450 ab 92 Euro?
• 8 – Phenom X3-Komplettsystem für nur 310 Euro
• 9 – Performance: Vergleich bei 2.40 GHz
• 10 – Performance: Phenom X3 8750 nur 4 % langsamer als 6400+
• 11 – Performance: Phenom X3 8450 15% langsamer
• 12 – Performance: Phenom X3 8750 vs. Core 2 Duo E6550
• 13 – Testsetup und verwendete Komponenten
• 14 – Software-Konfiguration
• 15 – Benchmarks und Einstellungen
• 16 – 3D-Games: UT2004, Prey
• 17 – 3D-Games: Quake 4, Warhammer

• 18 – 3D-Games: Supreme Commander, Serious Sam 2
• 19 – 3D-Rendering: Cinema 4D, 3D-Studio Max
• 20 – Anwendungen: AVG, WinRAR
• 21 – Anwendungen: Photoshop, PDF
• 22 – Anwendungen: Deep Fritz
• 23 – Audio Encoding: iTunes, Lame
• 24 – Synthetisch: Sandra CPU
• 25 – Synthetisch: Sandra Memory
• 26 – Synthetisch: Sandra Multimedia
• 27 – Synthetisch: PC-Mark
• 28 – Synthetisch: 3DMark06
• 29 – Video Encoding: Xvid, Pinnacle Studio
• 30 – Video Encoding: Premiere, Mainconcept
• 31 – Video Encoding: HDTV, DivX
• 32 – Video Encoding: CloneDVD
• 33 – Fazit: Phenom zum Hammer-Preis - hoher Stromverbrauch im Leerlauf
• 
  

---

• 1 – Phenom von AMD mit bis zu vier Kernen – ein Vergleich
• 2 – Phenom: Vor- und Nachteile
• 3 – Die Phenom Prozessor-Familie von AMD
• 4 – Testkonfiguration und Benchmarks
• 5 – Ergebnisse: 3D-Spiele

• 6 – Ergebnisse: Video-Benchmarks
• 7 – Ergebnisse: Audio und Anwendungen
• 8 – Ergebnisse: Synthetische Benchmarks
• 9 – Fazit

---

Vergleich von 3 AMD Prozessoren
Phenom X3 8450 vs. Athlon X2 6400+