Jump to content

mitzi

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

39 Excellent

1 Follower

About mitzi

  • Birthday 07/17/1970

Technical Information

  • Delphi-Version
    Delphi 10.4 Sydney

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 1.4.4 10.9.2021 + Embarcadero Delphi 11 Alexandria compatibility For more information see https://www.mitec.cz/pm.html
  2. 14.5.1 10.9.2021 + TMiTeC_CPU - added new AMD and Intel processor detection + TMiTeC_OperatingSystem - added Display version (ReleaseID becomes obsolete) + Windows 11 compatibility + Delphi 11 Alexandria compatibility For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page
  3. As you likely noticed, Delphi 11 officially does not support Windows XP anymore. You can make your application compatible with XP again by simple set. In Project Options|Building|Delphi Compiler|Linking set "Set OS Version fields in PE Headers" and "Set SubSystem Version fields in PE Headers" to "5.1". Unless your application uses System.Threading.pas (TTask etc) you should run it under Windows XP with no problems. But if so, then you have to tweak this unit. Threading objects actually use in their internals new TThread.GetTickCount64 method, which is hardwired to Windows API GetTickCount64 which is not available in Windows XP API. Take this unit from "source\rtl\common" folder in Delphi 11 installation. Declare new local function in the beginning of implementation section of this unit like this: function _GetTickCount64: UInt64; begin if TOSVersion.Major<6 then Result := TThread.GetTickCount else Result := TThread.GetTickCount64; end; and replace all occurrences of TThread.GetTickCount64 calls with _GetTickCount64. For Win32 applications then copy this modified unit to \lib\win32\debug and \lib\win32\release folders in Delphi 11 installation and rename original System.Threading.dcu to e.g. _System.Threading.dcu. Then build your project which uses System.Threading with Debug and Release configuration. New System.Threading.dcu should be created in mentioned folders. After this you should remove modified System.Threading.pas from these folders to prevent its recurrent compilation. Now your Delphi 11 Win32 applications should run under Windows XP with no External Exception crash.
  4. 14.5.0 + MSI_SysProcMon - Added process username to sampling data + TMiTeC_Display - added GPU property indicating GPU presence * TMiTeC_CPU - fixed cpu core and thread count detection + TMiTeC_CPU - added SocketCount and SocketDesignation properties * TMiTeC_SMBIOS - fixed cache size detection when its size exceeding word boundary For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page
  5. What is Project Maker? MiTeC Project Maker is tool for automated batch Delphi projects building. With Project Maker, you can set compiler and its configuration, define actions processed before and after building, patch version information of built binary, sign this binary with specified certificate, apply 3rd-party software protection and many more. How does Project Maker work? Project Maker offers clear powerful interface for project building task definition. Every project can contain unlimited number of tasks. Task represents Delphi project, defined in dpr or dproj file. In addition Project Maker features Profiles, where you can define common properties for project. The project can have unlimited number of profiles. Using profiles you can simply switch between variety of build configurations. Who is Project Maker targeted on? Project Maker is targeted on developers who need to make various build scenarios and make repeated actions automatic. Project Maker is simple but powerful and provides one-click building of very complex and dependent projects. For more information see https://www.mitec.cz/pm.html
  6. MiTeC Project Maker 1.2 released * Fixed CPU affinity adjusting for compiler process + Added Code signing properties to Bulk set More information here
  7. MiTeC Internet Browser History Component Suite 1.4 released + added standalone TIBH_EdgeChromium component for Microsoft Edge Chromium history + added standalone TIBH_Brave component for Brave Browser history More info: https://www.mitec.cz/mibhcs.html
  8. New version 14.4.0 released * TMiTeC_Machine - domain detection fixed + TMiTeC_AD - Active Directory object properties evaluation enhanced * TPerfMonThread - Multi-instance counters evaluation fixed + TPerfMonThread - GPU processes and engines monitoring added + TMiTeC_Display - property LUID, PhysID, DriverDesc, DriverVersion, Location, WDDM version and GPU node enumeration added * TMiTeC_Storage - SUBST drives are now correctly evaluated + TMiTeC_Storage - SSD NVMe disks temperature detection * TMiTeC_Internet - Default internet browser and email client detection fixed + TMiTeC_Security - Added product version + TPerfMonThread - Added Demo 33 - GPU Utilization * TMiTeC_CPU - Codename and technology evaluation enhanced + TMiTeC_CPU - CPUIDSignature and MicroCodeRevision properties added * TSysProcMonThread - Fixed process module enumeration + TMiTeC_MachineJournal - Added Power event 41 evaluation + TMiTeC_SMBIOS - Table 2 (Mainboard) compeletd + TMiTeC_SMBIOS - Table 3 (Chassis) completed + TMiTeC_SMBIOS - Table 5 (Memory Controller) completed + TMiTeC_SMBIOS - Table 9 (System Slots) completed + TMiTeC_SMBIOS - Table 12 (System Configuration Options) added + TMiTeC_SMBIOS - Table 13 (BIOS Language Information) added + TMiTeC_SMBIOS - Table 34 (Management Devices) added + TMiTeC_SMBIOS - SMBIOS value reading code example added + TMiTeC_SMBIOS - SMBIOS now saves SMBIOS raw memory to SIF file and reconstructs all data from this record (if available) on load + TMiTeC_Devices - Added Parent field to TDevice to ensure correct device hierarchy + MSIX application - UI enhanced and polished + MSIX application - added embedded vendor and product database so that VendorID and DeviceID/ProductID are now translated to real names + MSIX application - Bus tree is now correctly hierarchised + ROM BIOS Explorer application - UI enhanced and polished For more information about the library, download locations and documentation, see the MiTeC System Information Component Suite Home Page
  9. New version 2.4.0 released * Fixed version info parsing bug (out of memory) + QT Installer detection added + Executable description - property Description + Overlay data type detection - property OverlayDataType + Advanced Installer detection + StarForce protection detection + WinZip installer detection + Rich header table detection enhanced + Debug information type detection enhanced + Load Config detection enhanced For more information about the library, download locations and documentation, see the MiTeC Portable Executable Reader Home Page
  10. What is Project Maker? MiTeC Project Maker is tool for automated batch Delphi projects building. With Project Maker, you can set compiler and its configuration, define actions processed before and after building, patch version information of built binary, sign this binary with specified certificate, apply 3rd-party software protection and many more. How does Project Maker work? Project Maker offers clear powerful interface for project building task definition. Every project can contain unlimited number of tasks. Task represents Delphi project, defined in dpr or dproj file. In addition Project Maker features Profiles, where you can define common properties for project. The project can have unlimited number of profiles. Using profiles you can simply switch between variety of build configurations. Who is Project Maker targeted on? Project Maker is targeted on developers who need to make various build scenarios and make repeated actions automatic. Project Maker is simple but powerful and provides one-click building of very complex and dependent projects. For more information see https://www.mitec.cz/pm.html
  11. mitzi

    TCP Client in thread

    TCP clients are connected to devices (servers) or devices connects to TCP servers as clients and receive raw data to stream. Once the data is identified as valid input (data has header and terminator or etc) it is passed to thread which parses data by protocol (defined by header) and creates unified "signal" structure which is pushed to Buffer. Many data sources feed this Buffer this way (hundreds data packets per second). Other TCP clients are connected to other application (TCP server) which processes these signals. More sending TCP clients ensure faster signal delivery to main app. See attached scheme.
  12. mitzi

    TCP Client in thread

    I really don't know what is wrong with thread containing TWSocket where in Execute method buffer is repeatedly asked for data and if data is available then TWSocket sends it. Why this solution is not recommended? Buffer is FIFO and it is (and should be) independent of any communication or messaging. It features Push and Pop methods and it is up to any kind of client to ask it for data or feed it with data. No trigger mechanism is usable because if new client is created it simply can't wait for any message signalling there's data available. It must look itself for it. Repeatedly. Thread is the best solution for this in my opinion. Only problem is with issues I mentioned in initial post.
  13. mitzi

    TCP Client in thread

    Well, I'm really lost. I need several tcp clients to pop data from buffer simultaneously and send them as quick as possible. I need either timer or loop for this, but both are blocking, or thread where tcp client is its member but it does not work correctly :(. If there were some event like OnIdle or something like that where I would call pop and send when socket is ready or available then I understood how to do it without thread. But I didn't find anything like that. Buffer is fed with data from several processing threads massively so it is not too good idea to trigger all sending clients from it.
  14. mitzi

    TCP Client in thread

    New demo ICSTCP.ZIP
  15. mitzi

    TCP Client in thread

    No problem, I can rewrite demos to use standard non-thread model (they were written such way in the beginning).
×