...

...

Pate has released a new version of his Dos Emulator for the DS Console:

Sorry for the one day delay to my normal Sunday updates, but as this was a long Easter weekend I wanted to use the one extra day to work on DS2x86 and get as many fixes implemented as possible.
DS2x86 0.07 release info



Okay, this new version has the following fixes:

• There is now (finally) a blinking cursor in the text modes, most importantly in the 4DOS command prompt.
• HIMEM.SYS emulation added. This allows Chaos Engine to run, and will enable support for Windows 3.00a in Standard Mode in the future.
• Fixed a serious total crash problem in 32-bit string opcodes. This happened in games like Abuse, Ascendancy and Carmageddon. Those games still don't work properly, but they don't hang the system completely any more so I have a chance of debugging and improving them further.
• Fixed a stack alignment problem that could cause "Exception 4" BSOD errors. This fixes at least Micro Machines.
• Improved the BSOD reporting. Now the printed data includes a stack trace, so I can better determine the location of the problem.
• Improved horizontal blank reporting, this might solve hanging problems in some games, like Pinball Fantasy.
• Improved Mode-X graphics blitting code to handle wrap-around properly.
• Changed the screen refresh interrupt interval from 60Hz to 59Hz. This might help with the intermittent "stuck key" problem in some games.
• Direct file read to EGA memory is now supported (for example in Heimdall).
• Implemented a number of previously missing opcodes.

DS2x86 0.07 background information
After the previous blog post I worked on Jazz Jackrabbit for a while, but could not get any notable progress with it. It still needs a lot of debugging to determine the problem, and so I decided to move on to some other issues that might be faster to solve.
First, I decided to add HIMEM.SYS emulation, as I could simply port the code from the most recent DSx86 version. This in itself didn't take long, although I ran into a very strange problem where the whole DS2x86 hung immediately when launching any game. It loaded 4DOS.COM fine, and I could give internal commands like "dir" or "memory", but immediately after launching any game it hung totally. I then began commenting out the new HIMEM.SYS stuff, until the only things remaining were a couple of static integer variables in the new C++ module! Commenting these variables out got rid of the problem, but when I added these static variables back, the problem came back. One of the variables had an initial value based on the addresses of two other variables, which seemed to cause the problem. I switched to using a #define, and the problem was solved, but I still don't quite understand how a static variable initialization can break the whole software.
After the HIMEM.SYS emulation started working, Chaos Engine began to ran otherwise fine, except that the display had a moving line of black pixels, and scrolling the zoomed screen did not work properly. The game wraps the display around the A000 segment while scrolling (similarly to what Commander Keen 4 does in EGA mode), and this feature was not yet supported in my Mode-X screen blitting code. I took some time to make this work correctly in both Zoom and Scale screen modes, and now this type of wrap-around should cause no more visual glitches. This is what Chaos Engine now looks like, with a wrap around in the middle of the screen (but not showing :-).

After the HIMEM.SYS emulation in place, I wanted to see whether Windows 3.00a would run in Standard Mode. I had several problems with it, all due to various bugs in my protected mode implementation which I had to fix. There is still a problem with the Global Descriptor Table handling, as Windows uses a segment selector 0x0101 when returning from protected mode to real mode, but in DS2x86 the GDT entry points to a data segment, while in DSx86 and DOSBox it points correctly to a code segment. So, no Windows 3.00a in Standard Mode yet in this version, but I'll try to fix this problem in the near future.
Next, I was looking whether I had Hexen on my SD card. I didn't find it, but as there was Heimdall, I decided to test how it runs. It started fine, but when talking to a character I got a BSOD reporting an invalid store address of 0x600CE030. In this same situation DSx86 shows garbage on the screen, so I thought that this might be a chance to find out what exactly is wrong in my emulation code. I checked the address reported by the BSOD, but it pointed to inside the C library memcpy() function. Obviously, memcpy is used all around the code, so that was not of much help. I needed to find out what code it was that called the memcpy, so I implemented a simple stack traversal routine into my exception handler code. It attempts to find return addresses pointing to my own DS2x86 code by traversing the stack above the exception handler stack frame. When I ran Heimdall again, I got a stack trace that (after converting the hex addresses to function names ...

News via http://www.eurasia.nu/modules.php?na...ticle&sid=2775

Mathieulh probably just let the cat out of the bag with his obvious hint to the much talked bug that practically owned future PS3 firmware updates and also the mass growth of warez leechers with the help of 3.60 app keys. Yes, we’re talking about the unstoppable 3.60+ CFWs, you bitch. Provided that Sony won’t release unhackable PS3 consoles in the near future, of course. ...

News via http://ps3.gx-mod.com/modules/news/a...p?storyid=2737

PSN Qriocity systems and Sony have been suspended according to a message posted on his official blog. After five days of fighting, the firm still has no date of release to service.

On 20 April, a hacker attack, according to Sony, put the servers in the Playstation Network to knee. The day after the attack, Sony released a message explaining that he was working to resolve the problem would require a day or two. On 23 April, the company explained that it had disconnected NHP Qriocity to investigate the intrusion responsible for this incident. Yesterday she was still split by a message explaining that it is strengthening its infrastructure, but it still has no launch date. According to rumors, it would be an attack type LOIC (Denial of Service - DDoS, designed to make available a network by overloading it).

Sony let indirectly suggest that members of the group Anonymous were responsible. The group has denied these accusations and if they do not exclude that some of its members are acting independently, the operation organized by the community does more official Sony servers. Anonymous denounces against the incompetence of the Japanese, who needed a scapegoat.

