Jump to content
LaunchBox Community Forums

Recommended Posts

4 minutes ago, nadonate said:

Ok, the results of this-

151666342_2019-06-1519_31_13-Window.png.688580dcf32c739fea4934babc10351d.pngand this-

923581934_KodiY.thumb.png.6ef14e8a8bcb55a9595cf68fb15a601d.png...were successful. Launched from Y, and Kodi successfully.

Ok the script doesn't mount directly to the launchbox due to update installer compatibility, can you try:

net use Y: \\lyonas\games

Then browse to the launchbox folder (Y:\launchbox) and try launching it.

Also, the new test file still fails to launch it when the share location is used, correct?

Share this post


Link to post
Share on other sites
3 minutes ago, nadonate said:

1932702249_Yagain2.thumb.png.23ba09b06cc354f74d62549e3f0b1abc.png1900205991_Yagain.png.0a9cadd2c81a24bf757fbb18a19987a7.pngSuccess, works from Kodi, and manual launch

So, using smb share directly in the addon folder location still fails?

Share this post


Link to post
Share on other sites
5 minutes ago, CoinTos said:

So, using smb share directly in the addon folder location still fails?

It does not.... 

Kodi only supports SMB v.1, and my share is SMB 3, which means Kodi will never see the NetBios name of my server, So I have to manually create a path using the local server IP within Kodi. 

My source location looks like this:

SMB_IP.thumb.png.267feafd2479252057a69f2b4a031335.pngThis has worked fine to access my media. Do you think this might have something to do with the addon issue? The issue may be with Kodi and its SMB support, and not your addon. 

I have been reluctant to enable SMB 1 support on my share because its deprecated, but if you think it may help, I am willing to give it a shot and report back...?

Share this post


Link to post
Share on other sites
Posted (edited)
45 minutes ago, nadonate said:

It does not.... 

Kodi only supports SMB v.1, and my share is SMB 3, which means Kodi will never see the NetBios name of my server, So I have to manually create a path using the local server IP within Kodi. 

My source location looks like this:

SMB_IP.thumb.png.267feafd2479252057a69f2b4a031335.pngThis has worked fine to access my media. Do you think this might have something to do with the addon issue? The issue may be with Kodi and its SMB support, and not your addon. 

I have been reluctant to enable SMB 1 support on my share because its deprecated, but if you think it may help, I am willing to give it a shot and report back...?

As long as you can get a path to BigBox.exe folder in Launchbox folder field (ie. smb://192.168.1.11/games/launchbox/) the addon doesn't care about smb version because it uses external commands (net use) to create the mapping. So if you can try that with last test file and it still fails then it has to do with how I handle 'net use' creation in python. We have proved that commands and mapping work outside of Kodi so all that leaves is the mapping creation in addon's python code.

 

EDIT:

I can recreate it now, it has to do with using a IP instead of hostname. Looking into it now.

EDIT 2:

Nothing I can do to allow IP mapping support, from all my searching windows won't let exes run from a mapped drive created with an IP instead NETBIOS name. So unless you can get a netbios name in the launchbox location field, it won't run. I will have to work on a workaround.

Edited by CoinTos

Share this post


Link to post
Share on other sites
Posted (edited)

I am moving this test file from Alpha to Beta. Everything is feature complete for 1.5.6's release just need some testers for both with and without using a smb share. If you use an IPv4 address (IPv6 is not support at all) for your smb share you will need to enable SMB IP Override setting in Advance Settings and enter in your SMB host name of your share server. If you don't, a dialog will pop up telling you to do so or if no is selected, it will exit the addon.

Key Features:
Kodi SMB support (user/pass, IPv4 override support)
Python 2 and 3 compatible using Kodi Six library (Kodi restart is required on first install of Kodi Six module or addon won't see it)

 

Edited by CoinTos
removed test file

Share this post


Link to post
Share on other sites

I resolved my SMB/NETBIOS issue. Everything is working great using the last 1.5.6 on my SMB share.

 

1647584175_2019-06-1616_33_12-Kodi.thumb.png.b47df0a108fe2a131eaf8d2244eed393.png

For anyone else having issues, the solution was not only making sure SMB 1 support was enabled on the share, but enabling SMB 1 support in windows 10. I'm using Kodi 18 BTW.

 

Thanks for all your help @CoinTos !!

Share this post


Link to post
Share on other sites
1 hour ago, nadonate said:

I resolved my SMB/NETBIOS issue. Everything is working great using the last 1.5.6 on my SMB share.

 

1647584175_2019-06-1616_33_12-Kodi.thumb.png.b47df0a108fe2a131eaf8d2244eed393.png

For anyone else having issues, the solution was not only making sure SMB 1 support was enabled on the share, but enabling SMB 1 support in windows 10. I'm using Kodi 18 BTW.

 

Thanks for all your help @CoinTos !!

Glad, it's working for you now. The beta I posted this morning has work around for those that can't enable SMB1 support but letting you set the smb share with an IP in the addon's launchbox location and then setting the server name in the SMB IP Override option of the addon's Advanced settings. It then replaces the IP with server name supplied. As long as you can access  the share (\\server\share\folder-with-launchbox-folder\) directly in windows network browser, you can use the IP override without setting up smb1 for Kodi and the mapper will create the drive with server name instead of IP to launch BigBox.

Share this post


Link to post
Share on other sites
Posted (edited)

Beta 2 Released

Fixes:
Changed the smb label text in Advanced settings
Rewrote Update handler to work with smb shares support better in AHK script

 

Edited by CoinTos
Test file deleted, final version posted to downloads section.

Share this post


Link to post
Share on other sites
On 6/13/2019 at 5:04 AM, CoinTos said:

Ok, under process tab is it gone from background processes as well?

This is weird one because on my test machine in any version of Kodi, it stalls a little, not responsive due to loading over wifi, no issues on hard line and takes up to about 1gig of ram while loading up (I tested with and without a start up video) and runs without issue. I don't really know how to recreate this. I also did a launchbox update test over the mapped drive with addon and that is when I saw a 7zip extraction on first boot after update that stalled the start up a fair bit more but haven't had anything kill the process like your video suggests.

this was very helpful, thank you for taking out time to give out this information. 

Best regards

kevin. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...