Mar 4, 2015

How to Use Daemon Tools Lite

What is Daemon Tools Lite?

Daemon Tools Lite is a version of the Daemon Tools virtual drive emulator. It basically emulates that you have a CD/DVD drive on your system when you may not actually have one installed. This allows you to boot a CD or DVD image that is stored on your hard drive; these images can be games, movies or other applications. This lets you download ISO or MDS images ripped from the actual source and play them on your computer without installing a CD/DVD drive. It also runs faster than a hardware-installed drive which makes things smoother during the playback process.

How to use Daemon Tools Lite

First, you want to download Daemon Tools Lite and install it on your system. When you open it for the first time, you will have to set what you will call the drive. If you already have a CD/DVD drive installed, you want to ensure there are no conflicts with what is already installed. Once the drive is set, you can mount ISO, MDS or other mountable images. You right click on the logo in the toolbar to change settings, preferences and other ways you utilize Daemon Tools Lite. You left click to mount the image and begin using what you want to watch, play or interact with.

What can you do with Daemon Tools Lite

Daemon Tools Lite is used to do two things: You can use it to emulate a CD, DVD, HD or Blu Ray Drive and you can use it to create disc images from external media. Just by installing Daemon Tools, you have access to utilizing it as an emulation device for a drive installed of installing one. You then download or gain access to mountable images, mount them and use them just like you would if you had the disc, popped it into the drive and booted it up from there.

If you want to create images to store on your hard drive, you need the next version of Daemon Tools to do it. You simply pop in what you want to create as a mountable image, let Daemon Tools run through the process and then you have an ISO or MDS image to run, share or use in other ways without actually needing the disc to do so. Daemon Tools now supports creating mountable images from CD, DVD, HD or Blu Ray discs.

VMware ESXi – How to enable SSH Connectivity

VMware ESXi (formerly ESX) is an enterprise-class, type-1 hypervisor developed by VMware for deploying and serving virtual computers. As a type-1 hypervisor, ESXi is not a software application that one installs in an operating system; instead, it includes and integrates vital OS components, such as a kernel.

After version 4.1, VMware renamed ESX to ESXi. ESXi replaces Service Console (a rudimentary operating system) with a more closely integrated OS. ESX/ESXi is the primary component in the VMware Infrastructure software suite.

Step 1. Connect to ESXi console and press the Alt+F1 key combination.

Step 2. Type unsupported and then press . Note that nothing will appear on the screen whilst you type this.

Step 3. When prompted enter in the Root password and press.

Step 4. You will now be presented with a prompt on the console. From this prompt type vi /etc/inetd.conf

Step 5. vi (the file editor) has now opened the inetd.conf file. Using the direction arrows scroll through the lines until you reach the line that has #ssh and remove the hash (ie: #). This is effectively un-commenting this line so that the ssh service can be started.

Step 6. Now that you have made this minor file you want to save this change and exit out of the editor (vi). To do this press the ESC key (to put vi back into Command Mode) and then type :wq *Note: If you want to exit without saving any changes to the file then just press the ESC key (Command Mode) and then type :q!.

Step 7. With the SSH service now un-commented from this file we want to restart the ‘inetd’ process so that it starts again and reads in the newly altered file which will tell it to start the SSH service.

This is the part of the enabling SSH that has changed between minor revisions of ESXi as pre-ESXi Update 2 you would run the command ‘/sbin/ restart’ though for any release of ESXi Update 2 and more recent we have effectively kill the ‘inetd’ process to make it automatically restart again.

To do this we first need to find out what the process ID is of ‘inetd’. From the console command prompt type ps | grep inetd which will give you a result similar to the following.

Step 8. From running this command we can see that the process ID for ‘inetd’ is 1331. Now type kill –HUP where is the process ID seen in the previous step.

Finished! Congratulations – you should now be able to connect to your ESXi server via a SSH client such as Putty.


OpenMediaVault (OMV) is a complete and free open-source software (FOSS) network-attached storage (NAS) operating system (OS). It is developed and designed primarily for home use. Developer Volker Theile began development of OpenMediaVault in 2009 Previously he worked with the FreeNAS project.

OpenMediaVault is based on the Debian Linux distribution. It is licensed through the GNU General Public License v3 as published by the Free Software Foundation. OpenMediaVault uses Debian's official standard for package management, the Advanced Packaging Tool (APT). OpenMediaVault is designed to be configured and administered via the Webinterface, which is written in Ext JS, and is currently compatible with 32 and 64bit hardware


Through an Application programming interface (API),  OpenMediaVault is designed for features to be added to the Webinterface via the Plug-in System. The developer provides a group of core Plug-ins that can be installed via the Webinterface, while others are developed by the community. Many of the community supported Plug-ins are currently hosted in an unofficial plugin repository.

Other features include:
  • Multi Language web based graphical user interface (GUI)
  • Protocols: CIFS (Samba), FTP, NFS (Version 3 and 4), SSH, rsync, iSCSI, AFP and TFTP
  • Software-RAID with the RAID-Level 0, 1, 4, 5, 6 and 10 plus JBOD
  • Monitoring: Syslog, Watchdog, S.M.A.R.T., SNMP (v1/2c/3) (Read-Only)
  • Statistic reports per E-Mail
  • Statistic graphs for the CPU-workload, LAN transferrates, hard disk usage and RAM allocation
  • GPT/EFI partitioning >2 TByte possible, ext4 maximal 16TiB
  • Filesystems: ext2, ext3, ext4, XFS, JFS, NTFS, FAT32
  • Quota
  • User and groupmanagement
  • Access controls via ACL
  • Link Aggreggation Bonding, Wake On LAN
  • Plug-in system

