Bitcoin Forum
December 11, 2018, 03:44:32 AM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 2 [3] 4 5 6 7 »  All
  Print  
Author Topic: Official [ROKOS Core] Bitcoin Full node Raspberry Pi P64 IoT Feedback/Discussion  (Read 12533 times)
kingaltcoins
Hero Member
*****
Offline Offline

Activity: 756
Merit: 500


★Nitrogensports.eu★


View Profile
February 02, 2016, 09:54:55 PM
 #41

I am wondering what will happen when the size of the blockchain goes above limit! For example think of the blockchain size crossing 100 GB!
How will the memory card inside the pi be able to hold such a long chain?

Will there be an option to store it in cloud in future to deal with the storage issue?

Btw I like the whole concept though and I might try it soon on my spare pi. Wink


           █████████████████     ████████
          █████████████████     ████████
         █████████████████     ████████
        █████████████████     ████████
       ████████              ████████
      ████████              ████████
     ████████     ███████  ████████     ████████
    ████████     █████████████████     ████████
   ████████     █████████████████     ████████
  ████████     █████████████████     ████████
 ████████     █████████████████     ████████
████████     ████████  ███████     ████████
            ████████              ████████
           ████████              ████████
          ████████     █████████████████
         ████████     █████████████████
        ████████     █████████████████
       ████████     █████████████████
▄▄
██
██
██
██
██
██
██
██
██
██     
██
██
▬▬ THE LARGEST & MOST TRUSTED ▬▬
      BITCOIN SPORTSBOOK     
   ▄▄
██
██
██
██
██
██
██
██
██
██     
██
██
             ▄▄▄▄▀▀▀▀▄
     ▄▄▄▄▀▀▀▀        ▀▄▄▄▄           
▄▀▀▀▀                 █   ▀▀▀▀▀▀▀▄▄
█                    ▀▄          █
 █   ▀▌     ██▄        █          █               
 ▀▄        ▐████▄       █        █
  █        ███████▄     ▀▄       █
   █      ▐████▄█████████████████████▄
   ▀▄     ███████▀                  ▀██
    █      ▀█████    ▄▄        ▄▄    ██
     █       ▀███   ████      ████   ██
     ▀▄        ██    ▀▀        ▀▀    ██
      █        ██        ▄██▄        ██
       █       ██        ▀██▀        ██
       ▀▄      ██    ▄▄        ▄▄    ██
        █      ██   ████      ████   ██
         █▄▄▄▄▀██    ▀▀        ▀▀    ██
               ██▄                  ▄██
                ▀████████████████████▀




  CASINO  ●  DICE  ●  POKER   
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
   24 hour Customer Support   

▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
1544499872
Hero Member
*
Offline Offline

Posts: 1544499872

View Profile Personal Message (Offline)

Ignore
1544499872
Reply with quote  #2

1544499872
Report to moderator
1544499872
Hero Member
*
Offline Offline

Posts: 1544499872

View Profile Personal Message (Offline)

Ignore
1544499872
Reply with quote  #2

1544499872
Report to moderator
1544499872
Hero Member
*
Offline Offline

Posts: 1544499872

View Profile Personal Message (Offline)

Ignore
1544499872
Reply with quote  #2

1544499872
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1544499872
Hero Member
*
Offline Offline

Posts: 1544499872

View Profile Personal Message (Offline)

Ignore
1544499872
Reply with quote  #2

1544499872
Report to moderator
1544499872
Hero Member
*
Offline Offline

Posts: 1544499872

View Profile Personal Message (Offline)

Ignore
1544499872
Reply with quote  #2

1544499872
Report to moderator
wttbs
Legendary
*
Offline Offline

Activity: 1834
Merit: 1006



View Profile
February 02, 2016, 10:00:50 PM
 #42

I am wondering what will happen when the size of the blockchain goes above limit! For example think of the blockchain size crossing 100 GB!
How will the memory card inside the pi be able to hold such a long chain?

Will there be an option to store it in cloud in future to deal with the storage issue?

Btw I like the whole concept though and I might try it soon on my spare pi. Wink

You can store the blockchain on an USB device like USB memory stick or better an USB hard drive.

I plugged a 750GB USB 2.5" external harddisk in my Pi 2, the blockchain is there so no worries regarding size of the blockchain the next year(s). Bitcoind runs on the pi, only a simple edit (datadir= ) of the bitcoin.conf is needed. ROKOS recognized the USB HDD at once, no problem mounting it and stuff.


OKtoshi
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


OK


