haha i see.
the figure generally touted around as coin supply is really the
maximum coinage able to be handled in one tx (not sure of the finer details tbh)
in this case, probably a useful figure to be aware of ..
it's 2 billion coins
https://github.com/stronghands/stronghands/blob/master/src/main.h#L37so i guess you should never have been able to actually send those coins. so it sounds like only your client that is having a problem, and the coins should be fine.
i'm unsure if a simple mod of that value would cause a fork or not.
i'm unclear if your fresh install involved resyncing or ..
so suggestions would be,
starting with a rescanto rescan, open a command/terminal window,
drag and drop the qt.exe onto it, then add
-rescan
should look somethin like
c:\wherever\stronghands-qt.exe -rescan
,
or resyncing a quicker way of resyncying would be to use yr current chain as a bootstrap.
basically you can rename the blk.xx file as bootstrap.dat and restart
my general approach is to duplicate the entire data directory so you have an as is copy to fall back on,
then rename blk0001.dat (or wahetever it's called) to bootstrap.dat
delete everything else
except wallet.dat
stronghands.conf
peers.dat
leaves you with 4 files .
bootstrap, wallet,conf and peers.
then try restarting,
it should then import the chain from the bootstrap rather than downloading,
from experience, it can take quite a while depending on number of tx and height of chain,
also it can stop before syncing fully with yon bootstrap,
if this happens you can rename
bootstrap.dat.old
back to
bootstrap.dat
and restart.