Hi gator,
I'm completely in the dark here.
I can't imagine how Img is creating an .MDS file while being utililized by Fab as its burn engine and not as a standalone application.
I'm not quite able to connect the dots here.
You said,
"Ever since I tried doing StarTrek even though I got it set to write ISO to the HD, ImgBurn is making a MDS file instead."
Then you said,
"...haven't been able to try ST again since I am now using a reg version.".
What do you mean by a reg version?
and what were you using previously that is apparently not reg?
Are you using the retail app and selecting Img as the burn engine, then selecting .ISO as the target and still creating an .MDS file?
If you're ripping the movie, there has to be an .ISO file somewhere. The .MDS is almost invisible in terms of size and contains little info besides the LB
Please describe in detail what application and what versions were used and please post event logs, internal logs, burn logs