Here is the question:
programmers.stackexchange.com: Does it make sense to use “ys” instead of “ies” in identifiers to ease find-and-replace functionality?
2015-07-28
Woohoo! One more of my "Programmers SE" answers has received a score of -5 !
The question is on a controversial topic, and as usual, I take the controversial stance. So, it is no wonder that people do not agree with me.
Here is the question:
programmers.stackexchange.com: Does it make sense to use “ys” instead of “ies” in identifiers to ease find-and-replace functionality?
Here is the question:
programmers.stackexchange.com: Does it make sense to use “ys” instead of “ies” in identifiers to ease find-and-replace functionality?
2015-07-26
How to: Completely disable "Aero" in Windows 7
So, with Windows 8 sporting these god-awfully ugly opaque square boxes, which are not adorned in any way whatsoever, (not even the decent in all its simplicity gradient of Windows 98,) it seems like a confession on Microsoft's behalf that the spiffy "Aero" look of Windows 7 was nothing but an unnecessary gimmick afterall.
So, are you sticking with Windows 7 but want to disable Aero in order to enjoy considerable gains in performance, memory, power consumption, and GPU temperature? Here is how:
So, are you sticking with Windows 7 but want to disable Aero in order to enjoy considerable gains in performance, memory, power consumption, and GPU temperature? Here is how:
- Open up "Services".
- Locate the service "Desktop Window Manager Session Manager".
- Disable it and stop it.
2015-07-25
How to: Disable the administrative shares in Windows
To disable the administrative shares in Windows, (default shares like C$, ADMIN$, etc.) follow these steps:
1. Run the Registry Editor and go to the following key:
3. Reboot Windows.
This will disable things like C$ and ADMIN$.
I am not sure how to also delete print$ and IPC$. ("net share ipc$ /delete" appears to work temporarily, but the share automagically re-appears after the next reboot.)
1. Run the Registry Editor and go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\LanmanServer\Parameters2. Create a new DWORD, name it AutoShareWks, and leave the default value of 0.
3. Reboot Windows.
This will disable things like C$ and ADMIN$.
I am not sure how to also delete print$ and IPC$. ("net share ipc$ /delete" appears to work temporarily, but the share automagically re-appears after the next reboot.)
How to: Enable the Administrator account in Windows
To enable the Administrator account in Windows:
1. Open up an elevated command prompt. (If you do not know what this is, you should not be even thinking of enabling the Administrator account.)
2. Type the following command:
1. Open up an elevated command prompt. (If you do not know what this is, you should not be even thinking of enabling the Administrator account.)
2. Type the following command:
net user administrator /active:yes
2015-07-20
Solved: Windows: WiFi connect immediately after boot and before logon
In order to have your windows computer connect to your favorite WiFi access point immediately after booting, (without you having to first login to your computer,) follow these simple steps:
1. First of all, make sure that this computer has connected before to the WiFi spot of interest. (A so-called wireless profile is created as a result of this manual process.)
2. Run cmd.exe and issue the following command:
4. Run regedit.exe and navigate to this key:
Many thanks to user Soumya of superuser.com for posting this:http://superuser.com/a/133935/111757
1. First of all, make sure that this computer has connected before to the WiFi spot of interest. (A so-called wireless profile is created as a result of this manual process.)
2. Run cmd.exe and issue the following command:
netsh wlan show profile3. In the list of wireless profiles that are displayed, locate the one you want, and copy its name to the clipboard.
4. Run regedit.exe and navigate to this key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run5. Add a string value to this registry key. Name it anything you like, and give it the following value:
%comspec% /c netsh wlan connect name="<profile name>"Voila, next time you restart, your computer will immediately connect to this WiFi spot if it is in range.
Many thanks to user Soumya of superuser.com for posting this:http://superuser.com/a/133935/111757
2015-07-14
Solved: cannot eject USB device: "This device is currently in use."
Millions of people all over the planet continuously have this problem: they try to eject their USB drive so as to avoid data loss, but windows does not allow them. Which is very frustrating, because whatever reasons windows thinks it has for not allowing the removal should have lower priority than the user's explicitly stated direct wish to remove the damned thing!
Anyway, suggestions for solutions abound on the interwebz. Here are some that I found with a quick search:
1. Put your computer to sleep. When going to sleep, Windows flushes all buffers to all devices, so while the computer is asleep, it is safe to remove the device. The problem with this approach is that I don't want to have to put my bloody computer to sleep each time I want to take a USB device out.
2. Use SysInternals Process Explorer to search for the drive name, find which process has a handle open on the drive, and terminate it. The problem is that drive names are only one a letter and a colon, a search for "D:" may yield thousands of handles from several dozen processes, all of which are unrelated to your drive "D". Unfortunately, Process Explorer does not offer any option to search for a whole word only. Another problem is that this approach hardly ever works. Apparently, there are ways in which devices can be locked which do not show in Process Explorer. Even if you remember to launch it as Administrator.
3. Select "Quick removal" policy as opposed to "Better performance" policy in the drive properties. The problem with this is that it is not really a solution: we generally do specifically want the better performance, and we are willing to sacrifice quick removal for it, accepting slow removal instead. But this issue is not one of slow vs. fast removal, it is about not being allowed to remove your device at all, ever!
Here is the solution which worked for me, after the above failed:
4. Make sure that the drive, or any folders in it, are not shared on the network! (Use "NET SHARE" on the command prompt to quickly find out what you are sharing.)
Anyway, suggestions for solutions abound on the interwebz. Here are some that I found with a quick search:
1. Put your computer to sleep. When going to sleep, Windows flushes all buffers to all devices, so while the computer is asleep, it is safe to remove the device. The problem with this approach is that I don't want to have to put my bloody computer to sleep each time I want to take a USB device out.
2. Use SysInternals Process Explorer to search for the drive name, find which process has a handle open on the drive, and terminate it. The problem is that drive names are only one a letter and a colon, a search for "D:" may yield thousands of handles from several dozen processes, all of which are unrelated to your drive "D". Unfortunately, Process Explorer does not offer any option to search for a whole word only. Another problem is that this approach hardly ever works. Apparently, there are ways in which devices can be locked which do not show in Process Explorer. Even if you remember to launch it as Administrator.
3. Select "Quick removal" policy as opposed to "Better performance" policy in the drive properties. The problem with this is that it is not really a solution: we generally do specifically want the better performance, and we are willing to sacrifice quick removal for it, accepting slow removal instead. But this issue is not one of slow vs. fast removal, it is about not being allowed to remove your device at all, ever!
Here is the solution which worked for me, after the above failed:
4. Make sure that the drive, or any folders in it, are not shared on the network! (Use "NET SHARE" on the command prompt to quickly find out what you are sharing.)
Solved: The network folder specified is currently mapped using a different user name and password
So, I am on computer A, trying to map a local drive to a shared folder of computer B, and Windows gives me this message: "The network folder specified is currently mapped using a different user name and password".
Microsoft supposedly addresses this issue here: https://support.microsoft.com/en-us/kb/938120 and concludes that it is so by design.
Bullshit. They are missing the point. The error message is wrong. The network folder specified is not currently mapped using a different user name and password. Instead, what is happening, is that another folder of the same computer B is already mapped on computer A using a different user name and password.
So, apparently, with windows, if you connect from computer A to any share of computer B, then all subsequent attempts to connect from computer A to other shares of computer B must be done using the same credentials. Go figure.
So, apparently, with windows, if you connect from computer A to any share of computer B, then all subsequent attempts to connect from computer A to other shares of computer B must be done using the same credentials. Go figure.
Subscribe to:
Posts (Atom)