Jump to content

Sherlock

Moderators
 View Profile  See their activity

  • Content Count

    1291

  • Joined

  • Last visited

  • Days Won

    28

Posts posted by Sherlock

  7. Posted

    To expand (or perhaps reiterate) that answer: Components are not installed (or even bought) just to have them. If during programming you discover you would benefit from a ready to use component for some functionality over writing it yourself then you should consult the internet or perhaps this forum on where to find such a component. Event hen, if it is a commercial component, you might want to calculate the cost benefit over writing it yourself. Furthermore it is most often preferable to have sources for components to ensure their use over time.

  8. Posted

    2 hours ago, Der schöne Günther said:

    Would you be willing to tell more about your daily usage, maybe in a separate thread? I'd be absolutely interested in typical day to day usage, battery runtimes, standby/wakeup times and where it could start to get tricky (old printer drivers, shell extensions, obscure software,...).

    I think it would be fair to say that Windows on ARM is not for legacy environments. It is intended for new mainstream devices. So no immediate support for decades old printers and other old hardware should be expected. However(!) as soon as it gets more traction I expect that to change.

    • Like 1

  9. Posted

    You should rather read that as "they will open up the next major construction site as soon as there is money and manpower available, and it will take several releases until it is usable"...and even that should be taken with a grain of salt.

    • Like 1

  16. Posted

    On 3/23/2025 at 11:56 AM, Vincent Parrett said:

    Signotaur can sign MSIX files

    Oh, that sounds great. For a test run, I downloaded the installer and am quite overwhelmed by the further needs (service user, SSL-certificate, Server) to run the "server". For a small test if my msix could be signed by this, it seems quite the overkill. 😞 

  17. Posted

    2 minutes ago, DelphiUdIT said:

    I don't know if there is difference, but have you tried to use:

      

    
"C:\Program Files (x86)\Windows Kits\10\App Certification Kit\signtool"

     

    I have, and that uses an older version of signtool: 

    "C:\Program Files (x86)\Windows Kits\10\App Certification Kit\signtool.exe" sign /v /a /fd SHA256 C:\Win\SignTest\Win64\Release\SignTest\bin\SignTest.msix
The following certificate was selected:
    Issued to: My Company
    Issued by: Certum Extended Validation Code Signing 2021 CA
    Expires:   Sat Jan 08 12:11:18 2028
    SHA1 hash: E7C16794EA23F573DE3EA32B5B564717CE84CC75

Done Adding Additional Store
SignTool Error: An unexpected internal error has occurred.
Error information: "Error: SignerSign() failed." (-2147024885/0x8007000b)

    File version is  10.0.19041.685. I'm using 10.0.26100.0 which at least gives a slightly better error message.

    • Like 1

  18. Posted

    I actually don't want to upload to the store. I need this to be able to create a Kiosk application for Windows 10/11. At least that is how I understand what I have found on the net so far. msix is not a must, but recommended. Also signed msix is not a must, but from a customers POV nice to have. Thanks @Patrick PREMARTIN for the /tr hint. I just shortened the command for ease of use. I really hope once the easy signature works, adding the time server will not be an issue.

  20. Posted

    So, I've been kept from doing things by this little, trivial problem. I've been trying to sign an msix package for days now, and am getting nowhere. I can sign Win32 and Win64 executables just fine, Delphi will create unsigned msix packages just as good. But I just can't for the life of me sign an msix. I always get the same error message, it does not matter, if this package contains my application or just a simple dummy, or if it is win32 or win64: 

    "C:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x64\signtool.exe" sign /v /a /fd SHA256 C:\Win\SignTest\Win64\Release\SignTest\bin\SignTest.msix
The following certificate was selected:
    Issued to: My Company
    Issued by: Certum Extended Validation Code Signing 2021 CA
    Expires:   Sat Jan 08 12:11:18 2028
    SHA1 hash: E7C16794EA23F573DE3EA32B5B564717CE84CC75

Done Adding Additional Store
SignTool Error: This file format cannot be signed because it is not recognized.
SignTool Error: An error occurred while attempting to sign: C:\Win\SignTest\Win64\Release\SignTest\bin\SignTest.msix

Number of files successfully Signed: 0
Number of warnings: 0
Number of errors: 1

    I even built the msix externally with the makeappx tool from the SDK, that works just fine (as it should, Delphi uses it as well), but in the end...same error as above as soon as I want to sign the package. 

    The AppManifest.xml is in good shape, syntactically and content-wise. The only assets are two png Icons that can be read just fine. The executable itself can be signed with no trouble at all.

     

    What am I missing?

  21. Posted

    1 hour ago, Roger Cigol said:

    I think you are being a little unrealistic here in terms of business costings.

    There are always remote connection possibilities as a compromise. I firmly believe an unfixed product can cost more than a trip for two guys, that know their stuff, to find out what the hell is going on.

    • Like 5
×