DelphiUdIT

Yes, i know that. But arp implemented is very slowly (in some networks needs 15 minutes to be updated). In my solution you may have the knowledge immediately, of course like you told if there is the software running. Other way is to replicate the arp discovery for IPV4 (RFC826) scanning the whole net and do it more "fast". Of course one must implemented the NDP for IPV6 (RFC4861). But this means that you must run other software too. Bye

Another solution could be to create a simple UDP server with Indy on port x and use the UDP broadcast to send a packet (perhaps containing the list mentioned in my previous post). Obviously this solution works only on local networks. Each device connected to the LAN would receive that packet on port X from which you can detect both the "remote" address and possibly read the UDP packet data.

You can use Indy to find local addresses of every device. You can send these lists wherever you want. This is an example: uses IdStack, IdStackWindows; //<--- This is for Windows, but I think you can use others Units for others platforms (IdStacklibc, IdStackLinux, IdStack......) function GetLocalIpList(Name: string): TStringList; var Lista: TIdStackLocalAddressList; temp: TCollectionItem; GProva: TIdStackWindows; begin result := TStringList.Create; try Lista := TIdStackLocalAddressList.Create; GProva := TIdStackWindows.Create; GProva.GetLocalAddressList(Lista); for temp in Lista do if temp is TIdStackLocalAddressIPv4 then result.add((temp as TIdStackLocalAddressIPv4).IPAddress); GProva.Free; Lista.Free; except on e:exception do ; end; end;

Uses IdGlobal; procedure TForm1.Button1Click(Sender: TObject); var s: ansistring; t: TIdBytes; begin s := AnsiString('ABCD'); t := rawToBytes(s[1], length(s)); IdTCPClient1.IOHandler.Write(t); end; To communicate with older devices, I use ansistrings like that.

I agree with @Brian Evans, it is likely that BergSoft components or FasteReport need to be updated. Bye

I never had any issue with Jedi, but i always worked with license Embarcadero, not with CE. Just download 3 zipfiles from github, decompress them and run at cmd "install" two times. That's all. No path edit, no other things. Always working. But not with CE, because there is no support to command line compiler. Bye

With 11.3 it's the same. The .drc file is generated anyway.

My old projects (first made for Android 4.4) work in Delphi 11.3 (of course updating very little some code) and with old SDK. They run in Android 11 (and in the old Android simulator, still available with old SDK). Of course you cannot use new functions. I use local SQlite, Bluetooth and Internet. But of course I can't in any way guarantee you that your project will compile or work with it. P.S.: I don't distribute the APK via Google Play. I install it directly on the phone.

May be this should help: https://techcommunity.microsoft.com/t5/storage-at-microsoft/smb-signing-required-by-default-in-windows-insider/ba-p/3831704 It was released one month ago and I think it's now effective on the release channel.

HP have some laptop models with NVidia P600 Quadro (eg. HPZB15VG5). Like @FPiette said be sure that you use the latest driver installed. Also, try to force the app to works with integrated graphics (Intel GPU) or with NVidia. You can use the Optimus / GPU Nvidia settings from NVidia control panel. Bye

May be you can also use this: https://learn.microsoft.com/en-en/windows/win32/api/securitybaseapi/nf-securitybaseapi-createrestrictedtoken?redirectedfrom=MSDN If you use a thread to launch the activities, you can set new lower privilege with "SetThreadToken" and after that launch what you need. If you don't use a thread you must use "NtSetInformationProcess" to set lower privilege to current application. I use that very long time ago and I don't have any example at hand (and I don't know if it works now). Bye

I have no other suggestions, sorry. I had used that package several years ago only for the purpose of displaying various graphic formats in an application (and I had to display just a PLY coming from a 3D scanner). Good luck

You can try to see if you find anything useful in this project. It can open and view various graphic formats (including "PLY"). It is possible that something is also exposed on pascal the "PLY" and not only in DLLs. https://sourceforge.net/projects/glscene/files/GLScene/GLScene v2.2/

