Topic: Krayzie Ndure Installer (Gamesave Style) (Read 5640 times)

JMPovoa · « **Reply #150 on:** August 21, 2005, 05:41:00 PM »

There's one thing I'm confused about:

After installing this softmod when I turn my xbox on with the eject button it's supposedly in retail state right? So how come it loads unleash X (and the led still stays green)?

brick0044 · « **Reply #151 on:** August 21, 2005, 05:51:00 PM »

you have to boot to the game again and then in the extras tab choose the top option

ephesith · « **Reply #152 on:** August 21, 2005, 06:05:00 PM »

Or, you have to wait for the box to boot up totally by pushing the eject button. If you turn your box on with the eject button you cant hit the button again (close it) until it boots totally to "stock" state.

Cio · « **Reply #153 on:** August 22, 2005, 07:48:00 AM »

The tray state (ejected or closed) determines whether you get a retail kernel (open -> M$dash) or patched kernel (closed -> modded dash) when the exploit is loaded off the HD (thus, right after it tries to run xboxdash.xbe) and not on the actual power on

JMPovoa · « **Reply #154 on:** August 22, 2005, 02:46:00 PM »

I am aware of that, and that's why I got confused...

I leave the tray open until my Xbox fully boots, and it loads Unleash X and the LED stays GREEN, thus leading me to believe it's in a not-modded state... but it can't be, since it just loaded Unleash X, right? Maybe I have to do what brick0044 said... But I thought this dual-boot option was selected by default (I have not changed it after installing the mod)

Horscht · « **Reply #155 on:** August 22, 2005, 03:26:00 PM »

No, it's not enabled by default. You have to install it "manualy" (pretty bad word, as it's basicaly automated). Run your exploited game, select the savegame, then you go to the extras menu and instal dualboot.

JMPovoa · « **Reply #156 on:** August 22, 2005, 03:55:00 PM »

Oh ok. Good.

So is it a "bug" of some sort in the installer, that the LED stays green instead of turning orange?

DaddyJ · « **Reply #157 on:** August 22, 2005, 05:14:00 PM »

QUOTE(JMPovoa @ Aug 22 2005, 05:30 PM)

Oh ok. Good.

So is it a "bug" of some sort in the installer, that the LED stays green instead of turning orange?

not bug,
option

my_darxide · « **Reply #158 on:** August 22, 2005, 11:20:00 PM »

ok im gonna sound like a noob. i ran the installer and everything installed just fine but when it rebooted and setup shadow C it came up w/ an error (112 i think) evox boots and works fine but i cannot access the M$ dash from evox. also when i look @ the c dirve w/ xcommander c drive is blank. what can i do to fix this? i dont care bout XBL by the way i just want to access my M$ dash and have it in the "right" place

Nonny · « **Reply #159 on:** August 23, 2005, 02:00:00 AM »

Ok first off... great installer!

Had used your UXE installer before and I am continually impressed. Easy to install, informative readme and step by step info.

Which leads me to a (most likely stupid) question.

I've installed dual-boot to retail so now when I press eject it boots with green LED into the MS dashboard and in the readme it says its safe for XBL. As yet I havent ventured back onto XBL through this method but I've read previous posts that state downloading updates and accessing the Xbox LIVE menu / Friends list is not possible in this state.

With that in mind what exactly does safe for XBL mean? Can you go ahead and play retail games over XBL as normal without any risk of being banned (I realise there is always some risk)...

I guess your readme statement about this can be interpreted many ways and I am a bit confused... and not the only one it seems.

Cheers.

Ndure protagonist · « **Reply #160 on:** August 23, 2005, 10:54:00 AM »

Downloading game updates works with the Ndure 'retail' and 'fonts' setups (whereas it doesn't with UXE, UDE2, UDE and other font exploits).

Re. Ndure 'retail' being safe on XBL ... the MS kernel is left in memory (it's unhacked) so it complies with live's "unmodded bios" mandate.

triggernum5 · « **Reply #161 on:** August 23, 2005, 09:08:00 PM »

The patchback idea, while being a really cool proof of concept seems a little bit shady to me.. Don't get me wrong, at this point in time, I doubt M$ is focusing on that (unless it happens to fall into one of their proof of concepts for the 360).. It boots msxboxdash.xbe.. Although the kernel segment is patched back, the memory somewhere has to be poked to launch that file.. An M$ update could peek at memory I'm pretty sure.. (triggernum5 --> Far from an asm guru)

Correction: Proofs of concept*

Ndure protagonist · « **Reply #162 on:** August 24, 2005, 09:13:00 AM »

triggernum5, to get on XBL from the MS dashboard an original disc would have been warm-booted (via the kernel) in the regular, retail manner.

Consequently, the current executable's details in memory will be for the default.xbe (as normal).

scienide · « **Reply #163 on:** August 24, 2005, 09:33:00 AM »

QUOTE(my_darxide @ Aug 23 2005, 06:55 AM)

ok im gonna sound like a noob. i ran the installer and everything installed just fine but when it rebooted and setup shadow C it came up w/ an error (112 i think) evox boots and works fine but i cannot access the M$ dash from evox. also when i look @ the c dirve w/ xcommander c drive is blank. what can i do to fix this? i dont care bout XBL by the way i just want to access my M$ dash and have it in the "right" place

The C drive is a virtual C drive.... build from an image...

Boot to evox, and upload the files u need to the virtual C ...

U could just upload the original content of the C drive...

With kind regards
Marco

quadriko · « **Reply #164 on:** August 24, 2005, 10:23:00 AM »

tnx a ton dr oldschool!
btw, i'm slightly confused, does Ndure need the xonlinedash.xbe from the 4920 dash, or the 5960 dash?

Author Topic: Krayzie Ndure Installer (Gamesave Style) (Read 5640 times)