Print

[total_ass]

yes but that is just as potentially dangerous as changing the game region for the UDE2 is it not. that's why the UXE was invented, to avoid any eeprom modifications.

i mean if your exploit screws up then you gotta problem

[krayzie]

I'm not saying everybody should hose their eeproms. I just experimented with possibilities. if something get's messed up I could always restore my hd anyway. Also I'm goin to flash back my original eeprom cuz I like the ability to run my exploited save. This was just some testing to see if retail games can be kept from loading prior to nkpatcher.

[total_ass]

ok

but there's no worries at the moment as retail games remain harmless. and when they do become potentially harmful, the user could just simply wait for the exploit to load along with nkpatcher. though this is an unlikely future. let me check it out

*travels to future*

*returns to present*

i don't think we have much to worry about. (damn PS5!!!!)

[krayzie]

they could do harm since some games connect to live without notifying resulting in xbox live banning for modified xboxdash files.
Also UXE was found and not invented. If it wasn't found everybody would still be switching regions.

[total_ass]

ok good point.

me's glad my xbox isn't hooked up to the net. though i lose the ability to stream music, videos, browse the net and play system link. i don't care about LIVE.

LIVE is overrated anyhow.

[RiceCake]

EEPROM shadowing also does provide some security against Xbox Live.

You could use a fake EEPROM for your shadow, so that your real serial, HDD-key, and LiveID aren't given to servers.

The real EEPROM can still be grabbed through direct IO access though...and edited the same way. %99 of Xbox programs should use the kernel method and won't mess up your Xbox if you have it shadowed.

Linux based Xbox programs though don't use the kernel method - because its all supposed to be legal.

Anything else should be blocked because shadowing prevents the kernel method, but better safe than sorry.

[big ben bullet]

QUOTE

You could use a fake EEPROM for your shadow, so that your real serial, HDD-key, and LiveID aren't given to servers.

--<potential though very unlikely>--
If everybody would start doing this, there's bound to be someone 'innocent' banned from Live (a modder would eventually take the same 'virtual eeprom' of some unknowing retail user's real eeprom)... when more and more of these innocent people get banned, MS will be forced to remove the check

[krayzie]

if i'm not mistaken. as long as the shadow eeprom is active the xblive blocking is active too.

[DaddyJ]

QUOTE(Atreyu @ Dec 31 2004, 12:56 PM)

is there a way to get NKPATCHER to look for other files to boot, like a bios does

[cafu09]

vibe i'm kinda in the same boat man
i'm usin Avalaunch as my main dash bootin from shadowc i guess
when i ftp to it, can't seem to send anyfiles, i'm jus tryin to up date my skins.
when it boots up none of my settings is save if i make any change?

IF i boot with MA and connect to my real C:\ that way i can add file and stuff
then when i reboot with shodowc  my files don't show up

so how do we update or make changes to shadowc?

[RiceCake]

Want to edit your shadow drive? Boot with drive shadowing enabled and then add files to C. Since shadowing is enabled to a file, the files you write to C will then be put on this file, and show up in your shadow drive.

As for EEPROM shadowing, no it doesn't get enabled with Xbox Live blocking (Its all separate in the config files, avalaible before you assemble it).

Of course XBox Live blocking ain't perfect, and neither is a fake EEPROM shadow, but all I know is I've taken an old Pixel8 blank EEPROM to use as my shadow...

[rmenhal]

QUOTE(cafu09 @ Jan 1 2005, 12:22 PM)

not sure if it had something to do with me add a bigger drive with xboxhdm
i softmod the stock drive with uxe+nkpatcher10, set up shadowc, all works,
then i jus made a back of c:\  and use that to  set up the bigger drive, and it boots jus can't edit i it,

It's an xbox-linux bug: http://forums.xbox-s...dpost&p=2103192

What you could do is either boot nkpatcher without shadow C support or boot PBL with some other bios, then copy your shadowc.img file temporarily to some other drive than it is now, delete your current shadowc.img, then copy it back. Either that or format the drive where your shadowc.img is now and do it all again (be careful!). Note that formatting the shadow drive won't help, it's the shadowc.img file that is broken.

Don't use Linux to do any of this, because it creates broken files as explained in the linked post.

[Pojokunam]

Am I correct in thinking that nkpatcher10 will only patch the original MS kernel and I can't just put it on my softmodded xbox that is using an older version of nkpatcher and then run it to update nkpatcher to version 10?

[krayzie]

QUOTE(Pojokunam @ Jan 1 2005, 07:17 PM)

Am I correct in thinking that nkpatcher10 will only patch the original MS kernel and I can't just put it on my softmodded xbox that is using an older version of nkpatcher and then run it to update nkpatcher to version 10?

[Pojokunam]

So I installed nkpatcher-67 and it loads everything fine and I finally have IGR but my xbox still isn't showing my 200GB Western Digital HDD. I used xbhdm to format and I think that the problem may be that my computer's bios doesn't support 137+GB b/c I have the intel 845G mobo. Can I use software that is loaded on myxbox, or somethign built into evox to format my F drive to take up the rest of the HDD?