Any good web host will secure the contents of website directories which don’t have an index page by not allowing the files or folders to be listed, instead you’ll get a 403 error page saying access is forbidden. Whilst this is good in practice, sometimes you might actually need to list the contents – and its simple to enable on an Apache web server – add one line to your .htaccess file and you’re done!
How it’s done
If you have access you can edit your web server configuration and make it global
I used to be a customer of popular cloud backup service Livedrive. The upload and download speeds were nothing to shout about and one annoyance was having to pay extra to add a NAS drive to your account, but there is a workaround!
All you need to do is add a symbolic link to your NAS drive from your computer. Think of a symbolic link as a fancy shortcut, the only difference being it masks the destination instead of taking you straight there – you’ll see what I mean when you read on.
Imagine you have a Windows computer with your NAS drive with the root of the drive already mapped to Z:, you have a folder on your NAS called MyFiles and would be able to browse to Z:\MyFiles to see whatever is stored there. Next imagine we have a folder called C:\Backup which is already uploading to your Livedrive account, using the following command we will make C:\Backup\MyFiles lead to your NAS and in turn be included with your Livedrive backup.
mklink /d "C:\Backup\MyFiles" "Z:\MyFiles"
For me, this worked absolutely fine and I had a couple of TB uploaded without ever being caught out. I’ve since jumped ship to Amazon Drive, whilst it is more expensive per year I’ve got it running from multiple computers and the upload and download speed always tops out my connection, so I can’t complain!
Use the above guide at your own risk – I won’t be held liable if anything happens to your Livedrive account, files or anything else because of this!
This doesn’t work with Dropbox or Google Drive – sorry
You only need to run the command once, after that the link will be remembered
To remove the link just delete it as you would any other file or folder
I recently bought 2 Turnigy Nitro RC cars to have a little fun with, whilst being fully aware of them having a problem with the starter mechanism I hoped that HobbyKing would have resolved them by now, but unfortunately not.
I bought a Truggy for £50 and a Buggy for £70 and managed to start them both twice before the pull starter began to slip. I took the buggy engine apart and found no obvious problems, but there was a lot of oily residue covering pretty much everything, even the pull starters chord and this seemed to be the reason it was slipping.
Searching online at the HobbyKing website I found various posts about replacing different engine parts but the most promising said that a Graupner 92600.117A back plate was the ultimate solution and stops the oily residue from the fuel seeping everywhere.
All in all it looks like a design flaw with the engine, but two new back plates are on their way from Germany, £30 inc postage and should be here in a few weeks.
Update 16/08/2015 –
The new back plates fits nicely and the engines have both turned over flawlessly since. The pictures below show briefly how it was done to the buggy engine, the same steps were repeated for the truggy engine too.
A video will be attached soon showing the cars in action.
Imagine this… you have two decent network attach storage boxes which regularly backup one to the other using a built in Disk Backup tool – Brilliant huh, sounds almost like a nerdy dream! Now imagine part way through a backup you get a power cut or you just trip over the power cable ripping the plug out the wall… not to worry, things will pick up where they left off… unless those decent boxes are Buffalo LinkStations!
I first discovered this flaw a few weeks back when one of my nightly backups seemed to be taking longer than usual. I gave the box about a day or so to try and fix itself but it still kept saying that the disk backup was in progress and in the admin interface and I was unable to cancel or remove the backup, so it was pretty much stuck as you can see below:
I headed to the official Buffalo support website which seemed to have a fix for this common problem – See for yourself below:
Okay so you have to restore the box to factory defaults… no thanks! I can only assume that because the HS-DHGL is one of their older discontinued products they just can’t be bothered to make a firmware update as it’s not worth their time or effort, but the other option is to use SSH to edit a file which will force the backup to complete.
The following guide will assume you have already enabled SSH and are logged in ready to go, if you haven’t yet enabled SSH see this post here.
First of all we need to locate the backup configuration file and this depends on the job number specified on the admin interface, in my case it was number 1 so we need to type in the following command to open the file in a text editor:
You will now see the configuration file open, hit I (for indigo) on your keyboard to allow inserting of new text and change the line status=running to status=done
Hit the Escape key and then type :wq to save your changes and quit
Head back to the admin interface to the Disk Backup section and you’ll now see the backup showing as complete as seen below:
That’s it – The backup is unstuck, and we haven’t had to restore anything to factory defaults!
This has been tried and tested on the following models/firmware: HS-DHGL/v2.1
Finally, if you could let me know if you encounter any problems or can confirm if this works for other models I’d be grateful
There may come a time in your nerdy life where you want your computer to automatically log in at boot or whenever anybody signs out, this can be especially useful if you are running software that needs a user to be constantly logged in.
For example, I run CCTV software on my computer via a user called Console, the software displays live camera feeds on a second screen at my desk, the same signal is fed via a splitter through network cables eventually reaching various screens dotted around my house.
The setup requires my Console user to be constantly logged in, be it when the system boots or after I have finished checking my emails or being nerdy.
It is fairly straight forward to get going, in my case on Windows 10 Pro I ran the built-in netplwiz(.exe) utility and added one string value to the registry.
Part 1: Configuring automatic login at boot
Run netplwiz(.exe) and uncheck the box saying Users must enter a username and password to use this computer.
Press OK then enter the username and password you want the computer to automatically login as and press OK again
That’s the first part completed, so now whenever you boot your computer it will automatically sign in as the user account you have set.
Part 2: Configure automatic login when signing out/switching user
The next part involves adding a regsitry key with a string value, once this was done I found it worked straight away without having to reboot my machine.
Open regedit(.exe) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Right click on Winlogon and select New > String Value
For the value name enter ForceAutoLogon, double click the line you just added and enter the value date to 1
That’s it! Now when you sign out it will automatically sign back in to the user account set in first step.
If you want to log in as a different user, hold the shift key whilst locking your account, you’ll then see the normal Windows login screen
You can do step 1 via the registry if you want, but why over complicate things!