Did you just run into a file that has been digitally signed by Softland? If that's the case, please read on.
You'll probably see Softland when running the file. The publisher name is then displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:

You can also view the Softland certificate with the following procedure:
Here's a screenshot of a file that has been digitally signed by Softland:

As you can see in the screenshot above, Windows reports that "This digital signature is OK". This means that the file has been published by Softland and that the file has not been tampered with.
If you click the View Certificate button shown in the screenshot above, you can examine all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, and so on. You can also see the address for Softland, such as the street name, city and country.
VeriSign Class 3 Code Signing 2009-2 CA, VeriSign Class 3 Code Signing 2010 CA and UTN-USERFirst-Object has issued the Softland certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screengrab above.
These are the Softland files I have collected, thanks to the FreeFixer users.
| Detection Ratio | File Name |
|---|---|
| 0/40 | dopdfui7.dll |
| 0/48 | dopdfui7.dll |
| 0/43 | dopdfui7.dll |
| 0/39 | dopdfui6.dll |
| 0/47 | nvimgk6.dll |
| 0/55 | dopdfui6.dll |
| 0/57 | dopdfui5.dll |
| 0/56 | dpactx5.dll |
| 0/61 | dopdfin7.exe |
The detection percentage is based on that I've gathered 446 scan reports for the Softland files. 0 of these scan reports came up with some sort of detection. If you like, you can view the full details of the scan reports by examining the files listed above.
The analysis is done on certificates with the following serial numbers: