deaphroat

quand les disque dur Xbox fesait 60Go on pouvait mettre un 500Go...maintenant que les 320Go existe (même avec les 60.....) pourquoi les 1000Go serait pas compatible? (si on veut perdre 700GO)

Comment tu as fait pour faire disparaitre le message "Plugin update needed to connect" ? j'ai pas rallumer depuis, ca disparait tout seul?

Mise à jour en 0.9.1, merci.

ca sera juste bien pour ceux qui n'ont pas de 3Ds, sinon oui c'est une copie plus ou moins conforme (un montre du bestiaire en plus....)

Bonjour Maj sans problème : Mais le mot de passe de la WebUi a changé : Dans paramètre plugin, il faut activer LINK :

Article obsolète, merci de continuer la discussion ici : Freestyle Dashboard 3 Beta Rev 735

Article obsolète, merci de continuer la discussion ici : Freestyle Dashboard 3 Beta Rev 735

Resident Evil Revelations : Trailer du mode Infernal Capcom dévoile un nouveau trailer de Resident Evil Revelations pour présenter le mode Infernal. En plus d’une difficulté plus ardue, les ennemis sont plus présents qu’en mode normal et les objets sont placés différemment. La sortie du jeu est prévue pour le 24 mai. http://www.dailymotion.com/video/xxys47_resident-evil-revelations-infernal-gameplay-fr_videogames http://www.xboxygen.com/Medias/Videos-Xbox-360/Resident-Evil-Revelations-Trailer-du-mode-Infernal

Dead Space 4 annulé suite aux ventes du 3 ? Dead Space 3 est sorti il y a maintenant un mois mais les ventes ne sont pas à la hauteur des attentes chez Electronic Arts. Une suite était apparemment prévue mais a été annulée. Le projet Dead Space 4 était apparemment en pré-production chez Visceral Games, indique Videogamer. D’après leur source, un représentant d’EA est allé rencontrer les membres de l’équipe le mois dernier pour leur dire que le projet était arrêté et pour annoncer les détails d’une restructuration. Apparemment, le développement de Dead Space 3 ne s’est pas forcément bien passé et le jeu aurait subi plusieurs coupes budgétaires pendant la production. De même, EA aurait souhaité rendre ce troisième opus plus abordable pour une majorité de personnes, en se focalisant davantage sur l’action plutôt que la partie horreur. D’après la source, Visceral Montreal serait sur le point de fermer. http://www.xboxygen.com/Actualite-Xbox-360/Divers/Dead-Space-4-annule-suite-aux-ventes-du-3

Garde la non c'est pas mort... Demande à shakin

Sephi 2é fois précise quand tu parle de custom ca perd les gens Ben faut savoir les custom pour la bidouille c'est bien ou pas? (parce que linux ... ) Bref sur arch, il faut pas de patch JUSTE pour les jeux 4.31 ?

Bon ben ça ma permit d'apprendre que Eidos avait été racheté par Square Enix

ca s'adresse au personne avec console en dashboard officiel 15xxx+ pour récupérer la clé donc pas a toi

The Cobra ODE Team has just informed us today with a short news update on their progress and status, with more info and pictures to appear in a few days! March 4th, 2013 Release date is a little delayed since we're ironing out the last remaining bugs with the software and hardware in preparation for release. This has taken a longer than expected due to the extended range of consoles we support. Some pictures and further information about our hardware will follow over the next few days. Stay tuned for further info! http://www.ps3crunch.net/forum/threads/6741-Cobra-ODE-News-Status-Update

tu parle de phat la? sur slim il y a un port dedié, ca se branche pas dans un port usb et sur phat il faut un adaptateur ou un transfo je sais plus

faut pas mettre 2 Y.... +++++++++++++++++++++++++++isoMENU flag Y/N On/Off++++++++++++++++++++++++ MENUISO=N +++++++++++++++++++++++++++dvdMENU flag Y/N On/Off++++++++++++++++++++++++ MENUDVD=Y

