Menu

#26 ccrypt on Windows XP

v1.0_(example)
wont-fix
None
5
2019-04-25
2019-04-25
spaceman
No

Hi

Thank you very much for creating ccrypt.
I am using it on Linux and it is great.

I am using Windows XP SP3, 32bit, and tried use it there too.
I downloaded the "Windows (32 bit)" Precompiled distribution,
which is this link:
http://ccrypt.sourceforge.net/download/1.11/ccrypt-1.11.cygwin-x86.zip

And after extracting the ZIP, and running ccrypt.exe in the command line,
I get this MessageBox:


ccrypt.exe - Entry Point Not Found

The procedure entry point CancelSynchronousIo could not be located in the dynamic link library KERNEL32.dll.

See attached image..

What should I do?

Windows XP is not supported? :|

1 Attachments

Discussion

  • Peter Selinger

    Peter Selinger - 2019-04-25

    Thanks for reporting this. The error message likely means that the Windows XP kernel is too old to support this version of ccrypt. You have several options:

    (1) use an older precompiled version of ccrypt. You can find the older files here:
    http://ccrypt.sourceforge.net/download/

    For example, release 1.7 from 2004 will most likely run on Windows XP. There have been no major bugfixes since 1.7, so this version will work just fine.

    (2) Compile it yourself from sources. This requires installing Cygwin and being a bit technically savvy.

    I recommend trying (1) first. I hope this helps, -- Peter

     
  • Peter Selinger

    Peter Selinger - 2019-04-25
    • status: open --> wont-fix
     
  • spaceman

    spaceman - 2019-04-25

    Hi Peter

    Thank you very much for the reply.

    I downloaded v1.7
    (file: http://ccrypt.sourceforge.net/download/1.7/ccrypt-1.7.cygwin-i386.zip )
    and indeed it now runs well,
    and I also tested it and it Encrypts and Decrypts well.

    Is it maybe possible in the next version to compile it to work for XP too?
    (assuming it does not require any change in the code, and justmeans using a different/older compiler)

     

    Last edit: spaceman 2019-04-25
  • Peter Selinger

    Peter Selinger - 2019-04-25

    Hi Spaceman,

    the problem is that likely I will not have access to an older compiler. But the changes to ccrypt in the last 15 years have been mostly compatibility updates, so there is nothing wrong in principle with using ccrypt 1.7. Is this the latest version that runs on XP? -- Peter

     
  • spaceman

    spaceman - 2019-04-25

    Hi Peter

    >the problem is that likely I will not have access to an older compiler.
    In that case it means that I myself could not have performed Solution #2 either? (Compiling myself)

    >1.7. Is this the latest version that runs on XP?
    That's actually a terrific idea.
    I downloaded now 1.8 till 1.11 (wanted to try 1.11 again).
    The results are:
    1.8: Working :)
    1.9: Working :)
    1.10: Working :)
    1.11: Not Working :))

    So it seems the problem only starts from 1.11..
    All version upto it work great.

    I tried both running, and Enc/Dec/Cat a file.. all worked on 1.10..
    So I will stay with 1.10 (thank you so much for this idea)

    BTW If it stops working only on the last version, maybe the compiler you used before was worth staying with..
    I mean, unless the new compiler provides some functionality that was not included before,
    and is a must for the program..

    Just because I am a developer, I am curious to ask,
    what has changed? Compier version, or Compiler type?
    (for the "cygwin-i386" versions, that is)

     

    Last edit: spaceman 2019-04-25
  • Peter Selinger

    Peter Selinger - 2019-04-25

    In that case it means that I myself could not have performed Solution #2 either? (Compiling myself)

    I don't know. You have one decisive advantage, which is that you actually own a copy of Windows XP. I imagine that whatever compiler comes with XP would probably work. I haven't had a computer running XP in many years, so it is hard for me to test.

     
  • spaceman

    spaceman - 2019-04-25

    Allow me to suggest to be your WindowsXP test guy, should you decide to continue with the compiler that you used upto 1.10 :)

     

    Last edit: spaceman 2019-04-25

Log in to post a comment.