Bienvenido! - Willkommen! - Welcome!

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

Saturday, March 26, 2011

img image to iso standard image converters

convertir a imagen ISO una imagen de CD que se encuentra en formato IMG (son cuatro archivos del mismo nombre, pero con distinta extensión, .img, .sub, .ccd, y .cue).
En MS Windows es posible hacerlo con WinISO, CloneCD, ISOBuster, DaemonTools

Just rename it. Most image files are ISO images.
Use MagicISO or PowerISO 
Free img to iso converter download - small and easy CD/DVD image converter for Windows, converts IMG image to an ISO standard image.
Info: IMG is a CloneCD disc image file.
Linux converter:  MountISO 
Más fácil aún... resulta que MountISO hace uso de CCD2ISO, así que en realidad nos basta con ese pequeño programa, que utilizaremos desde la consola de comandos.
Para ello nos descargamos el archivo en formato tar.gz, lo descomprimimos, y ejecutamos lo siguiente:
make install

El uso a nivel de comandos es muy sencillo:
ccd2iso imagen.img imagen.iso
Para convertir imágenes NRG a ISO: usar NRG2ISO
convertir a ISO las imágenes en formato MDF (de Alcohol120%) mediante MDF2ISO.
Convertir imagen de formato .BIN (con su correspondiente .CUE) a formato ISO: Aquí descargar BIN2ISO ya compilado para usarlo en GNU/Linux. Descomprimir el paquete y mover el archivo "bin2iso" al directorio /usr/bin de l sistema, dar permisos de ejecución, y listo, ya puedes convertir tus imágenes .BIN en .ISO tecleando bin2iso imagen.bin.

Wednesday, March 23, 2011

Mac data recovery

Mac OS X in VirtualBox on Windows

[graphics at source]
We've shown you how to install Snow Leopard in VMWare, but if you haven't purchased VMWare, you can now do it using previously mentioned, free program VirtualBox. Apart from VirtualBox, you'll also need an OSX86 ISO. The group Hazard has put out a good patched Snow Leopard installer that should do fine (just search for it on Google).
Of course, if you feel bad about downloading the ISO of Snow Leopard, you could always go buy a copy to feel a bit better, karmically.
After you have them both, install Virtualbox. Open up Virtualbox and click on New at the top left.
At the Create New Virtual Machine window, click Next.
At this window type OSX as the name and it will automatically change the system and version. The next window will let you choose your RAM amount:
If you can spare it, crank it up as far as you can go, but 1024MB should be sufficient.
This is where you'll make your hard disk. 20GB should be enough so what it comes down to is dynamic or static. Dynamic will expand on use and Static will be a fixed 20GB no matter how much data is actually in it. Dynamic is better for not taking up your hard drive but static should give you better performance. I normally use dynamic. Click next unless you want to change it from dynamic or if you want to increase the disk size or file location.
It will show a summary of your settings. Click Finish, then click Settings at the top. At this window click on System in the left pane and uncheck Enable EFI.
Now click on the Storage button on the left. From there click on Empty under the OSX.vdi, then click the folder with the green arrow on the right (next to "CD/DVD Device").
At this window click the Add button at the top. Then find and add the OSX86 ISO you downloaded earlier. Then highlight it and click Select at the bottom. Then click OK, and hit the Start button on the left side of the main VirtualBox window.
As it starts up, click inside the window and hit F8. Then at the boot: prompt type –v so you can see what exactly went wrong if something does go wrong. All the services will run and eventually you should come to the language screen. Choose your language then click next. If you are unable to move your mouse around then hit Right-Ctrl + I. Click Continue and Agree. Next, start up Disk Utility by going to Utilities in the menu bar.
At this screen highlight 20GB VBOX HARDDISK. Then click the Erase tab, name it what you want in the name box and click the Erase button on the bottom right of the window. It shouldn't take long. Then click Disk Utility in your menu bar and quit it. Now you're back at the installer. Highlight the drive that is now showing up and click Continue.
The next window is important. Click the Customize button on the bottom left.
AMD Users check:
Any Updates included at the top.
Drop down Kernels and choose Legacy kernel.
AMD option below System support.
Intel Users check:
Any Updates included at the top.
Drop down bootloaders and check the newest Chameleon.
Drop down Kernels and choose Legacy kernel.
Then click Done and hit the Install button. To speed up the process you can click Skip when the disc check pops up.
As soon as it says "installation finished" and starts counting down to restart, press the right Ctrl key. Click on Devices at the top of the VirtualBox window, hit CD/DVD Devices and click Unmount CD/DVD Device. Then go to Machine > Reset and click Reset at the prompt. Next you'll see the Chameleon loader and then OS X will begin to boot.
After it boots you will see the setup screens for OS X! You're good to go. The only hiccup I've found is that it can only be virtualized with one core. It could be the OSX disc I was using or it might not be. And I have yet to find the right kext that will allow audio to work and the resolution is limited also. But other than that you'll have a fully functioning OSX virtualized!
Update: I'd like to post some answers to the resolution and audio. I should have looked around before posting this but I just didn't have the time. So anyways heres what you can do:
To fix the resolution issue, open Finder and go to the OS X drive on the left. Open the folder called Extras. Right Click on the file com.Apple.Boot.plist and open it with TextEdit. Under the first insert this:
Graphics Mode
or another compatible resolution. Select "Save As" at the top and save it to the desktop, unchecking the check under Unicode and then save it as After that drag and drop it into the extras folder and overwrite the original file, entering your password when prompted.
Instructions for the sound issue can be found here.
Don't install system updates. If you want updates you'll have to install another iso distribution with the updates on it. If you install the updates directly from apple it messes with the custom kexts and chameleon. Just a forewarning.
And for those of you getting boot issues try choosing a different version of Chameleon or a different kernel. Sometimes that seems to help. And If your getting one of the USB errors then try disabling USB in the VirtualBox settings and see if that helps.