Core Plug-ins are developed by Volker Theile
  • ClamAV - Antivirus software
  • Digital Audio Access Protocol - provides audio files in a local network (also for iTunes)
  • SAN and iSCSI - blockbased access datastores over the network
  • Lightweight Directory Access Protocol - Information request and changes of an Directory service
  • Logical Volume Manager - enables the possibility to create and administrate dynamic partitions
  • Netatalk - File-, time- and printserver for Apple Macintosh
  • Plug-in to support the use of an Uninterruptible power supply
  • easy changes to the Routing tables
  • Plug-in, which allows (automatic) backups to external USB hard disks
External Plug-ins are available via additional package repositories. The majority of those Plug-ins are developed by a group called OpenMediaVault Plugin Developers. The status of all Plug-ins can be viewed online.

Minimum System requirements
  • IA-32 (i386/i486) or AMD64 platform
  • 1 GiB RAM
  • 2 GiB hard drive, solid-state drive, or USB flash drive with static wear leveling support (NOTE: The entire disk is used as a system disk. This disk can not be used to store user data.)
  • 1 hard drive, solid-state drive, or USB flash drive for storing user data
  • 1 network card

Freenas 9.2.1 with Transmission and Couchpotato

Freenas 9.2.1 with Transmission and Couchpotato/Sickbeard as a DLNA-Server

I’m going to describe how to set up Freenas with the popular plugins couchpotato and transmissions to use them for downloading movies/series and streaming them via DLNA as well as mounting the storage on Linux.

With this setup, I manage my movie collection and my wanted movies with couchpotato, which uses transmission to download them. I also use Sickbeard to download TV series. Then I can stream them with the DLNA-server to my TV.

I’m running Freenas 9.2.1 on a HP ProLiant G7 MicroServer N54L (affiliate link). Freenas itself is running on a micro-USB stick. I’m not going to describe how to download and install Freenas on the stick, as described in detail in the docs.

Table of contents


After starting the server and waiting some minutes, Freenas is available under a web-front end. The URL is a local IP-address, which is shown when Freenas has finished starting. After opening it, you’re presented with the System information.


See the red alert in the upper right corner? Push it. It says that you need to set a password for the admin-account that you’re using.

Since Freenas 9.2.0 the first time you access the FreeNAS administrative interface, a pop-up window will prompt you to set the root password. You should set a hard to guess password as anyone who knows this password can gain access to the FreeNAS administrative GUI.

Network settings

Next on we have to edit the network settings. Go to network > Global configuration. There you can change the name of your Freenas, set the default gateway, name server and so on. Since I use my server at home, I set the gateway and name server to the address of my router. If you want to, you can enable the netwait feature. If enabled, your server will ping the addresses in the IP list when it starts to check if a network connection is possible.


General settings

There are some more settings that you should know about and edit. Open the System > Settings tab.
If your network is secure and only authorized people join it, you may let the “Protocol” option set to “HTTP”. Generally it is recommended to set it to “HTTPS“.

The next option defines the address and port your Freenas-installation listens to; set it to the IP-address the Freenas currently listens on. Set the HTTP-port to 80 and the HTTPS port to 443. Next on there are specific settings for your language, keyboard map and timezone. Set it according to your preferences.

If you’re not using a syslog server or directory service, leave the last two options empty.


Overview of storages and jails

The next steps will include creating storages and jails. To get a better understanding on how these components will work together, my beautiful girlfriend created two diagrams that show how the magic happens.

The first image shows the storages and jails that I created and what jails can access which storages.


The second image shows the steps that happen, when you want to download a movie or series via couchpotato/sickbeard.


Creating storage devices

Now is the time to add some storage to your server. That is the most important part and you should carefully read the documentation the Freenas community offers. I will not go into detail on what volumes or RAIDs to use. It mainly depends on your needs and what you’ve got hardware-wise.
My use-case is a simple movie- and music-streaming server with no personal or private information saved on it.

To simply create a new empty volume and attach disks to it, open Storage > Volumes > ZFS Volume Manager, give your new volume a name, add your disks and configure the layout.


Creating datasets

To logically separate your files, e.g. movies from music, you can create datasets. These datasets can have separate permissions, quotas, etc. allowing you more control over your data.

I created datasets for every kind of data I want to manage: movies, series, music, downloads and torrent-files. To create a dataset click on your created storage, then hit the “Create dataset”-button (the one that looks like an excel-document with a plus). There, set the name for the dataset. You can ignore all other options for now, as they are for advanced users.

Changing permissions of the storage

Since there are many plugins and users who want access to your storage, you’ll have to configure the permissions for it. The best way is to set the ownership of the storage to nobody and give read/write/execute permissions to everybody. You should only do this, if you trust the users of your network. To change permissions, click on the “Storage” tab, select the volume you want to edit and click the first button in the bottom line that displays hard disks and a key. There, set the Owner (user) to “nobody”, the Owner (group) to “nogroup” and activate all buttons in the mode. Type of ACL should be set to Unix. Tick the box that says “Set permission recursively” so all other folders and files in the volume will have the same permissions.


Adding sharing options

Since I want to access my music and movie collection not only with my TV but also with the computers I’m using, I have to add sharing possibilities. Freenas offers NFS, CIFS and AFP out-of-the-box. I don’t have an Apple-gadget or Windows machine at home, so I’ll only need NFS.


To add a NFS-share click on Sharing > Unix (NFS) Shares > Add Unix (NFS) Share. There, set the options “Mapall User” and “Mapall Group” to “nobody” and “nogroup” respectively. In the path, add all the storages-directories you want to share. You’ll have to create a separate share for every dataset. When you’re done, you can mount the directories via NFS, the address is the IP-address of your freenas-installation plus the folder you shared, e.g.

Installing the plugins

Installing plugins is very easy, as long as you stick to the available ones provided by Freenas. In the Plugins-menu, click on the plugins and then on Install, to install them. Each plugin is installed into a jail, a separate “operating system” in Freenas itself, but we’ll get to that in the next section.
When you’re done, your plugin-page should look like this:


Enabling access to the jails

SSH to your Freenas

You’ll likely need command-line access to your Freenas installation and to the jails as well. To enable SSH access to Freenas, go to Services and click on the screwdriver next to SSH. Tick the “Login as root with password” box and save the settings. After that, enable the SSH-Service by clicking the red OFF-button. Now you’re able to connect to your Freenas with SSH by entering the following line into your terminal-emulator of choice:

ssh root@

(change the address to the address of your Freenas)
Then enter the admin-password and you should be connected to your box.

Using Putty to enter your Freenas

If you’re on Windows and want to connect to your Freenas-installation using Putty, you have to enter the IP-address of Freenas into the “Host Name”-field, then press “open”.


If Putty cannot connect, you probably didn’t use the correct IP-address or you forgot to enable SSH.

Entering the jails

To enter one of the installed jails, type “jls” on the command-line. There you’ll see the available jails. To connect to them, enter “jexec # tcsh” where # is the number of the jail.

[root@freenas] ~# jls
   JID  IP Address      Hostname                      Path
     1  -               bit_1                         /mnt/media/jails/bit_1
     2  -               couchpotato_1                 /mnt/media/jails/couchpotato_1
     4  -               ownbutt_1                    /mnt/media/jails/ownbutt_1
     8  -               dlna_1                        /mnt/media/jails/dlna_1
[root@freenas] ~# jexec 8 tcsh
root@dlna_1:/ #

Adding storage to the jails

Now we’ll have to add the storage to the plugins, so couchpotato, transmission and the DLNA-server can access the same storage and work together. Since jails are separate systems in the server-OS itself, they cannot by default access other parts of your system.

To add the storage, go to Jails, click the plus next to the plugin, open the “Storage” tab and click “Add storage”. You’ll then have to enter the source and destination addresses. 

The source is the storage or dataset you created in the first place. If you did not create datasets before, you either have to do this now or create normal directories as sources with mkdir on the server.
The destinations are directories in the jails that get mapped to the storages outside the jails.
If the destination addresses in the jails do not exist, tick the “Create directory”-box.
To manually create the directories, enter the jail, then you can create directories with the following command:
mkdir -p /media/downloads

Then enter the following command the get the permissions right:
chmod -R 777 /media/downloads

The following part is really tricky as Transmission, Couchpotato and Sick Beard behave very differently with the directories they download data to. I had to edited the following configuration multiple times, so be sure to stay up to date.
  1. Transmission (bit_1): You need the torrent-directory, where Transmission looks for torrents and the download-directory where it downloads the data to.
    - Download-Source: /mnt/media/downloads
    - Download-Destination: /media/downloads
    - Torrent-Source: /mnt/media/torrentfiles
    - Torrent-Destination: /media/torrentfiles
    - Series-Source: /mnt/media/series
    - Series-Destination: /media/series
    - Movie-Source: /mnt/media/movies
    - Movie-Destination: /media/movies
  2. Couchpotato: You need the downloads-directory where transmission puts its data into; you’ll also need the movies-directory, where couchpotato moves the downloaded and renamed movies to.
    - Download-Source: /mnt/media/downloads
    - Download-Destination: /media/downloads
    - Movie-Source: /mnt/media/movies
    - Movie-Destination: /media/movies
  3. Sickbeard: You need the series-directory where Sickbeard puts its data into; you’ll also need the torrents-directory, where Sickbeard puts the torrent file for Transmission to download them.
    - Series-Source: /mnt/media/series
    - Series-Destination: /media/series
    - Torrent-Source: /mnt/media/torrentfiles
    - Torrent-Destination: /media/torrentfiles
    - Download-Source: /mnt/media/downloads
    - Download-Destination: /media/downloads
  4. MiniDLNA/Plex: You’ll need every directory where files are located that you want to play using DLNA, e.g. movies and series.
    - Movie/Series/Music-Source: /mnt/media/{movies|series|music}
    - Movie/Series/Music-Destination: /media/{movies|series|music}

Configuring the plugins

Now that you have added the storage to the plugins, you can finally start them. Go to the Plugins-page and click the red OFF-button of all plugins. After that, they should be listed as on, except for miniDLNA, which we’ll have to configure first, but not now.

You can find the IP-adresses of the plugins here:



The “watch”-directory where Transmission looks for torrent-files is normally:


That’s 50 characters and if you add the jail-directory to it, it exceeds Freenas’ directory-length limit of 88 characters, so you have to change this. Open up the Transmission-settings in the Plugins-tab of Freenas and edit the “Watch Directory” to “/media/torrentfiles” and the Download-Directory to “/media/downloads”.