Alors que le trailer officiel d'Assassins Creed 4 : Black Flag est prévu pour le 4 mars à 18h, Ubisoft est encore victime d'une fuite puisque la vidéo est déjà disponible sur la toile. Nous vous proposons une version encore disponible qui risque d'être supprimée vu que plusieurs vidéos de Youtube se sont retrouvées désactivées. Rendez-vous lundi à 18h pour retrouver la vidéo en français ainsi que les premières informations officielles ! http://www.dailymotion.com/video/xxwp50_assassin-s-creed-4-black-flag-trailer-fr_videogames?start=10 Comme nous sommes sous embargo jusqu’à lundi 18h, nous ne pouvons pas révéler des informations sur le jeu notamment le nom du héros. Mais le compte Twitter dUbisoft Press vient de confirmer son nom et on vous présente, donc, Edward Kenway ! Il n'aura pas fallu attendre longtemps avant d'avoir des nouvelles de la franchise. Cette fois exit les indiens d'Amérique, bienvenue dans le monde de la piraterie. - Le joueur incarne cette fois Edouard Kenway, le grand-père de Connor (héros de AC3). Laction se déroule en 1715 donc logiquement avant Assassins Creed 3 et le joueur possède un navire, le Jackdaw. C'est un élément central du jeu et il faudra l'améliorer au fil du jeu, ou même prendre soin de son équipage. - Barbe Noire sera présent, comme le laissait supposer limage leakée. Un autre personnage aura beaucoup d'importance, Calico Jack, un célèbre pirate qui était d'abord au service de l'Angleterre. - La carte des caraïbes leakée représente bien celle du jeu et comprendra 50 lieux uniques en faisant l'univers le plus varié de la série. On naviguera par exemple au port de La Havane, de Kingston, Nassau. On traversera également des villages de pêcheurs, des plantations, des criques cachées, des environnements dans la jungle, des forts, des ruines Maya... Le jeu est toujours de type monde ouvert et l'exploration sera encore plus importante. De nouveaux éléments de gameplay sont d'ailleurs là pour nous aider comme la longue vue. - Le jeu introduit également des phases de gameplay inédites, sous l'eau ou sur l'abordage des navires par exemple. - Un mode multijoueur est évidement toujours présent. - Date de sortie Fr : 31 octobre 2013 - Le jeu est prévu sur toutes les consoles, WiiU et PS4 comprise. - Trailer en français de l'annonce du jeu - Lire notre preview d'Assassins Creed 4 : Black Flag - Premières images - Trailer en français présentant Edward Kenway : http://www.dailymotion.com/video/xxxw0f_assassin-s-creed-4-black-flag-edward-kenway-un-pirate-entraine-par-les-assassins_videogames http://www.xboxygen.com

Day 7 Mortal Kombat $19.99 Mortal Kombat vs. DCU $4.99 Street Fighter IV $9.99 Street Fighter X Tekken$19.99 Super Streetfighter IV Arcade Edition $9.99 Tekken 6 $9.99 Tekken Tag Tournament 2 $19.99 The King of Fighters XIII $9.99

C'est quoi la rev de cette version? le download est à jour merci.