VirtualBox: Windows XP disk on virtual SCSI hd

I am still not able to install Windows XP (SP3) on SATA hard disk, so here you will find all you need to install XP on virtual SCSI (Lsilogic) hard disk.
The driver(s) and the tools except Oracle VM VirtualBox is available at the following link: 
You can also download the packages from their respective official sites (preferable).
1.First you need the SCSI driver for F6 install, I used Device Doctor to find the right one, you can download the driver from the previously mentioned link. Look for a file name starting with “LSI_SAS_MPT_Windows..”.
2. Now to create a virtual floppy disc get VFD at: . I have uploaded the floppy image I created to install 32-bit Windows XP SP3 ( xp_x86_lsi.vfd).
You will also find an appliance (XP_SP3.ova) without any attached hard drive to get you started quickly.
The trouble you have to go through to do this is the reason I prefer to use VMware Player but VirtualBox having a Open Source version is good enough reason to make things work and write this post. As far as the SATA installation is concerned I am not trying any time soon.
Device Doctor available at:
Create virtual floppy drive(s) and disk(s). Project hosted at MD5:669B32553C59D23B6E47C6CD2B7C0125 SHA-1:CDEFDF1730698F169734ED91D75E67B5CEEA5542
Virtual floppy disk with LSI SCSI 32-bit Windows XP driver for F6 installation on Oracle VM VirtualBox 4.0. MD5:DE53B8E70851C5EBBDE67BC6E9504F76 SHA-1:A8C2753E8B3E326A070AAAB47995D8DDB841077F

Monday, March 21, 2011

Arranque limpio en Windows XP


