can i migrate to SDA with ASF or any other way?

[Gagarin-ace]

is it even possible? as i remember when i start to use winauth there was option to take sda savings for a quick setup.
now i cant run winauth correctly for a few days, no matter how many times i restart computer. so i have to find another way to confirm trades - maybe SDA will run without lags and bugs.
i dont know any other way to ask for a help then here. if someone know how to help me - it will be great
thx

[Rudokhvist]

Migrating from ASF to SDA is not supported, because ASF don't store all information from maFile. Theoretically you can manually create mostly working maFile from data in <botname>.db and replacing rest of data with nulls and zeroes, but it's not guaranteed to work in all cases, so it's not recommended. If you have the same authenticator in winauth - I recommend migrating from it, even though it's also not straightforward - it's much more reliable than trying to get it from ASF.
If you will use my fork of SDA https://github.com/Ryzhehvost/SteamDesktopAuthenticator - you can also "move" authenticator to it (old authenticator will stop working, so you will have to import it to ASF again). This mechanism is provided by steam, so you are guaranteed to get fully working authenticator after that, but it's downside is a trade block for a day or two (don't remember how long exactly).
And, as a final word - I'm not very sure that SDA will run better for you. It's a terrible piece of code, and even if not discontinued formally - it's development stopped long ago. You can still give it a try though.

[Gagarin-ace]

Originally posted by Ryzhehvost:

Migrating from ASF to SDA is not supported, because ASF don't store all information from maFile. Theoretically you can manually create mostly working maFile from data in <botname>.db and replacing rest of data with nulls and zeroes, but it's not guaranteed to work in all cases, so it's not recommended. If you have the same authenticator in winauth - I recommend migrating from it, even though it's also not straightforward - it's much more reliable than trying to get it from ASF.
If you will use my fork of SDA https://github.com/Ryzhehvost/SteamDesktopAuthenticator - you can also "move" authenticator to it (old authenticator will stop working, so you will have to import it to ASF again). This mechanism is provided by steam, so you are guaranteed to get fully working authenticator after that, but it's downside is a trade block for a day or two (don't remember how long exactly).
And, as a final word - I'm not very sure that SDA will run better for you. It's a terrible piece of code, and even if not discontinued formally - it's development stopped long ago. You can still give it a try though.

maybe exist something better then sda or winauth?
i dont want to swith authentificator by creating new one and get trade block for a few weeks

if they are both laggy, why no one create a perfectly working one?
coz lots of people still dont have smartphones