KMAs from ZIP don't play...they use to

[BANDL]

I have a large number of KMA (from zip) files in my Hoster's hard drive. However, now they are not playing. When I bring them I get a message
"Unexpected error processing the zip file: 0x00000200"
C:Documents......\local\temp\auout.zzz

The files I am trying to play are KMA not zip, but they were nade from zip file. Other KMA files play fine.

I tried reloading Hoster 3.317
Could this be a problem with 3.317... I recently upgraded.

HELP!!!!

PS. Those files that do not play in Hoster, play very well in Microstudio so it is not the file that is corrupted but the manner in which Hoster seems to be handling the files.

[UPNext]

I just upgraded to 3.317 and am seeing the same problem. Unfortunately even after downgrading to 3.316 the affected files still don't play. Not sure what is going on. The affected files were definitely playing correctly before the upgrade.

[UPNext]

After trying multiple system restores, hoster reinstalls, hoster downgrades which all failed to fix anything I found out how to correct the problem. I went to the temp directory under my user account (larryw) and deleted all files and folders. Once I did that the zip files work in Hoster correctly again. The path to the directory is
C:\Documents and Settings\larryw\Local Settings\Temp

Not sure what was going on but this fixed it for me!

[mindonstrike]

Originally Posted by UPNext

After trying multiple system restores, hoster reinstalls, hoster downgrades which all failed to fix anything I found out how to correct the problem. I went to the temp directory under my user account (larryw) and deleted all files and folders. Once I did that the zip files work in Hoster correctly again. The path to the directory is
C:\Documents and Settings\larryw\Local Settings\Temp

Not sure what was going on but this fixed it for me!

Was this permanent fix or just for that session?

Sam

[UPNext]

I rebooted the system and started Hoster again and everything continues to work fine.

[UPNext]

I'm finding that the problem is coming back and the temporary fix is to clear everything out of the temp directory. I think support will need to figure out what is actually happening here to permanently correct it.