Next open the transmission-address in your browser. You’ll see the main interface of Transmission. Click the screwdriver icon in the down left corner to edit the settings. There you’ll see the “download to” option. There should be “/media/downloads” now, too.


Now we’ll have to connect to the jail of transmission to manually edit a configuration file. Connect via SSH into your Freenas and connect to the jail as described in the chapter “Entering the jails”. Then you’ll have to edit the file, by entering this on the commandline:

edit /usr/pbi/transmission-amd64/etc/transmission/home/settings.json

But first, stop the plugin or else the settings will be overwritten. In the file, scroll down to the end where you can see the configuration-point called “umask”. Replace the “18” with a “0”. Save the file by pressing “escape”, then “leave the editor” and then “save changes”. After that start the plugin.


HolyK in the Freenas-forums mentioned a great front end for the remote transmission server, transgui. You can find it here or in your favorite package manager. It’s a nice replacement for the rather featureless web front end of transmission. It’s available for Linux and even Windows.

Transmission GUI

After you installed it, point it to the IP address of your transmission-server and then you can see the movies downloading and even add torrent- or magnet-links so they will be downloaded to you Freenas.


Open the couchpotato-address in your browser. You’ll be greeted with the install wizard. Scroll down to advance in the wizard. Define a user name and password in the General section if you’d like and leave the port to 5050.

In the downloaders section choose Transmission. As host enter the address of your Transmission jail (you can find the address in the jail-section of Freenas). Set the “Directory” to the “Transmission-Destination” you set earlier.


Scroll further down to “Move & rename the movies after downloading?” (skip the “Are you registered at any of these sites?”-part).

In the “from”-folder set the same folder you just used for the Transmission-directory. The “to”-directory is where the renamed movies will be stored. Set it to the “movie-source” configured in the chapter “Adding storage to the jails”. Tick the “Cleanup”-box so leftover files will be removed after renaming the movies.


After that, scroll further down and click the huge green button and you’re done with the wizard.
On the main page of couchpotato, click the screw-icon in the upper right to get to the configuration-page. There are many things to tweak here, but I’m not going into detail about them. Right now you have to open the “General” Tab, click on “Show advanced settings” and then enter “0777” in the fields “Folder CHMOD” and “File CHMOD” as shown below.

If you do not do this, you probably will be getting an error-message later in Transmission, when downloading files (the download stops at around 4MB)!



Install Sickbeard as usual and open the web interface. Since I currently only load movies with (free) torrents, there are some settings to make.

Open up the “Search Settings” tab in the config-tab.

Disable the search for NZBs and enable the search for torrents. In the Torrent Black Hole” enter the Torrent-Destination “/media/torrentfiles” you configured in the jail-storage and save the changes. It should look like this:


Then go to the “Search Providers” tab. There, check the box for “EZRSS” as it is the only free torrent search for series. If you are a member of any other torrent sites listed there, check the boxes for them and enter your credentials for this site. Again save the changes.

Next, go to the “Post Processing” settings.

In the “TV Download Dir”, enter your Series-Destination “/media/downloads” and check the “Scan and Process”-box. You can also edit additional settings on this page but they are not important right now. In the end your settings should probably look like this:


If you’re done, you can add new or existing shows and let them download!


Now you have the choice to either use MiniDLNA or the Plex MediaServer. If you want a nice interface to manage you music and movies, use Plex. If you only need a DLNA-server, use MiniDLNA as it is easy to configure. I’ll describe the installation and configuration for both.


Open the Freenas-front end, go to plugins and open the MiniDLNA-configuration. There, set the name of the MiniDLNA-server to anything you like and the Media-directory to the destination set in chapter “Adding storage to the jails”. Leave the other options as they are.


The DLNA-server will only scan for new files in its directory on restart, so if you are adding a movie and do not restart the DLNA-server, it won’t be available for streaming. To work around this issue, use the fix described here. After rebooting the DLNA-server should now scan for new files every 5 minutes.

Plex MediaServer

After installing the plugin, open the address of the Plexserver and you’ll be greeted with the End User License Agreement. Agree to it and jump to the “Get Started”-section. You can skip the register as it’s not needed. Leave the settings in “Basic Setup” as they are and go to the next step. There, you can add your music and movie-directories. Click on “add section”, then on “Movies” and insert into the second box your movies-directory. It should look like this:


Do this for your music and series, too.

If you have everything added, jump to the next section. There you can add some channels to use with Plex. I skipped them. Click “Next” and “Done” and your are it..done! Now you should see the dashboard of Plex filling with your movies and music.

DLNA is enabled by default, so you don’t have to do anything in this regard.


Now you are able to download movies with couchpotato and transmission and once they’re downloaded, they are automatically available on you DLNA-server for further streaming.

Mar 3, 2015

How-To Install FreeNAS To USB Drive

FreeNAS is an Open Source Storage Platform based on FreeBSD and supports sharing across Windows, Apple, and UNIX-like systems. It comes with a lot of protocols and services – here are some to mention: CIFS (samba), FTP, NFS, TFTP, AFP, RSYNC, Unison, iSCSI (initiator and target) and UPnP, Software RAID (0,1,5), ZFS, disk encryption, S.M.A.R.T/email monitoring with a WEB configuration interface (from m0n0wall). You can use it to build your own secure network file server to store all your important information on.

