QUOTE (douceur @ Dec 10 2003, 09:34 PM)

Just out of curiousity, though, how are you planning to implement this? I mean, as some sort of option or what?

XBtool patch would be the easiest, of course

anything new?

QUOTE (smo @ Dec 10 2003, 01:16 PM)

I've written some pseudo-code and now I'm trying to figure out exactly how to patch the BIOS. I've got most of the points I need to work with identified and figured out, but as always, other work is getting priority over this. Patience

HAHA pseudo code, my sister can do that!!!

Sorry I'm drunk....

QUOTE (rjsachse @ Nov 28 2003, 02:21 AM)

ok ok ok ok well i have been reading around and read that if you save your xbox live account on the memory card and delete it of the hdd so you have to put in the memory card to go on live. Well there i said it

This is what I would do for now.

Interesting and good work on trying to figure this out for the bios.

it seems dvd2xbox 0.5.2 can patch files directly using acl control lists, hence applying smo's patch

QUOTE

dvd2xbox 0.5.2 * added: Action Control List (beta). Now you're able to control the post processing for each title using the dvd2xbox.acl file and the titleID. if it doesn't work for you or you do not like it set enableACL to 0 and standard patching is used. Currently acl supports four commands: SetMediaType,HexReplace,CopyFile and RemoveDir/File (see dvd2xbox.acl for more informations and the syntax). The acl list can only grow with the help of the community. Test it, add new entries and write me if you need new commands or to fix existing ones. from acl file: HexReplace: HR|*.xbe|1|E8CAFDFFFF85C0EB|E8CAFDFFFF85C07D| Searches all xbe's for E8CAFDFFFF85C0EB and replace the first occurrence by E8CAFDFFFF85C07D.

is this correct?

CODE

HR|default.xbe|1|A801750CC74|90909090C745|

while we wait for a bios patch we could use this method

Well this is my first post here, but here goes... My Xbox will show up Tuesday, so I have been educating myself.

The way to do this that makes sense to me is to just use routing to correct the issue. It would be easy to add to a dash the ability to use different IPs based on what bios is loaded. Force a non-routable IP when loaded in hacked mode, and allow a routable IP/DHCP when loading for live. You can make the ip non-routable by blocking it at your router easily.

If you don't have a router, it would be dangerous to choose an IP in the same subnet as your PCs. Because you might randomly end up hitting a valid one. The option then is to go to a new subnet, and use a private ip block like 10.0.0.x. Of course if you want your pc to be on the net and connect to the Xbox at once, you would have to put a second NIC in it and configure it for the Xbox's subnet.

The coding is easy, and the worst case cost is an extra NIC.

The prev post got me thinking, how does live games call home?

Do they rely on DNS to resolve the address?

I doubt the games are hardcoded with static ip, so what if we just set our xbox with invalid dns servers? It won't be able to resolve the address the games need to connect out.

Of cos we will need to use ip addresses for xbconnect as a consequence.

Setting a bad gateway should stop an internet connection as well. Is there an easy way to use a different gatway for which bios u boot too.... For people who boot one for live and one not for live?

auh... this might not be possible but couldnt you just have a seporate ms dash that you can get through your modded dash? Like have your ms dash link point to one without xblive installed or would that screw things up? just an idea

How about a bios that launches a firewall xbe/dash that blocks the live port ranges.

QUOTE (Moleman @ Dec 22 2003, 02:14 PM)

How about a bios that launches a firewall xbe/dash that blocks the live port ranges.

That would be great, because MS could change the code all they want and it would still work. just allow xlink and system link traffic through!

another solution (approved by me) : my mod bios do not load default.xbe but bootxbe.xbe on my dvd-drive

So i can't load any original game with my bios on (even if i forget an original in the tray)

-for an original game (especially live enable one) i change the swith my modchip position to off

-for a backup i modify the iso (put bootxbe instead of default), or i have the evox shortcuts.

i also add a d:default.xbe shortcut in my evox (with a double warning screen), if needed.

the only problem, is for backup of "live aware games", so i buy them !!!

QUOTE (...ReLLiK @ Dec 24 2003, 03:30 PM)

QUOTE (Moleman @ Dec 22 2003, 02:14 PM) How about a bios that launches a firewall xbe/dash that blocks the live port ranges. That would be great, because MS could change the code all they want and it would still work. just allow xlink and system link traffic through!

Yeah, it would be great.

IF IT WERE POSSIBLE, WHICH IT IS NOT! SO STOP FREAKING ASKING!

This sort of stuff has been covered ad fucking infinitum in the BIOS Hacks Suggestions thread.

Well, you know how evox has IGR, right? Well I was thinking, however it made IGR work inside of a game it would have a mini-firewall. Windows XP does it. But then we get into multitasking. Doh!

It's not impossible. Everyone said that it was impossible to have a harddrive larger than 120GB in an XBox be cause of LBA28s limitations, but someone hacked that and got it working right?! Well, whatever...

QUOTE (ivc @ Dec 17 2003, 04:53 PM)

it seems dvd2xbox 0.5.2 can patch files directly using acl control lists, hence applying smo's patch is this correct? QUOTE HR|default.xbe|1|A801750CC745|90909090C745| while we wait for a bios patch we could use this method

ivc,

Slight fix; missed the "5" at the end of the search string.

I just tested this idea with adding this to dvd2xbox's acl list. It worked while backing up Unreal Championship. Made sure my network cable was still pluged in, and made sure to test on my xbox that can access XBLive. It gave me a cannot connect error.

Just for info's sake, I used "dvd2xbox 0.5.2 tc1"

Now to see if this acl thing works nicely with my game file deletions...

QUOTE (DCarnage @ Dec 28 2003, 11:49 PM)

It's not impossible.  Everyone said that it was impossible to have a harddrive larger than 120GB in an XBox be cause of LBA28s limitations, but someone hacked that and got it working right?!  Well, whatever...

Everyone thinks it's impossible to live without an oxygen supply to your brain. I guess you've also demonstrated that this isn't true.

It has been explained *MANY* times over and over again as to why this would be unfeasible, if not downright impossible. I'll leave it as an exercise to you to pull your own head out of your ass and go read.

You sound like that retard that wanted to run his PS2 copy of SSX3 on his Xbox...

QUOTE (DCarnage @ Dec 28 2003, 11:49 PM)

Well, you know how evox has IGR, right? Well I was thinking, however it made IGR work inside of a game it would have a mini-firewall. Windows XP does it. But then we get into multitasking. Doh!

That's part of the problem right there.

There is a *huge* difference between setting extra BIOS interrupts (IGR) and embedding an XBE.

I didn't fiddle around at all with the whole X2-embedded-FTP-server, but if memory serves, it only runs if you hold A on boot, and then, it runs as a standalone application, and *not* as a background service.

Wow, do you still live with your parents? #1 I'm not an idiot. #2 I never put you down in any way. #3 It is possible, but it would be very difficult.

When I say, "It is possible" that means if a person spent enough time backward engineering the bios and rebuild it, it can be possible. Or even if they wrote their own. <-- very very very difficult, but NEVER impossible. There are no hardware limitations for doing what everyone has suggested in this thread.

Peace

No one, as of yet, has found a way to run two programs at one time on the xbox... That means, an xbe firewall is out of the question unless you want to come up with a way yourself to run two programs at one time (outside of linux.) It's possible to run WindowsCE now on your xbox (with problems) and everyone said it couldn't be done... That means that eventually, theoretically, you could run Windows XP/98/ME. The easiest option you have is to run the dvd2xbox acl string to stop the "known" live checking string. If this hex value makes it into a bios, (and it could) then that would stop ALL games using that string from connecting to xbox live... The problem therein lies with M$ Dashboard updates... a future dash could (possibly) allow for a secondary call, but it would still have to allow the one used now, otherwise all the current Xboxlive games would not be able to go live anymore. This seams unreasonable because the only reason M$ would do this is to purposefully ban people for modding... Wouldn't put it past them, but come on... this isn't a conspiracy. Has anyone tested this hex replacement to see if it allows system link? I'd rather take the risk of losing live to be able to play system link. and lastly... I set my xbox live account up to use a password (button sequence) the day I activated it. No game that I've played so far has EVER connected to live without asking me for this password. If I "accidently" activate live AND put in my password while the switch is on, then I'm just a freaking retard. (This has not been tested with ALL Live Aware games, but Prince of Persia didn't connect without password.)