multiMAN 04.20.03 update is available online and in the WEB column. * Added support for 4.30DEX CFW (REBUG) (TBA) * Added support for PS1 BIN+CUE (using ps1_emu/netemu) for 3.55DEX, 4.21DEX and 4.30DEX * Added DynaRec support: New option in Settings "Enable DYNAREC" * DYNAREC support for 3.55CEX/DEX, 4.21CEX/DEX, 4.30CEX/DEX, 4.31CEX * Fixed few minor issues in 4x2 and 8x4 modes (refreshing the game title when insert/ejecting a PS3 game disc) * Fixed a very rare bug in mmOS when icon names/texts are getting corrupted DYNAREC support tested on 4.21REX and 4.30ROGERO with ps3sx_Beta.pkg which is enough to assume that the implementation is proper. Thanks to Ing. Pereira for the htab info and PeteUK for the testing. All offsets can be found in my source below so Ing. Pereira can port his app for other firmwares, too. Also there is an easier way to detect all CFW firmwares and I posted about it at the end of this post. ============================================= Here is a slightly modified PS3SX: * You can install it on any mM supported firmware (3.55CEX/DEX, 4.21CEX/DEX, 4.30CEX/DEX, 4.31CEX) * The configuration file is USRDIR/CF.ini * Comes with bios and all paths set properly where the default ROM path is /dev_hdd0/PSXISO * EBOOT.BIN calls RELOAD.SELF so you can boot PS3SX directly from multiMAN * It has VERY POOR compatibility but shows that dynarec is working on all firmwares. PS3SX [bETA].pkg (5.95MB) Download PS3SX [bETA].pkg from Sendspace.com - send big files the easy way You can enable DynaRec in mM's settings and directly load PS3SX from mM's GAME column. Thanks to aldostools for the cover. Developers can use this dynarec option in mM if they wish to test their apps in this environment. ============================================= The implementation in mM is different than IngPereira's approach, because it doesn't use the 0x700000 area for the payload and the patches, there are no issues with PKG files and works on all firmwares. Still the kammy data for the hvsc redirections is used, but dynarec's usage is greatly simplified by an "On/Off" option in mM. I'm just saying this because some morons will go again with their idiotic comments about copy/pasting. Parts of the mM code is here, along with info how to make it work on all firmwares. Dean It is as simple as that: /* (c) 2010-2013 multiMAN, Dynarec Enabler (c) 2013 Ing Pereira */ #define HTAB_BASE 0x800000000f000000ULL #define HTAB_LV2_START_421 (0x01000000ULL) #define HTAB_LV2_START_421D (0x08000000ULL) #define HTAB_LV2_START_430 (0x01000000ULL) // base_addr = address of mM's payload // base_addr + 0x100 = address of htab payload void dynarec_payload() { u64 base_addr=0; u64 patch_htab1=0; u64 patch_htab2=0; u64 patch_htab3=0; HTAB_LV2_START=0; if(c_firmware==3.55f && !dex_mode) { base_addr=0x2BE0D0; patch_htab1=0x59944; patch_htab2=0x5A37C; patch_htab3=0x5A844; } else if(c_firmware==3.55f && dex_mode) { base_addr=0x2D5B20; patch_htab1=0x5D230; patch_htab2=0x5DC68; patch_htab3=0x5E130; } else if(c_firmware==4.21f && !dex_mode) { base_addr=0x2D0C98; patch_htab1=0x5CCA4; patch_htab2=0x5D6DC; //+A38 patch_htab3=0x5DBA4; //+4C8 } else if(c_firmware==4.21f && dex_mode) { base_addr=0x2EB418; patch_htab1=0x605BC; patch_htab2=0x60FF4; patch_htab3=0x614BC; } else if(c_firmware==4.30f && !dex_mode) { base_addr=0x2D2418; //0x6ff000; to test htab patch_htab1=0x5CDF4; patch_htab2=0x5D82C; patch_htab3=0x5DCF4; } else if(c_firmware==4.30f && dex_mode) { base_addr=0x2ECB48; patch_htab1=0x6070C; patch_htab2=0x61144; patch_htab3=0x6160C; } else if(c_firmware==4.31f && !dex_mode) { base_addr=0x2D2428; patch_htab1=0x5CDF8; patch_htab2=0x5D830; patch_htab3=0x5DCF8; } else return; base_addr|=0x8000000000000000ULL; patch_htab1|=0x8000000000000000ULL; patch_htab2|=0x8000000000000000ULL; patch_htab3|=0x8000000000000000ULL; if(patch_htab1 && HTAB_LV2_START) { Lv2Syscall2(7, base_addr + 0x100, 0x7C0802A6F8010010ULL); Lv2Syscall2(7, base_addr + 0x108, 0xF821FF81F8410070ULL); Lv2Syscall2(7, base_addr + 0x110, 0x3C40800060420000ULL); Lv2Syscall2(7, base_addr + 0x118, 0x784207C664420000ULL | ( ((base_addr+0x198)>>16)&0xFFFF) ); Lv2Syscall2(7, base_addr + 0x120, 0x60420000E8020000ULL | ( ((base_addr+0x198))&0xFFFF)<<32 ); Lv2Syscall2(7, base_addr + 0x128, 0xE84200087C0903A6ULL); Lv2Syscall2(7, base_addr + 0x130, 0x4E800421E8410070ULL); Lv2Syscall2(7, base_addr + 0x138, 0x38210080E8010010ULL);// BCTR <htab_write_caller> desc Lv2Syscall2(7, base_addr + 0x140, 0x7C0803A64E800020ULL); Lv2Syscall2(7, base_addr + 0x148, 0x78C607647C0802A6ULL);// <htab_write_caller> Lv2Syscall2(7, base_addr + 0x150, 0xF801001060C60002ULL); Lv2Syscall2(7, base_addr + 0x158, 0xF821FF914800001DULL);// -> BL <lv1_write_htab> Lv2Syscall2(7, base_addr + 0x160, 0x6000000038210070ULL); Lv2Syscall2(7, base_addr + 0x168, 0x7C6307B4E8010010ULL); Lv2Syscall2(7, base_addr + 0x170, 0x7C0803A64E800020ULL); Lv2Syscall2(7, base_addr + 0x178, 0x7C0802A6F8010010ULL);// <lv1_write_htab> Lv2Syscall2(7, base_addr + 0x180, 0x3960000144000022ULL); Lv2Syscall2(7, base_addr + 0x188, 0x7C6307B4E8010010ULL); Lv2Syscall2(7, base_addr + 0x190, 0x7C0803A64E800020ULL); Lv2Syscall2(7, base_addr + 0x198, (base_addr + 0x148)); // htab _Custom call desc Lv2Syscall2(7, base_addr + 0x1A0, 0x8000000000700000ULL); /* enable full r/w/x access */ uint64_t pte0, pte1; /* process entire lv2 */ for (int i = 0; i < 128; i++) { /* read the old value */ pte0 = Lv2Syscall1(6, HTAB_BASE | (i << 7)); pte1 = Lv2Syscall1(6, HTAB_BASE | (i << 7) + 8); /* verify entry is lv2 */ if ((pte1 >= HTAB_LV2_START) && (pte1 < (HTAB_LV2_START+0x800000ULL))) { /* patch proper htab settings */ lv1_write_htab_entry(0, i << 3, pte0, (pte1 & 0xff0000) | 0x190); } } Lv2Syscall2(7, patch_htab1, (0x480000012C230000ULL) | ( ((base_addr+0x100-patch_htab1)&0xFFFFFF)<<32) ); Lv2Syscall2(7, patch_htab2, (0x480000012C230000ULL) | ( ((base_addr+0x100-patch_htab2)&0xFFFFFF)<<32) ); Lv2Syscall2(7, patch_htab3, (0x480000012C230000ULL) | ( ((base_addr+0x100-patch_htab3)&0xFFFFFF)<<32) ); } } u64 CEX=0x4345580000000000ULL; u64 DEX=0x4445580000000000ULL; if(peekq(0x80000000002E79C8ULL)==DEX) {dex_mode=2; c_firmware=3.41f;} else if(peekq(0x80000000002CFF98ULL)==CEX) {dex_mode=0; c_firmware=3.41f;} else if(peekq(0x80000000002EFE20ULL)==DEX) {dex_mode=2; c_firmware=3.55f;} else if(peekq(0x80000000002D83D0ULL)==CEX) {dex_mode=0; c_firmware=3.55f;} else if(peekq(0x8000000000302D88ULL)==DEX) {dex_mode=2; c_firmware=4.21f;} else if(peekq(0x80000000002E8610ULL)==CEX) {dex_mode=0; c_firmware=4.21f;} else if(peekq(0x80000000002E9F08ULL)==CEX) {dex_mode=0; c_firmware=4.30f;} else if(peekq(0x8000000000304630ULL)==DEX) {dex_mode=2; c_firmware=4.30f;} else if(peekq(0x80000000002E9F18ULL)==CEX) {dex_mode=0; c_firmware=4.31f;} else // unknown firmware... In IDA for 4.30CEX where: base_addr=0x2D2418 which makes the payload go at base_addr+0x100 -> 0x2D2518: ROM:002D2518 # =============== S U B R O U T I N E ======================================= ROM:002D2518 ROM:002D2518 ROM:002D2518 sub_2D2518: # CODE XREF: sub_5C9D4+420p ROM:002D2518 # sub_5D590+29Cp ROM:002D2518 ROM:002D2518 .set var_10, -0x10 ROM:002D2518 .set arg_10, 0x10 ROM:002D2518 ROM:002D2518 mflr r0 ROM:002D251C std r0, arg_10(r1) ROM:002D2520 stdu r1, -0x80(r1) ROM:002D2524 std r2, 0x80+var_10(r1) ROM:002D2528 lis r2, -0x8000 ROM:002D252C mr r2, r2 ROM:002D2530 sldi r2, r2, 32 ROM:002D2534 oris r2, r2, 0x2D ROM:002D2538 ori r2, r2, 0x25B0 ROM:002D253C ld r0, 0(r2) ROM:002D2540 ld r2, 8(r2) ROM:002D2544 mtctr r0 ROM:002D2548 bctrl ROM:002D254C ld r2, 0x80+var_10(r1) ROM:002D2550 addi r1, r1, 0x80 ROM:002D2554 ld r0, arg_10(r1) ROM:002D2558 mtlr r0 ROM:002D255C blr ROM:002D255C # End of function sub_2D2518 ROM:002D255C ROM:002D2560 # --------------------------------------------------------------------------- ROM:002D2560 ROM:002D2560 loc_2D2560: # DATA XREF: ROM:002D25B4o ROM:002D2560 clrrdi r6, r6, 2 ROM:002D2564 mflr r0 ROM:002D2568 std r0, 0x10(r1) ROM:002D256C ori r6, r6, 2 ROM:002D2570 stdu r1, -0x70(r1) ROM:002D2574 bl sub_2D2590 ROM:002D2578 nop ROM:002D257C addi r1, r1, 0x70 ROM:002D2580 extsw r3, r3 ROM:002D2584 ld r0, 0x10(r1) ROM:002D2588 mtlr r0 ROM:002D258C blr ROM:002D2590 ROM:002D2590 # =============== S U B R O U T I N E ======================================= ROM:002D2590 ROM:002D2590 ROM:002D2590 sub_2D2590: # CODE XREF: ROM:002D2574p ROM:002D2590 ROM:002D2590 .set arg_10, 0x10 ROM:002D2590 ROM:002D2590 mflr r0 ROM:002D2594 std r0, arg_10(r1) ROM:002D2598 li r11, 1 ROM:002D259C hvsc # hvsc(1): lv1_write_htab_entry ROM:002D25A0 extsw r3, r3 ROM:002D25A4 ld r0, arg_10(r1) ROM:002D25A8 mtlr r0 ROM:002D25AC blr ROM:002D25AC # End of function sub_2D2590 ROM:002D25AC ROM:002D25AC # --------------------------------------------------------------------------- ROM:002D25B0 .long 0x80000000 ROM:002D25B4 .long loc_2D2560 ROM:002D25B8 .long 0x80000000 ROM:002D25BC .long unk_700000 002D2518 7C 08 02 A6 F8 01 00 10 F8 21 FF 81 F8 41 00 70 002D2528 3C 40 80 00 60 42 00 00 78 42 07 C6 64 42 00 2D 002D2538 60 42 25 B0 E8 02 00 00 E8 42 00 08 7C 09 03 A6 002D2548 4E 80 04 21 E8 41 00 70 38 21 00 80 E8 01 00 10 002D2558 7C 08 03 A6 4E 80 00 20 78 C6 07 64 7C 08 02 A6 002D2568 F8 01 00 10 60 C6 00 02 F8 21 FF 91 48 00 00 1D 002D2578 60 00 00 00 38 21 00 70 7C 63 07 B4 E8 01 00 10 002D2588 7C 08 03 A6 4E 80 00 20 7C 08 02 A6 F8 01 00 10 002D2598 39 60 00 01 44 00 00 22 7C 63 07 B4 E8 01 00 10 002D25A8 7C 08 03 A6 4E 80 00 20 80 00 00 00 00 2D 25 60 002D25B8 80 00 00 00 00 70 00 00

