Go back to the 80s

Reading the “historical” articles on Filfre.net and watching the Halt and Catch fire TV series, I got hit by nostalgia, from when I was playing with my AMD 386 DX, still in service until the end of the 90s.

So, I immediately downloaded PCem and 86box, searching for the BIOS ROMs of my old PCs. I got a lot of problems, but I will talk about that another time. Then I found IBMulator and I immediately reminded my friend and his old PS/1. Even if when it was introduced (1990) was already incredibly outdated (a 286 CPU when you could buy a PC with a 486… of course with a much higher price), I was impressed because of its “simplified” OS, very fast to load.

In a few minutes, I found all the files on https://ps1stuff.wordpress.com/download/downloads-for-type-2011/ (even n my language!!!) and I immediately did a manual restore on the empty virtual disk (if you bought a new system at the time, this was already done in the factory, you just needed to turn it on)

This emulator is awesome, it simulates all the disk and floppy noises, and also the CRT screen. But it also simulates the fan noise, that at the time was very noisy ūüėÖ

I got some initial problem to let it load the OS from the floppy. That error “press F1” at the start, means something changed in the system, for example, more memory, or a new hard drive, you need to confirm by running the “configuration” program.

In total, I took about 15 minutes, to copy 5 megabytes from 4 floppy disks… so slow! I forgot this part!

What does “root” means?

In computer terms, with root we can mean:

  • Root as user
  • Root as in file path

If we mean root as an user, we mean the main user, the one with the “master” control of the machine. For example, if you have root on Android, it means you can do whatever you want it it.

If you mean root as a file path, it’s the base, just place the file outside any folder. If you’re using the D: drive, by saying “place the file in root”, it means just place it on D:

How to convert a VM from VirtualBox to KVM

Converting the virtual machine images is very easy, but many guides suggest you to convert¬† from VDI to RAW and then from RAW to QCOW2. It doesn’t really make sense, you’ll waste double the time, and it’s gonna be hours if the drive is big.

To convert from VDI to QCOW2 just use qemu-img:

qemu-img convert -f vdi -O qcow2 [VBOX-IMAGE.vdi] [KVM-IMAGE.qcow2]

If the virtual machine was Windows-based, probably will crash at first boot, because of the virtual hardware changes, and because there are no virtio drivers installed (unless you make a VM with IDE emulation)

For fix the BSOD at boot you can do onf of this:

Personally I chose the first option, but then I had to install again hundreds and hundreds of security updates, it would have been better if I installed the patch before migrating.

Update: I noticed that the converted Windows XP VM uses the cpu at 100% even when idle. This is a nasty bug that would take ages to fix. I tried to force enabling ACPI, but all I can get is a BSOD on boot. I’ll just scratch the VM and rebuild it…

How to do a quick CPU benchmark on Linux

With Enki (a Brain Training app for coders – if you want to try iy, and you need an invite, you can my code: MAGNE985) I found a quick benchmark to for Linux, to see the speed of a CPU core.
dd if=/dev/zero bs=1M count=1024 | md5sum
This line tells the CPU to calculate an md5 hash for an 1gb of “zeroes” and measure how long it takes. For example, on the Pentium G3420 that I have in my office I get this:
dd if=/dev/zero bs=1M count=1024 | md5sum
1073741824 byte (1,1 GB) copiati, 2,10036 s, 511 MB/s dd if=/dev/zero bs=10M count=2048 | md5sum
21474836480 byte (21 GB) copiati, 49,0278 s, 438 MB/s
while on an Intel Xeon W3520 (my web server) I get this:
dd if=/dev/zero bs=1M count=1024 | md5sum
1073741824 bytes (1.1 GB) copied, 2.79137 s, 385 MB/s

dd if=/dev/zero bs=10M count=2048 | md5sum
21474836480 bytes (21 GB) copied, 56.9042 s, 377 MB/s
Hey! It takes 10 seconds more! What? An expensive Xeon is slower than a cheaper Pentium????
Yes, the server is outdated, but I did not expect to have such a difference! It is time to change my web server!

How to solve the Adobe Shared Technologies failed install problem

I wanted to try the Photoshop Elements demo (it’s on sale for cyber monday for just $40!), but it wasn’t working.

Searching on the Internet, it looks like it’s a common problem to have an error like those:

¬†“The wizard was interrupted before Adobe Photoshop Elements could be installed. Below mentioned application has failed to install: Shared Technologies.”

“The Adobe Premiere Elements installation wizard was interrupted while installing Shared Technologies.”

“The installation process has encountered an error while installing Shared Technologies.”

Why? The reason is simple, but it’s not explained by the error message.

The installer does not run correctly if it has more than 255 characters in the file path.

This is because, usually, the setup is run from d:\setup.exe , and a few people gets the error.

Instead, when you download a demo from the Internet, you can run it from a long path, as this:


The file path it’s too long, and it doesn’t work.

So, if you get this error while installing Adobe Shared Technologies, move the setup in another folder, for example c:\temp

Photoshop can’t save file – disk full

Sunday I upgraded my Windows Home server with a new 2TB hdd, because it was becoming full.

Then, I saved an image in Photoshop 7, and i get an error “Disk full”

What?? The server has more than 1.3 TB free!

I search for a solution from Adobe and I find:

“Adobe recommends that you not save directly to servers, because writing directly to servers adds a level of complexity to the function of saving.”

Oh, great! They won’t fix the bug!

It happens that Photoshop has a known bug from year 2002 that won’t save a file in a disk that has more than 1 TB free!

How to fix the problem? Unfortunately, the only way is to create an huge garbage file to have less than 1 TB free.

How to create an huge garbage file in a short time? It’s very easy, using the command prompt!¬†ūüĎć

First open the command prompt with administrative privileges (On Vista and Windows 7, select “run as administrator”, on XP and below, just run it)

Then, write:

net use z: \\server\yoursharename

The share will be temporarily connected as z:, and going in z: and writing dir this comes out:

Directory Z:\

17/01/2011  19:31    <DIR>          .
17/01/2011  19:31    <DIR>          ..

0 File              0 byte
0 Directory  1.282.964.344.832 byte available

We must have less than 1000 billions of bytes available to have Photoshop working on this drive, so we have to create a file that has a size of at least 283 billions of bytes.

For creating an huge file in seconds, we use fsutil, that has this syntax:

Z:\>fsutil file createnew file.name 12000

Where 12000 is the size in bytes

I wrote this è:

Z:\>fsutil file createnew photoshop.bug 290000000000
The file Z:\photoshop.bug has been created
Directory Z:\

24/05/2011  10:59    <DIR>          .
24/05/2011  10:59    <DIR>          ..
24/05/2011  10:59 photoshop.bug
1 File byte
0 Directory  992.930.263.040 byte available

After that, Photoshop 7 allowed to save files in that location¬†ūüėČ

The best video converter EVER!

SUPER is an awesome video converter. It can convert any kind of video without problems. Even rare containers like *.NSV, *.STR, *.VIV!

It can produce any video format:


Once chosen the video container format, we choose the video codec, the audio codec, the video resolution, the framerate, the bitrate, and presto! In just a few minutes, it converts ANYTHING!


SUPER (acronym of “Simplified Universal Player Encoder & Renderer”), can be downloaded from the official Website, but, that Website is a kind of a mess, so you can download it from here (version updated to April 2009).

Update 18th august 2016: their latest installer contains adware. Be careful and read carefully what are you agreeing to, don’t install toolbars and other useless and deceiving adware.