Print

[rocky5]

Mine was all working fine till this afternoon then error 1033 (sync and eject button) have to send it off to get fixed as i don't have the stuff to flash the nand (outside of the 360 software solutions).

i flashed with flash360 and i got the error ... Zeropaired kv so any one else have this problem.

the xbox worked all morning so haven't a bloody clue lol

[soulwarrior]

QUOTE(dufc1983 @ May 23 2010, 04:41 PM)

when using flash installer i get error opening GAME:\launch.ini for read
did not open GAME:\launch.ini for read, error 2

everything is were it should be any ideas?

It's because you didn't have the ini file in the flash installer folder when you ran the program. You don't need to have there as long as you have your ini file in the root of your hdd/usb/memory card

[dufc1983]

QUOTE(soulwarrior @ May 23 2010, 10:02 PM)

It's because you didn't have the ini file in the flash installer folder when you ran the program. You don't need to have there as long as you have your ini file in the root of your hdd/usb/memory card

yeah only just noticed luckily i did put it on root of hhd and its working perfectly none of this pressing rb or rt bla bla it just works pressing yellow button

[dryan433]

QUOTE(ZprivateZ @ May 23 2010, 04:48 AM)

Can someone please explain this to me

- with the included patch set, launch.xex acts as a helper to detect when
    xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator
    to function together.

Does it mean memory unlock is always there except when you launch an xbox1 title then it knows to switch to xbox1 emulator?

yes this is what the read me say so you can have it patched for system mem hacks and still be able to run xbox1 emu as it suppose to be able to detect when you run xbox1 mode if I'm correct please correct me

[cory1492]

QUOTE(DarkProphecy @ May 23 2010, 11:08 AM)

I guess it works on xb1 games, it just doesn't work sometimes. I never have a disc in the ODD, so I can't say why. Can it have 'activity' if there's no disc in the drive?

There are some random/fluke things that can mess it up, but it's pretty rare (mostly ODD disk related, but in some cases not) and seems it's not possible to reproduce on a machine that doesn't have the issue to begin with. Most people aren't having issues, the ones that can be reproduced will be solved, and either way the code is there for anyone who has run into NXE when they shouldn't to try and tinker a bit.

pulz:
it was a omission in the nfo on #1, you still have to install launch.xex to flash before it will work.

