Disk ID stored as XXXXXX when importing
 

When I try to index a file as a KMA, it imports fine EXCEPT it stores the diskid as XXXXXX. When I try to import another file the diskid "XXXXXX is in use error pops up". File import formats are all correct. I put in a support ticket.

Re: Disk ID stored as XXXXXX when importing
 

We think that we just found/fixed this issue. Can you email me at Support@mtu.com and I can give you a version to test.

Re: Disk ID stored as XXXXXX when importing
 

Hats off to Bryan and the rest of the team for an immediate fix to the problem:). I have been with Hoster since version 1.0 and have never had that kind of turnaround anywhere. Thanks again!

Re: Disk ID stored as XXXXXX when importing
 

Diggerwertz,
We could not have fixed it so fast without your help in testing! Thank you!

This will be released in version 5.40.02 hopefully on Monday 8/23/2015.

Re: Disk ID stored as XXXXXX when importing
 

Latest version doesn't allow importing a BIN file as Hoster states it cannot find the DiskID and wants me to strip the DiskID so that Hoster can assign its own DiskID. Uploaded a JPG to show the Hoster Message. Going back to previous version so I can import songs and to get rid of the incessant long reading of BookIDs upon loading Hoster. I'll deal with all the problems in the previous version.

Re: Disk ID stored as XXXXXX when importing
 

More Info:
I see that, somehow, upon Processing my ZIP file I ended up adding a DASH ONE (-1) to my DiskID. As in:
SF355-1-01 instead of
SF355-01

I apologize for not seeing this problem and will be a little more attentive in the future.

Re: Disk ID stored as XXXXXX when importing
 

Solved and closed.