dear infinityhell and me try to use Yelo Debugger based on yeloDebug.dll from Yelo neighborhood but this debuger fail to connect to our (retail to debug and DVT4 xbo) have you got any idea for fix this problem? Thanks
I had the same issue with the program either not finding the dvt4 or the pc side of the program crashing.
I'm working on a fix if you want I have a working version but only work on windows XP Send me a pm if you want a link because I not know if I can post the link here...
I know the fix not work for memDump on Windows7 but i don't know for Windows10 it could be interesting to have the error report of windows10 to see if it can be fixed On windows7: connect to xbox works but only eeprom dump working On windowsXp: all fonctionality work except kernelDump
The console has to be running xbox7887's modified xbdm.dll. Can you post the exception details from the original Yelo Debugger program?
It was running the modified xbdm.dll at the time. I can replicate the error and give that info to you in a bit.
on windows 7 I have problem to fix it seems Windows 7 does not like connecting the devkit to pc and return timeout exception i think it's caused by this warning: 'System.Net.IPAddress.Address' is obsolete: 'This property has been deprecated. It is address family dependent. Please use IPAddress.Equals method to perform comparisons. http://go.microsoft.com/fwlink/?linkid=14202' H:\Yelo Debugger\Yelo Debugger\Main.cs but i don't know how to correct this without rewrite yelo debug from the scratch
The problem isn't window 7, and just because the System.Net.IPAddress.Address property is obsolete doesn't mean it doesn't work. However, in the event that Microsoft really did remove the underlying code for the System.Net.IPAddress.Address property, I would recommend installing the .Net framework 3.5 redistributable, considering that was what YeloDebugger and YeloDebug were built on. Alternatively you can post the exception details from YeloDebugger and I will see about resolving the real issue.
