• DCEmu Homebrew Emulation & Theme Park News

    The DCEmu the Homebrew Gaming and Theme Park Network is your best site to find Hacking, Emulation, Homebrew and Theme Park News and also Beers Wines and Spirit Reviews and Finally Marvel Cinematic Universe News. If you would like us to do reviews or wish to advertise/write/post articles in any way at DCEmu then use our Contact Page for more information. DCEMU Gaming is mainly about video games -

    If you are searching for a no deposit bonus, then casino-bonus.com/uk has an excellent list of UK casino sites with sorting functionality. For new online casinos. Visit New Casino and learn how to find the best options for UK players. Good luck! - Explore the possibilities with non UK casinos not on Gamstop at BestUK.Casino or read more about the best non UK sites at NewsBTC.
  • xg917

    by Published on September 17th, 2007 16:20

    M33 Official Website

    Hello, world.

    As you have seen, some things have changed between Sony and the developing of custom firmwares.

    Due to the leak (that we've always gone against this crime) of the OE sources from a private svn, everyone can
    take a peek into the patches done from the Open Edition to the original firmwares to allow the development
    into this scene that was growing day after day. And, when we say anyone, we include Sony.

    This intrusion into one of the basis of the actual PSP Scene, has just made harm to the entire world of the
    PSP Scene. Therefore, Sony saw this and made some interesting changes in some modules (mainly loadcore), plus
    the change of some nids that are used to the development of M33 Custom Firmware.

    So, if you can't wait for the new release, you'll have to wait; and this is cause this leak and this changes
    made upon the material we work and we try to release asap to the *entire* psp community. Looks like, as always,
    there is someone that wants to be important in this world when no-one asks him, and his result is this delay
    on the development of the new versions.

    This "benefit" that much lammers talked about in foreign forums, talking about OE leak, will just made a result
    in the near future: that serious developers (including us) will think twice before releasing anything else.

    And also, speaking about the new "custom firmwares" that have been released, such as AoP, and others addons
    that use M33Cf, will be deeply studied and reversered to see if *anything* of the core, reboot, or whatever
    from our work has been ilegally used. If this is afirmative, we'll have to act against this.

    This changes won't probably last too long and won't be an important problem, but it's just, as we have just said,
    another resultant of trying to be someone on this world by stealing and leaking instead of studying.

    Please have patient and stay tuned for the next Custom Firmware for PSP and PSP Slim and Lite

    M33 Team.

    So hang in there guys! ...
    by Published on August 21st, 2007 18:47

    PSPTube seems to have been updated today but with SofyaCat's 8/17/2007 release?


    Google Translation..

    Known trouble Known bugs †
    During animated picture playing back there are times when playback stops -> restarting, it is the [ku]
    It is. (While investigating)
    Sound there is an animated picture which slips

    Download †
    PSPTube20070817.zip -- Version20070817 summer [komi] (C72)
    The [te] we distributed.
    Modifying contents, as for redistribution please do not do.


    Renewal past record †
    0817 edition C72 summer [komi] distribution
    At [konhuigu], is dialogue used in the initialization part of network?
    How, it tried to be able to choose. (Debugging function)
    In case of 200over, setting of priority of main thread 1.00 and
    1.50 Correcting the fact that it is different from edition
    In order favorites to be able to set the place of the folder with [konhuigu], the stripe it does,
    It is.
    It tried to indicate the sum nail with [huairumodo].
    The same jpg file as file name is indicated.
    If “xxxxxxx.flv” indicating “xxxxxxx.jpg” as the sum nail
    It does.
    When there is no favorite folder, from the cache folder the search stripe
    It does.
    0813 editions (at instant) secret
    It tried using dialogue in the initialization part of network.

    Sorry for this post being sloppy, if this were in english it wouldnt be so.. out there

    Download and Give Feedback Via Comments ...
    by Published on August 20th, 2007 23:37

    Via M33 Forums comes a new version of the Custom Firmware for the PSP, Heres the details:

    Spread this news



    IMPORTANT: agree with LICENSE.TXT conditions before installing the program.

    Changes in M33-4 (mainly bugfix)

    - Fixed the bug that caused CRC error when writing to flash usb in the XMB. Now writing
    is OK.
    - Added the new speeds to vshmenu and core, because we forgot in recovery.

    AS we didnn't want to release a new update without something new, we worked in making
    3.10/3.11 to work with popsloader, and that's it, the new popsloader plugins supports them.
    Instruction for 3.10 and 3.11 are same as 3.30: you need pops.prx, popsman.prx and pafmini.prx
    with the correct names in popsloader directory. And remember that savedata of 3.10-3.30 are incompatible
    with those of 3.40+. We'll research if a solution for this is possible.

    Team M33

    ---------------------------------------------------------------------------------------------
    As for yankee paranoids, a little word about the "brickers" issue.
    We repeat it again: THERE IS NO MALICIOUS CODE inside M33.
    Some of the files of this update are protected by encryption schemes to protect ourselves
    from that page that annoys homebrew developers.
    The keys for the decryption: the own update file.
    So if the file is changed, the decrypted data is not the original one, and this causes the
    wrong data to be written. There is no way you can call this malicious code as there is no explicit
    code to brick nothing, it is the corruption of the update what actually causes the bad decrypted
    data to be written.

    Anyways in this update we check if decrypted data is wrong and in that case we write a recovery
    warning the user what happened. It will activate usb, and it will allow you to execute a recovery
    eboot.pbp... in a curious path ("ms0:/PSP/GAME/PS3NEWS_ARE_STEALERS_I_AM_NOT_GONNA_VISIT_THEM/EBOOT.PBP")
    which is not at sight of an hex editor

    If you visited ps3news and bricked in last release, then blame his administrator.
    He is the one that modified the files and had them in the server for lots of hours
    knowing the consequences.

    Spread this news



    We (DCEmu) warned users that some people were getting bricked because the had visted ps3new.com, and advisted you to clear you cach before upgrading, it turns out we were wrong and it was only users that had downloaded from ps3news.com that were getting brick (and know we know why).

    We would like to apologise to M33 and our readers for that incorrect warning.

    but as always: Update at your own risk, we are not responsible to what happens to your psp using this!




    Download and Give Feedback Via Comments ...
    by Published on August 12th, 2007 03:03

    Sofiya has updated PSPtube, here is the translated changelog from the Nekomimi web site.


    - Download performance of animated picture was added
    * It is possible to download animated picture in the favorite folder.
    [huairumodo] was added
    * The animated picture which is in the favorite folder is played back
    - When the full range is used with YUV, with the rubbish corrected [ru] in the picture
    IDCT of On2VP4,5 furthermore was optimized
    ○ it corresponded to the swap of the button and the ## button
    - When firmware 1.0 is, being automatic with language setting, it tried to change.
    - If your PSP is Japenese,now select with O button. Cancel with [] button
    - If the PSP is in other languages, select with X button. Cancel with ○ button
    - When it is firmware 1.5 or more, it is due to the setting of [konhuigu]. (Perhaps)
    - Network the part where information of setting is acquired by mistake corrected the fact that it is
    - There is network setting in spite, nothing keeping saying, it is the expectation where having ended is gone.
    - The Google cache error has been corrected
    Looking at the sample, it corrected the part which solves name.
    - It was designed in such a way that it can do also sum nail indication unnoticed.
    * You think it is, that it is all right, but because the case which does not move is many, it is in the midst of investigating.
    - With the original software security other than WEP it probably is to be able to use?

    DIGG THIS NEWS



    CONTROLS:

    X - Select
    O - go back/new search
    Triangle - (when viewing the list of videos press Triangle to download video to favorites)
    Start - pause/play video
    Select - change size of video & View Favorites/Go back to video list (press X on your downloaded video, a black screen will come up with no text. press select again and the video should start)
    L & R Triggers - Flip Through Pages


    Download and leave feedback via comments. ...
    by Published on June 14th, 2007 03:59

    Via http://strmnnrmn.blogspot.com/

    Tracking down the SSB Dynarec Bug - Part 2

    On Monday I talked about the fragment simulator and how this could be used to help track down bugs in the dynarec implementation. In this post I'm going to talk a bit about a tool I use mostly for regression testing, but also to help determine the exact point at which the fragment simulator and the interpretative core go out of sync. It's a bit of a long post, so apologies in advance

    Daedalus can be compiled with a flag which enables a special 'synchronisation' mode. This build configuration creates an instance of a synchronisation class which can be initialised in one of two modes - either as a producer or as a consumer. At various points during program execution I pass information about the internal state of the emulator to the synchroniser for processing. In the case of the producer, it simply writes this data out to a file on disk. The consumer is a bit more interesting; it reads data of the required size from disk, and compares this 'baseline' value against the value provided by the emulator. If these two values are found to be different, the synchroniser knows that things have drifted out of sync and it can trigger a breakpoint and drop out into the debugger.

    This technique relies on the fact that the emulator is deterministic, i.e. running the emulator twice in a row with the same inputs generates exactly the same results. By 'inputs' this means not just the same rom image, but external inputs such as data from the controller must match exactly too. Obviously pressing buttons on the controller in exactly the same order with the same timings would be impossible to duplicate, so the other function the synchroniser performs is to record input from the pad in the case of the producer, or play input back in the case of the consumer. Other external input, such as calls to timer functions (e.g. time(), QueryPerformanceCounter() or rdtsc) can be synchronised in the same way.

    The synchroniser works with as few or as many sync points as you provide. For debugging very simple problems, you can get away with just checking the value of the program counter as each instruction is executed. For more tricky problems you can end up adding many more sync points - for instance you can synchronise the entire register set after every instruction to ensure that the synchroniser catches any instruction which generates a different result from the baseline.

    I add sync points to Daedalus using a set of macros. When synchronisation is enabled, the macros expand out to calls to a virtual method on a global instance of the synchroniser class. An example sync point in the code might look like this:


    u32 pc = gCPUState.CurrentPC;

    SYNCH_POINT( DAED_SYNC_REG_PC, pc );

    OpCode op;
    if( CPU_FetchInstruction( pc, &op ) )
    {
    CPU_Execute( pc, op );
    }



    The interesting line here is the SYNC_POINT macro, which synchronises on the current program counter value. For producers, this just writes the value of 'pc' to disk. For consumers, it checks that the value we have for 'pc' matches the one read from disk.

    The DAED_SYNC_REG_PC argument is simply a flag to describe what is being synchronised. Another global constant allows easy control of what is synchronised:


    enum ESynchFlags
    {
    DAED_SYNC_NONE = 0x00000000,

    DAED_SYNC_REG_GPR = 0x00000001,
    DAED_SYNC_REG_CPU0 = 0x00000002,
    DAED_SYNC_REG_CCR0 = 0x00000004,
    DAED_SYNC_REG_CPU1 = 0x00000008,
    DAED_SYNC_REG_CCR1 = 0x00000010,

    DAED_SYNC_REG_PC = 0x00000020,
    DAED_SYNC_FRAGMENT_PC = 0x00000040,
    };

    static const u32 DAED_SYNC_MASK(DAED_SYNC_REG_PC);

    #define SYNCH_POINT( flags, x, msg ) \
    if ( DAED_SYNC_MASK & (flags) ) \
    CSynchroniser::SynchPoint( x, msg )



    If I want to enable more thorough debugging, I can change DAED_SYNC_MASK and OR in more values:


    static const u32 DAED_SYNC_MASK(DAED_SYNC_REG_PC|DAED_SYNC_REG_GPR) ;



    Changing the mask value requires the emulator to be rebuilt from scratch and the baseline synch file to be recreated. This is a bit time consuming but doing it in this way means that the compiler can optimise out any synch points which we aren't interested in, keeping things running as quickly as possible.

    One problem with this technique is that the synchroniser can quickly generate a massive amount of data, so much that most of the execution time is spent shifting this data to or from disk, slowing debugging to a crawl. In the example I gave on Monday, it can sometimes take over 500 million instructions before things go out of sync. ...
    by Published on February 19th, 2007 00:11

    Just things left that ST has been working on and that he has to work on. Glad he is back in action

    Direct Quote from his Blog: http://strmnnrmn.blogspot.com/

    R9 Status Update

    It's been a couple of days since my last post, so I wanted to give a quick update on what's left on my R9 TODO list.

    - I've been working over the weekend at fixing a number of outstanding graphical glitches, putting in place a system to automatically translate n64 blend modes to the psp. This should hopefully nearly eradicate nearly all of the purple and black textures that have shown up all over the place in previous releases. This is quite an interesting feature from a technical point of view, so I'll talk about this in a bit more depth once R9 is out.

    - I have a few glitches in the new UI to fix (e.g. audio can't be disabled once the rom has started, controller can't be remapped once the rom has started).

    - I need to hook up a few things to the new UI (e.g. 'reset to main menu', 'take screenshot' etc)

    As you can see, it's quite a short list now, so I'm still on track for releasing R9 by next weekend

    What Nintendo 64 Games Would you most like to see running at a playable rate on the PSP ? ...
  • Search DCEmu

  • Advert 3