Spotted @ Armin Van Buuren - A State of Trance - podcast 411!
- Power down your Ubuntu virtual machine
- Download SystemRescueCd from https://www.system-rescue-cd.org/SystemRescueCd_Homepage
- Attach the .iso to the Ubuntu virtual machine
- Start the Ubuntu virtual machine and make sure you boot from CD/DVD
- Root into your system. Once logged in, execute the command zerofree on your partition (this can take several minutes!). E.g.:
$ zerofree /dev/sda1
- Stop the Ubuntu virtual machine
- Compact the Ubuntu virtual machine in your host Windows OS. Edit disk > Compact
I recently bought a Samsung SSD 850 EVO (256GB) for my old Macbook Pro 13" (mid 2011). I copied all data from my HDD to my SSD with the Super Duper! app.
After swapping the disks, I noticed my Macbook was constantly crashing. I also sufferered a lot of the so called 'beachball effect'.
My SSD was running on firmware: EMT01B6Q. After upgrading the firmware to the EMT02B6Q version, all problems were resolved.
Unfortunately, I cannot find any changelog for the EMT02B6Q version - so it is still a mystery why the SSD is working now flawly with the latest firmware version ... Maybe it's related to the old SATA2 controller which is in my Macbook? ...
Android version: Android 5.0 Lollipop
The following message kept appearing on the screen (in Dutch: Xperia Home gebruiken voor startscherm). Even if you choose Always; 10 minutes later, the message appeared again.
After trying everything (changing settings, factory reset - with backup & restore), we found out the app: Connect for Hotmail is the culprit one. The phone thought the app was a home screen launcher. So everytime I opened the app it changed the default setting for the launcher. After uninstalling the app, the problem was gone ... We now switched to the Microsoft Outlook.com app, hoping this app will act better then Connect for Hotmail
- Open SQL Server Management Studio
- Right click database server and choose Properties
- Choose tab: Memory
- By default, the value is set to 2147483647, which is the integer's max value. Adjust the Maximum/minimum server memory (in MB) to any number you would like
By default, access requests, errors, and some other segmented data, is written into separate log files, which are not rotated by Apache.
These log files grow in size as new log data is appended with each additional access request made. And it’s left to the user to (once in a while) stop Apache, and rotate (i.e., rename) or delete the log files, so everything starts from size-zero again.
To automatically rotate a website's access.log (and other log files such as the error.log) every 24 hours (daily), Apache's included rotatelogs.exe tool can be used.
ErrorLog "|bin/rotatelogs.exe -l #PATH_TO_ERROR_FILE%/errorlog.%Y-%m-%d.txt 86400" CustomLog "|bin/rotatelogs.exe -l #PATH_TO_ACCESS_FILE%/accesslog.%Y-%m-%d.txt 86400" combinedtrueout_host
- Press the Windows + R keys to open the Run dialog, type lusrmgr.msc, and click/tap on OK.
- In the left pane, click/tap on the Users folder, then in the middle pane, double click/tap on Administrator
- To enable the built-in elevated "Administrator" account, uncheck the Account is disabled box, click/tap on OK.
- To reset the password, right click the "Administrator" account and choose Reset password
When opening multiple RDP sessions on a server (for the same credentials), the second RDP session was not able to open a Chrome window if the first session already fired up Chrome.
The problem is exactly that the two RDP sessions do not share the desktop although they are logged in with the same credentials. The desktop meaning not the "Desktop" folder but the logical entity in windows where the applications run. Therefore the instances running in both sessions can't see each other and the first one locks the profile for exclusive use which is critical to ensure no profile corruption can occur.
This problem has been discussed in the past and the best solution for this problem is to modify the startup link of Chrome to make sure every logged in user gets his own profile. this can be achieved using the --user-data-dir flag (or UserDataDir GPO policy). For example using this command line to start chrome will even guarantee that every client will reach the very same profile every time he/she logs in from the same client machine:
This will create unique folder for every user under the default profile location for Chrome. Right now there is no way to specify the client name variable in a policy therefore this particular example will work only as a command line flag.
Source: Chromium support issue #160676
I recently had a strange login issue when firing up an old Windows 2003 Server. When I wanted to login, the form fields were colored black (see screenshot on top). The text color was black. When you typed a letter, you could not see what exactly you were typing.
After Googling a while, I ended up on this article.
This issue occurs if all the values under the following registry subkey are set to "0 0 0":
The correct colors
|Value name||Value data|
|ActiveBorder||212 208 200|
|ActiveTitle||10 36 106|
|AppWorkSpace||128 128 128|
|Background||102 111 116|
|ButtonAlternateFace||181 181 181|
|ButtonDkShadow||64 64 64|
|ButtonFace||212 208 200|
|ButtonHilight||255 255 255|
|ButtonLight||212 208 200|
|ButtonShadow||128 128 128|
|ButtonText||0 0 0|
|GradientActiveTitle||166 202 240|
|GradientInactiveTitle||192 192 192|
|GrayText||128 128 128|
|Hilight||10 36 106|
|HilightText||255 255 255|
|HotTrackingColor||0 0 128|
|InactiveBorder||212 208 200|
|InactiveTitle||128 128 128|
|InactiveTitleText||212 208 200|
|InfoText||0 0 0|
|InfoWindow||255 255 225|
|Menu||212 208 200|
|Menubar||212 208 200|
|MenuHilight||210 210 255|
|MenuText||0 0 0|
|Scrollbar||212 208 200|
|TitleText||255 255 255|
|Window||255 255 255|
|WindowFrame||0 0 0|
|WindowText||0 0 0|
Apache HTTD 2.4: Invalid command ‘Order’, perhaps misspelled or defined by a module not included in the server configuration
I recently upgraded one of my HTTPD severs from version 2.2 to 2.4. When I tried to start the Apache HTTPD daemon, I got the following exception:
Invalid command ‘Order’, perhaps misspelled or defined by a module not included in the server configuration failed
The problem was related to a change in the configuration specs of the "allow & deny rules". More info was found here. For a 2.4 configruation, you need to enable the following modules to be able to work with "authentication":
LoadModule access_compat_module modules/mod_access_compat.so LoadModule authz_host_module modules/mod_authz_host.so