Upgrade to 3.319 failed

[PaulK]

Hi guys

I need help please, I have upgraded my hoster to 3.319, on restarting it says it needs to move my kma files for microsoft compatability, the next popup says my files were moved safely and the data base will be rebuilt.

The problem is now everytime I try and load hoster I get these two popups again and again hoster itself doesn't load up so now cant do my shows.

Any ideas? Im running XP, fully updated, internal HD, my 7000 files all appear to have move moved ok, I can see them in c:\documents and settings\all users\shared documents\shared music\mtu\songs

I also have microstudio, which detected the new file location and rebuilt the database right away and functions fine. It's just hoster that's broken.

Thanks
Paul

[Beavis]

did you manually rebuild your database ?

[PaulK]

I wouldnt know how to im afriad. Hoster wont run, I just get the popup saying files need to be moved, then the next popup saying move successfull. but no actual hoster program to do anything.

I have microstudio which reloaded the songs, but I dont know of they are connected or not.

Simply put, hoster doesnt even start, Im quite desperarte as I have pending shows to do/ Wish i'd never upgraded now :(

Paul

[Beavis]

did you try re-installing hoster?

[ddouglass]

Check the old location for the KMA files and see if there are any still there. It should have moved the files to new location, leaving nothing in that folder. If just the folder is there try deleting it.

[lmcmains]

Originally Posted by PaulK

I wouldnt know how to im afriad. Hoster wont run, I just get the popup saying files need to be moved, then the next popup saying move successfull. but no actual hoster program to do anything.

I have microstudio which reloaded the songs, but I dont know of they are connected or not.

Simply put, hoster doesnt even start, Im quite desperarte as I have pending shows to do/ Wish i'd never upgraded now :(

Paul

The is a fix from another post from MTU. It worked for me.

If you are ok with editing the registry, take a look at the following key:

HKEY_CURRENT_USER\Software\Micro Technology Unlimited\Hoster\Default\SongFromFolder

What is its value? If it contains "C:\Program Files\..." anywhere in there, this is what Hoster detects when it puts up those messages. You can delete this key, and Hoster will restore it to a value without "C:\Program Files\..." the next time it runs. You may need to rebuild your Songs Database (Tools > Build Songs Database). Make sure it points to the directory that now has your songs (C:\Documents and Settings\...).

[lmcmains]

Originally Posted by PaulK

Hi guys

I need help please, I have upgraded my hoster to 3.319, on restarting it says it needs to move my kma files for microsoft compatability, the next popup says my files were moved safely and the data base will be rebuilt.

The problem is now everytime I try and load hoster I get these two popups again and again hoster itself doesn't load up so now cant do my shows.

Any ideas? Im running XP, fully updated, internal HD, my 7000 files all appear to have move moved ok, I can see them in c:\documents and settings\all users\shared documents\shared music\mtu\songs

I also have microstudio, which detected the new file location and rebuilt the database right away and functions fine. It's just hoster that's broken.

Thanks
Paul

I have the same problem. Does the same thing. Program won't start for me either. It does it with 3.319. Dale, all the files are where they were moved by hoster. Every time I try to load Hoster it brings up the screen saying it will move the files and then the screen saying the files were moved and the next time I try to load hoster the same screens come up and it won't start Hoster. I done and unstall and not upgrade when I installed it.

[ddouglass]

Reboot? Actually I would recommend shutting down and then restart. That should clear out any thing left in memory.

[lmcmains]

Re-booted lots of times and don't do any good

[ddouglass]

Larry post this in the current beta thread. Maybe they have a solution for it.

[admin]

As I understand, you are running the Hoster 3.319 (2/20/08 dated version) and it is showing you the two screens that it must move your KMA files, and then that you must reboot.

Here is the critical question. Are you running the INSTALLED HOSTER when you reboot, or are you running the installation program a second time?

You SHOULD be running the installed Hoster from the Hoster icon, not running the installation program a second time.

Please each of you tell us which you are doing. If there is a bug, we will be on this first thing Monday morning and get a fix out fast, but we need to know what you are seeing.

[Metalgodz]

I am getting a error reading documents and settings all users documents my music mtu songs was not found on the hard drive. What happened and what do i do?

[Metalgodz]

WOW its all gone. I loved it while it lasted.All my problems started after the upgrade. Should have let well enough alone I guess. Anyways I was bummed that i could'nt load up my divx files unto hoster without having to reload all the disks. Oh well back to the old faithful Vocopro jukebox.

[lmcmains]

What version are you using?

[Metalgodz]

3.319

[admin]

Originally Posted by Metalgodz

3.319

Merged your Thread to here as this is the Thread we are answering in.

[admin]

Originally Posted by Metalgodz

I am getting a error reading documents and settings all users documents my music mtu songs was not found on the hard drive. What happened and what do i do?

DON'T DO ANYTHING with your drive that held your KMA files.

It is starting to appear that Hoster 3.319 has a problem.

We're trying to discern what is happening. If you do not do anything to that computer, your KMA files may be recoverable.

We'll try to have a suggestion tomorrow.

[admin]

Read this Post about Hoster 3.320, and then download and install it.

The problem is in 3.318 and 3.319, now fixed in 3.320.

We too thought we had a virus when we unknowingly lost files not related to Hoster at all. We are confident we found the code that along with Windows' random operations did the NTSF index damage. We are confident we have fixed the problem, but only you folks seeing the problem repeatedly can tell us it is fixed.

Thank you for your patience. We truly are sorry this happened, and believe we have solved it.