Her er en oppskrift for å få alle Norges poststeder inn i en egnet tabell.
A student came to my office today. His browser showed our
fronter.com instance protected by a peculiar SSL certificate issued by
royalvulkan.com. The norm for
fronter.com instances are SSL certificates issued by COMODO CA Limited. The intrusive SSL certificate has a validity period spanning from 1996 to 2056, which is very odd. The certificate probably has a wildcard Common Name, causing it to cover all conceiveable hostnames. I have no idea how this certificate got introduced into our student’s computer. Luckily, Google Chrome spotted the faulty certificate and the student was wise enough to come and see me. Shortly after, I had to leave the student and go to class. I’ll try and update this post if he shows up again with the same problem.
I pondered this issue during the weekend. Maybe the student has somehow activated the proxy setting, sending all his (sensitive) internet traffic to an unknown third party.
If you run into error 30174-4 while installing MS Office and related software, try running a full repair of the product from the Control Panel.
After installing Autodesk Revit 2017 on a student’s laptop, the software started whining about missing
msvcr100.dll. This was solved by repairing Microsoft Visual C++ Redistributable for Visual Studio 2012 Update 4, both x86 and x64.
I was installing Autodesk Vault Professional 2017 in the wee hours today, and I noticed the Autodesk Network License Manager was installed in
C:\Autodesk\Network License Manager. That’s a bit strange when
C:\Autodesk has until now been a temporary location for extracting the setup files.
I can confirm moving the files to a saner location like
C:\Program Files\Autodesk\Autodesk Network License Manager doesn’t work at all. The NLM simply won’t start and nothing gets logged.
It gets even stranger as one of the LMTOOLS shortcuts wants to run
lmtools.exe from the
C:\Program Files\Autodesk\Autodesk Network License Manager directory, i.e. the old location. Note, this was done on a newly installed Windows Server.
In short: Be very careful when emptying the
Warning! Your server is on fire! Also, you are out of milk.
Ref.: Linux Journal, Issue 267, July 2016, pp. 14-15.
Det er to ting jeg har sluttet å bli overrasket over. Etterretningenes kynisme og befolkningens naivitet.
Fourth law of programming:
Anything that can go wrong wi
Our product is broken, so just tell the OS not to use the broken feature and hey presto you’re a winner! Now stop bugging us with your Loonixes and stuff.