Yes, you're right. I've tried all d2x versions from v1 up to v8 with success on 6.5.1 and 6.6.1 an both v10-beta52 and beta53 failing. So it's not a bug of ModMii itself. Glad you figured it out!So this makes no F'ing sense, but apparently only if ModMii is running from the Program Files folder (as admin as is necessary for it to be run from this location), this line causes it to crash
Code:if /i "%Drive:~1,1%" EQU ":" (set fulldrive=%Drive%) else (set fulldrive=%cd%\%Drive%)
but if you edit and replace it with these 2 lines, everything works!
Code:if /i "%Drive:~1,1%" EQU ":" set fulldrive=%Drive% if /i "%Drive:~1,1%" NEQ ":" set fulldrive=%cd%\%Drive%
it's funny because the less efficient code with 2 lines instead of just 1 works better apparently... sometimes I have to wonder if some of my old "inefficient" code was actually trial and error to get things to work in messed up situations like this one
Anyway, please test it again with ModMii still installed to your Program Files folder, and manually edit replace the lines indicated, and I think it will work for you! If you can confirm this, I'll include it in the next update!
edit: modmii skin still failing (or rather, classic crashes when trying to use ModMii skin), but classic is working with this change.
I will put some effort into getting this to work from the Program Files directory, but I suspect there will be lots of random things that just can go wrong and generally people should not install here... yes I know, it's counter intuitive.
--------------------- MERGED ---------------------------
This isn't what I asked you to test, but I'm glad you did because this is actually very helpful information, thank you!
But can you test 6.5.1 (not 6.6.1)? Also with 6.5.1 can you test one of the d2x v10 betas (but not the 65535 version I linked to earlier, that is expected to fail on anything lower than 6.6.0)? If this fails, then I at least know that 6.5.1 and 6.6.0 have the same issue for you (which is building any d2x that is greater than v8). I am going to edit this post some more stay tuned
edit: tmd edit is not used to build d2x cIOSs v8 or lower, now it all totally makes sense!! I'm 100% positive you will have the same problem on older versions of ModMii when building d2x cIOSs newer than v8. This was just never something you experienced because the default was v8 prior to v6.6.0! Now that it's the default, I'm sure if it's a common issue I will hear more and more reports about it.... but so far you're the only one, so maybe your windows environment truly is funky somehow?
edit again: so there's a couple things we can do. First, if you are somehow able to figure out how to get tmdedit to work on your PC, that knowledge is power! Otherwise, the easy solution is to switch to d2x v8-final, which is basically the same as v10-beta52 but ModMii doesn't use tmdedit to build it. And the final thing is going to be a bit of a pain but not that bad... I can have ModMii construct the tmd without tmd edit for the default d2x, but it will still be required for any other betas... which would basically just be v10beta53alt, so maybe I should avoid tmd edit for all the current releases and only use it for new betas (if ever applicable). The only reason why tmd edit was developed was for davebaol to be able to have ModMii build his cIOSs based on his source ciosmaps.xml quickly and easily without requiring me to manually do the patches and build support for each new beta.
here's some info on tmd edit, this was a tool developed by person66 with me and davebaol for ModMii and there's almost zero info on it anywhere except a private convo that I've clipped this quote from
edit: holy crap I'm an editing champion, I feel like I've been editing this same post for 2 hours!
This is from 6.5.1: