Schedule commands in LFTP using “at”

You can schedule downloads and uploads in LFTP in a simple manner by using the “at” command. Anything following the syntax described in this image below should work.


Mirror/download a remote folder two hours from the current time, using 10 connections + segmentation

at now + 2 hours -- queue mirror --use-pget-n=10 yourdirectory/

Mirror/download a remote folder at 1AM tomorrow, using 10 connections + segmentation

at 1:00 tomorrow -- queue mirror --use-pget-n=10 yourdirectory/

PC stats monitoring on your phone with Logitech Arx & AIDA64

Ever since the original Logitech G15 keyboard came out I’ve really taken a liking to the idea of having a little LCD screen near the keyboard for stat monitoring. I much prefer this to an on-screen overlay. The G15 and G19 are pretty old now and I don’t believe the LCD screen concept ever took off past those models. Logitech now has “Arx” which aims to replace this concept. Logitech have keyboards now with an “Arx dock”, which is basically a phone dock. The idea is that you can use the Arx software on your PC along with the Arx app on your phone to monitor all sorts of things. AIDA64 has support for Arx, so you can pipe your AIDA64 stats into Arx. This is particularly useful when overclocking – you can monitor your temps and resource utlisation while gaming or encoding. You can even take your phone into the bathroom and keep monitoring!


Here is a basic guide on how to get this going. I’m going to assume you do need a Logitech keyboard to use the Arx software, but this may not be the case. There is no technical reason for Arx to require a Logitech keyboard to function, but it’s entirely possible that Logitech stop the software from running if you don’t have one.

Enable Logitech Arx support in AIDA64.


Setup your template under “LCD Items”.

Make sure AIDA64 is enabled within Logitech Arx / Logitech Gaming Software.

Install the Logitech Arx app on your phone. It can auto discover Arx over your network. On your PC you will have to allow your phone to connect to Arx via a popup notification that should appear. When you first run Arx on your phone AIDA64 will suggest a resolution to set within AIDA64’s LCD config, you can see that I’ve already done this in the first screenshot. Once you’ve setup your LCD template in AIDA64, you should be good to go.

Lossless video capture without needing fast and huge storage – x264vfw

To get the best quality out of your video captures, it’s best to capture losslessly and encode the content post-capture rather than trying to do it in real-time via software encoding or using hardware encoders. Unfortunately normal raw lossless capturing requires very fast storage and a pretty hefty amount of disk space. SSD drives can cope, but depending on the length of your captures you may well need over 2TB of space, which is currently quite expensive in SSD form. An alternative is to use RAID0 arrays or similar. If your storage cannot keep up with the required write speeds you will end up with dropped frames.

amarectv & x264vfw

A great solution is using the x264vfw codec in lossless mode. You will still have large file sizes (expect past 1GB or more for every minute), however the sizes are much smaller than normal raw lossless capture. This also means the write speeds required for capturing without losing any frames are lower. The highest I’ve seen x264vfw jump in lossless mode is ~60MB/s when a ton of action is going on, otherwise in my captures I’ve seen speeds generally hang around 20MB/s. A standard HDD can cope with this without issue, just make sure the drive isn’t being used by anything else.

For more info on x264vfw, other lossless codecs, and capturing in general – Check out “TheThrillness Blog”.


Fixing “Can’t connect to Group Policy Client service” on Windows 10

This is the method I’ve used to fix the “Can’t connect to Group Policy Client service” error on Windows 10. Symptoms – Log into Windows, no desktop icons, start bar not really working, and a little lock icon in the taskbar with that error message. A system restore will probably fix this problem, however it wasn’t an option for me as I’ve disabled the system restore feature.

In the start bar type cmd so that you see the command prompt shortcut.

Right click it and run as Administrator.

Type netsh and press enter.

Type winsock reset and press enter.

Reboot the PC.

This might not work on your first try, so try it twice just to be sure.

You should now be back at a working desktop after logging in.
Go to Start > Settings > System > Power and sleep > Additional power settings

Click on choose what the power buttons do over on the left.

Scroll down to shutdown settings.

Uncheck turn on fast startup
(If this is greyed out, up the top you need to first click “change settings that are currently unavailable”)

Save the changes.


Roughly three months have passed since connecting to NBN FTTN via TPG. I’m on the “up to” 100/40mbit plan. At a guess I’m ~500meters from the node. At this point I haven’t had any issues with the horrible speeds/congestion that some users report. FTTN sucks compared to FTTH for a ton of reasons that I won’t go into. The bottom line so far is that I’m more or less able to saturate the speed that I’m syncing up at regardless of peak/offpeak.

Modem Stats (TPG supplied Huawei HG-658)
Line standard VDSL2
Channel type Interleaved
Downstream line rate (kbit/s) 62945
Upstream line rate (kbit/s) 29311
Downstream SNR (dB) 6.7
Upstream SNR (dB) 6.5
Downstream line attenuation (dB) 15
Upstream line attenuation (dB) 5.1
Downstream output power (dBmV) 14.3
Upstream output power (dBmV) 8.4 result - Unusually high latency from the server on this result. result – Unusually high latency from the server on this result. I’ve seen much better results matching right to the sync speed. – (Updated 08/09/2016)

Ahhh that's more like it!

2019 Update

Having all additional phone sockets unwired from the first phone socket/point of entry has resulted in a nice increase. The wiring was daisy chained from socket to socket, so it only had to be removed from the first socket/point of entry to be effectively disconnected. This removes a lot of additional noise from the line and thus an increase in sync rates and some differences in attenuation stats.

Modem Stats (TPG supplied Huawei HG-658)

Line standard VDSL2
Channel type Interleaved
Downstream line rate (kbit/s) 83712
Upstream line rate (kbit/s) 35122
Downstream SNR (dB) 5.7
Upstream SNR (dB) 6.9
Downstream line attenuation (dB) 14
Upstream line attenuation (dB) 5.3
Downstream output power (dBmV) 14.3
Upstream output power (dBmV) 7.4 & Steam – (Updated 2019)

Segmented SFTP downloading using LFTP

If you’ve every tried saturating a fast connection using FTP/SFTP you may have run into problems where you can only achieve limited download speeds using a single thread. Segmented downloading can often be a solution. Bare in mind that segmented FTP/SFTP will open many sessions to the server you are connecting to. Depending on the situation this might not be ideal, however if you’re sure you have sufficient resources to do it (without generating too much load if your server is within a shared environment), then it can work very well.

You’ll need to install lftp – I run it on a Raspberry Pi.

sudo apt-get install lftp

Login to your server using lftp

lftp sftp://[email protected]

Change into the directory with files you want to download

cd /hdd01/downloads

Start a segmented download

A pget command using segmentation is used for single files.

pget -n 15 somefile.iso #where 15 is the number of segments

A mirror command using segmentation is for downloading whole directories.

mirror --use-pget-n=15 SomeDirectory #where 15 is the number of segments

You’ll need to experiment with the amount of segments – It’s best to use as few as you can, while still getting as much speed as you need. I tend to use 8 – 15 at absolute maximum.

lftp has queue support which can also be pretty useful. Essentially you can queue up a bunch of different transfers and pull up the status later on. You simply need to add queue to the start of your command. To check the queue you can use jobs -v