Método 2: iniciar manualmente XP con un arranque limpio (sólo para usuarios avanzados)
 Esta sección está pensada para usuarios de equipos avanzados. Si no se siente cómodo con la solución avanzada de problemas, puede pedir ayuda a alguien o ponerse en contacto con el servicio de soporte técnico. Para obtener información acerca de cómo ponerse en contacto con el servicio de soporte técnico de Microsoft, visite el siguiente sitio web de Microsoft: (
Para iniciar manualmente Windows XP con un arranque limpio, siga estos pasos:

Paso 1: iniciar la Utilidad de configuración del sistema

  1. Haz clic en Inicio y en Ejecutar, escriba msconfig y haz clic en Aceptar.
  2. Aparece el cuadro de diálogo Utilidad de configuración del sistema.

Paso 2: Configurar las opciones de inicio selectivo

  1. En el cuadro de diálogo Utilidad de configuración del sistema, haga clic en la ficha General y, después, en Inicio selectivo.
  2. Haga clic para desactivar la casilla Procesar archivo SYSTEM.INI.
  3. Haga clic para desactivar la casilla Procesar archivo WIN.INI.
  4. Haga clic para desactivar la casilla Cargar elementos de inicio. Compruebe que están activadas Cargar servicios del sistema y Usar archivo BOOT.INI original.
  5. Haga clic en la ficha Servicios.
  6. Haga clic para activar la casilla Ocultar todos los servicios de Microsoft.
  7. Haga clic en Deshabilitar todo y, a continuación, haga clic en Aceptar.
  8. Cuando se le pregunte, haga clic en Reiniciar para reiniciar el equipo.

Paso 3: Iniciar sesión en Windows

  1. Si se le pide, inicie sesión en Windows.
  2. Al recibir el mensaje siguiente, active la casilla de verificación No volver a mostrar este mensaje o iniciar la Utilidad de configuración del sistema cuando se inicie Windows y, a continuación, haga clic en Aceptar.

    • Ha ejecutado la utilidad de configuración del sistema para realizar cambios en la forma en que Windows se inicia.
    • La Utilidad de configuración del sistema está actualmente en modo de Diagnóstico o de Inicio selectivo, haciendo que se muestre este mensaje y que la utilidad se ejecute cada vez que se inicia Windows.
    • Elija el modo de inicio Normal en la ficha General para iniciar Windows normalmente y deshacer los cambios que efectuó con la Utilidad de configuración del sistema.

Paso 4: paso opcional para deshabilitar las características

Si el arranque limpio ha corregido el error, no tiene que realizar este paso.

Importante: si el problema no se ha corregido y tiene que seguir este paso, este procedimiento quita de manera permanente todos los puntos de restauración del equipo. La característica Restaurar sistema utiliza los puntos de restauración para restaurar el equipo a un estado anterior. Si quita los puntos de restauración, no podrá restaurar Windows a un estado anterior.

Este paso deshabilita temporalmente características de Microsoft como Plug and Play, conexión de red, registro de eventos e informe de errores.
  1. Haz clic en Inicio y en Ejecutar, escriba msconfig y haz clic en Aceptar.
    Aparece el cuadro de diálogo Utilidad de configuración del sistema.
  2. Haga clic en la ficha General, haga clic para desactivar la casilla Cargar servicios del sistema y, a continuación, haga clic en Aceptar.
  3. Cuando se le pregunte, haga clic en Reiniciar para reiniciar el equipo.
Si estos pasos le han ayudado a iniciar el equipo en un estado de arranque limpio, ya ha terminado. Consulte la sección "Pasos siguientes" en caso de que estos pasos no le hayan sido útiles. Si tiene que devolver a su equipo a un estado de inicio normal, vaya a "Pasos para configurar Windows para utilizar un estado de inicio Normal".

Pasos para configurar Windows para utilizar un estado de inicio Normal

Después de haber usado el arranque limpio para resolver el problema, siga estos pasos para configurar Windows XP para que se inicie normalmente.
  1. Haga clic en Inicio y, a continuación, en Ejecutar.
  2. Escriba msconfig y haga clic en Aceptar.
    Aparece el cuadro de diálogo Utilidad de configuración del sistema.
  3. Haga clic en la ficha General, haga clic en Inicio normal: cargar todos los controladores de dispositivos y servicios y, a continuación, haga clic en Aceptar.
  4. Cuando se le pregunte, haga clic en Reiniciar para reiniciar el equipo.

Más información
Para obtener más información acerca de cómo solucionar problemas de inicio, hag...

Para obtener más información acerca de cómo solucionar problemas de inicio, haga clic en el número de artículo siguiente para verlo en Microsoft Knowledge Base:
308041  ( ) Solución avanzada de problemas generales de inicio en Windows XP

Si estos métodos no han solucionado su problema, puede consultar el sitio web de...

Si estos métodos no han solucionado su problema, puede consultar el sitio web de Servicios de soporte al cliente de Microsoft para encontrar soluciones alternativas. A continuación, se mencionan algunos servicios que se encuentran en dicho sitio web:
  • Búsqueda en Microsoft Knowledge Base ( : puede buscar información de soporte técnico y herramientas de autoayuda para productos de Microsoft.
  • Centros de soluciones ( : puede consultar las preguntas más frecuentes específicas de productos y lo más destacado de soporte técnico.
  • Grupos de noticias de soporte técnico de Microsoft ( : consulte con sus homólogos, colegas y los Profesionales más valiosos de Microsoft (MVP).
  • Otras opciones de soporte técnico ( : puede utilizar el sitio web para formular una pregunta, llamar a los Servicios de soporte al cliente de Microsoft o enviar comentarios.
Si el problema persiste, debe ponerse en contacto con el Servicio de soporte técnico: (

Saturday, March 19, 2011

MS office

Virtualization and microprocessors
Processor Year Bus width Description
4004 1971 4 First microprocessor.
4040 1972 4 Enhanced version of the Intel 4004 processor.
8008 1972 8 First 8-bit microprocessor.
8080 1974 8 Successor to Intel 8008 CPU.
8085 1976 8 Enhanced version of Intel 8080 CPU.
8086 1978 16 First generation of Intel 80x86 processors.
8088 1979 8/16 8 bit (external) version of Intel 8086 CPU.
80186 1982 16 Next generation of 80x86 processors. Used mostly as embedded processor.
80188 1982 8/16 Next generation of 80x86 processors. Used mostly as embedded processor.
80286 1982 16 Second generation of 80x86 processors:
new instructions, protected mode, support for 16MB of memory.
80376 1989 32 Embedded 32-bit microprocessor based on Intel 80386.
80386 1985 32 Third generation of 80x86 processors: 32 bit architecture, new processor modes.
80486 1989 32 Fourth generation of 80x86 processors: integrated FPU, internal clock multiplier.
80486 overdrive 19?? 32 Overdrive/Upgrade processors for Intel 80486 family.
Pentium 1993 32 Fifth generation of x86 processors: superscalar architecture, MMX.
Pentium II 1997 32 Sixth generation of x86 processors.
Celeron 1998 32 Low-cost version of Pentium II, Pentium III and Pentium 4 processors.
Timna   32 Low-cost microprocessor with integrated peripherals (never released)
Pentium III 1999 32 Enhanced and faster version of Pentium II.
Pentium 4 2000 32, 64 New generation of Pentium processors.
Pentium M 2003 32 Pentium microprocessor specifically designed for mobile applications
Celeron D 2004 32, 64 Low-cost version Pentium 4 desktop processors.
Celeron M 2004 32 Low-cost microprocessor specifically designed for mobile applications
Pentium D 2005 64 Dual-core CPUs based on Pentium 4 architecture.
Pentium Extreme Edition 2005 64 Dual-core CPUs based on Pentium 4 architecture.
Xeon 200? 32, 64 High-performance version of Pentium 4 CPU.
80860 1989 32 Embedded 32-bit microprocessor with integrated 3D graphics.
80960 1988? 32 Embedded 32-bit microprocessor.
Itanium 2001 64 High-performance 64-bit microprocessor.
Core Solo 2006 32 32-bit single-core microprocessor.
Core Duo 2006 32 32-bit dual-core microprocessor.
Core 2 2006 64 64-bit microprocessor.
Pentium Dual-Core 2007 64 64-bit low-cost microprocessor.
Celeron Dual-Core 2008 64 64-bit low-cost microprocessor.
Atom 2008 32, 64 Ultra-low power microprocessor.
Core i7 2008 32, 64 64-bit microprocessor.
Core i5 2009 32, 64 64-bit microprocessor.
Core i3 2010 32, 64 64-bit microprocessor.

Hamachi2 Error de conexión al motor

El error "No se pudo conectar al motor" es causado por el túnel del motor de Hamachi2 o no se inicia, o se encuentra en estado de error. Para ver el estado del motor:
  1. Pulse las teclas de [Windows] y la [R] en el teclado.
  2. En el cuadro Ejecutar escriba services.msc, y pulse [Intro]
  3. Busque el Túnel del Motor de LogMeIn Hamachi 2.0
Si el motor se encuentre en cualquiera de los siguientes estados:
  • Comenzado
  • A partir de Comenzar
  • Parando
A continuación, intente reiniciar el servicio o todo el equipo.
Si el servicio no se está ejecutando, o cuando intenta iniciarlo recibe un error, compruebe la ubicación siguiente de Registro.
Debe haber un Valor alfanumérico de cadena (REG_SZ) etiquetados EngineConfigDir. Si esto no está presente, créelo haciendo un clic derecho en el espacio en blanco y seleccionando Nuevo -Valor de Cadena. Usted puede entrar en cualquier ubicación de la carpeta que desee, y creará los archivos necesarios allí para que el motor funcione.
Descargar archivo de
descomprimir en carpeta C:\Archivos de programa\LogMeIn Hamachi
Se crea un acceso directo en el escritorio Hamachi2svc con el ejecutable descargado, cuya terminacion es ".svc", y cada vez que quieras iniciarlo lo haces desde el nuevo acceso directo, no desde el anterior.

Error message changing DNS

Warning: Multiple default gateways are intended to provide redundancy to a
single network such as and Intranet or the Internet. They will not function
properly when the gateways are on two separate, disjoint networks (such as
one on your intranet and one on the Internet). Do you want to save this

It's telling you to remove the default gateway from one of your connections as you should only have one.
But that error message is still saying you are connected to two different networks.
Reset everything temporarily to dynamic and then run an ipconfig. What are the numbers? Does your router allow you to reserve an ip address for a specific network adapter? Might be a better way to go

The GNU-Darwin [5] project works on porting the GNU system to Darwin [6], the basis of the proprietary MacOS X. Darwin itself is based on FreeBSD and Mach 3.0 and currently runs on PowerPC-based architectures. Apple is working on a port for Intel-architectures, however. So after GNU/Linux and GNU/Hurd there will be a third GNU-based system available.
A very interesting feature of the GNU-Darwin system is to be able to run Macintosh-applications parallel to the well-known Unix-programs. This allows the direct comparison of Macintosh- & GNU-based programs, something that has been impossible before. So this feature makes GNU-Darwin very well suited for Mac/Unix hybrid-structures and with the port of SAMBA to GNU-Darwin heterogenous networks with Mac/Unix/Windows will be easy to implement.
But of course the main use of GNU-Darwin is not to be able to run proprietary software. It will rather create another bridge between the Macintosh platform and Free Software as the user will quickly realize that there is more Free Software for his computer than there is proprietary software. Software developed on GNU-Darwin is better-suited for interoperability with MacOS X, too, so Free Software can be brought into this world.
The big amount of available Unix-based Free Software and the unique capabilities for heterogenous structures and parallel development are strong arguments for GNU-Darwin instead of MacOS X.
In addition, GNU-Darwin offers several advantages over the LinuxPPC-Project which is the reason why a user-migration to GNU-Darwin can be seen. First of all GNU-Darwin is (like GNU/Hurd) microkernel-based which gives it capabilities that the Linux kernel cannot match. Also the hardware support for Darwin is done by Apple itself as it also is the basis for MacOS X. So a better hardware support is to be expected here.
But not everything is better. Although the contributions of the GNU-Darwin project are of course released under the GNU General Public License, Darwin itself has been released by Apple under the Apple Public Source License (APSL). In version 1.1 this license did not qualify as Free Software for three important reasons [7].
First of all it was forbidden to make changes for personal use without making those changes public. In the perception of the GNU Project, the right to change things for personal use only is closely related with the right for privacy; that is why the GPL was designed to allow this.
Furthermore the developer and non-scientific user of a modified version was forced to report to a specified institution (in this case Apple). This central control is in direct contradiction to the thought of Free Software.
And finally there was a disclaimer that allowed Apple to terminate the license and stop the further use of the software at any point if copyright or patent claims are being made against Apple. This made every user on this planet dependent on the very problematic U.S. patent-system.
Version 1.2 of the APSL was released in January 2001 and it solves a big part of the problems - the restriction on private modifications and the disrespect for privacy remains, however.
So in a way the APSL takes step after step into the direction of the NPL which is definitely a Free Software license although it does allow a proprietarization of the source-code. Even if the APSL finally gets to the point of the NPL, it would still be less than satisfactory as it would probably still be incompatible with the most often used Free Software license, the GPL.
So the situation is comparable to that of KDE a few years ago in a way, as it is about a clean Free Software project built on a weak fundament and hence in danger of being cut off at the knees by legal means. Because of this the GNU-Darwin project takes a stand to release Darwin under the GNU General Public License. Especially for this advocacy work, Michael L. Love, one of the participants of GNU-Darwin, asks for support from the community. In the eyes of the GNU-Darwin project, GNU-Darwin will only be truly free once Darwin is GPL'ed.
The current technical issues are porting more packages to GNU-Darwin and the creation of a CD-Distribution. In the long run it is planned to put the special abilities of GNU-Darwin to good use.
As the team currently consists of only six active developers, there is a wide field of possible activities for interested people to choose from. Especially developers with experiences regarding Mozilla, SDL, GNOME & Audio-Support (ALSA) will be received with open arms.
By the way: the origin of GNU-Darwin is the desire of Michael L. Love to use his Apple for protein-crystallography as this is his normal occupation.


Packages available now from GNU-Darwin

# of packages
total unique packages6366
total overall10200







Friday, March 18, 2011

PureDarwin Xmas

The PureDarwin project announces the immediate availability of "PureDarwin Xmas", a developer preview of the upcoming operating system based on Apple's Darwin 9 sources and other Open Source projects such as X11. At the same time, the PureDarwin project would like to invite the community to discuss, participate and contribute. The developer preview is available for download as a pre-configured virtual machine for VMware Fusion 2.0 on Macintosh, and the code used to generate it is available in a Subversion repository.
Darwin is the Open Source operating system from Apple that forms the basis for Mac OS X, and PureDarwin is a community project to make Darwin more usable (some people think of it as the informal successor to OpenDarwin). One current goal of this project is to provide a bootable ISO of Darwin 9.x (the version that corresponds to 10.5.x Leopard). Another goal of this project is to provide additional documentation.
puredarwinxmas.tar.bz2 (md5: fd0ade4da224475e5dc33c2c11d9d0bc)
VMware Fusion 2 virtual machine or VirtualBox
See the google code repository for stuff and scripts.
See for instructions on how to use this repository
List of all files in Darwin
build 9C31 which were
available as binary
roots as of today 
297k v. 4 Jan 30, 2009 
Aladin Quet

PAM module needed
to create a user security
session for login.
See the
"User Management"
page under "Users"
for more details. 
2k v. 2 Mar 19, 2009
Aladin Quet

This is expected to work.

  • with VMware
    • Darwin 9 boots in a VMware Fusion 2 virtual machine on a Macintosh
    • DTrace 
    • X11
    • ZFS
  • with VirtualBox

Known issues

These issues will be addressed in future releases.
  • Works with VMware Fusion 2 on Macintosh, VirtualBox on Linux
  • login does not work, user is working as root
  • Lots of error messages during the boot process
  • X11 does not work with mach_kernel.voodoo
  • WindowMaker will not be the default WM
  • halt doesn't work reliably, "shutdown -h now" doesn't work reliably
  • /var/log gets filled quickly
  • No network
  • Due to a restriction of VMware Fusion 2.0.1, you cannot run PureDarwin Xmas on 32-bit CPUs such as the Core Duo in the first-generation Intel Macs (Thanks gireesh). However, you can downgrade to VMware Fusion 2.0.0 which seems to run Darwin fine on a 32-bit CPU (thanks Stuart).
Darwin Server running
A PureDarwin 9 server is up and running (in private, for now - see below). 
We have created a custom PureDarwin 9 ISO with the scripts and tools from our repository as described here, installed networking, OpenSSH, Apache, MacPorts, Netatalk, configured Bonjour, even installed TightVNC for graphical applications... set up SpeedStep to save some power... all runing nicely.
Thanks for everyone who has contributed toward making PureDarwin this viable.
At the moment we are looking for a co-location and hardware sponsor so that we can run a PureDarwin 9 server system 24/7 and make available its services publicly.

VirtualBox 4
Saving the state of the machine
When you click on the "Close" button of your virtual machine window (at the top right of the window, just like you would close any other window on your system), VirtualBox asks you whether you want to "save" or "power off" the VM. (As a shortcut, you can also press the Host key together with "Q".)
The difference between these three options is crucial. They mean:
  • Save the machine state: With this option, VirtualBox "freezes" the virtual machine by completely saving its state to your local disk.
    When you start the VM again later, you will find that the VM continues exactly where it was left off. All your programs will still be open, and your computer resumes operation. Saving the state of a virtual machine is thus in some ways similar to suspending a laptop computer (e.g. by closing its lid).
  • Send the shutdown signal. This will send an ACPI shutdown signal to the virtual machine, which has the same effect as if you had pressed the power button on a real computer. So long as the VM is running a fairly modern operating system, this should trigger a proper shutdown mechanism from within the VM.
  • Power off the machine: With this option, VirtualBox also stops running the virtual machine, but without saving its state.
    WarningThis is equivalent to pulling the power plug on a real computer without shutting it down properly. If you start the machine again after powering it off, your operating system will have to reboot completely and may begin a lengthy check of its (virtual) system disks. As a result, this should not normally be done, since it can potentially cause data loss or an inconsistent state of the guest system on disk.
    As an exception, if your virtual machine has any snapshots (see the next chapter), you can use this option to quickly restore the current snapshot of the virtual machine. In that case, powering off the machine will not disrupt its state, but any changes made since that snapshot was taken will be lost.
The "Discard" button in the VirtualBox Manager window discards a virtual machine's saved state. This has the same effect as powering it off, and the same warnings apply.

Error 1303 installing OOo 3

==================== .
You will receive the above error if either of the following is true for the folder in which you are installing Office:
  • The SYSTEM group does not have Full Control privileges.
  • The Everyone group does not have Full Control privileges. 
READ this

""If you perform an administrative installation using setup /a, you need to make sure that the file msvc90.dll is installed on the system. This file is required for to start after an administrative installation. You can get the file from ... 4B9F2BC1BF""
Once installed try to install open office again and it should work.
For example, this problem has been reported to occur when there were only Read permissions on the following folders or any other subfolders of these folders:
  • \Program Files\Microsoft Visual Studio
  • \Program Files\Common Files\Microsoft Shared
  • \Program Files
  • \Program Files\Common Files
Even though Microsoft Office is being installed into the \Program Files\Microsoft Office folder, there are shared features that must be installed into other folders on your hard disk.
 To resolve this problem, ensure that you have the necessary permissions on your hard disk or disks. To do this, follow these steps.
NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
  1. In Windows NT Explorer, select the folder.
  2. Right-click the folder, and then click Properties on the shortcut menu.
  3. On the Security tab, click Permissions.
  4. Select the Everyone group, and then click Full Control in the Type of Access list.
  5. Select the Replace Permissions on Subdirectories check box.
  6. Click OK.
  7. Click Yes to the prompt confirming whether you want to replace permissions on all subdirectories.
  8. Click OK in the folder name Properties dialog box (where folder name is the name of the folder that you selected in step 1).
  9. Run Office Setup.

Java Quick Starter


  • Platform(s): Windows 7, Vista, Windows XP, Windows 2000
  • Java version(s): 6.0

Java Quick Starter (JQS) improves initial startup time for most Java applets and applications. This feature was added to Java in release Java SE 6 update 10 (6u10) and will be available in all future releases.

JQS is enabled by default in Windows XP and Windows 2000 operating systems and is not necessary on Windows Vista as Vista offers its own pre-loading mechanisms. A process called jqs.exe will run in the background in order to allow quick startup. jqs.exe will be loaded after a Windows restart. Instructions on how to disable the JQS and the jqs.exe process are below.

The startup performance improvement is achieved by periodically pre-fetching some of the most heavily used Java files into memory (occupying no more than 20Mb of RAM). Later, when Java is launched, much less disk I/O is required which makes startup much snappier and noticeably faster.

Note: JQS service will perform runtime checks and stop running when a laptop is running on batteries. JQS service will resume when the power cord is plugged in, as performance benefit of JQS is largely dependent on overall system configuration.

Steps to disable Java Quick Starter:
  1. Click Start.
  2. Click Control Panel.
  3. Double click on Java Control Panel.
  4. Click Advance tab in Java Control Panel.
  5. Scroll to Miscellaneous entry and Expand.
  6. Uncheck the check box for Java Quick Starter.
  7. Click Ok and restart the system.

Tuesday, March 15, 2011

SMART and TestDisk

kaspersky AV

Monday, March 14, 2011

1610-Temperature violation detected

1610-Temperature violation detected
Waiting 5 minutes for system to cool
Press Esc key to resume booting without waiting for the system to cool.
WARNING: Pressing Esc is NOT recommended as the system may shutdown unexpectedly

HP Proliant ML350 G6
HP Proliant ML350 G3

HP ProLiant ML350 G3 - Torre - 1 x Xeon 3.06 GHz - RAM 256 MB - HD: ninguno/a - CD - LAN EN, Fast EN, Gigabit EN - Monitor : ninguno - 5 U
Especificaciones de detalle de este modelo (PDF)

HP / Compaq Smart Array 641 U320 64MB 133MHz PCI-X Controller 
  • 64MB of DDR-RAM of memory upgradeable to 128MB with the 64 MB BBWC Enabler
  • U320 SCSI interface
  • 133Mhz PCI-X

Saturday, March 12, 2011

Nuxeo Enterprise Content Management

The Nuxeo Document Management offering, Nuxeo DM, helps manage and track the flow of content through the business cycle. From initial capture and creation, sharing and collaboration, across approval, review and revisions, to the final publication and archiving, Nuxeo DM ensures that information workers can find, use, share and secure valuable corporate content.
Nuxeo DAM is a digital asset management solution that helps catalogue, process, store, retrieve, and distribute rich media content, including images, audio, and video.
For those new to ECM, a simple way to explain it is to use AIIM's official definition:
"Enterprise Content Management (ECM) is the strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists."
More specific examples of the above would include:
  • document management
  • digital asset management
  • records management
  • correspondence management
and more. More ambitious readers are welcome to read that entire AIIM document, which discusses additional issues related to all of the above, including collaboration possibilities, legal compliance issues, workflow tools and much more.

In addition, readers interested in current ECM market trends are welcome to read this Nuxeo World 2010 keynote address.

What is Nuxeo Enterprise Platform (EP)?

All of Nuxeo's ECM applications are built on top of what is called the Nuxeo Enterprise Platform, or "Nuxeo EP." Nuxeo EP is not, by itself, a downloadable and runnable product. It is, instead, Nuxeo's underlying, Java-based software platform, providing the technical infrastructure and high-level services needed to build customized ECM applications. While there is extremely detailed documentation on the architecture of Nuxeo EP, the following graphic should give you a general idea of how individual ECM products are constructed on top of Nuxeo EP:
As you can see, the common EP component is used as the basis for actual runnable "distributions" by simply adding package-specific code above the EP foundation.
Finally, all of the above requires a certain software infrastructure below that, including:
  • A Nuxeo-approved Java development suite, such as Oracle's Java 6 or OpenJDK 6,
  • An application engine, such as the JBoss application server or the Tomcat servlet engine,
  • A Nuxeo EP-approved underlying database, such as PostgreSQL, Oracle or Microsoft SQL Server, and
  • An operating system that supports all of the above, such as Linux, Windows or Mac OS X.
In short, because Nuxeo EP is fully Java-based, you have a great deal of flexibility in how you can set up a Nuxeo server. (Readers interested in the significance of the choice of the word "platform" here are welcome to take a few minutes to understand the difference between platforms, suites and condominiums to appreciate what makes Nuxeo's Enterprise Platform offering unique.)

The current Nuxeo "distributions" and their variations

At the moment, there are three primary Nuxeo distributions (all sitting above Nuxeo EP) that you can download and immediately start to run:
  • Nuxeo DM, Nuxeo's flagship Document Management product,
  • Nuxeo DAM, the Digital Asset Management software, and
  • Nuxeo CMF, Nuxeo's Case Management Framework product.
All of these can be downloaded from Nuxeo's download page and, based on the choice of underlying technology, you will generally have to choose what particular packaging you want for any given distribution, such as:
  • a standalone, JBoss-based Zip file,
  • a standalone, Tomcat-based Zip file,
  • an EAR file for JBoss, or
  • in some cases, a .deb-format file for Debian/Ubuntu installation
DIfferent Nuxeo distributions might have different packaging choices so you'll have to select from the available options for each package.
Finally, for those who simply want to test out Nuxeo DM or DAM, Nuxeo provides OVF-format, Ubuntu/Tomcat-based virtual machine (VM) images that can be run within either VMware or VirtualBox. These VM images are also available from the corresponding distribution download page.