John Doe

I agree that removing obsolete features and algorithms makes VeraCrypt cleaner and more secure. I am at peace with this decision if care is taken by the installer to prevent an unbootable system that uses now-removed algorithms that were still available in the previous install/bootloader of VeraCrypt. As for release 1.25.9 it seems to be the last version to install and run correctly on Windows XP (both 32-bit SP3 and x64 Edition SP2). Version 1.26 refuses to install due to missing "bcrypt.dll" (if...

Remove TrueCrypt Mode support Complete removal of RIPEMD160 and GOST89 algorithms. Legacy volumes using any of them cannot be mounted by VeraCrypt anymore. In my personal opinion this is a mistake because it breaks backwards compatibility. Consider this hypothetical example: what if one day AES and SHA2 are completely broken? In the name of security you'd remove them from VeraCrypt. Then suddenly nobody will be able to mount their volumes anymore with the new version of VeraCrypt. Treat the user...

I still use 3.5" 1.44 MB floppy diskettes and I make them bootable like so: $ dd if="VeraCrypt Rescue Disk.iso" of=/dev/fd0 bs=512 skip=104 count=184 I'm happy this actually works on a physical floppy and I hope it won't change. The problem: I did try booting such a floppy image with syslinux and though it displayed the VeraCrypt menu and allowed me input the password, it never accepted that which I was sure was the correct password. Does the VeraCrypt Rescue Disk use hardcoded values for where it's...

Eventually compatibility with old systems will be removed. That's perfectly OK because you've made the effort to maintain compatibility in the first place; other devs have dropped XP support almost as soon as Microsoft did, as if they were in a giant hurry to make "progress". Thanks again, I'm perfectly happy with the 32-bit version of SciTE on XP.

:) You need to invent self-expanding tabs before you can conquer the Universe.

Thank you for quickly fixing this issue! I can confirm that version 5.3.7 of 32-bit SciTE and Sc1 work perfectly on Windows XP SP2 x64 Edition. The 64-bit versions of SciTE give the error: The procedure entry point LCMapStringEx could not be located in the dynamic link library KERNEL32.dll. I'm not really bothered by this, though: a text editor needn't be 64-bit. Besides, XP x64 Edition has always been less compatible than its 32-bit sibling.

Sharing my SciTEUser.properties