Quote: "and what could be done to (at the very least) suspend or alleviate the delist, at least until the full development occurs in a few months time."

How long has development on this coin been suspended?
How long has the official website (influxcoin.xyz) been dead?
How long has CWI been in charge of this coin?
Why is it taking a few more months before development occurs?

It seems like CWI isn't doing anything with this coin.... please prove this wrong and show us what you are doing!

Thank you for the reply! I look forward to the new site and everything the CWI team is planning.

The project still references influxcoin.xyz in the readme.md file; but if that domain is no longer under control of this project then the links in the official repository should be updated.

CoinMarketCap correctly references this thread and the CWI github page, but it still lists influxcoin.xyz as the official site; so that may need to be updated also.



The CWI website has been 'coming soon' for well over 6 months, maybe even longer...

What is a realistic timeframe for something more than a 'coming soon' page to be available?

I am still using the old 2.0.0 wallet on Windows 10 x64,
I think it was released over a year ago from the old dev,
Pretty sure it is the same one found here:
https://github.com/chainworksindustries/influx/releases
https://github.com/chainworksindustries/influx/releases/download/2.0.0/influx-v2_0_0_LTS-win.zip

--

If this helped you and you want to toss some INFX at me you can use this address:
iK8Epz4fZgg8M7qhb1GVG25QrbjCGLNdQi

First off, the XMR_stak_cpu application is a CPU miner, so i don't think that doing anything with the GPU Drivers will affect it.

If it is the 3rd party miners that are crashing, and they only crash when elevated privileges are enabled, then maybe you could try two instances of the NiceHash application, like the following:

1) In NiceHash settings, enabled "allow multiple instances"
2) Launch two instances of NiceHash; launch 1 instance with elevated privileges and launch the other instance without  elevated privileges
3) In the NiceHash instance with elevated privileges untick the GPU so that instance only controls the CPU mining
4) In the NiceHash instance with regular privileges untick the CPU so that instance only controls the GPU mining

In this way, you will have an elevated instance controlling the XMR_Stak_CPU miner, and a regular non-elevated instance controlling the GPU miners including the 3rd party ones.

Regarding this error:

[2017-06-09 16:43:51] : MEMORY INIT ERROR: Obtaning SeLockMemoryPrivilege failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.
[2017-06-09 16:43:51] : MEMORY ALLOC FAILED: VirtualAlloc failed.

In order to obtain SetLockMemoryPrivilege you must do the following:
1) Be running with elevated (Administrator) privileges
2) The user running the application must have the "Lock pages in memory" permission in GPEDIT.MSC under
/Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignment/
http://imgur.com/a/mY3Dl

If you haven't done those two things, then you will get that error.

Not sure what to say about the 3rd party miners crashing... Sorry.