Even though TeeChart uses a year and minor version number during installation, that’s not the only version number available or used.
For instance their bug reporting site bugs.teechart.net uses build versions.
They are easy to get for your product: just look at the units TeeConst, VCLTee.TeeConst or FMXTee.Constants having consts like these:
TeeChartVersion =String('9'); // Cast to String to force CPP *.hpp generation as AnsiString instead of AnsiChar
TeeProductName =String('2015');
TeeVCLMinorVersion ='.15'; // ie: '.01' '.02' , etc
TeeVCLBuildVersion ='150420'; //YYMMDD
TeeVCLBuildVersionInteger = 150420; // <-- Same as above as integer number
You probably get the drift:
TeeProductName.TeeVCLMinorVersion is what you see when installed.
TeeVCLBuildVersion is what is on the bug report site.
Sometimes RDP limits you to 2048 pixels vertical (or 4096 pixels horizontal)
Just found out why on some Windows versions, the RDP sessions form my 4K monitor has some small black bands on top/bottom: older versions of Windows limit their RDP server to 4096 x 2048.
A 4K monitor will not hit the width limit (as 4K cheats: it is usually “just” 3840 pixels wide), but it does hit the height limitation (2160 is slightly more than 2048: you miss 112 pixels that show as two small black bands).
A 5K monitor is worse: it will hit both limits (5K does not cheat: at 5120 × 2880 it is exactly 5*1024 pixels wide) so you miss 124 pixels horizontally and a whopping 832 pixels vertically.
Don’t buy a 5K monitor yet if you do a lot of RDP work to older Windows versions.
The link below has a table listing various Windows versions, but it omits end-of-life versions so I’ve done some testing: Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2003 R2 share the same limitations as Windows Server 2008 most likely because their latest service packs share the same RDP 6.1 version.
By constructing such an invitation URL you can get people to directly start a Google Hangouts chat with you.
The above steps will give you a lot of JSON output which includes an id field somewhere in the middle. With one more trick you can get just the id field.
You can limit the output by putting id in the fields to request as the image on the right shows.
Sometimes clicking on G+ posts, you even get the id for free, I’m just not sure under what circumstances G+ builds a G+ URL with username or with id.
There are quite a few pages on Webserver Cypher Hardening. This is yet another one born because I didn’t know how to compare these lists and why they were so different.
Apparently, OpenSSL has various ways of naming (groups of) cyphers. OpenSSL also disregards any cyphers it doesn’t have.
Basically there are two far ends for cypher lists:
Fully name all cyphers and their order: long list fine grained control
Name groups including group order and let OpenSSL expand the groups: short list but coarse grained control.
Delphi Component/Tool vendors have to support a truckload of Delphi and C++ Builder versions which can be a pain: they have to work around problems in Delphi and C++ Builder versions that have long been abandoned by Borland/CodeGear/Embarcadero/Idera/…
This means that sometimes the Delphi Component/Tool vendors have to work around stuff in a way normal applications vendors would never do.
Recently I learned that sometimes this can be a painful thing: keeping DFM files in binary state.
I’m not kidding about either the DFM file format nor about supporting old versions:
That’s why TeeChart still has most DFM files stored as binary files (again the ‘most’ word).
For version control and searching this is a pain, so normal application developers (the ones not using Delphi XE5 Update 1 for Android work) should run convert.exe with the -t (target=text) switch on DFM binary files.
In practice, either makedepend, or the alternative is available, so when prepping for a build you have to choose which one to use.
Some of those open source projects use Perl as a bootstrapper. I’ll write more about those boots trappers in the future, but first lets go back to the post title:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
I knew the APC download site http://www.apc.com/nl/en/tools/download/index.cfm was slow and navigation unfriendly (lots of ERR_CACHE_MISS as you cannot ctrl-click on downloads), but it’s also buggy: Some of the ftp download URLs do not contain the authentication and one file would not download at all.
The solution for that is to prepend the credentials as username:password@ like these URLs where each first one is generated by the download site and each second one works:
Otherwise you will get bash errors like these: event not found for the part starting with an exclamation mark and Login incorrect. for the parts having a dollar.
One file would not download at all: ftp://ftp.apc.com/apc/public/software/pnetmib/mib/417/powernet417 as all download attempts would time out:
Chrome with and without username:password@ (you will get a ERR_FTP_FAILED)
wget with and without username:password@ (it will result in a )
plain curl with and without username:password@ (it will result in a curl: (28) Timeout was reached)
The Wiert Corner - irregular stream of stuff 