ANSWERED Jrunner's Dashlaunch and xeBuild Settings

[Spid3rCyd3]

I've been doing homework on the various options prior to building an image, was just curious, what settings do you guys personally use when making a RGH, or Jtag image, or do you go the default route? Trying to mix and match to come up with the best setup. I'd like to be able to FTP, but I don't even want to plug in a cat5 due to reports of some consoles still trying to reach out.

 

[printf(howdy)]

Mine -

[QuickLaunchButtons]
Default = Usb:\FS3\default.xex
BUT_X = Usb:\Apps\XeXMenu\default.xex
BUT_Y = Usb:\


[Settings]
pingpatch = true
contpatch = true
fatalreboot = true
regionspoof = true
dvdexitdash = true
xblaexitdash = true
fatalfreeze = false
nxemini = true
liveblock=true
remotenxe=true

 

[webnomix]

[QuickLaunchButtons]
Default = hdd:\freestyle\default.xex
fakeanim = hdd:\fakeanim\fakeanim.xex
BUT_X = hdd:\Apps\XeXMenu\default.xex
BUT_Y = hdd:\


[Settings]
pingpatch = true
contpatch = true
fatalreboot = true
regionspoof = true
dvdexitdash = true
xblaexitdash = true
fatalfreeze = false
nxemini = true
liveblock=true
remotenxe=true

Even though I use liveblock I always disable live in the family settings. I also heard about live trying to reach out (don't know how valid) but I have always done it, and I cant see that it hurts - better safe... etc.:cool2:

 

[Spid3rCyd3]

Thanks guys, good info. I guess...at least from the mouse over message in jrunner, liveblock is always on, even if the option isn't checked? It would make sense though. Definitely better safe.

 

[webnomix]

I have heard of people keeping the box on an isolated ip range etc, but frankly if you have disabled in family settings and run live block then you couldn't be doing much more to protect yourself, other that wrapping your console in a prophylactic - and that would cause a heat issue

If you don't plug in your network cable then you miss out on all the good stuff. Remote management, covers, updates TU's etc.