FreeNAS can be installed on compact Flash/USB key, hard drive or booted from LiveCD (version 7.x). Personally I like to install it on USB key to keep the software separate from the data on the hard disk. The rest of this article will show you how to do it. At the time of writing the current stable version is 8.0.2. The little graph on the right shown the number of downloads – this is what people download most:

They also have a 32-bit version (FreeNAS-8.0.2-RELEASE-i386.iso) and 64-bit version (FreeNAS-8.0.2-RELEASE-amd64.iso). You should choose 32-bit or 64-bit based on the hardware of the computer you are going to run FreeNAS on:

Download the .iso file from Source Forge and save it to your hard drive, for example in C:\Temp folder.

From here you can do two things:

1. Burn the .iso file to a CD. This will give you a bootable CD from where you can install FreeNAS to a hard drive or USB stick. The older versions (7.x) also had an option to run FreeNAS from the CD without installing it. With version 8.x this option is not available anymore.

2. Extract the embedded version of FreeNAS from the .iso file and write it directly to a USB stick. This is a faster way of getting FreeNAS installed but will not allow you to add additional software later.

In this article we are going to take the second approach. I will provide a separate posting on how to do variant 1 and install Transmission.

Note: As of version 8.0.1-BETA3 the image size increased. The new size requires a 2 GB USB storage device.

Step 1) Extract the FreeNAS image

We need to extract a file from the .iso file. If you already have a tool that can do that go ahead and use it. If not you can install the Daemon Tools Lite which is free for home personal use. Mount the .iso file and extract the FreeNAS_i386_embedded.xz (32-bit version) file. In case you downloaded the 64-bit version the name of the file will be FreeNAS_amd64_embedded.xz. Copy it to your hard disk.

For the rest of the article I will assume we chose the 32-bit version.

The .xz file is a compressed file. Un-compress it and extract FreeNAS_i386_embedded which is the image we have to write to the USB drive.

I use 7-Zip for extracting the files from .xz file. Make sure you use the latest version of 7-Zip. Right-click the FreeNAS_i386_embedded.xz file and choose 7-Zip -> Extract Here. This will extract FreeNAS_i386_embedded file and place it in C:\Temp

Step 2) Prepare the USB key

Plug the USB key in your PC and format the disk as FAT32. Sometimes Windows will not be able to format it (if it was partitioned or formatted with Linux file system for example). In this case you should try a “low-level” format using this tool:

HP USB Disk Storage Format Tool

Step 3) Write the FreeNAS image to USB key

