or something along those lines in d2xdrivestatus.cpp for debug purposes. I'm unable to compile it myself. I mean, I KNOW the disc is in there and I KNOW that the drive and all Xbox software can read it. It's just a matter of ignoring the warning that there is no disc in there. Maybe there are changes that could be made (or have been made in more recent builds of the XDK) to the GetTrayState() function to correct this.
bump
That's curious. A friend had a similar problem with his samsung and he need to replace it. The detect media function is from XBMP and didn't change recently.Your code change isn't an alternative as it may crash for users which no dvd inserted.
Do you have any problems with the XBMC/XBMP detection ?
I'll recheck with their code and will think of an alternative (maybe something in the settings).
Yes, I realize something must have happened with the drive or the cable as older versions of dvd2xbox used to work fine but no longer do. Also my suggestion above was in no way intended to be a change in the code indefinitely. I was just hoping that change could help me diagnose my problem, and possibly provide some insight into a more robust method of media detection. XBMP does still work for me. My thought is just that if every other Xbox application can read the disc without issue and dvd2xbox cannot in this case, then perhaps there is a more reliable method of checking the status of the drive and tray that dvd2xbox could possibly use.
As we discussed via PM, I'll try out the app when compiled with a change similar to the one above. If it works, then at least we'll know that the media detection method is flawed (even if only in some small way, and even if the hardware is flawed as well).
I just thought I'd mention that about a year ago I had removed 4 wires from the yellow DVD cable to try a Samsung 616T mod. The drive didn't fit, so I put the Thomson back in. The wires were (obviously): READY, EJECT, TRIN (tray-in), and TROUT (tray-out). dvd2xbox has worked perfectly even since this incident (up to about a month ago), so I never considered it to be related to the cable. Even now, my thought is that if one of these wires was not properly reseated into the harness and was not conducting the signal properly, it would be manifested in other functionality of the console. However, everything else about the console is fine.
So my thought is that it must be either the drive or the code.