View Profile
February 04, 2016, 07:37:00 PM
 #43

Hi how would I update to 0.12 ? I hear it has a pruned function so it will actually fit on my zero


New Bitcoin client is awesome, you can prune the blockchain to a 2Gb size, here is the update procedure.

Code:
sudo apt-get install libevent-dev

git clone -b 0.12 https://github.com/bitcoin/bitcoin

cd bitcoin

export CPATH="/usr/local/BerkeleyDB.4.8/include"

export LIBRARY_PATH="/usr/local/BerkeleyDB.4.8/lib"

./autogen.sh

./configure --enable-upnp-default --with-gui

make -j2

sudo make install

Enjoy your new and updated Bitcoin Fullnode 0.12

OK is open-source; its design is public, nobody owns or controls OK and everyone can take part.
OKtoshi
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


OK


View Profile
February 04, 2016, 07:38:54 PM
 #44

I am wondering what will happen when the size of the blockchain goes above limit! For example think of the blockchain size crossing 100 GB!
How will the memory card inside the pi be able to hold such a long chain?

Will there be an option to store it in cloud in future to deal with the storage issue?

Btw I like the whole concept though and I might try it soon on my spare pi. Wink

You can store the blockchain on an USB device like USB memory stick or better an USB hard drive.

I plugged a 750GB USB 2.5" external harddisk in my Pi 2, the blockchain is there so no worries regarding size of the blockchain the next year(s). Bitcoind runs on the pi, only a simple edit (datadir= ) of the bitcoin.conf is needed. ROKOS recognized the USB HDD at once, no problem mounting it and stuff.



Thanks for your support to Bitcoin and the community! very nice setup, will use the image at twitter.

OK is open-source; its design is public, nobody owns or controls OK and everyone can take part.
OKtoshi
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


OK


View Profile
February 04, 2016, 08:01:19 PM
 #45

Hi how would I update to 0.12 ? I hear it has a pruned function so it will actually fit on my zero


New Bitcoin client is awesome, you can prune the blockchain to a 2Gb size, here is the update procedure.

Code:
sudo apt-get install libevent-dev

git clone -b 0.12 https://github.com/bitcoin/bitcoin

cd bitcoin

export CPATH="/usr/local/BerkeleyDB.4.8/include"

export LIBRARY_PATH="/usr/local/BerkeleyDB.4.8/lib"

./autogen.sh

./configure --enable-upnp-default --with-gui

make -j2

sudo make install

Enjoy your new and updated Bitcoin Fullnode 0.12


About Bitcoin Pruning and How to  (Bitcoin 0.12)

Block file pruning
This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. To recap, there are four types of data related to the blockchain in the bitcoin system: the raw blocks as received over the network (blk???.dat), the undo data (rev???.dat), the block index and the UTXO set (both LevelDB databases). The databases are built from the raw data.

Block pruning allows Bitcoin Core to delete the raw block and undo data once it’s been validated and used to build the databases. At that point, the raw data is used only to relay blocks to other nodes, to handle reorganizations, to look up old transactions (if -txindex is enabled or via the RPC/REST interfaces), or for rescanning the wallet. The block index continues to hold the metadata about all blocks in the blockchain.

The user specifies how much space to allot for block & undo files. The minimum allowed is 550MB. Note that this is in addition to whatever is required for the block index and UTXO databases. The minimum was chosen so that Bitcoin Core will be able to maintain at least 288 blocks on disk (two days worth of blocks at 10 minutes per block). In rare instances it is possible that the amount of space used will exceed the pruning target in order to keep the required last 288 blocks on disk.

Block pruning works during initial sync in the same way as during steady state, by deleting block files “as you go” whenever disk space is allocated. Thus, if the user specifies 550MB, once that level is reached the program will begin deleting the oldest block and undo files, while continuing to download the blockchain.

For now, block pruning disables block relay. In the future, nodes with block pruning will at a minimum relay “new” blocks, meaning blocks that extend their active chain.

Block pruning is currently incompatible with running a wallet due to the fact that block data is used for rescanning the wallet and importing keys or addresses (which require a rescan.) However, running the wallet with block pruning will be supported in the near future, subject to those limitations.

Block pruning is also incompatible with -txindex and will automatically disable it.

Once you have pruned blocks, going back to unpruned state requires re-downloading the entire blockchain. To do this, re-start the node with -reindex. Note also that any problem that would cause a user to reindex (e.g., disk corruption) will cause a pruned node to redownload the entire blockchain. Finally, note that when a pruned node reindexes, it will delete any blk???.dat and rev???.dat files in the data directory prior to restarting the download.

