My W.I.P. port of the amazing GBA emulator gpSP (originally made by Exophase), has been given a name. At least until something better comes up, it is being called gpSPhone.
I have got input and the dynarec working. I am cleaning up the controls and making sure it runs ok.

Open the champagne !!!

I've here a new pad plugin I wrote. It's MegaPad and it uses SDL. No worry, the latest actual version of the SDL (1.2.12) is provided.
This plugin offers, as LilyPad, a complete pad support, many possibilities, but is much simpler than LilyPad.

First place SDL.dll in the root PCSX2 folder (not the plugins folder), else the plugin won't start.

1. Mapping and config

After having selected MegaPad in the Pad plugins list and launched its GUI by clicking the
Config button, you must configure it. You can select the Pad 1 or the Pad 2 with the
buttons in the top-left corner of the window. For mapping press any of the 20 buttons.
The pressed button will become grayed. Then you can do various things :

a. Keyboard

For the buttons press a key and the selected button will be bound to the pressed key. Pressing
Escape or Backspace allows you to delete a value. For the axes press any key with old versions, or click right button whth new versions, and the selected
axis will be bound to the mouse. Note that if the axes of the 2 players are bound to the mouse,
they will move simultaneously.

b. Joystick

For the buttons press a button, a POV hat in the wanted direction or move an axis in the wanted
direction and it will be bound to the selected button. Note that if you bind an axis to a
pressure-sensitive button*, the pressure will match the value of the axis. Try this feature in
games which need pressure sensitive buttons. For the axes move an axis and it will be bound to
the selected axis. Warning : the GUI has a little difficulty to detect the moves of the vertical
(y) axes, but there is no problem in the games.

c. Misc

There are 4 general options under the mapping buttons.
1. Axis sensitivity : can be 3 values (affect the GUI as the games). This is the sensitivity of the
plugin to axis moves.
-Very sensible : for precision games or low-sensibility axes.
-Normal : default, I recommend you to use it.
-Low sensibility : use it if your axes are very sensible.
2. Enable logging : This enables a pad log stored in logs\megapad_log.txt, which can be used only for
debugging purposes. As mentionned, this logging makes the emu slower.
3. Always show cursor : Use it with ZeroGS if you use the mouse, to see where is the cursor.
4. Low-visibility cross cursor : The arrow cursor is replaced by a low-visibility cross cursor.
Use it if you don't want to see the arrow cursor.

Then click OK.

2. Emu

I think I don't need to detail how to use the keyboard or the joysticks, but I will tell you how does
the mouse support work.
Press the left button for left axis, the right button for right axis. When you release a button, the
corresponding axis will be "centered". When you press a button the cursor is automatically centered.
Move it as an analog axis. When a button is pressed the cursor cannot get out the GS window. The
mouse support has been seriously improved in the new version, axis positions are calculated from
the size of the GS window, so it works better than PadWinKeyb mouse support.

If you encounter any bug using this plugin tell it to me.

Version 1.3.0

F keys work now, thanks RpgWizard for signaling me this bug, the GUI does not allow you to bind them to any control, and if the input detection loop detects that a F key has been pressed it directly returns.

Here is an Atari 800 XL emulator for DS!
This emulator is based on atari800 (http://atari800.sourceforge.net/) to emulate all components of the Atari.

History
The family XL was introduced by the model 1200xl. But its incompatibility with the veterans 400 and 800 made him quickly obsolete. It was the 600XL and 800XL, built in 1983, which could make the most extensive libraries of their predecessors. He succeeded in atari 400 (1979), the atari 800 (1979), the 1200 XL (1982), and 600 XL (1983).

The 600XL was the model entry level, with 16K of RAM, expandable to 64. The 800XL came with 64k of RAM. The big differences with the ancestors were linked to the memory and the operating system.



But Commodore, with the C64, practiced aggressive prices and took advantage. The trouble began for Atari at the beginning of 1984, with the boom of video game consoles.

The problems associated with the new production lines have delayed the entry of the machine on the market. Originally intended to replace the 1200XL in mid-83, the machines did not arrive before the end of 1983, and far fewer machines than expected were available during the Christmas period 1983.

Nevertheless, the 800XL is the most popular computer sold by Atari. The 1400XL and 1450XLD saw their delivery date postponed to give priority to the Atari 600XL/800XL and later by the system 3600. Ultimately, the 1400XL was eventually canceled outright, and 1450XLD delayed until also be canceled. The XE System was the answer to the soft Japanese. Without success.

We must also know that we could connect to the chain via a large square, a floppy drive, tape, printer, and so on. The USB hour before then. This is called pseudo USB then ORC.

I’ve just rolled a new maintainance release of dswifi, the library for Nintendo DS wifi communication. The changes are fairly minor but improve UDP support and fix a rare issue with broadcast addresses.

Added gethostname and sethostname.
Provide DNS record for localhost.
Correct minor issue with broadcast address checking.
Enable select support for UDP.
Correct code for ntoa.
Close DNS socket on no answer.
As usual the update is available through the automated installer/updater with the source and binary tarballs hosted on sourceforge.