[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 6.

3429z781678124

newbie

Activity: 11

Merit: 0

Can someone help to answer this questions for CoinMarketCap.com registration?

What is the coin's official website?
slimcoin.club

Please provide a URL of the coin's official logo:
https://ip.bitcointalk.org/?u=https%3A%2F%2Fslimcoin.org%2Fimages%2Fmy_slimcoin.png&t=549&c=AICi28FKP0hADA

Please provide any other information that would be useful:
proof of burn whitepaper: slimcoin.org
announcement thread: https://bitcointalksearch.org/topic/ann-slimcoin-proof-of-burn-new-block-gen-mineable-by-low-power-computer-613213

Please provide a URL that shows the total number of coins in real time.
Huh

??

Superxfast

full member

Activity: 161

Merit: 100

Dear all

I have 10 servers, can i mine with 10 minerd on 10 servers and only one wallet, how?

Or any pool?

d5000

legendary

Activity: 3906

Merit: 6249

Decentralization Maximalist

Thanks BitcoinFX for your suggestions! Unfortunately, even with a fresh wallet I was unable to sync. I always got stuck at block 228116.

Now http://slimcoin.club has uploaded a new snapshot at 236000 that allowed me to sync again.

Doesn't this mean that a123 is reading here and is active again? That would be great news!

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Quote from: d5000 on February 08, 2015, 06:11:15 AM

...

I have already tried going back to block 205xxx (the last snapshot I have) and start slimcoin connecting only to the block explorer with -listen=0. Will try out BitcoinFX's new node now. What I don't have done still is revising the peer list in slimcoin.conf for bad nodes, will do this too and then tell you if I had success.

Quote

I'm not sure the cause of this, but if it's a problem with handling orphan blocks then that's not good. Can't have users getting stuck on random points of the blockchain...

Agree, the client is WAY more stable now that some months ago, but this bug is really annoying.

Node is running v.0.3.2.1-alpha on win server. I also used the snapshot from slimcoin.club and got fully synced in under 3 hours, without adding / changing any .conf settings.

Try syncing with a fresh wallet.dat and then replacing it with your main wallet once synced, if your not already doing that. Anyway this new node seems to be very stable and the provider seems to have a good and fast network upstream. Number of connections is > 20 currently.

I will try to compiled and run a new windows version when we know its stable.

Cheers!

d5000

legendary

Activity: 3906

Merit: 6249

Decentralization Maximalist

Quote from: Mr E on February 07, 2015, 11:37:13 PM

I'm not sure. I'm at block 235487 with no errors right now. I could try to zip up my copy of the blockchain for you, if anyone knows whether that will work? Another option is you could try starting from an old snapshot again with a limited peer list of nodes you know have the good blockchain...

If you could upload a blockchain snapshot that would be awesome (I have already used snapshots, it works, needed files are, if I remember right, addr.dat, blk0001.dat, blkindex.dat and the database folder). Obviously even better would be if we manage to really solve the issue.

I have already tried going back to block 205xxx (the last snapshot I have) and start slimcoin connecting only to the block explorer with -listen=0. Will try out BitcoinFX's new node now. What I don't have done still is revising the peer list in slimcoin.conf for bad nodes, will do this too and then tell you if I had success.

Quote

I'm not sure the cause of this, but if it's a problem with handling orphan blocks then that's not good. Can't have users getting stuck on random points of the blockchain...

Agree, the client is WAY more stable now that some months ago, but this bug is really annoying.

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: 3429z781678124 on February 08, 2015, 02:28:04 AM

By trying a clean install from scratch I got a error by loading "blkindex.dat" - Genesis Block not accepted.

Thanks for the report.

I've added this as an issue: https://github.com/gjhiggins/SLIMCoin/issues/1, so's I don't forget.

Cheers

Graham

3429z781678124

newbie

Activity: 11

Merit: 0

Quote

I can confirm that the vanilla wallet compiles without problems on Ubuntu 14.04 at least.

Yes!!! Thank you very much. I'm happy. I can confirm that the wallet compiles and works without problems on Lubuntu 14.04 ARM. Grin

But only on a existing data directory. By trying a clean install from scratch I got a error by loading "blkindex.dat" - Genesis Block not accepted.
Huh

Mr E

newbie

Activity: 21

Merit: 0

Quote from: gjhiggins on January 31, 2015, 09:10:58 AM

I've been doing some integration work on the quiet. I intended to do more testing before announcing the results of my efforts but contemporaneity trumps caution.

I've been hacking around with the PPCoin git repos and (with a bit of judicious conflict resolution) have been able to retrofit SLIMCoin as a branch , thereby recruiting the full PPCoin commit history as the base for “John Smith’s” SLM initial commit and subsequent commit history.

I was able to merge all the way up to the latest commit of the standard PPCoin master (not the more extensive “develop” branch tho' which is a shame because it integrates the 0.8.6 codebase, leveldb, coincontrol and all).

I've also integrated all the contributions from the recent changes in the three extant forks

https://github.com/gjhiggins/SLIMCoin

http://i61.tinypic.com/23kc239.jpg
That's awesome. It's pretty much what I wanted to do next, except am not expert enough with Git to do properly.
When I get a chance, I'll check it out and see if I can build it, then test it for a while.

Quote from: d5000 on February 07, 2015, 05:01:53 PM

Quote from: bonipper on February 06, 2015, 05:18:23 PM

A forum would be good but I bet most people would look here first for any important updates.

Obviously this thread would continue to be an important communication channel. But a forum enables to coordinate development, marketing etc. much better. I remember the experience of Peercoin: Before they got a forum (Peercointalk) it was more-or-less a one-man project. When the forum opened, soon there emerged discussions about future developments and a marketing team was formed, which drove attention to the coin and made it a top-5 coin for most of 2013 and 2014.

Indeed, this thread is rather awkward for discussing more than one topic at a time; a separate forum would be nice if things start happening faster.

Quote from: d5000 on January 31, 2015, 08:12:03 AM

Quote from: Mr E on January 28, 2015, 08:35:41 PM

I seem to have gotten rid of the slimcoin-qt crashes by compiling a version which is more aggressive at banning 'old version' clients (ones that keep spamming getblocks requests). This suggests that the crash is due to dealing with large numbers of requests in close proximity or something similar - which would be consistent with what I've seen where the memory usage suddenly spikes upwards before a crash. I'm just not sure about pushing that pach out widely, since I don't know what the chances are of it banning a legitimate node by accident. I am still showing 27 active connections, though, which suggests it hasn't banned everyone (yet?).

I don't know if slimcoin on linux has the same problem; as far as I know, I'm the only one reporting issues with this and I'm mainly running the Windows client. (I should try running a linux one too and see how it goes.)

I'm running the linux version (without gui) and I get the errors and crashes only when I run it with too low memory / swap space (512 MB seems to be too low, for example). But here I can't help you because I'm not so much of a techie ...

Interesting, it's possible that it could be a memory-related crash that is triggered by the large quantity of requests, or something.

At any rate, my slimcoin has been running stable for the last week or so and I haven't dropped any more nodes (currently at 28 connections), so I'm cautiously ok with the change for now.

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: gjhiggins on February 07, 2015, 09:15:27 PM

I can confirm that the vanilla wallet compiles without problems on Ubuntu 14.04 at least.

I think we can do better than that ...

I've configured Travis CI to track changes to https://github.com/gjhiggins/SLIMCoin. The continuous integration script clones and compiles the coin afresh, each time the code repository receives a commit or a push. Currently, the vanilla “slimcoin” branch Qt and CLI apps are both compiling successfully:

https://travis-ci.org/gjhiggins/SLIMCoin

(I've got plans to extend the CI coverage to include executing the (rather limited) test suite.)

Cheers

Graham

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: 3429z781678124 on February 06, 2015, 03:01:45 PM

I got some errors by compiling from github. Please help.

Quote

error: no ‘void OverviewPage::updatePlot(int)’ member function declared in class ‘OverviewPage’

I do apologise, for some reason I missed your post.

Mea culpa. I managed to add a fragment of the diffplot code to the vanilla wallet.

Fixed in commit 61c7314, along with a couple of other header declaration omissions. I can confirm that the vanilla wallet compiles without problems on Ubuntu 14.04 at least.

Cheers

Graham

BitcoinFX

legendary

Activity: 2646

Merit: 1722

https://youtu.be/DsAVx0u9Cw4 ... Dr. WHO < KLF

Syncing a new node:

addnode=108.61.197.252

d5000

legendary

Activity: 3906

Merit: 6249

Decentralization Maximalist

Quote from: bonipper on February 06, 2015, 05:18:23 PM

A forum would be good but I bet most people would look here first for any important updates.

Obviously this thread would continue to be an important communication channel. But a forum enables to coordinate development, marketing etc. much better. I remember the experience of Peercoin: Before they got a forum (Peercointalk) it was more-or-less a one-man project. When the forum opened, soon there emerged discussions about future developments and a marketing team was formed, which drove attention to the coin and made it a top-5 coin for most of 2013 and 2014.

I have currently syncing problems at block 228116. Somebody knows what to do? The last block seems to be on the main chain, at least it has the same block hash as 228116 on the bchain.info block explorer. Have redownloaded blockchain from an earlier snapshot three times now, without luck. Looking at debug.log I see a "Check proof-of-burn error", probably caused by an orphan block.

masterOfDisaster

sr. member

Activity: 321

Merit: 250

Quote from: 3429z781678124 on February 07, 2015, 07:58:43 AM

Which nodes that are currently working?

The peer list on slimcoin.club explorer seems outdated ... Cry

My current connections:

Code:

getpeerinfo
[...]
        "addr" : "37.187.100.75:41682",
[...]
        "addr" : "5.9.81.9:41682",
[...] 
        "addr" : "188.16.203.240:41682",
[...]

rfcdejong

hero member

Activity: 798

Merit: 500

i cannot wait until the new version is launched, meanwhile still getting more and more coins from my burned stash Wink

3429z781678124

newbie

Activity: 11

Merit: 0

Which nodes that are currently working?

The peer list on slimcoin.club explorer seems outdated ... Cry

pantheist

member

Activity: 63

Merit: 10

Quote from: bonipper on February 06, 2015, 05:18:23 PM

Quote from: d5000 on February 01, 2015, 04:59:57 PM

Very interesting developments, thanks gjhiggins!

Now if we decide to hard fork: It's true what rfcdejong says, it could weaken the network. It would be nice to have some kind of "census" of active slimcoin users, or even better, to have an own forum to coordinate the protocol switch. Well, at least we have a reddit, it's pretty inactive but could be used for these cases: http://www.reddit.com/r/slimcoin/ I've seen at least some recent post have been made ... things are getting better.

I am a bit delayed with my little "PoB report" project but expect to launch it next week. Will announce it here and at Reddit.

A forum would be good but I bet most people would look here first for any important updates.

Yeah, despite my pessimism sometimes, I still run the client and watch this thread. I'll bet I'm not the only one. Couldn't hurt to post on reddit, but please at least cross-post anything important here.

bonipper

sr. member

Activity: 246

Merit: 250

Quote from: d5000 on February 01, 2015, 04:59:57 PM

Very interesting developments, thanks gjhiggins!

Now if we decide to hard fork: It's true what rfcdejong says, it could weaken the network. It would be nice to have some kind of "census" of active slimcoin users, or even better, to have an own forum to coordinate the protocol switch. Well, at least we have a reddit, it's pretty inactive but could be used for these cases: http://www.reddit.com/r/slimcoin/ I've seen at least some recent post have been made ... things are getting better.

I am a bit delayed with my little "PoB report" project but expect to launch it next week. Will announce it here and at Reddit.

A forum would be good but I bet most people would look here first for any important updates.

3429z781678124

newbie

Activity: 11

Merit: 0

Hi Graham,

I got some errors by compiling from github. Please help.

Quote

At the moment, the repos is under my personal GitHub a/c and I've taken the liberty of adding the other forkers as collaborators:

https://github.com/gjhiggins/SLIMCoin

Code:

g++ -c -pipe -fstack-protector -D_FORTIFY_SOURCE=2 -static -static-libgcc -static-libstdc++ -O2 -D_REENTRANT -Wall -Wextra -Wformat -Wformat-security -Wno-invalid-offsetof -Wno-sign-compare -Wno-unused-parameter -fdiagnostics-show-option -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DUSE_UPNP=1 -DSTATICLIB -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtWebKit -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -I/qt -I/QtGui -Ibuild -Ibuild -o build/overviewpage.o src/qt/overviewpage.cpp
src/qt/overviewpage.cpp:220:40: error: no ‘void OverviewPage::updatePlot(int)’ member function declared in class ‘OverviewPage’
 void OverviewPage::updatePlot(int count)
                                        ^
make: *** [build/overviewpage.o] Fehler 1

hankrules

hero member

Activity: 673

Merit: 500

Quote from: Superxfast on February 03, 2015, 01:56:57 AM

Dear all,

Can you share me some nodes to add. My nodes can not finish syncing.

Rgrds,

getpeerinfo
[
{
"addr" : "106.186.126.57:44352",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1416736361,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 162261,
"banscore" : 0
},
{
"addr" : "37.187.100.75:41748",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1417086229,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 166191,
"banscore" : 0
},
{
"addr" : "144.76.118.179:52210",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946668,
"conntime" : 1417832829,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 174387,
"banscore" : 0
},
{
"addr" : "106.186.126.61:43879",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1420686662,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 183991,
"banscore" : 0
},
{
"addr" : "106.187.88.14:56517",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946525,
"conntime" : 1420814478,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 207301,
"banscore" : 0
},
{
"addr" : "176.31.9.212:50587",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946525,
"conntime" : 1421178193,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 211286,
"banscore" : 0
},
{
"addr" : "222.190.105.10:38786",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946704,
"conntime" : 1421564335,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 215563,
"banscore" : 0
},
{
"addr" : "5.9.81.9:50921",
"services" : "00000001",
"lastsend" : 1422946702,
"lastrecv" : 1422946702,
"conntime" : 1421679997,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 216771,
"banscore" : 0
},
{
"addr" : "37.187.176.184:45233",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1421918405,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 217942,
"banscore" : 0
},
{
"addr" : "146.199.109.85:63310",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946524,
"conntime" : 1421940752,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 219692,
"banscore" : 0
},
{
"addr" : "37.187.100.75:46031",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1422092953,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 221302,
"banscore" : 0
},
{
"addr" : "5.9.39.9:39943",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1422322693,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 223908,
"banscore" : 0
},
{
"addr" : "123.2.121.70:61150",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946480,
"conntime" : 1422634849,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 227384,
"banscore" : 0
},
{
"addr" : "217.65.8.75:40780",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946434,
"conntime" : 1422640432,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 227434,
"banscore" : 0
},
{
"addr" : "95.90.206.213:3445",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946702,
"conntime" : 1422750836,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 228587,
"banscore" : 0
},
{
"addr" : "54.191.21.109:56601",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946525,
"conntime" : 1422784817,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 228982,
"banscore" : 0
},
{
"addr" : "72.174.193.254:57577",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1422849250,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 229727,
"banscore" : 0
},
{
"addr" : "141.48.30.99:34811",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1422875233,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 229131,
"banscore" : 0
},
{
"addr" : "203.217.58.32:60094",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946434,
"conntime" : 1422882898,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 230123,
"banscore" : 0
},
{
"addr" : "85.152.4.141:41682",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422945047,
"conntime" : 1422908311,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 43592,
"banscore" : 68
},
{
"addr" : "178.222.74.174:15963",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946524,
"conntime" : 1422910488,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 227992,
"banscore" : 0
},
{
"addr" : "81.207.93.95:52316",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1422915179,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 230489,
"banscore" : 0
},
{
"addr" : "67.148.153.3:21699",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946524,
"conntime" : 1422924952,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 230583,
"banscore" : 0
},
{
"addr" : "31.18.103.45:58896",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946706,
"conntime" : 1422926740,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 223632,
"banscore" : 0
},
{
"addr" : "195.19.128.122:64066",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1422940047,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 230739,
"banscore" : 0
},
{
"addr" : "217.219.253.246:1200",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422945274,
"conntime" : 1422941117,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 52461,
"banscore" : 39
},
{
"addr" : "85.212.91.151:49488",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1422941708,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 230263,
"banscore" : 0
},
{
"addr" : "78.97.211.167:3440",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422941907,
"conntime" : 1422941907,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 58409,
"banscore" : 0
},
{
"addr" : "74.78.123.81:54726",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946703,
"conntime" : 1422943457,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 230759,
"banscore" : 0
},
{
"addr" : "5.141.226.7:48747",
"services" : "00000001",
"lastsend" : 1422946703,
"lastrecv" : 1422946524,
"conntime" : 1422943990,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 230785,
"banscore" : 0
},
{
"addr" : "109.199.64.140:1059",
"services" : "00000001",
"lastsend" : 1422946464,
"lastrecv" : 1422946466,
"conntime" : 1422945895,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : true,
"releasetime" : 0,
"height" : 55588,
"banscore" : 40
}
]

Superxfast

full member

Activity: 161

Merit: 100

Dear all,

Can you share me some nodes to add. My nodes can not finish syncing.

Rgrds,

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 6. (Read 284959 times)