The next step is to download Physdiskwrite from here. It is a ZIP file. Unzip it and copy physdiskwrite.exe and PhysGUI.exe to C:\Temp. Run PhysGUI.exe. It has a graphical interface and will display information about storage devices (hard drives and USB devices:

Remember the Device ID (first column) of your USB stick. Open a command prompt, change the folder to C:\Temp and type:
physdiskwrite -u FreeNAS-i386-embedded
It will list the disks (the same Device ID you got from Physdiskwrite) and will ask you to which of them to write the file. In my case it is drive 1 (type 1 and press)

It will ask you to confirm (press y followed by)

The program will start writing the file and you can see the progress. After it is done you have USB stick with FreeNAS installed on it. To try it reboot your computer and make sure it boots from the USB stick (either change the boot sequence in BIOS or use one of the hot keys during boot to enter the menu where you can select the device to boot from).

Some people are experiencing problems at this step. One suggested solution (thanks Jim) is:
Open a command window as admin (“cmd”)
Type “diskpart” and hit enter.
Type “list disk” and hit enter to find out the number of your drive.
Type “select disk X” (where you replace X with the number of your drive) and hit enter.
Type “clean” and hit enter.
after that go back to your temp folder and then try the process again.

If something goes wrong and you do not get a working FreeNAS on USB stick then try the first method – burn the .ISO file to a CD, boot from the CD and install FreeNAS to USB.

If you decide to go for version 7.x you get bit-torrent client (Transmission). It is missing in 8.0.2 but there are plans to be included in the future versions.

See Roadmap for 8.1

That is all.

Or almost. Probably you could have got the same information elsewhere – in the Google’s age it is hard to be original. Actually some time ago I came across a discussion about whether the blogging was declining. There were several responses in support of this – people were not seeing much sense in re-posting information available in 1000’s other places.

Saying that I would like to thank you for visiting my blog.

Feb 18, 2015

ASRock 960GC-GS FX Share Experience

I got this motherboard a month ago and it runs great so far. I bought it because I had a Phenom Quad Core 9500 2.2GHz in one of our old computers that wasn't being used. I installed that CPU in this mobo and it started up with no problems along with the DDR2 RAM. It worked fine with that CPU, internet browsing and streaming online videos was now a breeze especially on Netflix. 

Yesterday I received my new AM3+ 6300FX black edition CPU and installed it with some new RAM DDR3 8GB Kingston Hyperx 1600MHz at first it didn't start so I thought it was defective memory module but tried them in my other computer but it booted up fine so I reseated them and I had to push them in a little more with a bit of force and it booted up just fine. I also had to take out my Geforce GT610 graphics card also for it to boot I don't know why but I read on a forum somewhere that could be the problem for it not to boot up. I will update this if anything should happen.

My setup:
ASRock 960GC-GS FX Motherboard (of course)
AMD 6300 FX 8-3.5 GHz Black Edition unlock
HyperX DDR3 1600
Sapphire R7 260X 2GB GDDR5 OC
Western Digital 1TB HDD
Corsair CX600M watt PSU
Cooler Master G-Elite 430 Black Mid-Tower ATX Case

ASRock 960GC-GS FX Support | Drivers Download | Manual | CPU Support List | Memory QVL


I've had this board for two months now still running great. I got a new graphics card last week, a new Sapphire R7 260x 2gb GDDR5 overclock edition. I installed in with the drivers from the cd that came with it and is working awesome. I first bought this mobo just to use my older parts from an older computer but I ended upgrading everything, making it into a decent computer. So far I've really enjoy it and I can even play Farcry 3 on ultra joke. For my ram to run 1600mhz I went to BIOS and adjusted there. I do not intend to use this motherboard that long for gaming I just wanted something now. In the near future I plan on getting a MSI 970 gaming motherboard or a Gigabyte 990FX series motherboard but have to save up for that first. Overall I do enjoy this motherboard for internet browsing, Netflex, and playing Farcry 3 cause that's the only game I got right now lol.




- Support for Socket AM3+ processors

- Support for Socket AM3 processors: AMD Phenom™ II X6 / X4 / X3 / X2 (except 920 / 940) / Athlon II X4 / X3 / X2 / Sempron processors

- Support for Socket AM2+ / AM2 processors: AMD Phenom™ FX / Phenom / Athlon 64 FX / Athlon 64 X2 Dual-Core / Athlon X2 Dual-Core / Athlon 64 / Sempron processor

- Supports 8-Core CPU

- Supports AMD OverDrive™ with ACC feature (Advanced Clock Calibration)

- Supports AMD's Cool 'n' Quiet Technology

- FSB 2600 MHz (5.2 GT/s)

- Supports Untied Overclocking Technology

- Supports Hyper-Transport 3.0 (HT 3.0) Technology


- Northbridge: AMD 760G

- Southbridge: AMD SB710


- Dual Channel DDR3/DDR2 Memory Technology*

- 2 x DDR3 DIMM Slots**

- Supports DDR3 1866(OC)/1600(OC)/1333/1066 non-ECC, un-buffered memory

- Max. capacity of system memory: 16GB***

- 2 x DDR2 DIMM Slots****

- Supports DDR2 1066*****/800/667/533 non-ECC, un-buffered memory

- Max. capacity of system memory: 8GB***

*DDR3 and DDR2 are supported separately.

**DDR3 memory is only supported by installing AM3/AM3+ CPU.

***Due to the operating system limitation, the actual memory size may be less than 4GB for the reservation for system usage under Windows® 32-bit OS. For Windows® 64-bit OS with 64-bit CPU, there is no such limitation.

****DDR2 memory is only supported by installing AM2/AM2+/AM3 CPU.

*****Support with AM3 / AM2+ CPU.


- 16Mb AMI legal BIOS

- Supports "Plug and Play"

- ACPI 1.1 compliance wake up events

- Supports jumperfree

- SMBIOS 2.3.1 support

- CPU, VCCM, NB Voltage multi-adjustment

 Audio, Video and Networking


- Integrated AMD Radeon 3000 graphics

- DX10 class iGPU, Pixel Shader 4.0

- Max. shared memory 512MB

- Supports D-Sub with max. resolution up to 2048x1536 @ 60Hz


- 5.1 CH HD Audio (Realtek ALC662 Audio Codec)


- PCIE x1 Gigabit LAN 10/100/1000 Mb/s

- Realtek RTL8111G

- Supports Wake-On-LAN

- Supports LAN Cable Detection

- Supports Energy Efficient Ethernet 802.3az

- Supports PXE

 Expansion / Connectivity


- 1 x PCI Express 2.0 x16 Slot (PCIE2 @ x16 mode)

- 1 x PCI Express 2.0 x1 Slot

- 2 x PCI Slots


- 6 x SATA2 3.0 Gb/s Connectors, support RAID (RAID 0, RAID 1, RAID 10 and JBOD), NCQ, AHCI and Hot Plug


- 1 x ATA133 IDE Connector (Supports 2 x IDE devices)

- 1 x Floppy Connector

- 1 x IR Header

- 1 x Print Port Header

- 1 x Chassis Intrusion Header

- 1 x CPU Fan Connector (4-pin)

- 1 x Chassis Fan Connector (3-pin)

- 1 x Power Fan Connector (3-pin)

- 1 x 24 pin ATX Power Connector

- 1 x 4 pin 12V Power Connector

- 1 x CD In Header

- 1 x Front Panel Audio Connector

- 1 x SPDIF Out Connector

- 3 x USB 2.0 Headers (Support 6 USB 2.0 ports)

Rear Panel I/O

- 1 x PS/2 Mouse Port

- 1 x PS/2 Keyboard Port

- 1 x Serial Port: COM1

- 1 x D-Sub Port

- 4 x USB 2.0 Ports

- 1 x RJ-45 LAN Port with LED (ACT/LINK LED and SPEED LED)

- HD Audio Jack: Line in / Front Speaker / Microphone

 Other Features / Miscellaneous

Unique Feature

- ASRock OC Tuner

- ASRock Intelligent Energy Saver

- ASRock Instant Boot

- ASRock Instant Flash


- ASRock APP Charger

- ASRock XFast USB

- ASRock XFast LAN

- ASRock XFast RAM

- ASRock X-Boost

Hybrid Booster:

- CPU Frequency Stepless Control

- ASRock U-COP

- Boot Failure Guard (B.F.G.)

- ASRock AM2 Boost: ASRock Patented Technology to boost memory performance up to 12.5%

Support CD

- Drivers, Utilities, AntiVirus Software (Trial Version), CyberLink MediaEspresso 6.5 Trial, Google Chrome Browser and Toolbar


- Quick Installation Guide, Support CD, I/O Shield

- 2 x SATA Data Cables

Hardware Monitor

- CPU/Chassis temperature sensing

- CPU/Chassis/Power Fan Tachometer

- CPU Quiet Fan

- CPU Fan multi-speed control

- CASE OPEN detection

- Voltage Monitoring: +12V, +5V, +3.3V, Vcore

Form Factor

- Micro ATX Form Factor


- Microsoft® Windows® 8 / 8 64-bit / 7 / 7 64-bit / Vista™ / Vista™ 64-bit / XP / XP Media Center / XP 64-bit compliant



- ErP/EuP ready (ErP/EuP ready power supply is required)

Feb 16, 2015

Drive Image and Backup for Windows

R-Drive Image is a potent utility providing disk image files creation for backup or duplication purposes. A disk image file contains the exact, byte-by-byte copy of a hard drive, partition or logical disk and can be created with various compression levels on the fly without stopping Windows OS and therefore without interrupting your business. These drive image files can then be stored in a variety of places, including various removable media such as CD-R(W)/DVD, Iomega Zip or Jazz disks, etc.

R-Drive Image restores the images on the original disks, on any other partitions or even on a hard drive's free space on the fly. To restore system and other locked partitions R-Drive Image is switched to the pseudo-graphic mode directly from Windows or bootable version created by the utility is launched from CD disc or diskettes.

Using R-Drive Image, you can completely and rapidly restore your system after heavy data loss caused by an operating system crash, virus attack or hardware failure. You can also use R-Drive Image for mass system deployment when you need to setup many identical computers. In other words, you can manually setup one system only, create an image of the system, and then deploy it on all other computers, saving your time and costs. If you need to restore only certain files from a disk image, you can connect that image as a virtual disk and copy those files directly from the disk image using Windows Explorer or any other file utility.

R-Drive Image is one of the best backup and disaster recovery solutions to prevent losing your data after a fatal system failure.

A free fully functional 30-day trial version is available for evaluation purpose.

R-Drive Image Features
  • A simple wizard interface - no in-depth computer management skills are required.
  • On-the-fly actions: Image files are created on-the-fly, no need to stop and restart Windows. All other disk writes are stored in a cache until the image is created. Data from image files are restored on-the-fly as well, except on a system partition. Data to the system partition can be restored either by restarting R-Drive Image in its pseudo-graphic mode directly from Windows, or by using specially created startup disks.
  • Image files compression. Image files can be compressed to save free storage space.
  • Removable media support. Image files can be stored on removable media.
  • Startup version. A startup version can be used to image / restore / copy partitions locked by the OS. The computer can be re-started into the startup version either directly from Windows, or from an external USB device, a CD/DVD disk, or 6 floppies. The startup version can use either a graphic user interface, or a pseudo-graphic mode, if the graphic card isn't supported. Support for UEFI boot for modern computers.
  • USB 2.0 and 3.0 support in the startup version. With hard drives prices constantly going down, an external IDE-USB 2.0 or 3.0 HDD case with an appropriate hard drive is an ideal (fast and reliable) solution for storing backup files for system and other partitions that can be restored only in the startup version. Do not use numerous unreliable CD discs and slow CD/DVD recorders any more. Remember: with the incremental backup, this hard drive is not to be too large.
  • Network support in the startup version. R-Drive Image startup version supports disk image file creation and restoration over the Microsoft network (CIFS protocol).
  • Extended List of the supported devices in the startup version. The list of hardware supported by R-Drive Image startup versions has been extended. VIEW THE LIST
  • An image file can be connected as a read-only virtual disk. Such disk can be browsed through and files/folders can be found and copied.
  • Individual files and folders restoration. Individual files and floders rather than entire disk can be restored either during the restoring action or from a image file connected as a virtual disk.
  • Image files splitting. Drive images can be split into several files to fit a storage medium.
  • Image Protection. Disk image files can be password-protected and contain comments.
  • New partition creation. Data from a disk image can be restored on a free (unpartitioned) space on any place on a hard drive. The size of the restored partition can be changed.
  • Partition replacement. Data from a disk image can be restored on other existing partitions. R-Drive Image deletes such partitions and restores data on that free space.
  • Disk to Disk copy. An entire disk can be directly copied on another one.
  • Image files verification. You may check if your image files are good before you store them or restore data from them.
  • Scheduler. A time for disk image creation may be scheduled and the process can be run in unattended mode.
  • Script creation for frequent or unattended actions. Such scripts for creating an image file and appending data to an existing image file are created from the R-Drive Image interface the same way the actual action is performed. Scripts are executed from a command line and such command can be included to any command file.
  • Action Report. When disk image is successfully created or the action fails the report can be automatically sent over e-mail or an external application can be launched.
  • Support for the ReFS file system (Resilient File System), a new local file system Microsoft has introduced in its Windows 2012 Server. All disk actions are supported, except partition resizing.
  • Full support for the GPT partitioning layout. R-Drive Image can create GPT disks, resize them, and change their partition layout during copy/restore operations.
  • Support for Windows Storage Spaces (Windows 8/8.1 and 10), Linux Logical Volume Manager volumes, and MacRAIDs.

How To Make Windows 7 OS On USB Flash Drive

As you all know creating a bootable USB, or installing Windows 7 or Vista using USB is a piece of cake. It doesn’t take much time and effort to have a bootable USB. Now, after replying to several e-mails about installing Windows 7 or Vista on a USB drive, I have decided to write this detailed guide.

Requirements to install Windows 7 on USB:

# An USB flash drive with a minimum of 6 GB disk space to install Windows 7 or Vista. You can use a 4 GB drive to install XP.

# Bootable Windows 7 USB or DVD.

# Free time

So let’s begin with the installing Windows 7 on USB procedure:

1. First of all, connect your USB to the machine and backup all the data from the USB drive.

2. Download VirtualBox portable here, double-click on the executable file and extract the contents to your USB.

3. Now, go to the VirtualBox portable folder in USB, and execute the Portable-VirtualBox (.exe) file.

4. From here onwards, you need to follow the onscreen procedure to create a virtual disk and install Windows 7 on USB. Follow the install Windows 7 on VirtualBox guide to complete the process.

5. Once you finish the installation process, you can safely close VirtualBox and remove your USB drive.

6. You can now use this Windows 7 USB drive on any Windows machine that you want. To use Windows 7 on other machine, connect the Windows 7 USB, open USB drive, and run portable-VirtualBox file.

How To Convert Windows 7 OS To A Virtual Machine

In this guide, we will cover how to create a virtual Windows machine by cloning your existing Windows operating system. And once you have a clone of your OS in the form of virtual drive you can use free virtualization solutions like Virtual Box, VMware Player or Microsoft Virtual PC to carry and access your personalized Windows OS on any machine.

Here are the steps that you need to follow in order to clone your Windows OS. In this guide, we are cloning our Windows 7.

1. First download and install Paragon Go Virtual software. Paragon Go Virtual is available for free of cost, but you need to register (free) with Paragon software to avail the free license. During installation, click Get free serial button to head over to the official registration page and enter particulars to get the license via email. Enter the product key and serial key, and complete the installation.

Pargon Go Virtual

2. Once installed, you will be asked to reboot your machine to complete the procedure.

Pargon Go Virtual Installation2

3. Run Paragon Go Virtual application and click P2V Copy option to start the P2V Copy Wizard.

Convert Your Windows 7 Into A Virtual Machine To Carry On USB Drive Step2

4. Once the wizard is launched, click Next button to see disk volumes and external hard drives, if any.

5. Check the box next the Widows installation drive and click on the Next button to proceed further.

Convert Your Windows 7 Into A Virtual Machine To Carry On USB Drive Step3

6. The wizard will detect the OS present in the selected drive and prompts you select a virtual software that you want to use to run the virtual machine. Select a virtual software from the available three (VMware, VirtualBox and Microsoft Virtual PC) that you are familiar with and then click Next button (we have selected Oracle VirtualBox).

Convert Your Windows 7 Into A Virtual Machine To Carry On USB Drive Step4

7. In the properties page, enter a name for your virtual machine and change the memory allocation before hitting the Next button.

Convert Your Windows 7 Into A Virtual Machine To Carry On USB Drive Step5

8. In the next window, you can change the properties of virtual disks. Click Next button to go with the default one.

Convert Your Windows 7 Into A Virtual Machine To Carry On USB Drive Step6

9. On this screen you need specify the location where you want to save the virtual machine. You are almost done. Click Next button again to the start the process of virtual machine creation.

Convert Your Windows 7 Into A Virtual Machine To Carry On USB Drive Step7

Convert Your Windows 7 Into A Virtual Machine To Carry On USB Drive Step9

10. Depending on the amount of data present on your Windows drive, it might take a few minutes to hours. Once the process is completed, install a virtual machine and then open the virtual machine by clicking the appropriate option. You are done!

How To Backup VirtualBox Disk Image

VirtualBox is one of the best free virtualization software out there, if not the best. Users who have used VirtualBox for some time probably know how difficult it is to clone or move a virtual machine as VirtualBox assigns a unique identity number (UUID) to each virtual machine.

Even though there are guides available to backup or move a VirtualBox virtual machine (.VDI) without using third-party tools, you need to follow a very lengthy procedure. So, here we are to share a free utility to backup virtual machine in a few steps.

CloneVDI is a free utility that lets you backup VirtualBox virtual machine (VDI) with ease. Other than backup, you can use this tiny tool to increase virtual drive size, view virtual drive info, and header info as well.

Here are the key features of CloneVDI:

# Reads VDI, VHD, VMDK, Parallels HDD, RAW files and physical drives, writes VDI

# Ability to compact the clone virtual machine

# Ability to enlarge the maximum size of a virtual disk

# Generate new UUID for the clone

# Information about the source VDI, internal file system, & partition map

How to use CloneVDI tool:

Step 1: Make sure that your virtual machine is shut down and powered off.

Step 2: Download CloneVDI zip file and extract the zip file contents to a folder on desktop.

Step 3: Run CloneVDI (.exe) file. Select the VDI file that you want to clone and then select the destination.

Step 4: Use the option Increase virtual drive size to option if you need to enlarge the clone virtual machine.

Step 5: Click Proceed button and wait for a few minutes to complete cloning process.