USB Dongle

[WilliGrundmann]

Hi to everyone,

Just installed the Proton IDE on a new laptop with Windows 10.
Currently I want to work on a project from over 10 years ago. The project is compiled with Proton V3.5.5.5. I learned the hard way not to change compiler versions for completed projects. Therefore I would like to use V3.5.5.5 for this product.

There seems to be a problem with the USB dongle. When compiling it comes up with "missing security key". The dongle works fine on my old laptop, which is running on Windows 7. The new laptop also make a sound, when the dongle is plugged in and removed.

What can I do to make the dongle work on the Windows 10 laptop?

[Dolci]

https://protoncompiler.com/index.php/topic,361.msg2229.html#msg2229

[joesaliba]

Check post #2 here: - https://protoncompiler.com/index.php/topic,137.msg636.html#msg636

[Stephen Moss]

Currently I want to work on a project from over 10 years ago. The project is compiled with Proton V3.5.5.5. I learned the hard way not to change compiler versions for completed projects. Therefore I would like to use V3.5.5.5 for this product.

A potential issue with that is that if you then need help any code provided could use commands/features that were not available in Proton and most users have updated and so it would be of no use to you (it may be difficult for users to think back to what was not available in the older versions).

I can understand your reluctance to update and to also have to fix any potential compatibility issues with the latest version of Positron along the way, however if you are having to modify the code anyway then surely that is the best time to update it to Positron (make a copy first so you can recover if case it all goes wrong), I did write some software that could help to some extent which can can read about here.

The reason I suggest updating using Positron now rather than sticking to the older Proton is that...

• I am currently having to update software at work that was targeted at XP and .Net Framewwork 4.7 to .Net 8 & Windows 10 because Visual Studio not longer supports .Net Framework or 32-bit, and often won't load the old files properly but is necessary to avoid potential compatibility issues.
  This has been a huge pain and thrown up many unexpected issues (as well as some expected ones) due to .Net Framework stuff being either dumped altogether in .Net core or moved to NuGet Packages. Maybe if it had been updated regularly every couple of years it would have been a more painless conversion process/easier to import the files.
  The same may be true for Proton to Positron conversion, in that the sooner you convert it the easier it may be.
• Could the fact that Visual Studio no longer allows you compile for 32-bit and anything less than .Net 6 simply be to make maintaining it easier/more secure, or could it be an early indicator that Windows support for 32-software will be coming to an end as it was probably intended to only be retained for a certain time as legacy software support until people updated their existing software to the 64-bit version?
  If the latter and if Proton is only 32-bit then there may come a point when it will no longer run on a 64-bit system (I am assuming Positron is/can be compiled for 64-bit) and you so may be forced to convert the code to Positron at some point the anyway, so why not now.