In good condition, preferably a later batch.  Would like to work with someone who's established a rep/trust.

I'm on the east coast of the US.

M

EDIT: Scammers need not apply.

I don't get why all the newbies are promoting this.  They can't be all _that_ ignorant of ROI calculations.

M

Here's a minor change, released as a beta of 3.4b.  It's literally a one line change that appears to get it to work with the prior firmware version for the S3s.  Since I only have one S3, it's a bit awkward to continually reflash to the other version to make sure it works.  This worked for me with the prior version, and the current version.  Note that I didn't test it with the questionable version that was just released within the last few days.

Download link: MAntMonitor34b.zip

M

Are they all using the latest firmware?

What does the error log show?

M

I'm not sure it's a scam.  But it's certainly not a good idea to "invest" into.  It'd be the same as me telling folks to sent me 1.6 BTC, and over the course of the next year and I'll slowly send most, but not all, of it back to you.

M

no.  you'll never recoup your costs. 

M

No, that's expected.

M

1gh/s is nothing.

M

Wow Hash, you got the newbies sucked in good.

M

You're the 2nd person to report this.  I must have something broken there.  Is this an S1 or S3?

M

Hello, see version 3.3.  It addresses the issue with Ants not found when you enter the addresses with leading zeros, which you did by my suggestion for them to sort properly.

MAntMonitor33.zip

M

My p2pool node in LA is unstable.  My host is having hardware problems.  My VPS keeps rebooting or shutting down of its own accord.

M

Also don't expect to ever ROI on your investment.

M

Dear Bitmain,

You've earned the reputation for being a reliable and well liked ASIC manufacturer by doing several things that set you apart from the rest of the crowd:

1 - No pre-orders.  You accepted payment only when stock was in hand and ready to ship.
2 - Sticking to you word.  When you said your Ants will do X, they did X.  When you had problems, you compensated your customers.
3 - Reasonably pricing your Ants so that miners could reasonable expect to get ROI.

Now you've changed your tune, and you're becoming like most other ASIC manufacturers out there: greedy bastards who don't really care about your customers. 

You've:

1 - Started pre-orders.  S3+, L1 come to mind.  BAD idea.
2 - Took over a cloud company and sold GH/s at a price that will almost guaranteed never ROI.
3 - Have your S3+ priced such that they'll likely never ROI.

What are you thinking?  Please change your tune.  You are rapidly becoming disliked and will end up being "just another ASIC manufacturer who only cares about lining their pockets instead of taking care of their customers".

Regards,

M

I think you might have to change your refresh to every 2 seconds.  Prior to the multithreaded change, the "responded" message would be based on the round of checking all the Ants.

Now there's no longer a round.  Each time an Ant refresh completes, it checks to see how many have "" and that becomes the responded message.  Because you're running every second, there will be times when one has because it was just submitted.

M

Try setting the display delay to 0.

M

Here's v3.3. 

This fixes the problem with leading zeros in Ant addresses not working.  ie, 192.168.000.091 doesn't work, but 192.168.0.91 does.
This also starts the process of removing the theoretical code to support DNS addresses instead of pure IP addresses.

Download link: MAntMonitor33.zip.

M

I confirmed, for some reason the microsoft tcpclient doesn't know what a leading zero is in IP address.

I should be able to fix this quickly.

M

Actually, I think you're saying when they are entered without the leading zeros, they work.  Otherwise they do?

M

It's flown by .. not used by.  Sorry.

M