To enable block pruning on the command line:

    -prune=N: where N is the number of MB to allot for raw block & undo data.

Modified RPC calls:

    getblockchaininfo now includes whether we are in pruned mode or not.
    getblock will check if the block’s data has been pruned and if so, return an error.
    getrawtransaction will no longer be able to locate a transaction that has a UTXO but where its block file has been pruned.

Pruning is disabled by default.

OK is open-source; its design is public, nobody owns or controls OK and everyone can take part.
salaman112
Member
**
Offline Offline

Activity: 104
Merit: 10


View Profile
February 08, 2016, 04:46:12 PM
 #46

Great work on this!
Running it atm on my  raspberry 2b+ Grin

██████████    YoBit.net - Cryptocurrency Exchange - Over 350 coins
█████████    <<  ● $$$ - $$$ - $$$ - $$$ - $$$ - $$$ - $$$   >>
██████████    <<  ● Play DICE! Win 1-5 btc just for 5 mins!  >>
rikrikrik
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500


where am i? HELLO WORLD


View Profile
February 08, 2016, 06:49:22 PM
 #47

ok when i boot my pi (no monitor) and then i vnc into it, i get a terrible resolution how do i get it to something better

Code:
pi@rokos ~ $ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 656 x 416, current 656 x 416, maximum 656 x 416
default connected 656x416+0+0 0mm x 0mm
   656x416        0.00*
pi@rokos ~ $

I sell small amounts of BTC for PayPal msg me for details and spot rate
rikrikrik
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500


where am i? HELLO WORLD


View Profile
February 08, 2016, 11:32:32 PM
 #48

so i keep make -j2 until it finishes?

Code:
pi@rokos ~/bitcoin $ make -j2
Making all in src
make[1]: Entering directory '/home/pi/bitcoin/src'
make[2]: Entering directory '/home/pi/bitcoin/src'
  CXX      libbitcoinconsensus_la-hash.lo
  CXX      libbitcoinconsensus_la-pubkey.lo
  CXX      libbitcoinconsensus_la-uint256.lo
  CXX      libbitcoinconsensus_la-utilstrencodings.lo
make[3]: Entering directory '/home/pi/bitcoin/src/secp256k1'
gcc -I. -g -O2 -Wall -Wextra -Wno-unused-function -c src/gen_context.c -o gen_context.o
  CXX      bitcoind-bitcoind.o
gcc gen_context.o -o gen_context
./gen_context
  CC       src/libsecp256k1_la-secp256k1.lo
  CXX      libbitcoin_server_a-addrman.o
  CCLD     libsecp256k1.la
make[3]: Leaving directory '/home/pi/bitcoin/src/secp256k1'
  CXX      libbitcoin_server_a-alert.o