This condition is extremely rare and even Microsoft took the opportunity to explain the voice of a charge that it supports Sony in this difficult time but also praises the merits of his platform of online games has not been Such difficulties. He hopes to attract players disappointed by the Japanese delivery.

Meanwhile servers could be accessible again tomorrow and Thursday for Japan to the United States and Europe (or tomorrow according to other sources).

Source: Presence-PC ...

News via http://mobiles.gx-mod.com/modules/ne...p?storyid=9583

The Japanese developer neur0ner now known to all, is back with a new revision of its Standing 6.38 CFW for PSP 1000 and 2000 (No. 8C). The M33 driver and a new driver named EO were added in this release to further improve the compatibility of the firmware.

News / Corrections:
- Added iso M33 driver.
- Adding a new driver ISO OE.
- Fix for launching the update from CFW PRO-B4 (already corrected in the old version).

Installation:

1) For those who are already in ME CFW 6.38, you just copy the UPDATE folder in the downloaded folder PSP / GAME / and run it from the games menu, press X to install and restart.

2) Those who are on another CFW or HEN, follow this method to install the 6.38 revision 2 ME:

1 - Download the 6.38 OFW and CFW6.38 ME 2
2 - Rename the EBOOT of the OFW 6.38 into 638.pbp.
3 - Put the renamed file in the folder 638.pbp UPDATE ME CFW 6.38 Revision 2.
4 - Copy the UPDATE folder (which contains the EBOOT of the OFW and 6.38 ME 6.38 renamed) on your memory card to: ms0: / PSP / GAME /
5 - If you are not standing CFW (GEN or M33), start your HEN 6.20/6.35.
6 - Now run the UPDATE CFW 6.38 ME and follow the instructions exactly.
7 - At the end, once the 6.38 Update is complete, restart the PSP twice to see the CFW enabled (just the first time).

NB:

- Some permanent CFW, you may be faced with the refusal of the PSP Update (Error: PSP firmware 9.99 is already no longer need a SHIFT .... etc.). To solve this problem, we can use the update CFW GEN D3 but to go to the OFW 5.50, you go beyond the official firmware 6.20, it installs NT 6.20 HEN then you can follow the second-mentioned installation procedure above.
- There is another solution to this problem is to use a version.txt a version lower than 6.38 to distort history information of the PSP, which lets the SHIFT.

Download Here ...

News via http://www.scummvm.org/news/20110422/

The ScummVM team is announcing another round of release testing in preparation for our next release: 1.3.0!
Since our last release, we've been very busy working on adding support for more of your favorite games. Backyard Baseball. Backyard Baseball 2001, Hugo's House of Horrors, Hugo 2: Whodunit?, Hugo 3: Jungle of Doom, Playtoons: Bambou le Sauveur de la Jungle, Toonstruck, and Urban Runner are all ready for our loyal fans to play through to their hearts' content. Several Living Books games are also supported now: Aesop's Fables: The Tortoise and the Hare, Arthur's Birthday (v1), Arthur's Teacher Trouble, Dr. Seuss's ABC, Green Eggs and Ham, Harry and the Haunted House, Just Grandma and Me (v1), Little Monster at School, Ruff's Bone, Sheila Rae, the Brave, Stellaluna, The Berenstain Bears Get in a Fight, The Berenstain Bears in the Dark, The New Kid on the Block. You can see more info on the bugs we fixed and the features we added over here.
Like with our last release testing, not all games will be tested; only games that have had significant changes to their codebase since the last release are up for testing. As usual, the list of games to be tested is on the wiki.
Those games aren't going to test themselves! Download a daily build and report any bugs you find to the bug tracker. If you complete a game, please let us know on the forums so we can throw the results up on the wiki page. Be sure to provide the version, language, and platform of your game when reporting a completion. Any other questions? Go check out the release testing guidelines. ...

News via http://wololo.net/wagic/2011/04/24/6...sony-products/

A few months ago, Sony sued a security researcher, George Hotz, for jailbreaking the PS3.
At some point, the group Anonymous even started protesting against Sony, both in the digital world and in real life.
We all have our opinion on this story, but it seems this lawsuit didn’t help Sony’s image. A while ago, I asked you if you were going to boycott Sony’s products, and the results are in. As I type this, 36% of the voters said they won’t boycott Sony, 35% said they will boycott Sony, and 30% said they would buy “less” Sony products [than they would have if this lawsuit hadn't happened]. Overall, this means that Sony now has a bad image as a company for 64% of the voters. Way to go, Sony, I’m sure your marketing department has a few words to say to your legal department

Now, /Talk is just a small forum, and our members probably don’t represent the average customer’s opinion… or do they? This blog is of course biased, and the majority of my readers probably don’t represent the average Sony customer population. But the same way movie downloaders are also the ones that buy the most Blu-rays, I believe that people who hang out on a technical forum such as /talk are probably the people who will shape the future of device purchases… ...

News via http://wololo.net/wagic/2011/04/24/t...ploit-on-6-38/

As you probably know, firmwares 6.37 and 6.38 allow you to play “regular” homebrews through HBL, as well as “signed” homebrews, including some backups with the fake_np tool. But these two firmwares cannot run Custom Firmwares or HENs, which offer a much more “integrated” experience, as well as the support for custom themes and plugins. In order to run a CFW, a Kernel exploit is required, and the Kernel exploit that is used on firmwares 6.20 and 6.35 has been patched by Sony in firmware 6.37.
However, Developer Total_Noob announced via a video on his youtube Channel that he found a new Kernel exploit on firmware 6.38.



The video doesn’t show much, and a user-mode fake homebrew could do the same, but given the source I’m inclined to say that this is legit
Total_Noob states in his video that he has no current plan to release anything for now, so let’s wait a little bit ...