A long while ago, DelphiBasics.info (they are hosted on Google Sites) posted a very interesting via: uExecFromMem unit. It was only a code snippet, not much usage info.
One of the things you can do with this unit, is load the memory image of an executable from a database BLOB, then execute that.
It opens way for some interesting deployment scenarios. Not for the everyday ones, but for the occassional situation where a regular deployment is impractical.
Comment by Craig Peterson at G+: https://plus.google.com/109418621512564781181/posts/WZSa6Nt44rK
It’s a handy looking unit, but has a licensing bomb in it: The PerformBaseRelocation routine is lifted directly from BTMemoryModule.pas, which is only licensed LGPL without the binary linking exception. That means providing your DCUs so anyone can relink your app. It’s also a bit less maintainable than BTMemoryModule, since they replaced a bunch of declared constants with magic numbers.
Today is a good day. I just had a call from a telemarketer. Did I yell and scream at them, you ask? Certainly not. Like a good IT administrator I put my skills to use for their benefit. Here’s how the conversation went.
Which ended with the phone of the Telemartketeer being factory reset.
If you ever had one of the below errors and your system does not have Restore Points, then you’re hosed: virtually no chance for recovering from that (except for once case, see below).
The errors are these:
Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
Windows XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SOFTWARE
Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\SOFTWARE or its log or alternate
System error: Lsass.exe
When trying to update a password the return status indicates that the value provided as the current password is not correct.
We’re excited to announce Sysmon, a new Sysinternals utility that monitors and reports key system activity via the Windows event log, including detailed information about process creation, network connections and file creation timestamp changes. With Sysmon installed on your systems, you can collect and analyze these events to identify the presence of attackers, and correlate events across your network to track them as they traverse your network.
Most things are simple when you know how to do it.
In this case it was to move the Dock to a different monitor (or to restore it to your main monitor when you accidentally moved it to a secondary monitor).
TbonesTech explains it in the below video, and it is this simple:
On the monitor on which you want the Dock to appear, move the mouse to the bottom of the screen.
Then wait a moment for the Dock to move to that location.
It works in Mavericks. It might work in older versions as well, but I’ve not checked that yet.
The Wiert Corner - irregular stream of stuff 