Day 6 Batman Arkham Asylum $9.99 Fallout 3 $4.99 Max Payne 3 $14.99 Left for Dead 2 $9.99 Metal Gear Solid HD $9.99 Metal Gear Solid Peacewalker $9.99 Orange Box $9.99 Sid Meier’s Civilization Revolution $9.99

Merci pour l'information. Hddhackr 1.40

Merci pour l'information. La Mort du DGX

Merci pour l'information. La Mort du DGX

Bonjour Ça doit être un tool pour les développeurs et non pas l’émulateur Ps1 de demonhades.... This weekend Spanish PlayStation 3 developer IngPereira has enabled DynarecPS3 support for PS3 CFW 4.21 CEX and DEX Firmware with details below. To quote: DynarecPS3 - This tool make possible running JIT code on GameOS PS3 by loading patches to lv2, using peek / poke lv2 calls based in some codes from libkammy stuff on 3.41, right now just work on CFW 4.21 DEX or CEX, it need to be ported to others CFW. It can be ported too to work on MFW (implementation on lv2_kernel.self, see bugs) If anyone need help with porting to MFW (LV2_KERNEL) like cfw ps3ita or Rebug so have dynarec support patched without any pkg or lv2 patcher, just try to send me a pm or email. So now is possible already to run dynamic recompiler on GameOS LV2, like i say by now just support 4.21 CFW CEX / DEX. POC: USING PSX DYNAREC EMULATOR - You can now try to use dynarec from PS3SX for example. PS3SX POC First run dynarec enabler to patch dynamic recompiler code support, it will beep and log on hdd0. To use dynarec from ps3sx you have to leave "interpreter mode"=OFF so it will try to use dynamic recompiler maded by anonymous, if you don't launch first dynarec enabler then you will have a Black screen when trying to run any iso from ps3sx menu, so you need to run dynarec enabler before doing anything that need jit code support like this POC. If you have run dynarec enabler before then you will see depending of the game (because this dynarec from ps3sx is too old and outdated, games works more faster but is not so compatible) that ps3sx will launch the game instead of black screen because GameOS is now patched. Now we can make our own dynarecs for emulators that may use it, like n64 one or dosbox. To see bugs, info see git. Finally, from the FAQ: DynarecPS3 Homebrew tool loading patches on to LV2 allowing dynamic recompiler code support on PS3 GameOS. The tool make possible running JIT code on GameOS PS3 by loading patches to lv2, using peek / poke lv2 calls based in some codes from libkammy stuff on 3.41, right now just work on cfw 4.21 DEX or CEX, it need to be ported to others CFW. It can be ported too to work on MFW (implementation on lv2_kernel.self, see bugs) If anyone need help with porting to MFW (LV2_KERNEL) like cfw ps3ita or Rebug so have dynarec support patched without any pkg or lv2 patcher, just try to send me a pm or email. Usage Just run the tool, it will beep and leave a log in /dev_hdd0/APP.log. Actually the tool make a .log (/dev_hdd0/APP.log) with some info if there are errors with the patches, i made this right now because this can help a lot in the porting process as right now just work on 4.21 dex and the patches when are wrong can actually make appear a black screen so again this can speed up the porting. Notes Bugs known: Cannot install pkgs, error 0x80029F0A , because this is recommended right now to use this only when is needed (Before running any emulator for example) and if you have previusly installed what do you need later. Building Building requires PS3 SDK right now, included are some batch stuff to help in the compile stuff by using MSYS properly installed. Porting Right now it can support any cfw just need rights offsets to work good, by now just use lv1 poke to patch lv2 protection and later it use hv call lv1_write_htab_entry (so it install hvsc redirect to call hvcalls) to apply execution permissions on high area of lv2 0x700000 so we can put executable piece of code right there and apply the right patches that make possible running dynamic recompilers code on PS3 GameOS LV2. It can work too again by patching lv2_kernel just need to relocate the htab payload address and apply permissions by modifying lv2_kernel.self segments page or in a more easy way by relocating branches of htab_payload to fit it in other space with good execution access known on lv2. This SOFTWARE is not licensed, approved or endorsed by "Sony Computer Entertainment, Inc." (SCEI), SNEI, SEN or any other party. Notes from STLcardsWS: PS3SX package gives a signing error on CEX 4.21.2 Rebug. I assume it is a DEX signed PKG? Also the Dynarec Enabled package just black screened and froze the PS3. http://www.ps3news.com/ps3-hacks-jailbreak/dynarecps3-support-for-ps3-cfw-4-21-cex-dex-by-ingpereira-out