Summary:

1. Xbox Live blocking CAN be enabled through the BIOS, but you would need someone with knowledge of how the BIOS is compiled and edited to do that.

2. Put a password on your Live account... It helps!!!

3. UnleashX is the best dash to date.

Just thought I would mention that if you backup your Live account to a memory card, and then delete the account from your Xbox, your Xbox will NEVER connect to Live in a manner that could ban your account, and you just need to plug in the memory card to play on Live. A solution I figured out months ago when Live 2.0 came out, but nobody seemed to take seriously.

And yes, I have tested.

And btw, I have Live 2.0, run Live-Aware games all the time, and have even clicked on Live tabs in games and the dashboard while mod-chip was on (for testing purposes). I have been doing it for months now, and I am still not banned, so ....

As with BrienJ, I have been using my acct on a memory card with no problems either. I have also been doing this for several months and have posted this in the forums somewhere once ago.
Did you all notice xbox live! may be disabled in the new X2 bios?? I bet they are incorporating the hex idea....

I have no problem the way it works for me now, but I would like to have this in bios for my nephews' xbox! That way they can get live! and not render the xbox live useless on accident! After all, they are not old enuff to know better!

QUOTE (...ReLLiK @ Jan 2 2004, 02:53 PM)

As with BrienJ, I have been using my acct on a memory card with no problems either. I have also been doing this for several months and have posted this in the forums somewhere once ago. Did you all notice xbox live! may be disabled in the new X2 bios?? I bet they are incorporating the hex idea.... I have no problem the way it works for me now, but I would like to have this in bios for my nephews' xbox! That way they can get live! and not render the xbox live useless on accident! After all, they are not old enuff to know better!

Nice to see another intelligent individual on the boards, and thanks for hopefully stopping the "No, that can't be true" and "but what if, ..." posts.

According to Executor's post (the one referenced on xbox-scene's main page today) the new X2 bios's strategy *is* based on smo's findings in this thread!

http://www.teamxecuter.com/modules.php?nam...c&p=32574#32574
(free registration required)

Sounds pretty cool, huh? That will be a relief for those of us paranoid about getting banned from XBL.


In the meantime, I'm pretty pleased with a little hack I've just devised tonight. I fashioned a handy little Network A/B Switch box that allows me to turn the ethernet connectivity on or off. My Xbox is in a tight little shelf, and constantly pulling it out to unplug the ethernet cable was becoming a drag. Now I can easily turn it on or off with the turn of a dial. My Xbox gets to stay put. Yeah, I'm pretty pleased with my handiwork.

The BIOS Live-disable would work exactly the same as the no patch hack and no patch hack2 works. It just patches the XBE in memory. Why do you guys think this would be difficult (never mind impossible)?

How I have mine setup currently is I have modified the BIOS so that when I boot up with the chip on the LED is Red as is the Xbox Logo. Also I have messed with the .xbe file the BIOS looks for on the CD/DVD Rom (just called it asdfasfafa.xbe or whatever) so that with the chip on it will not boot straight from the CD/DVD. This is enough to make me realise I have the chip on as to boot any game from EvoX I have to tell EvoX to boot from the CD.

It's not perfect but it's working fine so far. I may get myself a memory card and transfer my Live! Account to that though - sounds like a good idea.

btw, seems like xecuter is testing a bios with live disabling

QUOTE

... however a new x2 bios being finished now disables live so you will not have an accidental connection.

Original forum post (seems to be down atm)

and its out...
(unpinning)

Can't wait to hear Curtiss' reply as to why it's not possible now

LOL.
Good work on this subject to SMO, Shadow_MX, Psilocybe, Leftyfb & MaDgamEr especially!

Great work by SMO and the executer team.