garus:
Ah, you are right, it does seem to work from USB. You can try pointing it at the freestyle-usb USB CON instead, also be sure you have the path correct (if you have multiple usb devices you will probably have to try each of the usb#'s) all I have for usb drives here is a 2G data traveler and everything seems to work great from there. I've even used it to launch xexmenu con in USB MU created by the new MU thing for 9199 on this same card.

launch.ini (on usb device so it overrides my flash one, since I disconnected the HDD) - as I have only one usb drive hooked to the machine, I know I can safely use Lusb0 and have it work.

CODE

[QuickLaunchButtons]
BUT_X = LHdd:\Freestyle\FreestyleDash.xex
BUT_Y = LMuu0:\Content\0000000000000000\00000001\00080000\000000010F586558
LBump = LHdd:\Freestyle\FreestyleDash.xex
Default = LUsb0:\Freestyle\FreestyleDash.xex

[plugins]
plugin1 =
plugin2 =
plugin3 =
plugin4 =

output in cygnos toolbox:

CODE

Booting....
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Harddisk0\Partition1 to LHdd: sta:Success
launch.xex: mount \Device\Mass0PartitionFile\Storage\ to LMuu0: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: mount \Device\Harddisk0\Partition1 to LHdd: sta:Success
launch.xex: mount \Device\Mass0 to LUsb0: sta:Success
launch.xex: launch LUsb0:\Freestyle\FreestyleDash.xex
[t:XEX2]
[dv:LUsb0:]

(note that symbolic links can be successfully created for devices that don't exist but have kernel driver objects registered.)
Hope that helps some?

[Lisko]

Me again. If I boot in xexmenu all works well. If I boot in FSD 1.20 the hooking doesn't work, it returns to NXE. But if I eject the tray while playing it reboots into FSD. Why using miniblades won't work?

[dufc1983]

QUOTE(Lisko @ May 24 2010, 10:07 AM)

Me again. If I boot in xexmenu all works well. If I boot in FSD 1.20 the hooking doesn't work, it returns to NXE. But if I eject the tray while playing it reboots into FSD. Why using miniblades won't work?

you have to hold rt then press y as normal should work

[kettenschutz]

hi there again
it seems like i finally got the flash right
freestyle is booting up fine, flashed launch.ini into nand

if i now power on my box and hold a,b,y or y button the box just reboots and starts in nxe after that
if i didnt press any button, fsd boots fine

if i press the guide in freestyle, then y and then "yes" after that holding a,b,x or y then happens nothing

some ideas ? :-/

[Sonic-NKT]

Xexmenu is your Default in launch.ini? maybe try setting FSD the default and see what happens then

PS: you have to press RB and Y in the miniblade, and it will bring you back to NXE! Read the Readme correctly.

[Lisko]

QUOTE(Sonic-NKT @ May 24 2010, 01:12 PM)

Xexmenu is your Default in launch.ini? maybe try setting FSD the default and see what happens then

PS: you have to press RB and Y in the miniblade, and it will bring you back to NXE! Read the Readme correctly.

If Xexmenu is the default item all goes well. If FSD 1.20 pressing y in the miniblade will return to NXE. To return to FSD I have to open-close tray. I don't understand why xexmenu works and FSD not....

[dustin6908]

i never get nothing but nxe ive tried launch.ini on usb0 hdd1 and flash
launch.xex flashed to flash

my ini looks like this

Default = LHdd:\Freestyle\FreestyleDash.xex;


old dash lounch worked .01 and .02

cant get this one to work

i got my image the same way i built my org freeboot .032 one except i changed out the patches file.
It was build with wasy freebooot 2 and everything thing else but works

any ideas?

[ZprivateZ]

QUOTE(dustin6908 @ May 24 2010, 01:23 PM)

i never get nothing but nxe ive tried launch.ini on usb0 hdd1 and flash
launch.xex flashed to flash

my ini looks like this

Default = LHdd:\Freestyle\FreestyleDash.xex;
old dash lounch worked .01 and .02

cant get this one to work

i got my image the same way i built my org freeboot .032 one except i changed out the patches file.
It was build with wasy freebooot 2 and everything thing else but works

any ideas?

Try taking the ; out of your default line behind FreestyleDash.xex

[Midnight Tboy]

Hiya,

Yesterday, I just finally updated my Xell XBR3 xenon.....first to Xellous, and then (with an E72 problem - sorted afterwards) to Freeboot v0.32 using FreeBoot ToolBox Maker v2.3.

can I ask.....

I read this bit

"- with the included patch set, launch.xex acts as a helper to detect when
    xbox1 emulator loads, allowing memory unlock patch and xbox1 emulator
    to function together
"

I'm trying to work out what that means exactly?

Does it mean we no longer have to set in the Freeboot Toolbox Maker, between "Maintain Xbox 1 Emulator Functionality" and "Full Memory Access (RAM)"?

Also......Is there a way to find out which option I chose by dumping the nand again or any other means?  I was meaning to choose the Full Memory Access, but after having to reload the app and try again cannot remember if I did set it the 2nd time round as it defaults to the xb1.

[dustin6908]

QUOTE(ZprivateZ @ May 24 2010, 07:12 PM)

Try taking the ; out of your default line behind FreestyleDash.xex

still not working
just nxe over and over

no disc in drive at all

any more ideas?
i got a zephyr 4558 if that matters

[p4r0l3]

Same problem here, applied the patches to freeboot, placed launch.ini (and launch.xex) at root of hdd.

Always goes to NXE so I tried installing xex/ini to flash, said it was a success. However, still the same behavior.

Any ideas? Falcon box here