virtual memory exhausted: Cannot allocate memory
Makefile:3687: recipe for target 'libbitcoin_server_a-alert.o' failed
make[2]: *** [libbitcoin_server_a-alert.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/pi/bitcoin/src'
Makefile:6904: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/pi/bitcoin/src'
Makefile:641: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
pi@rokos ~/bitcoin $ make -j2
Making all in src
make[1]: Entering directory '/home/pi/bitcoin/src'
make[2]: Entering directory '/home/pi/bitcoin/src'
  CXX      crypto/libbitcoinconsensus_la-hmac_sha512.lo
  CXX      crypto/libbitcoinconsensus_la-ripemd160.lo
  CXX      crypto/libbitcoinconsensus_la-sha1.lo
  CXX      crypto/libbitcoinconsensus_la-sha256.lo
  CXX      crypto/libbitcoinconsensus_la-sha512.lo
  CXX      primitives/libbitcoinconsensus_la-transaction.lo
  CXX      script/libbitcoinconsensus_la-bitcoinconsensus.lo
  CXX      script/libbitcoinconsensus_la-interpreter.lo
  CXX      script/libbitcoinconsensus_la-script.lo
  CXX      libbitcoin_server_a-alert.o
  CXX      libbitcoin_server_a-bloom.o
virtual memory exhausted: Cannot allocate memory
Makefile:3687: recipe for target 'libbitcoin_server_a-alert.o' failed
make[2]: *** [libbitcoin_server_a-alert.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/pi/bitcoin/src'
Makefile:6904: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/pi/bitcoin/src'
Makefile:641: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
pi@rokos ~/bitcoin $ make -j2
Making all in src
make[1]: Entering directory '/home/pi/bitcoin/src'
make[2]: Entering directory '/home/pi/bitcoin/src'
  CXXLD    libbitcoinconsensus.la
  CXX      libbitcoin_server_a-alert.o
  CXX      libbitcoin_server_a-chain.o

I sell small amounts of BTC for PayPal msg me for details and spot rate
OKtoshi
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


OK


View Profile
February 09, 2016, 04:32:03 PM
 #49

ok when i boot my pi (no monitor) and then i vnc into it, i get a terrible resolution how do i get it to something better

Code:
pi@rokos ~ $ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 656 x 416, current 656 x 416, maximum 656 x 416
default connected 656x416+0+0 0mm x 0mm
   656x416        0.00*
pi@rokos ~ $

Hi, this is a known issue on Pi, please trouble shot with this guide/tut :  https://www.raspberrypi.org/forums/viewtopic.php?t=8081&p=97803

Future ROKOS versions will come with integrated and easy to use VNC to avoid this kind of issues for new users.

OK is open-source; its design is public, nobody owns or controls OK and everyone can take part.
OKtoshi
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


OK


View Profile
February 09, 2016, 04:34:32 PM
 #50

so i keep make -j2 until it finishes?

Code:
pi@rokos ~/bitcoin $ make -j2
Making all in src
make[1]: Entering directory '/home/pi/bitcoin/src'
make[2]: Entering directory '/home/pi/bitcoin/src'
  CXX      libbitcoinconsensus_la-hash.lo
  CXX      libbitcoinconsensus_la-pubkey.lo
  CXX      libbitcoinconsensus_la-uint256.lo
  CXX      libbitcoinconsensus_la-utilstrencodings.lo
make[3]: Entering directory '/home/pi/bitcoin/src/secp256k1'
gcc -I. -g -O2 -Wall -Wextra -Wno-unused-function -c src/gen_context.c -o gen_context.o
  CXX      bitcoind-bitcoind.o
gcc gen_context.o -o gen_context
./gen_context
  CC       src/libsecp256k1_la-secp256k1.lo
  CXX      libbitcoin_server_a-addrman.o
  CCLD     libsecp256k1.la
make[3]: Leaving directory '/home/pi/bitcoin/src/secp256k1'
  CXX      libbitcoin_server_a-alert.o
virtual memory exhausted: Cannot allocate memory
Makefile:3687: recipe for target 'libbitcoin_server_a-alert.o' failed
make[2]: *** [libbitcoin_server_a-alert.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/pi/bitcoin/src'
Makefile:6904: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/pi/bitcoin/src'
Makefile:641: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
pi@rokos ~/bitcoin $ make -j2
Making all in src
make[1]: Entering directory '/home/pi/bitcoin/src'
make[2]: Entering directory '/home/pi/bitcoin/src'
  CXX      crypto/libbitcoinconsensus_la-hmac_sha512.lo
  CXX      crypto/libbitcoinconsensus_la-ripemd160.lo
  CXX      crypto/libbitcoinconsensus_la-sha1.lo
  CXX      crypto/libbitcoinconsensus_la-sha256.lo
  CXX      crypto/libbitcoinconsensus_la-sha512.lo
  CXX      primitives/libbitcoinconsensus_la-transaction.lo
  CXX      script/libbitcoinconsensus_la-bitcoinconsensus.lo
  CXX      script/libbitcoinconsensus_la-interpreter.lo
  CXX      script/libbitcoinconsensus_la-script.lo
  CXX      libbitcoin_server_a-alert.o
  CXX      libbitcoin_server_a-bloom.o
virtual memory exhausted: Cannot allocate memory
Makefile:3687: recipe for target 'libbitcoin_server_a-alert.o' failed
make[2]: *** [libbitcoin_server_a-alert.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/home/pi/bitcoin/src'
Makefile:6904: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/pi/bitcoin/src'
Makefile:641: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
pi@rokos ~/bitcoin $ make -j2
Making all in src
make[1]: Entering directory '/home/pi/bitcoin/src'
make[2]: Entering directory '/home/pi/bitcoin/src'
  CXXLD    libbitcoinconsensus.la
  CXX      libbitcoin_server_a-alert.o
  CXX      libbitcoin_server_a-chain.o

By using -J2 we are indicating the compiler to use 2 cores from the processor, this speeds up the process a lot, but if you have more programs open and you are using resources while building then it will throw up a memory exhaust problem, to avoid one can do 1 of the 2 solutions,

1st) just use   make     instead of  make -J2

2nd option) close every open program except for the terminal to do the compilation with the -J2 flag.

Cheers.

OK is open-source; its design is public, nobody owns or controls OK and everyone can take part.
sanitarium616
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
February 12, 2016, 01:03:19 PM
 #51

i redownloaded the os image but when i go to unzip it it says the archive is corrupt (ive downloaded it a few times to see if it was a problem with the the download).
am i the only one?
rikrikrik
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500


where am i? HELLO WORLD


View Profile
February 12, 2016, 02:08:46 PM
 #52

i redownloaded the os image but when i go to unzip it it says the archive is corrupt (ive downloaded it a few times to see if it was a problem with the the download).
am i the only one?

Yes and no, it's not a Windows file its a image you burn to your sd card

I sell small amounts of BTC for PayPal msg me for details and spot rate
sanitarium616
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
February 12, 2016, 02:26:38 PM
 #53

i redownloaded the os image but when i go to unzip it it says the archive is corrupt (ive downloaded it a few times to see if it was a problem with the the download).
am i the only one?

Yes and no, it's not a Windows file its a image you burn to your sd card


its the rar file that the img file downloads in that is throwing up the error not the img file itself
rikrikrik
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500


where am i? HELLO WORLD


View Profile
February 12, 2016, 03:25:10 PM
 #54

Filename.img.zip

No rar ?

I sell small amounts of BTC for PayPal msg me for details and spot rate
sanitarium616
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
February 12, 2016, 03:32:48 PM
 #55

Filename.img.zip

No rar ?

well i'm using winrar to unzip it so i guess i'm just used to saing the rar term
rikrikrik
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500


where am i? HELLO WORLD


View Profile
February 12, 2016, 03:53:17 PM
 #56

I'm on my iPhone right now so I can't tell


Have you tried mounting the img (or rar which I have never heard someone call a zip file before this day) onto your sd card?

I sell small amounts of BTC for PayPal msg me for details and spot rate
sanitarium616
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
February 12, 2016, 04:02:26 PM
 #57

I'm on my iPhone right now so I can't tell


Have you tried mounting the img (or rar which I have never heard someone call a zip file before this day) onto your sd card?

am used to working with .rar files so i'm in the habit of calling all compressed files rar files.

i have and it appears to work i was just wondering if it was just me that gets the error and if it has any effect in the actual .img file
OKtoshi
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


OK


View Profile
February 12, 2016, 05:24:27 PM
 #58

I'm on my iPhone right now so I can't tell


Have you tried mounting the img (or rar which I have never heard someone call a zip file before this day) onto your sd card?

am used to working with .rar files so i'm in the habit of calling all compressed files rar files.

i have and it appears to work i was just wondering if it was just me that gets the error and if it has any effect in the actual .img file

It is an error as Windows is trying to read it as a file instead of an image and was made on linux (no real error), should have no issue at all with mounting to use with your Pi devices, you can always make sure your file is not corrupted by checking the SumCheck.

OK is open-source; its design is public, nobody owns or controls OK and everyone can take part.
sanitarium616
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
February 12, 2016, 05:29:07 PM
 #59

I'm on my iPhone right now so I can't tell


Have you tried mounting the img (or rar which I have never heard someone call a zip file before this day) onto your sd card?

am used to working with .rar files so i'm in the habit of calling all compressed files rar files.

i have and it appears to work i was just wondering if it was just me that gets the error and if it has any effect in the actual .img file

It is an error as Windows is trying to read it as a file instead of an image and was made on linux (no real error), should have no issue at all with mounting to use with your Pi devices, you can always make sure your file is not corrupted by checking the SumCheck.

ok cool cheers i just wanted to make sure the file wasnt damaged somewhere in the download process
OKtoshi
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000


OK


View Profile
February 12, 2016, 06:07:52 PM
 #60

I'm on my iPhone right now so I can't tell


Have you tried mounting the img (or rar which I have never heard someone call a zip file before this day) onto your sd card?

am used to working with .rar files so i'm in the habit of calling all compressed files rar files.

i have and it appears to work i was just wondering if it was just me that gets the error and if it has any effect in the actual .img file

It is an error as Windows is trying to read it as a file instead of an image and was made on linux (no real error), should have no issue at all with mounting to use with your Pi devices, you can always make sure your file is not corrupted by checking the SumCheck.

ok cool cheers i just wanted to make sure the file wasnt damaged somewhere in the download process

Awesome, let us know if you need further support, enjoy your ROKOS

OK is open-source; its design is public, nobody owns or controls OK and everyone can take part.
Pages: « 1 2 [3] 4 5 6 7 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!