VU+ Kodi Support .xbmc in root

[steven]

hi, i flashed with blackhole 2.1.7 my solo2 yesterday. every time i start xbmc it creates the .xbmc folder in flash, no problem move it to media/hdd, and delete it in home/root. so even thought its in hdd and each time i do this i initialise and check filesystem of the hdd, xbmc starts and it tells me its for the first time and makes another file in home/root. ive reflashed the box a few times once with the vu+ image and then the 2.1.7 image in case it had old crap in there. any ideas?

 

[steven]

i also have the same .xbmc folder in autofs/sda1 which i cant delete and im not sure i should

 

[DirtyDonki]

Are you sure they are folders and not symbolic links to the folder on hdd?

If you initialise the HDD it is wiped clean and so yes, xmbc will see it as a fist run because the .xbmc folder won't be there.

I reflash images very often because I do a lot of backup images for the forum but I never re-initialise my hdd and so .xbmc is alwasys there and always works exactly the same on any image I happen to use at any time. As long as it is compatible of course.

 

[steven]

Thanks for the reply, i phrased that wrong, i initialise before moving the root folder to hdd. I only started doing that to see if it would fix the problem. Xbmc did work once but it was in root and crashed the stb when i tried to watch anything.
Im using flashfxp as a ftp and im fairly sure they are the folders not links as i can fek around with other stuff and it works.

 

[DirtyDonki]

There are actually two folders but only the one on hdd is called .xbmc. The one in root is called xbmc and it will not hurt to leave it there. You can move it if you want however, but you must then create a symbolic link to the new location or else xbmc will crash.

 

[steven]

thanks for the replies, i fixed the problem by throwing in the bin the hard drive and throwing another new one in the solo, it must have been just a little bit feked.

 

[steven]

hi, i flashed with blackhole 2.1.7 my solo2 yesterday. every time i start xbmc it creates the .xbmc folder in flash, no problem move it to media/hdd, and delete it in home/root. so even thought its in hdd and each time i do this i initialise and check filesystem of the hdd, xbmc starts and it tells me its for the first time and makes another file in home/root. ive reflashed the box a few times once with the vu+ image and then the 2.1.7 image in case it had old crap in there. any ideas?

 

[steven]

i also have the same .xbmc folder in autofs/sda1 which i cant delete and im not sure i should

 

[DirtyDonki]

Are you sure they are folders and not symbolic links to the folder on hdd?

If you initialise the HDD it is wiped clean and so yes, xmbc will see it as a fist run because the .xbmc folder won't be there.

I reflash images very often because I do a lot of backup images for the forum but I never re-initialise my hdd and so .xbmc is alwasys there and always works exactly the same on any image I happen to use at any time. As long as it is compatible of course.

 

[steven]

Thanks for the reply, i phrased that wrong, i initialise before moving the root folder to hdd. I only started doing that to see if it would fix the problem. Xbmc did work once but it was in root and crashed the stb when i tried to watch anything.
Im using flashfxp as a ftp and im fairly sure they are the folders not links as i can fek around with other stuff and it works.

 

[DirtyDonki]

There are actually two folders but only the one on hdd is called .xbmc. The one in root is called xbmc and it will not hurt to leave it there. You can move it if you want however, but you must then create a symbolic link to the new location or else xbmc will crash.

 

[steven]

thanks for the replies, i fixed the problem by throwing in the bin the hard drive and throwing another new one in the solo, it must have been just a little bit feked.