However, I would like to state that NO GAME WHATSOEVER, including live aware games, will connect
automatically to live if you just follow simple rules:

1) disable autologon from your dash
2) pasword-protect your xbl-account
3) for added security, play live-aware backups using a different profile (account) name as your xbl-account
4) only access your msdash with modchip off (switches)

I never unplug my networkcable and have had dozens of live (-aware) games on my HD (including RBS and PGR2) and never ever had any problems with live. whenever I am gonna play live I just switch the chip off and insert the original gamedisc. I play RBS singleplayer off the HD while online I play it with the chip off and original disc.
Also, my neighbour once selected xbox live from the multiplayer menu in PGR2 while playing it from the HD. He got a nice password prompt and not knowing the pass, he backed out. No connection to live was made and no banning occured.

To conclude, this new bios hack is great stuff, it prevent accidents. But stop being paranoid or spread untrue stories about xbl aware games connecting no matter what. Those stories are just plain horse shit

QUOTE (openwindow @ Jan 5 2004, 05:26 AM)

Can't wait to hear Curtiss' reply as to why it's not possible now

Way to stuff words in my mouth.

I said that FIREWALLING Xbox Live in the BIOS was impossible.

Implementing smo's hack (which I said a ways back was quite clever) in the BIOS is entirely different.

Yea Cutriss is still correct, the bios does not firewall XBOX live, rather it hacks the memory on-the-fly to make it seem as if the ethernet cable was not plugged in.

Thanks for the backup, AsTnBoMb. :-)

And for the record, I am running smo's hack in dvd2xbox, as I prefer doing it that way as opposed to running a newer version than 4977. Props to the X2 guys, definitely, but I like 4977, and the only way I'm gonna change it anytime soon is if I patch in the LBA48 hack. :-)

Sorry openwindow, but cutriss is correct. He was talking about putting a firewall in a bios.

Mea Culpa, Mea Culpa, you are right. Sorry bout that.

QUOTE (openwindow @ Jan 7 2004, 03:45 AM)

Mea Culpa, Mea Culpa, you are right. Sorry bout that.

No prob. Thanks for the apology...that's rare on the Intarweb these days.

hmm.. Anyone knows actually what the xb live ip ranges are? Came looking here for those so that i could filter them away, .

Really fellas, some of you must be quite stupid, i mean, why over and over propose that the live filtering should be done on the xb level?
I think that most of you have a small network at home, i mean, not many of you pay for internet acess just to plug your xb into the wall.

Soo. I belive that the best option is to let your local packet router handle the droppings and take the pressure off our pros and let them develop something more useful than a hardware filter for the fellas with no network experience or what so ever.

I'll happily write you a tutorial on how to filter out ip-addresses and ranges on both *nix and windos systems; if you have a regular pc as a router that is. (supposly that i can find the ip ranges without needing to unplug my net cable and put up a sniffer to figure it out.)

And if you have one of those hardware routers doing the job for ya, then you should do what you should have done instead of comeing up with such a stupid idea as a button sequence:
Read The Fucking Manual!

Xecuter has already developed a BIOS that addresses this issue based upon Smo's original concept.

The issue was not that people did not know how to deal with a router. It was adding a second step besides switching a mod on/off since you'd have to unblock the IP again. Plus - backing up a Live aware game and accidentally hitting a button was becoming a problem for people. There's a thousand ways to get around something but the new bios is by far the most elegant and foolproof solution.

I think I got a better way of disabling Live connectivity - for dashboards updates etc:

Patch hex string "24 01 F6 D8 1B C0 23 C6" to "24 00 F6 D8 1B C0 23 C6".

This is untested, but I verified its existence in couple of XBEs (including update.xbe). Someone willing to test this?

Okay, so if the first one disabled the call to a function that checked for a cable, yet didn't prevent the dashupdate from working then apparently dashupdate never called that function so disabling the function or the call to it wouldn't make a difference...

Right?

or am I thinking of this wrong?

Basically i'm thinking to block dashupdate you'd have to block the function it uses after the function that checks for a cable cause it seems dashupdate just tries that without ever checking for a cable plugged in...