Lost songs and unable to import from Program Files

[skart5301]

I too downloaded the 3.319 update. Afterward the program stated that not all my songs were transferred and asked if I wanted to move them. I clicked yes (nothing appeared to happen) and then I had about 1/4 of my songs. I have tried just about everything I can to recover. I don't have a C:\Documents or C:\Songs. I am no longer allowed to import from the programs (MTU) and can only use Hoster with an external hard drive where I have KMA songs stored. Hoster says my KMA's are no longer in th Hard Drive (Vista OS) I can't imagine having to start all over again..Song books won't match my inventory any longer....

[ddouglass]

The location is not C:\Documents. It is
C:\Documents and Settings\Allusers\Shared Documents\MTU\Songs

If you cannot see the Documents and Settings then you need to open Windows Explorer. Then go to Tools\Folder Options. Next click on the View tab at the top. Change the settings to allow viewing hidden files and folders and uncheck the following two settings. Then Apply. This will allow you to see system folders and files.

If your KMA files were only on an external hard drive then none should have been moved. Only those KMA files that were originally in the C:\Program Files\Micro Technology Unlimited\Hoster\Songs folder would have been moved.

[admin]

skart5301, did Ddouglass's suggestion solve your problem?

Please post your current status on this Thread problem?

[backroads]

I only store my kma files on external drives. My kma files keep disappearing. Luckily I have 4 externals so I have been able to copy my files back to the drives that lose them. I had to change drives during a long show last weekend because of lost files. I don't think I used "remove" when I downloaded 3.319 but I had skipped 3.318.

[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 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.