This may be the info we needed.

I too get that error message when I play a HDZIP created by Hoster and often they are causing MS to crash

Songverted KMA from Zip play fine for me. I'm only getting the error from one made by Hoster

Hoster KMA's from CDG (cdcdg) play fine and produce an out.dat file in the temp folder.
Hoster KMA's from mp3g and bin, and songverted KMA's from zip creates 2 files in the temp folder, auout.dat and auout.cdg .
Unlike Zip files MS only creates these temp files for KMA when the songs are played.

HDZIPS create an auout.zzz & rsn.mp3 file

Curious if the guys who've switched back to 4.001 have this same temp folder.

Sam

For the record, last Friday to Tuesday were MTU holidays. Thus, no response. Of course we're now digging out from support issues over that period. :r

We acknowledge there is a bug in 4.002. We haven't identified it yet, but "suspect" the new code we are using that allows us to process ZIP files using MAX compression. We never did MAX ZIPs before, including MS 4.001 and all of Hoster. Only Microstudio 4.002 and Songverter 1.000 have this new code.

It appears that temp filenames are getting confused, and contrary to our belief, are not getting cleared when we OPEN MS/SV again for processing ZIPs. We will make sure that we clear the buffer on RUN, as temp files are left if a program crashes.

We're on this right now and hope to have at least a target today, if not a fix. I'll post back here later on what we find.

mtu staff
thankyou for getting back to me i did not know you were on hollidays
until this email you just send to me otherwise i would not have sent emails like i did to try to fix the problem, i,m glad to see you are looking to fix it.
just a concern to me as a devoted mtu user mabye when there is a problem, and you see there is ,if its mine or somebodys elses that there is a area on you site we can go and let us know your working on the problems.

thanks again NORTHLAND

Interesting idea. One problem is that competitors watch what we do. We used to "tell all" in the Factory News page, but that became a nightmare as we saw function after function appear in competing products before we released. So we stopped telling. :s

What we do is exactly what has happened here. Some of our Betas are here, working with you and the others to identify the problem. Once they determined it was a bug, not system related, they sent up a flare and we came running. :g

We think we solved the problem. We are sending out 4.003 Beta 1 tonight to our testers. If they approve quickly, you'll see it either Friday or next Monday (probable). :c

mtu
thank you very much its hard when you don't now the in and outs i have learned alot by what as happen,and will conitue to be a mtu fan and user

thankyou northland.

4002
 

just to let everyone know that the good people at mtu fixed my problem
and i,m very pleased. i,m very happy with there products and software
microstudio family etc thats why there number one.
northland

How Was It All Fixed?
 

What was wrong? How did you get your problem solved?

all the problems i had and talk about , mtu has fixed with a a upgrade
for microstudio 4003-beta 1 which they had talked about, i would say should be coming soon. northland

Any idea when the maintenance release will be ready?
 

I too have experienced the problem described in this thread. It's not critical but it is annoying. I'm just wondering what the status is?

Still working on it. Northlander's problem isn't the only thing being worked on in the update, so it isn't ready yet.

Thanks!
 

Thanks for the info...:)