[meridius]

If it was me doing it, I would:
1. exit both XBMC 12.2 instances so that they are not connected to the database
2. on the SQL server, rename MyVideos75 to tempMyVideos75
(and it there are DBs of versions less than 75, rename or delete those too)
3. start up a Kodi 17 instance and allow it to create a new blank MyVideos107 database
4. on the SQL server, rename tempMyVideos75 back to MyVideos75

I think that would allow meridius to have the two databases co-existing on the same MySQL server...

@meridius, did you try what I said earlier in this thread?

Once you rename it, Krypton won't try to update it - it will just create a blank Krypton DB.
Once the Krypton DB is there, Krypton will never look at the older DB

I will try that, thanks

also noticed a
mymusic7
myvideos34.db

what are these as I can not find this info in any kodi or xbmc wiki about these db file names

[zerocool_ie]

MyMusic7 is from Kodi v10
MyVideos 34 is from pre-v10

Database versions (wiki)

[meridius]

thanks

also noticed I have 3 users

root
xbmc
root

can I delete the 2 root versions ? or just leave them be I am not to sure if I created them or if they where there when I installed

also in database I have
information_schema
MySQL
performance_schema

are these normal should they be there ? or should I delete them

thanks

[meridius]

sorted had to remove the xbmc data base then run kod17 and then run xbmc 12 to create the database, quit xbmc and copied over database and rerun and back to normal,

now have two sets of database so I can play with kodi and see how I go. I have noticed kodi crashes a lot when you try and close it down happens about 50/50 but see many people having the same problems but since mine is a totally fresh install There must be some sort of windows bug.