For zip you can use Delphi integrated library System.Zip.TZip https://docwiki.embarcadero.com/Libraries/Sydney/en/System.Zip.TZipFile For 3des and others you can use getit to get for example LockBox 3 2021.11 or DEC Lite 6.3. Both components can also be found on github. Bye

Using "priorities" to manage threads and their (hypothetical) distribution between cores is not simple and as mentioned it is not the right tool. For now multiple processors, processor groups and numa nodes are out of Delphi's handling, or better let's say Delphi is not optimized for that. Memory and all shared and non-shared resources are handled "differently" in these systems. Those who have programmed in multiprocessor systems (such as Xeon platforms) have experienced this. Bye

I'll never used affinity mask, 'cause my experience is that ThreadDirector does a good work. But like told if you want max performance one should use it. There are other systems too, for using max power form the system (eg. if one has additional graphic card): using OpenCL. One can start form here: https://github.com/LUXOPHIA/OpenCL Bye P.S.: I never used it, normaly i use OpenCL with others advanced library (artificial vision).

You can try to call this: function uCoreId: uint64; register; asm //from 10 gen it reads the IA32_TSC_AUX MSR which should theoretically //indicate the CORE (THREAD in the case of HyperThread processors) in which rdpid runs rdpid RAX; end; This function returns the ID of the core (means CORE THREAD) in wich rdpid runs. It works form Intel 10th generation CPU. The first Core Thread is numbered 0 (zero). You will see that also the efficients core will be sometimes used. This is because the ThreadDirector allocates threads (meaning processes) based on various factors. The distribution is not predictable. If you want to avoid using the efficient cores you have to use the affinity mask (for the whole program) and select only the performance cores. Bye P.S.: this is for WIN64 program.

Hello, with CHET you don't have do include nothing. It works on LLVM and this should be available in your system. A community edition of Visual Studio is typically necessary for this. Read the instructions for CHET. I cannot share the include file, 'cause they are not redistributable, but like i told in previous post you have to copy the .h files of halcon in one directory and go on. Some errors will be exposed because some files exposed a subdir path, change this and all will be done. Again, some functions refer to a wrong dll and you must change this in the wrapper (.pas file), but in my previous attachment you can see that. PS.: all Halcon libraries are converted in the wrappers that I posted. But in the wrapper that are only declarations, no code inside of course. Bye

It's a bit complex to explain, however I try. First, to use CHET you have to put all the includes you need into one directory, and then you have to change the definition in the individual file references, which originally point to subdirectories. Second, unlike C, where you can declare variables or definitions anywhere and even out of order, in the wrapper, declarations must be "ordered" (ie first you declare something, then you use it). So you have to take the generated .pas and move several declaration blocks at the head of the wrapper (or between various other declarations). It's not very complex, it just takes a little patience and taking into account that I do it every three years or so, everything is manageable. Another good thing is that once you've done it, you can use tools like Beyond Compare to help you: between the various versions of Halcon there are no abysmal differences, so much so that normally you just need to recompile the projects (or at least change some variables) to port to the new version. In updates between versions (for example between 20.11.01 and 20.11.03) there are no changes in the includes (unless it is explicitly highlighted in the notes) and therefore there is no need to change the wrapper. I normally use the Draw_Rectangle and similar functions without problems. If you want advice, when you can use the functions without the T_ as they use normal variables and not tuples. var ro1, co1, ro2, co2: double; //SomeWhere should be decalre "fWindowHandle: HLong;" and should be assigned of course Draw_Rectangle1(fWindowHandle, @ro1, @co1, @ro2, @co2); //and you can use of course also the _mod function ..... Bye P.S.: Beware of one "thing": when a function returns multiple elements (for example a list of points), it MUST be used in the form "T_" i.e. with tuples, unless it is certain that only one value is returned, such as example when preceded by the SelectObj function.

