I don't have it :( can your post the config without your piv key?

WTF the "#" disappear when copy config ini

Endpoint for P2P node to listen on

p2p-endpoint =

Maxmimum number of incoming connections on P2P endpoint

p2p-max-connections =

P2P nodes to connect to on startup (may specify multiple times)

seed-node =

seed-node = seed.steemed.net:2001
seed-node = seed.cubeconnex.com:2001
seed-node = steem.clawmap.com:2001
seed-node = seed.steemwitness.com:2001
seed-node = steem-seed1.abit-more.com:2001
seed-node = 185.82.203.92:2001
seed-node = 52.38.66.234:2001
seed-node = 52.37.169.52:2001
seed-node = 52.26.78.244:2001
seed-node = 192.99.4.226:2001
seed-node = 46.252.27.1:1337
seed-node = 81.89.101.133:2001
seed-node = 52.4.250.181:39705
seed-node = 85.214.65.220:2001

Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints.

checkpoint =

Endpoint for websocket RPC to listen on

rpc-endpoint = 127.0.0.1:8090

Endpoint for TLS websocket RPC to listen on

rpc-tls-endpoint =

The TLS certificate file for this server

server-pem =

Password for this certificate

server-pem-password =

Block signing key to use for init witnesses, overrides genesis file

dbg-init-key =

API user specification, may be specified multiple times

api-user =

Set an API to be publicly available, may be specified multiple times

public-api = database_api login_api

Plugin(s) to enable, may be specified multiple times

enable-plugin = witness account_history

Defines a range of accounts to track as a json pair ["from","to"] [from,to)

track-account-range =

RPC endpoint of a trusted validating node (required)

trusted-node =

Track market history by grouping orders into buckets of equal size measured in seconds specified as a JSON array of numbers

bucket-size = [15,60,300,3600,86400]

How far back in time to track history for each bucket size, measured in the number of buckets (default: 5760)

history-per-size = 5760

Defines a range of accounts to private messages to/from as a json pair ["from","to"] [from,to)

pm-account-range =

Enable block production, even if the chain is stale.

enable-stale-production = false

Percent of witnesses (0-99) that must be participating in order to produce blocks

required-participation = false

name of witness controlled by this node (e.g. initwitness )

witness="steemeando"

name of miner and its private key (e.g. ["account","WIF PRIVATE KEY"] )

miner = ["steemeando","xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]

Number of threads to use for proof of work mining

mining-threads = 8

WIF PRIVATE KEY to be used by one or more witnesses or miners

private-key =

Account creation fee to be voted on upon successful POW - Minimum fee is 100.000 STEEM (written as 100000)

miner-account-creation-fee =

Maximum block size (in bytes) to be voted on upon successful POW - Max block size must be between 128 KB and 750 MB

miner-maximum-block-size =

SBD interest rate to be vote on upon successful POW - Default interest rate is 10% (written as 1000)

miner-sbd-interest-rate =

declare an appender named "stderr" that writes messages to the console

[log.console_appender.stderr]
stream=std_error

declare an appender named "p2p" that writes messages to p2p.log

[log.file_appender.p2p]
filename=stm/logs/p2p/p2p.log

filename can be absolute or relative to this config file

route any messages logged to the default logger to the "stderr" logger we

declared above, if they are info level are higher

[logger.default]
level=warn
appenders=stderr

route messages sent to the "p2p" logger to the p2p appender declared above

[logger.p2p]
level=warn
appenders=p2p

for private-key you can use any key so just generate one on: https://bitaddress.org
(read step 8 in this post: https://steemit.com/steem/@pfunk/guide-maximize-your-mining-hashrate-in-windows-by-mining-steem-in-a-vm)

you can only mine one account on one machine at a time ... so you can have 2 computers mining for 2 accounts ...

also consider adding more accounts to your config for example : steemeando1, steemeando2 ... so your miner won't go idle when one account's in queue ... like this:

witness = "steemeando"
witness = "steemeando1"
witness = "steemeando2"

miner = ["steemeando","xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
miner = ["steemeando1","xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
miner = ["steemeando2","xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]

these accounts don't have to exist ... they'll be created when you'll find a block ... and will be accessible with the key assigned to them in the config ...