Jump to content

Search the Community

Showing results for tags 'xbdm'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements
    • Site News
    • Scene News
  • Phoenix
    • Aurora releases
    • Aurora support
    • Aurora Localization
    • Skins, Coverflow Layouts, Scripts and Trainers
    • Skin development and LUA scripting
    • Unity Support
    • Requests and Suggestions
  • FreeStyle Dashboard / F3
    • News
    • FreeStyle Dashboard Releases
    • Support
    • Skins
    • Skin Dev
  • Xbox
    • Tutorials
    • Homebrew
    • LibXenon
    • Games
    • Software
    • Other topics
  • PlayStation
    • Tutorials
    • Homebrew
    • Games
    • Software
    • Other Topics
  • Matchmaking
    • North America
    • Central & South America
    • Europe
    • Asia
    • Africa
    • Australia
    • Modded Lobbies
  • MarketPlace
    • Buy
    • Sell
  • Miscellaneous
    • Feedback
    • Other Topics
    • LiNK News

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. I've been wanting to implement a small TCP server on my RGH for a while but I've found that the server stops accepting clients once a game title has loaded. I was wondering if anyone has any idea why this may be (or even how to get around this). Relevant information is as follows: The server module is a dashlaunch plugin, it launches in a system thread. The server accepts clients just fine whilst on dashboard but no longer accepts clients when a game title is loaded. I've verified that the module isn't being unloaded or anything like that by running the "modules" command over XBDM (and looping a DbgPrint to show that the background thread can still execute whilst a game title is running, just seemingly _accept_ blocks indefinitely or does nothing). I've set the "undocumented" socket options for running the sockets unencrypted (i.e. the 0x5802 and 0x5801 flags) and, as I say, it works perfectly when just sitting on dashboard. I've even went as far as to add the "0" and "6" privileges to my xex.xml (inspired by FreestyleDash's source) - I'm not sure what these do but applied them in a last ditch effort in copying existent sources. I've come to the conclusion that some other work is involved in order to make the socket server persistent upon game loading (perhaps some kind of hook or further undocumented flags or system priority trickery). If I look at xbWatson, when a game title is launched, it says "Xbox is restarting" and I think something must be done in order to allow the bound socket (and port) to remain active once a game title has loaded. This seems like a long shot but if anyone happens to know precisely how one can get around this, I'd really appreciate to know. Similarly, if any hoarders out there happen to have a copy of nateleroux's XBDM (the one that was removed from GitHub a number of years ago) that would be equally as helpful (I've reversed various bits of it and verified that it does set the same undocumented flag etc. - but nothing I've found strikes me as a solution). Any help is much appreciated, thank you.
  • Create New...