Hello everyone, sometimes it's good to have some good news in the forums and not always requests for support (even if these always improve technical skills). With Alexandria Rad Studio 10.3 I tried to enable TLS 1.3 support using a trunk version of Indy "https://github.com/mezen/Indy/tree/NewOpenSSL_PR" already described in issue 299. Uninstalled Indy from RAD STUDIO. Known Issues: - Lost support for FMX LivePreview (which I don't use). - Each time Rad Studio is closed, a runtime error is generated in the RTL library.... It is not recursive and when OK it disappears without a trace. I only close RAD Studio 1 or 2 times a day so it doesn't give me any problems. Care must be taken to remove all references to the original Indy sources in the RAD STUDIO LIBRARY path. To make it faster I saved the Windows registry with REGEDIT, edited with a NOTEPAD removing all references to INDY from the various keys and re-imported again with REGEDIT. I then entered the new paths (Core, Protocols, System, OpenSSL) of the new archive (unzipped in a directory on the disk) again in RAD Studio. Without touching anything, recompiling the old project with native OpenSSL 1.0.2 support worked perfectly. Then I modified the source by inserting a $DEFINE and some $IFDEFs to easily switch from version 1.1.1 to version 1.0.2 and vice versa. Version 1.1.1 actually only needs to specify the security keys (cipher) to use which are different from those of 1.0.2, and obviously have access to the two OpenSSL 1.1.1 DLLs. Everything works, with TLS 1.3 support and automatic downgrade to TLS 1.2 (as already reported in other TOPICs). Changing the $DEFINE and recompiling switches to the old "original" version with TLS 1.2 support with OpenSSL 1.0.2 All third-party components (obviously in source format) that use Indy work perfectly even with the new version once recompiled. I haven't tested all of my projects that use Indy to see if there were any issues, but the last 10 recompiled projects didn't produce any glitches. When I have some time I will try to reinstall RAD STUDIO from scratch and directly upgrade the Indy TRUNK in the original RAD Studio version just to see if by recompiling from there you can avoid LIBRARY PATH updates (except the OPENSSL which you have to add by hand) and above all if you manage to avoid the error when closing RAD Studio. Bye P.S.: the project is an HTTPS server directly derived from an Indy demo. It is online in Internet without any filter, protection or other with no issue at all after more than one years in two systems Windows desktop and Linux server (now the Linux server is not anymore online).

You can create different empty projects and see the differences between them. I think that an empty project consists in two relevant files: .cbproj and .cpp (or .c). Use Beyond Compare to see the differences. Bye

This is not an interface with .net assembly. It's a wrapper around C library. This will use the HalconC.dll. Nothing to do with .Net. And Yes i created lot of projects, may be not very big but most of them use 20 and more thread like that in the examples (of course with more and more functions inside) with Halcon. I don't have memory leak, but you must care to "clear" every single hobject that you use, before use it (not need if you are sure that is nil). If you reuse an object without clear it and it's already in use you will "lost" the memory (means LEAKS). Also, the wrapper don't has any know about macro, so you cannot use Halcon macro in Delphi. But this was never a problem for me. Bye

I used that tool, but to use it i had modified the include file (.h) of Halcon and after that i had manually adjust the pas file results of Chet. Some manually works, every 3 years

This is sample program ready for Halcon 20.11 Steady. https://cloud.dyn-o-saur.com/Project_H2011.zip Bye

I knew that Halcon informally supported COM up to version 18.05. After that, COM support was dropped entirely. I think that you can use COM with 20.11 only for the old functions. But that doesn't matter, since they decided to remove COM support anyway and therefore it was still necessary to switch to something else. Meanwhile, I'm attaching the wrapper for 20.11 Steady (which is the penultimate version), then I'm attaching an example for 20.11 to use the wrapper similarly to how you now use COM. I'll give you the example with a THREAD, which is the best way to use Halcon. HalconC_2011.pas Bye