Did anyone else test the windows installer yet (https://bitcointalk.org/index.php?topic=684090.msg8918376#msg8918376)?

I see some posts again from people that are having trouble / questions about the install. This might help easing up the install.

Installer is here: https://bitcointalk.org/index.php?topic=684090.msg8918376#msg8918376

Would still like someone else than me to test it, so if someone has time...
It's only windows though...

I don't see any problems with those steps.

I don't have any Token on AE, but happy to test it with some other asset, or on test net. I'll be available in about 21 hours from the time I'm posting this (can never figure out what time that is in other places

In that case there's almost no need for any installer anymore. Sounds nice!

The only thing I can think of that you might need, is an option somewhere in the client to rebuild the database of blocks. That way a normal user never has to do something outside the client.

Just let me know when it's ready, and I'll create a new Windows Installer.

Good to know, but already found a better way to solve my problem .

I used the version from the OP, as I haven't got a clue yet how to build it. Checksums were fine when I downloaded to a clean machine. Worked on the clean machine, and when finished created the SHA-256 checksum.
Uploaded on my main machine.
Downloaded on a 2nd clean machine, and still gave the same checksum. So I fugured all should be ok.


I would say that every release should have the same version on all platforms. Usually the first 3 numbers are/should be used for external releases, the forth number for internal builds.
So everytime a version is released, update at least the 3rd number. Current version is 1.0.0.0, so next should be at least 1.0.1.0.
I might (but still need to test that a bit further) even need the 2nd one to go up to keep the updates working as intended. If so, I'll keep using a different version for the installer only, just like I did now.

Lets start with, please be carefull, only use at your own risk. I tried and used everything I could think of to keep this virus/malware free, but you never know.

Hopefully we'll see the version of the .exe of the wallet increase when a new version arrives. Until then I'll use a different version for the installer (0.1.0 for this first one).
This installer will:
- Backup the %appdata%\BitcoinDark to %appdata%\BitcoinDark__, and reuse the wallet.dat and BitcoinDark.conf if present.
- Install the .exe in default location C:\Program Files\BitcoinDark or C:\Program Files (x86)\BitcoinDark on 64-bits systems. This is customizable in the wizard.
- Will install the %appdata%\BitcoinDark\BitcoinDark.conf (if not present), with the rpcuser and rpcpassword both with random 32char UIDs.
- Depending on the chosen settings, creates shortcuts in startmenu and/or desktop.
- Give a warning if the wallet is still running, you have to close the wallet, to continue. (Did not find a better solution yet)

Future installers will:
- Do the same as this one
- Uninstall older installations
- Prevent older installers to overwrite the newer versions that I made

Windows Installer version 0.1.0:
Download here
SHA-256: 733603F0680A53EE247C2B995A78D0F8B1930B4644A6564FF431C6F9384CA9E6

Have fun!
Qwitnix

PS. last test took over an hour to get connections, but in the end it got there, so be patient.

Edit:
Tested on:
Win8.1 64-bit
Win7 64-bit
Win7 32-bit

As far as I know, you should place the bitcoindark.conf in the C:\Users\\AppData\Roaming\BitcoinDark folder.

PS. I'm still working on the installer. Just need a bit more info and time.

A few more questions about the wallet.

Is there a way to see if all lines of the BitcoinDark.conf are read without errors?
Is it ok to add a section head in the .conf like used in an ini file? [Settings] or something?
In the examples the .conf files all start with the rpcuser= and end with a list of the addnode=. Is it ok to mix up the sequence of the lines in the .conf? so start with a addnode= then the rpcuser= then another startnode= etc.

Is there a unique version number for each new version of the wallet?
if so, where can I find it?
if not, are you planning on doing that? It would be user friendly to have it, and I would like to try and use the same version numbers in the installer.

That's it for now.
Grtz,
Qwitnix

Ok, I'll try that.

So rpcuser and rpcpassword should not be in the default .config, people that will need it, will have to add it manually?
Or should the installer ask for it?
I haven't got a clue what it's for so if included in the installer wizard, I need a text to explain it to a user and/or a default value.

Grtz,
Qwitnix

Hi all,

I see quite some people having some troubles with the installation of the wallet.
I myself also had some issues with the new version after the last fork.

So I'm planning of making an installer for windows (.MSI) that will do:
1. Check if a previous version of this installer is installed, if so, uninstall the old one first / upgrade the old one.
2. If not (otherwise, in the future, this will be done by the uninstall of the old msipackage), check if wallet is running, if so kill process. Is there a way built into the wallet to close the wallet nicely from a commandline?
3. Place the .exe in a folder on C:\Program Files\BitcoinDark (location customizable in install wizard)
4. Place shortcut in startmenu (by default)
5. Place shortcut on desktop (Optional, not default, will be a checkbox on install)
6. Start .exe on windows startup (not the default option, will be a checkbox on install, will probably write a key in run under HKLM)
7. If exist, backup %appdata%\BitcoinDark to %appdata%\BitCoinDark_PrevVersion (if this already exsists, remove the old, create the new backup) and remove all in %appdata%\BitcoinDark, except wallet and .conf (Also optional, but default)
8. If not present create .conf in %appdata%\BitcoinDark
9. Start .exe when installation is finished (Optional, but default)

To make this there's a few more things I need to know:
If I include this .conf file as default, will that do for the general end-user (it is the one you can downloaded from OP)?

Or would it need the version that's written in text on the OP?

Or maybe even a completely different one?
How do I make sure that the file I upload is 100% virus, malware, etc free? Is there a trusted site or something?
Is there a guide that I can follow to make a checksum thingy, so people can checkt it's the exact same thing I uploaded?
Anything else needed?

Grtz,
Qwitnix

tl;dr: Incoming windows installer, but need some input to make it work.

Meh... agian too late for the Beta test... Would it be possible to have a testnet up inbetween te releases?

I understand it would need some restarts every now and then, but I keep missing the actual testing window, and I really would like to test it a bit.

Hi Anon136,

Just send you 1.009BTC (1BTC exo + 0.009 fee)
TransactionID:  5b55e5d0b5be44e89ed59fcf55945a39af466945c4e561fcb19fbc83046e1324

Thanks,
Qwitnix

Interested,
80 NXT send, transaction id: 12120797183585756378

so premine = scam?

why?.. hmmm I'd better read up on it some more before buying then...

Hi all!

Started a few days ago reading some stuff about all sorts of coins and it got me interested. Thought I'd register here as a nice starting point to get some more info.
At the moment I'm reading up on Bitcoin (and several altcoins) and NXT (interested in buying some NXT, so it keeps me interested a little longer than just reading about it) and playing around on some exchanges.

That's it for now, cya around!

Qwitinix