I’m pretty sure. I think. I can’t find a core2.dat in my Linux filesystem so i assume it works some other way, and therefore it’s cooked.
The reason i want to do this is because transplanting core2.dat is what you usually do to recover your settings and transfers. I this case though i’ve installed it on my Linux PC so i don’t think this is going to work.
I’ve resorted to exporting all magnets and re-importing them, but that has a few drawbacks.
I’ll update if i find better solutions. So far, if you want to transfer your Tixati from Windows to Linux, my advice is probably don’t
Does this work? https://support.tixati.com/settings - import export
I assume you’d need to either try and unravel the export to correct the paths or do it after the fact.
No i haven’t tried that yet, my assumption is that this only includes the settings and not the actual transfers. If it did include the transfers then Tixati users would just do that, instead i was always told to transplant core2.datWait, now that i read that, it DOES include transfers! I did not know that, that’s a solid lead thank you
EDIT: It works, all the transfers are backed up; this is a lot better, especially because i preserves dates (Created, Completed, Bits uploaded, Ratio, etc).
BUT, the file locations are also backed up. This is a problem because i’m switching from Windows to Linux, so i can’t recreate the file structure because it starts with D:/ instead of starting with /media
Once i update the file location, it triggers a force check, which is the point where some of them fail and display 99% even though they were 100% before. That problem is still unsolved, and i now realize it probably can’t be solved.
Overall though this is great, you made me notice something i didn’t and it’s way better than what i was doing, thanks!