Jump to content

chmichael

Members
  • Content Count

    52
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by chmichael


  1. On 9/1/2022 at 11:18 AM, Sherlock said:

    Out of curiosity: How would binaries created with this fare on a Ryzen processor? Are Intel and AMD still 100% compatible? AFAIK Ryzen had problems on Win11 well into this summer, but that was because of TPM.

    They fixed ryzen problems with bios updates. I'm running the library (SeaMM & SeaRTL) on my Ryzen 5800 and it's working fine!


  2. 14 hours ago, Dave Nottage said:

    What do you consider "alive"?


    The last commit was April 27th, which isn't a real long time ago. The last issue closed was March 12th, and before that October 2021.

     

    There some bugs in the github issues list for months


  3. On 2/9/2021 at 5:47 PM, c0d3r said:

    As usual I sent email to Kim last week, no response.  Wish me luck if I get response.  Try registrating to its forum to ask questions, nope,  my work email was used and can't register,  try 'Forgot/Lost Password' link,  Oops,  your email doesn't exist.  I sent email to Kim about registration issue on Sunday,  lets see when I would get the response, so far no any response. 

      

    EDIT:   Oh, Oh,  the only email I can always get from him was the email that asking me to pay the annual subscription fee on due date.

     

    Well i made him notice you! Post the report on his forums and if it's an Indy bug i'm sure that @Remy Lebeau will help!

    • Thanks 1

  4. Hello,

      When i'm closing the application eg, after 30 seconds OTL will raise an exception with error code 1400 invalid window handle. Any ideas ?

     

    Thank you

     

    Code: 

    var
      FTask1: IOmniTimedTask;
      FTask2: IOmniTimedTask;
    
    procedure StartTimedTasks(const Task: IOmniTask);
    begin
      FTask1 := Parallel.TimedTask.Every(1000).Execute(DoSometing1);
      FTask2 := Parallel.TimedTask.Every(1000).Execute(DoSometing2);
    end;
    
    procedure TFormApplication.FormShow(Sender: TObject);
    begin
      Parallel.Async(StartTimedTasks);
    end;

     


  5. On 10/13/2020 at 12:00 AM, Vincent Parrett said:

    Umm, you might want to edit your reply so it doesn't look like I said it!

     

    What is the api you are calling? If an api you are calling is blocking, and doesn't take an event handle or have some way of cancelling then you cannot safely kill it.  Killing a thread on windows is dangerous, 

     

    https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-terminatethread

     

    Hello,

      Yes i know but i couldn't find any timeout for this API. It's the Winsock.Connect.

      Do you know how i can use the TerminateThread on Parallel.Async ?

     

    Thank you

     


  6. On 10/11/2020 at 5:07 AM, Vincent Parrett said:

    There is no point calling Async with CancellationToken since the above will timeout after 5000ms also!

     

    The reason i want to call it Async is because the API has 5000ms timeout and i want to timeout after 2000ms

    so in case it's still hasn't timeout i'll kill the async thread!

     

    Thank you

     

     


  7. Hello,

      Any ideas why the below code does not send the email: (it doesn't through an exception either)

     

    var
      vSMTP: TSmtpCli;
    begin
      vSMTP := TSmtpCli.Create(nil);

      with vSMTP do
      begin
        Host := 'my.mailhost.com';
        Username := 'user@mailhost.com';
        Password := 'password';
        OwnHeaders := True;

        ContentType := smtpPlainText;
        CharSet := 'UTF-8';

        HdrFrom := 'user@mailhost.com';
        HdrTo := 'user@mailhost.com';
        HdrSubject := UTF8Encode('Subject');
        MailMessage.Text := UTF8Encode('Body');

        Connect;

        while State <> smtpReady do
        begin
          ProcessMessages;
          Sleep(50);
        end;

        Mail;
        FreeAndNil(vSMTP);
      end;
    end;

     

    Thank you


  8. 3 hours ago, Arnaud Bouchez said:

    Also be aware that some FastCode pascal is not compatible with 64-bit, nor with FPC, since it targeted 32-bit Delphi only at that time.

    Yes, but I think that we have some FreePascal developers in here to sort this out.

     

    3 hours ago, Arnaud Bouchez said:

    And, as with FastCode, you will need to have a system to register benchmarks, on actual diverse computers.

    A centralized DB would be better than some XLS files (as with FastCode): any dev could compile and run the code on its own HW, for a given Delphi version, then send it to the main DB.

    See my answer to Tommi


  9. 5 hours ago, Tommi Prami said:
    1. When the FastCode was alive and kicking I suggested some kind of online server where benchmark/validation app could post results. Now hosting such a thing would be way easier.
    2. This could be good new contribution, to start with https://github.com/davidberneda/FastDateTime  (Not my code, just to be clear)

    1. I already have this in my design plans but it seems i can not host a database on the Github so currently i'll have to use my personal hosting.

    2. Thanks! I'll contact him after Benchmark/Validation apps are made.

    • Like 1

  10. 46 minutes ago, David Heffernan said:

    Hmm. Seems like an odd way to go about it. Choosing to contribute to an open source project means making a commitment. I personally wouldn't want to do that without knowing that the project will have strong leadership and values.

     

    Making a an empty box and asking people to throw stuff in it as they please isn't at all enticing. 

      Well i was on updating the FastCode "RTL replacement" then. Anyhow that is not my point, if you want to be the leader be my guest!

      My point is that all these years after FastCode nothing else is done and Microsoft has already made .Net Core open source. At least to me it's a start man to motivate your minds!
      I'll start to work moving the old FastCode code into this new project and on new Benchmark and Validation tools (on my free time), just follow the repository to see updates.

     

    That's all i can do for now.

    Thank you

     

     

    • Like 3
    • Thanks 1

  11. 2 hours ago, Arnaud Bouchez said:

    1. I wouldn't stick to 64-bit - do why call it UltraCode64 ?

    2. FPC compatibility could be very beneficial - as we did for mORMot.

    All the currently platforms are 64 bit so i don't think there is much point wasting time for 32bit code. Anyhow it's up to developers to choose not me! Free Pascal compatibility will bo no problem also. 🙂

     

    Also are the mORMot assembler routines 64 bit ?

     

    ps:

    I updated the first post with a Poll for 32-bit

×