(2019-07-14, 22:40)Txxb161 Wrote:

(2019-07-14, 22:27)jocala Wrote:

(2019-07-14, 21:58)Txxb161 Wrote: Is there a way to force it?  

Try this build...

http://www.jocala.com/test.exe  

Thanks, but I was able to fix it using regedit and deleting the extraneous uninstall references that were pointing to the long-ago previously deleted directory. I am now presented with a directory installation option. 

(2019-07-14, 22:40)Txxb161 Wrote:

(2019-07-14, 22:27)jocala Wrote:

(2019-07-14, 21:58)Txxb161 Wrote: Is there a way to force it?  

Try this build...

http://www.jocala.com/test.exe  

Thanks, but I was able to fix it using regedit and deleting the extraneous uninstall references that were pointing to the long-ago previously deleted directory. I am now presented with a directory installation option. 

(2019-07-14, 22:51)Txxb161 Wrote:

(2019-07-14, 22:40)Txxb161 Wrote:

(2019-07-14, 22:27)jocala Wrote: Try this build...

http://www.jocala.com/test.exe  

Thanks, but I was able to fix it using regedit and deleting the extraneous uninstall references that were pointing to the long-ago previously deleted directory. I am now presented with a directory installation option.  

Okay, so after installing 4.2 in the directory of my choice, I attempted to do another installation of 4.2 and was not presented with a directory option, so tried test.exe and was presented with it. Test.exe should probably be moved to production. 

(2019-07-14, 23:07)jocala Wrote:

(2019-07-14, 22:51)Txxb161 Wrote:

(2019-07-14, 22:40)Txxb161 Wrote: Thanks, but I was able to fix it using regedit and deleting the extraneous uninstall references that were pointing to the long-ago previously deleted directory. I am now presented with a directory installation option.  

Okay, so after installing 4.2 in the directory of my choice, I attempted to do another installation of 4.2 and was not presented with a directory option, so tried test.exe and was presented with it. Test.exe should probably be moved to production.  

The download now in production displays a directory choice option by default. Thanks for the feedback! 

(2019-07-14, 22:07)jocala Wrote:

(2019-07-14, 22:01)VonMagnum Wrote: Is it normal to have to constantly refresh ADB with FireTV now?  It does it almost every time here.

I have one device (a cube) that requires a refresh adb almost every time.  I'm still looking for a solution. 

(2020-11-08, 18:11)upsfeup Wrote: Itjocala.com seems to be down for the last few days.

Anyone knows of a reliable mirror? I lost the previously binary when I got a new computer.

(2021-01-05, 16:52)dubster Wrote: Hey guys, looking for a bit of help.

I've used adblink to move my fire tv kodi data to a usb stick and now Kodi wont start.

It's created me an xbmc_env.properties file in /mnt/sdcard which contains the following line :

xbmc.data=/storage/336D-52D7/kodi_data/Android/data/org.xbmc.kodi/files/

And then if I go to the path listed above I can see a .kodi directory with all the stuff in it you'd expect.

but when I try and start kodi it now won't start up.

Any advice?

Thanks

(2021-01-05, 19:50)jocala Wrote:

(2021-01-05, 16:52)dubster Wrote: Hey guys, looking for a bit of help.

I've used adblink to move my fire tv kodi data to a usb stick and now Kodi wont start.

It's created me an xbmc_env.properties file in /mnt/sdcard which contains the following line :

xbmc.data=/storage/336D-52D7/kodi_data/Android/data/org.xbmc.kodi/files/

And then if I go to the path listed above I can see a .kodi directory with all the stuff in it you'd expect.

but when I try and start kodi it now won't start up.

Any advice?

Thanks

Is the usb stick formatted as portable?  If it's not, Kodi won't see it.  Also, see if Kodi's log has any info after you attempt a start-up.

(2021-01-05, 20:49)dubster Wrote:

(2021-01-05, 19:50)jocala Wrote:

(2021-01-05, 16:52)dubster Wrote: Hey guys, looking for a bit of help.

I've used adblink to move my fire tv kodi data to a usb stick and now Kodi wont start.

It's created me an xbmc_env.properties file in /mnt/sdcard which contains the following line :


And then if I go to the path listed above I can see a .kodi directory with all the stuff in it you'd expect.

but when I try and start kodi it now won't start up.

Any advice?

Thanks

Is the usb stick formatted as portable?  If it's not, Kodi won't see it.  Also, see if Kodi's log has any info after you attempt a start-up.

Not sure if its formatted as portable, but Kodi can definitely see it as I can browse to the usb stick from within Kodi. 
Cool, ok I'll take a look for the log file tomorrow.

(2021-01-05, 21:06)jocala Wrote:

(2021-01-05, 20:49)dubster Wrote:

(2021-01-05, 19:50)jocala Wrote: Is the usb stick formatted as portable?  If it's not, Kodi won't see it.  Also, see if Kodi's log has any info after you attempt a start-up.

Not sure if its formatted as portable, but Kodi can definitely see it as I can browse to the usb stick from within Kodi. 
Cool, ok I'll take a look for the log file tomorrow.

 This link explains portable vs internal formatting:  https://bit.ly/3fBKtCU

Thanks - that looks like SD rather than USB.  And the method for doing it doesnt look like a fire TV thing either.
Since Kodi can see the drive and play videos off it Im assuming it must be fine.

(2021-01-06, 00:37)dubster Wrote:

(2021-01-05, 21:06)jocala Wrote:

(2021-01-05, 20:49)dubster Wrote: Not sure if its formatted as portable, but Kodi can definitely see it as I can browse to the usb stick from within Kodi. 
Cool, ok I'll take a look for the log file tomorrow.

 This link explains portable vs internal formatting:  https://bit.ly/3fBKtCU

Thanks - that looks like SD rather than USB.  And the method for doing it doesnt look like a fire TV thing either.
Since Kodi can see the drive and play videos off it Im assuming it must be fine.