gcc (Ubuntu 4.8.4-2ubuntu1~14.04.1) 4.8.4

I'l download it and give it a try.

Edit: downloaded, compiled and runs ok on hodl.

You've been around long enough, are you being deliberately obtuse?

Anyway, party's over, HP went down again and I don't expect it to some back with 175 DNET blocksize,
if at all. someone likely got stiffed.

There's definitely something dodgy about DNET but as long as I'm getting paid I don't care. Wallet? What wallet?
HP autoexchanges to BTC for me.

The chain has forked and one branch in incorrectly producing 175 DNETs per block istead of 22.5. Why are coins
maturing and successfuly exchanged? Again as long as I'm getting paid I don't care.

How long will it last? Again, I don't care.

I'm just enjoying the ride while it lasts.

My Asus Z97 has a config for the second x16 slot: x2 with both x1 slots enabled or x4 with x1 slots disabled.
SATA express always uses PCIe so it should be disabled. Other devices may use  PICe lane depending on the
motherboard.

PCIe link speed should probably be auto. The only reason not to is if the card has incompatibilities.

What version? That wastefull c++ code is to support non AES_NI.

I'm currently using 3.2.3 and I made no changes to hodl in 3.2.4 or 3.2.5.

Just compiled and ran 3.2.5, no porblem.

mingw, even better, no messing around with vstudio. Thanks.

So It's the hmage fork that's working? I'll have to  give it a spin.

It's probably good that you missed several versions, it was a little messy for a while. It's stabilized quite a
bit so now is a good time.

I see you've made some recent changes to the windows branch. Is that what I should use? Are the changes
mostly large blocks of code or is it line by line? In other words how hard will it be to manually
merge?

I already have cpuid working thanks to a contributor, don't know about windows but I don't see why not.

That's great news, yes please discuss, I have many questions.

If HMW1725 works then many other algos such as x11, quark etc will work.
Hodl is a special case and so are a few other unique algos but I think I'll be able to work it out.
Can't wait to see the source.

None at the moment, hmq1725 was last adddition and lyra2v2 the last optimization.

Isn't this the problem exactly?

Edit: And it probably is related to PCIe lanes because those devices sometimes use them.

If you mean Windows it's because it won't compile in Windows. If you mean Linux you get
better performance compiling yourself.

I love your analysis but I have to throw another dart.

I'm not sure I'm understanding this data correctly, you don't have it so I can't compare.

http://hashpower.co/site/block?id=1376

It shows the balance at 1.3M and the last 7 days produced 1.2M so the balance has been acumulating for
more than 7 days yet I got my last payout Monday at 16:00 EST, 3 days ago. That being the case I was
being payed in BTC while the DNET balance was already accumulating. So unless they are operating on some
kind of margin where they pay out BTC before they've actually sold the DNET they must be valid coins.

I also noticed that HP is not getting all the blocks on the alternate chain, most but not all. They aren't yours
because I found duplicate block numbers so someone else is mining on this chain.

I'm definitely suspicious but I don't see the typical red flags. I've never lost coins that have matured.
The only time I lost coins on HP was when they dropped MUE, but again it was only the immature coins
I lost.

At this point the only thing I'm convinced of is the blockchain has forked and your branch agrees with
the coin's roadmap. Until Monday HP was paying what they advertise until a system crash. When the
system came back up everything was functioning as it should be except there have been no payouts
since the crash. Coins including DNET continue to get found, mature and exchanged, just one small step
remaining.

Although there appears to be a critical issue with the DNET blockchain there is no direct link between it
and to the lack of any payouts since the crash. It is more likley the crash triggered the subsequent payout failures.

I understand what you are saying but there is too much conflicting evidence, I'm still hopeful I'll get my coins.

Lanes are reduced.

I know I'm being picky but I appreciate your responses and consider you an authority.

Those numbers look weird but t makes no sense to display phantom block maturation and exchange
to BTC. And the fact remains before the crash they were real. The only visible difference after the crash
is no final payouts.

I guess time will tell but I hope you are arong because I have a BTC balance of DNET found before the crash
but matured  and exchanged after.

That's the remaining issue but may be unrelated. The payout problem only started after the crash on Monday,
before that it was paying out real BTC into MY wallet.

You know the yaamp code. When the BTC show up in the balance isn't it real?

Very interesting I hadn't thought of PCIe lanes being the issue. But you're talking about PCIe3 which usually
only serves the x16 slots with PCIe2 serving the others. I would also expect a decent MB to be able to
configure all the equipped slots.

One quick way to confirm is to check the CPU model on the previously working 6 card rigs.

The BTC they were exchanged to look pretty real.

I don't understand what you are saying. Blocks on the wrong fork shouldn't confirm but the DNET at HP
is confirming:

If that's true why are the coins still confirming?