Skype freezes and hangs your system?

The best solution is uninstall the Skype and never use it again!

But if you still need Skype application to contact your siblings and co-workers, here is a useful trick

New Design

Old blog template looks bad on huge monitors and there was no mobile version of website. So I fix it by applying some modern theme, hope you'll like it :)

Also I've add some advertising slots. You can purchase something at Alibaba.com and I'll get few bucks. Wish you good shopping ;)

Wrap Headphones in the Right Way

Here is a lifehack to wrap headphones and earphones quickly, without any twisting:

Also you can use "devices" like this:

Запускать такое на #KickStarter или выложить чертежи и модели для 3d печати в открытый доступ? ;)

A photo posted by Anton Karpenko (@karpolan) on Aug 8, 2015 at 10:48am PDT

Touchpad Scrolling doesn't work on Windows 10?

If two or even single finger scrolling doesn't work after update to Windows 10 and your touchpad is manufactured by Synaptics company, download and install driver for touchpad version 16.2.x. Everything will work like a charm.

Open this link Synaptic Touchpad Driver 16.2, supports scrolling on Windows 10, check "I agree" options on the bottom of page and press "Submit" button. The driver will be downloaded.

Cat Tomas

Tomas or Thomas is big funny cat!

Lives on Suvorova 14, Dnepropetrovsk, Ukraine.

How to assign reserved IP to existing Virtual Machine in Microsoft Azure Cloud

I don't know why Microsoft cannot offer a single click tool to add a permanent static IP to any Azure resource. Moreover I don't understand why it is not possible to assign a reserved IP address to an existing Virtual Machine :(

The only way (as of April 2015) to assign a permanent public IP address (reserved IP) to Virtual Machine in Microsoft Azure Cloud is the following:

1. Stop Virtual Machine
2. Make captured image with a custom name ("image-of-virtual-machine" for example)
3. Manually write out all Endpoints (insane!)
4. Delete VM and associated Cloud Service
5. Create Reserved IP using Azure PowerShell
6. Create a new Virtual Machine from the saved disk image
7. Set back all Endpoints manually (insane again!)

If you have finished deleting of Virtual Machine at step 4, start Microsoft Azure PowerShell. Creating of Reserved IP is easy, just a single command call:


New-AzureReservedIP -ReservedIPName "reserved-ip-address-for-your-vm" -Label "SomeTextHere" -Location "North Europe"


To verify that Reserved IP was successfully created, call:


Get-AzureReservedIP


We've got Reserved IP, so it's time to create a new "old" Virtual Machine.

First of all call this command in Microsoft Azure PowerShell:


Get-AzureSubscription


You'll get something like that:


SubscriptionId : 123456-e123-1234-a123-1234567890
SubscriptionName : BizSpark
Environment : AzureCloud
SupportedModes : AzureServiceManagement,AzureResourceManager
DefaultAccount : some@some.com
Accounts : { some@some.com }
IsDefault : True
IsCurrent : True
CurrentStorageAccountName :
TenantId : 00000000-0000-0000-0000-000000000000


If CurrentStorageAccountName is empty set it to the value you can find in Azure Management -> Storage.


Set-AzureSubscription -CurrentStorageAccountName "get_id_from_web_panel_something_like_portal23423ns43" -SubscriptionName "BizSpark"


Otherwise you've got strange errors on next steps, for example:


New-AzureVMConfig : Must specify MediaLocation or set a current storage account using Set-AzureSubscription.


Now we can create a new virtual machine from the saved image with reserved ip address. Lots of tutorials offer to call the following command (don't do it):


New-AzureVMConfig -Name "your-virtual-machine-name" -InstanceSize "Small" -ImageName "image-of-virtual-machine" | New-AzureVM -ServiceName "could-be-same-as-vm-name" -ReservedIPName "reserved-ip-address-for-your-vm" -Location "North Europe"


But in 99% you'll get error:


New-AzureVM : BadRequest: A ProvisioningConfigurationSet was not found in the ConfigurationSet collection of the virtual machine with name your-virtual-machine-name. When creating a virtual machine from an image, ProvisioningConfiguration Set must be specified.


So add Add-AzureProvisioningConfig section into the command (call this):


New-AzureVMConfig -Name "your-virtual-machine-name" -InstanceSize "Small" -ImageName "image-of-virtual-machine" | Add-AzureProvisioningConfig -Linux | New-AzureVM -ServiceName "could-be-same-as-vm-name" -ReservedIPName "reserved-ip-address-for-your-vm" -Location "North Europe"


BTW, don't set any LinuxUser/AdminUsername or Password if you are creating Virtual Machine from disk image, otherwise you've got an error:


New-AzureVM : BadRequest: No Configuration Set should be specified while using a VMImage with a specialized OS Disk Configuration.


Almost done, you'll get a new virtual machine with the permanent public IP running in a few minutes.

Don't forget to add all endpoints! I prefer to do that using web interface. Also update internal IP address for all services on the Virtual Machine. New VM has a different IP address, either public or internal one.

Hope that helps and there were no problems on the Azure side while you are following these instructions :)

Why is it so hard?!

Microsoft Remote Desktop on Mac OS X

Quick guide (in a single picture) how to properly setup remote desktop connection using Microsoft Remote Desktop software on Mac OS X:

Text variant:

• Don't use old Remote Desktop Connection software Mac OS X version 10.10.x and higher! Use Microsoft Remote Desktop from App Store instead.
• Don't add domain or PC name with back slash into username! Put just a login name, official instruction is wrong.
• Specify the port number in the connection filed! Different RDC protocols uses different port numbers by default.