w0wbagger

Tristan, did this fix the issues you were having with the FTP component(s) as well? Thanks, Ian

Is RSB-503 a reference number for the Embarcadero quality portal? I went to look for it there and all the reference numbers start with RSS-

Ah, sorry Angus, this was in the 9.4 download (latest stable version) from the Overbyte website. Should've downloaded the overnights instead. Apologies.

Amazon Echoes (I believe) do ARP scans of your local network. Could that be what you're seeing?

FYI, I just downloaded the latest version and this -k option is still in there for this cbproj file in the 32-bit debug build.

Verdict: Can confirm that if I remove the ICSPing.dcr file from the Common project file and the -k from the debug compilation additional parameters, it compiles fine in both debug and release modes, 32-bit. Will try FMX next. Then, will remove everything one more time and try the single-installation method. Edit to add: FMX installed correctly out of the box.

FWIW, got these three *warnings* when compiling VCLNew - not critical, but FYI: [DCC Warning] OverbyteIcsDnsQuery.pas(2248): Symbol 'StrLen' is deprecated: 'Moved to the AnsiStrings unit' [DCC Warning] OverbyteIcsDnsQuery.pas(2249): Symbol 'StrCopy' is deprecated: 'Moved to the AnsiStrings unit' [DCC Warning] OverbyteIcsMQTT.pas(1159): Comparison always evaluates to True For the last line, it's referring to this, specifically the first comparator. Because we've just done an and $03, x will always be >= 0, so: x := ReadByte (FRxStream) and $03; // V9.5 v3.1.1 may return x80 for failure if (x >= 0) and (x <= 2) then could become: x := ReadByte (FRxStream) and $03; // V9.5 v3.1.1 may return x80 for failure if x <= 2 then to eliminate the warning.

Hey Angus, this is in the IcsCommonCBNewDesign.cbproj file that I just downloaded from the overnights: <PropertyGroup Condition="'$(Cfg_1_Win32)'!=''"> <BCC_Defines>_DEBUG;$(BCC_Defines);$(BCC_Defines)</BCC_Defines> <BCC_UseClassicCompiler>false</BCC_UseClassicCompiler> <BCC_UserSuppliedOptions> -k</BCC_UserSuppliedOptions> <BPILibOutputDir>$(BDSCOMMONDIR)\BPL\$(Platform)\$(ProductVersion)</BPILibOutputDir> <DynamicRTL>false</DynamicRTL> <ILINK_Description>Overbyte ICS Common Design-Time Package for C++ Builder</ILINK_Description> </PropertyGroup> Also confirming that the .dcr file for ICSPing is still hanging out there alone in the CommonCBNewDesign.cbproj with no .pas file. TimeList, MimeDec, MimeUtils, and Logger correctly include the .pas in this file. Maybe your configuration ignores the spare .dcr file for some reason? Which project file should ICSPing.pas be in? common or VCL/FMX? (I haven't tested FMX yet because I don't use it, but happy to help debug it as well for other potential users). Edited to add: The difference is in whether you're doing debug or release compilation. Release has -r (which I guess is okay?), and debug has -k (which is not)

Roger that. I've just pulled down the overnight, am clearing all my directories, and will try again with these files.

I was using the overnight from 05/17/2025. ICSCommonCBNewDesign.cbproj is dated 02/10/2025 the '-k' shows up in this one. I can try to pull the most recent overnight and try again.

Okay! I've figured out why this was happening. There are a few units for which *only* the .dcr files are included in the icsCommonCBNewRun.cbproj file. Missing from the project file: OverbyteICSLogger.pas OverbyteICSMimeDec.pas OverbyteICSMimeUtils.pas OverbyteICSPing.pas OverbyteICSTimeList.pas In the case if OverbyteICSPing, the .dcr appears in both Common and VCL, but the .pas only appears in VCL. I don't know if it's meant to be in Common or VCL, but it probably shouldn't appear in both. For testing, I'm going to take it out of the VCL, but please let me know. I made these changes, and it compiled and installed in the 32-bit compiler. Will test with my application, but if it works it seems like we might be able to start using this new IDE! Let me know if you need further testing, after making these changes, Angus. Maybe we can get this on GetIt after all. Cheers, Ian

Edited to remove: LLM sent me down the wrong track.

Getting closer. I was able to compile icsVCLCBNewRun and icsVCLCBNewDesign after wrestling a bit with paths in the project, but it failed on installing the components with "Cannot load package 'IcsVCLCBNewRun290'. It contains 'OverbyteicsLogger', which is also contained in the package 'icsCommonCBNewDesign290'.. This is where my lack of understanding of creating/installing components is evident. Any ideas? I'll keep trying with the LLMs.

Solved this too: Project was not finding the icsVclCBCommonRun.bpi, which was created by that project in C:\Users\Public\Documents\Embarcadero\Studio\23.0\Dcp I added it to my global Libraries path in RAD Studio (although I could also have added it just to the project), and it compiled. I noticed that when compiling 64x, it puts the .bpi files in C:\Users\Public\Documents\Embarcadero\Studio\23.0\Dcp\Win64x, but it does *not* put the 32-bit one in C:\Users\Public\Documents\Embarcadero\Studio\23.0\Dcp\Win32 - maybe it should, and then we could add to Libraries C:\Users\Public\Documents\Embarcadero\Studio\23.0\Dcp\$(Platform) ? On to Design.

Understood. For my purposes, I just need to get it working in 32-bit, but it's the only component pack I use that's keeping us from moving to 64-bit, so I'll keep my eye on that once I've got 32-bit working. Thanks, Angus. My first attempt at compiling icsVclCBNewRun resulted in this: [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicstypes [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsticks64 [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsutils [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicscharsetutils [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicswinsock [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsftpsrvt [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicszlibhigh [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsstreams [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsonetimepw [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsmd5 [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicscrc [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsssleay [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicswsockbuf [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicswebsession [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsformdatadecoder [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicshtmlpars [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsurl [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsmimeutils [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicsntlmmsgs [ld.lld Error] ld.lld: error: undefined symbol: __init_record_Overbyteicssspi [ld.lld Error] ld.lld: error: too many errors emitted, stopping now (use /errorlimit:0 to see all errors) Investigating now.