GExperts and older / unpatched Delphi IDEs

 Delphi, GExperts  Comments Off on GExperts and older / unpatched Delphi IDEs
May 162021
 

GExperts is always compiled with the latest update of any of the supported Delphi versions. That unfortunately means that it may not work if the IDE hasn’t been updated to the latest version. E.g. The latest GExperts release will not work with Delphi 10.2, but only with Delphi 10.2.3, the latest update to Delphi 10.2. This is due to changes in the runtime packages that are not always backward compatible.

Until a few years ago, this was no problem because when you bought Delphi you were automatically entitled to receive all updates for this version. E.g. if you bought Delphi 2007 you could download all updates for it and GExperts would simply work for you.

This changed when Embarcadero tried to force all their customers to buy a maintenance subscription. Now, if you don’t have such a subscription, you will no longer receive updates and bug fixes. You automatically get a subscription for 1 year when you buy a new Delphi license so this sounds like a minor issue. But a subscription not only gets you updates but also upgrades to the yearly major releases, e.g. from 10.2 to 10.3.
So, if you do not extend an existing subscription shortly after a new major release you will not get updates and bug fixes for this release. You have only two options then: Stick with the previous major release + all updates and bug fixes, or keep using the latest major release and hope that you don’t need the updates for it. Of course that’s on purpose to keep customers extending their subscriptions.

This also affects GExperts: If you are stuck using a non-updated major release GExperts might not work for you.

I have been asked whether I could make releases for these cases. Unfortunately this would require me to keep all minor Delphi releases around, e.g. 10.2, 10.2.1, 10.2.2 and 10.2.3. These cannot be installed on the same computer so that would mean 4 virtual machines for Delphi 10.2.x alone + several for other major versions. Yes, I could do that. But since GExperts is currently a one man (me) show, it would take quite a lot of my time for very little gain. (But everybody is invited to contribute!)

So, what can be done? If you are one of those people affected by this, simply build your own DLL. It’s not difficult at all. This will create a DLL that is compatible to the Delphi version you are using, so your problem is solved.

If you want to comment on this blog post, you can do so in the corresponding topic in the international Delphi Praxis forum.

 Posted by on 2021-05-16 at 16:59

Adding a Windows 10 computer to a Samba (NT4) domain

 Linux, Windows, Windows 10  Comments Off on Adding a Windows 10 computer to a Samba (NT4) domain
May 042021
 

Microsoft is trying to force everybody to update from the old NT4 domain system to the “new” (as in “was new >10 years ago”) Active Directory system. While that’s probably a good idea for most people there are some like me stuck with a working Samba installation that for some reason needs to continue to use NT4 domains.

Getting a Windows computer to join such a domain has become more difficult with Windows 10. Here is what needs to be done (I write this mostly so I can look it up myself):

  1. Make sure your samba server is configured to enforce the NT4 (SMB1) login. samba.conf must contain the following entry:
    [global]
    // other entries here
    server max protocol = NT1
    
  2. Install the SMB1 protocol on the Windows computer. This is done using the “Turn Windows Features on or off” dialog (just type this into the start menu). You need to set the check marks for two entries under “SMB 1.0/CIFS File share Support”:
    • SMB 1.0/CIFS Client
    • SMB 1.0/CIFS Server

    I’m not 100% sure whether the latter is required. I haven’t tried it without.

  3. Add the following entries to the registry:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]
    "DomainCompatibilityMode"=dword:00000001
    "DNSNameResolutionRequired"=dword:00000000
    

    You can either add them manually or copy the above to the .reg file and import that into the registry.

  4. Reboot the computer to activate these changes.

Now it should be possible to join the Windows 10 computer to the Samba Domain.

Source: Required Settings for Samba NT4 Domains on the Samba Wiki.

 Posted by on 2021-05-04 at 15:32