Quote from: andyatcrux on September 13, 2015, 09:23:07 PM

Quote from: MinermanNC on September 13, 2015, 06:20:48 PM

Ok, to stop siad on W7: NOT USING TASK MANAGER

Using CMD prompt, change directory (cd) to, example command line: cd C:\Users\XXX\Desktop\Sia-UI-v0.4.2-beta-win64\Sia-UI-v0.4.2-beta-win64\resources\app\Sia (or wherever you have you SIA 4.2 directory) in my case it is on my desktop.

Then type: siac stop

Got the message: Sia daemon stopped

Restarted wallet, unlocked it, all good.

Just not sure if I did not do the above step to close siad, and I do a PC restart will that corrupt file again? I don't feel like testing that lol.... in the event of a power failure, PC shut down etc. that could result in corrupt files again.... we will need a better way to totally close siad in the future so there is NO risk of corruption in any way Wink

Yeah, good question. I'd use Siac to avoid the possible inconvenience, which is what it is. I don't like the fact that I have two wallet files, one for the imported wallet and one for the new. I wonder if I should just send all my coins associated with the imported address to the new seed associated address. Hm... maybe do a few tests first.

IDK what to say on that one myself, not sure of the differences it may have? I still have the bulk of my coins sitting in a separate laptop on 0.3.3.3 until I feel 110% confident in 4.2. I had a few hundred coins in the legacy wallet (0.3) I imported from, into 4.2 for testing. All seems to be ok, and I have sent a few of those coins to Poli as well from 4.2. Let us know what you find out if you test that out

What OS do you use?