Demon Cleaner 12:48 18th June 2009
Release v132:
Originally Posted by :
0.132
-----
MAMETesters Bugs Fixed
----------------------
- 03013: [Misc.] [debug] "Error: free a non-existant block" on
TMS57002 source generation (Atari Ace)
- 03241: [DIP/Input] aladbl: Unable to "Press Start" (Fabio Priuli)
- 03238: [Crash/Freeze] gtmr and clones: Access Violation (Tafoid)
Source Changes
--------------
Fixed colors in the Aristocrat Mark-IV driver. [Angelo Salese]
Hooked up 2nd player mahjong panel in mjkjidai. [Angelo Salese]
Watchdog hooked up in twinkle.c so test mode exits. [smf]
Fixed for good the colors in 86 Lions. [Angelo Salese]
Fixed address line swapping in Mirax. [Olivier Galibert]
Fixed rom 2 decryption in Mirax. [Tomasz Slanina]
Improved the video emulation in Mirax. [Angelo Salese]
Fixed a minor typo in the SSEM debugging features. [MooglyGuy]
Fixed a number of year listings known to be unknown or incorrect the
current MAME source. The source for these changes come from the book:
Arcade TV Game List (Edition: Domestic and Overseas, 1971 - 2005).
[Tafoid, Fujix]
Update ghosteo driver with information out of eolith.c about QS1000
and added the sample rom, with a note about it NOT being dumped from
this PCB but is a common sample rom used by Eolith. [Brian Troha]
Fixed minor cycle counting inaccuracy in Z80 core. [Marshmellow]
Added the concept of device contracts. A contract is a well-defined
set of interfaces supported by a device, and identified by a unique
string identifier. A device may support any number of contracts,
described in a list via the DEVICE_CONTRACT_LIST* macros. The purpose
of contracts is to provide a means for devices to expose a standard
set of interfaces to other parts of the system. For example, the PCI
device should expose a contract that includes functions for
configuration register access, and 32-bit I/O. Then any device with
a PCI interface should implement the PCI contract, so that the PCI
bus device can route things appropriately. [Aaron Giles]
Removed the MDRV__REMOVE macros. A simple DEVICE_REMOVE
works now that device types are not needed. [Aaron Giles]
Verified clocks on Samurai Aces pcb. [Corrado Tomaselli]
Added missing static and const qualifiers throughout the source.
[Atari Ace]
Changed several internal interfaces to be more consistent, namely
(1) passing device_config as a const always, (2) passing
running_machine as a non-const always, (3) eliminating running_machine
where possible, (4) passing machine/device first, and (5) preferring
(screen, bitmap, cliprect) over (machine, bitmap, cliprect) when all
are needed for rendering. [Atari Ace]
New games added or promoted from NOT_WORKING status
---------------------------------------------------
Mirax [Olivier Galibert, Angelo Salese, Tomasz Slanina]
Super Crowns Golf [Angelo Salese, Tomasz Slanina]
Jockey Club [Andrew Welburn, Dumping Union]
New clones added
----------------
Shadow Force (Japan Version 3) [Guru]
New games marked as GAME_NOT_WORKING
------------------------------------
Enchanted Forest [Palindrome]
Janputer [alien_mame, Dumping Union]
Dolphin Treasure [AGEMAME]
[Reply]
Harrison 13:30 18th June 2009
I saw that last night on PD and already updated my set.
However I still haven't got around to bringing my CHD set up to date. It's quite old now and from what I've read the structure has now changed and so I might need to download the lot again, which is going to be a big download and a huge hit to my PD upload credit.
[Reply]
Demon Cleaner 14:09 18th June 2009
Yep, the news is already a bit older, forgot to post it earlier. My set has also been updated already.
Don't worry about your PD ratio though, as the CHD set is also for free.
[Reply]
Harrison 15:00 18th June 2009
Oh cool, I hadn't noticed that. Will queue it up now!
[Reply]
Demon Cleaner 15:59 18th June 2009
Check this out
One more question, since yesterday I get following message at PD, even my torrents are uploading fine, I don't notice any difference:
Originally Posted by :
You are not CONNECTABLE (firewalled?)
The tracker is unable to contact your client on the IP address and port you are reporting, which means other clients cannot initiate a connection to you either.
This can seriously impact your transfer rates: you are advised to check your port forwarding to resolve the issue.
[Reply]
Harrison 16:07 18th June 2009
Nice. I was getting excited about being close to 1TB, but you already are double that amount. Hmm...
I have been a Ruby member for some time though as my ratio has been above 2.1. Although I've dropped back to Platinum at the moment because of updating my Amiga TOSEC ISO sets and that took a hit to the ratio. It is building back up though and is already as 2.02 so should be back to Ruby by next week.
Regarding the Connectable message. This is due to port forwarding on your router or the firewall on your PC. Check your PCs IP address using the commandline and the IPConfig command. Once you know that set port forwarding on your router. Set the port that you have uTorrent using and forward that port to your PCs IP address.
If that doens't fix it, also make sure the firewall on your PC isn't blocking the port uTorrent is using.
[Reply]
Demon Cleaner 16:17 18th June 2009
Originally Posted by Harrison:
Regarding the Connectable message. This is due to port forwarding on your router or the firewall on your PC. Check your PCs IP address using the commandline and the IPConfig command. Once you know that set port forwarding on your router. Set the port that you have uTorrent using and forward that port to your PCs IP address.
If that doens't fix it, also make sure the firewall on your PC isn't blocking the port uTorrent is using.
My PC is running 24/7 for years now, and I didn't change anything, so why should my port forwarding have changed?
[Reply]
Harrison 16:44 18th June 2009
Sometimes something odd can happen. Has the PC been rebooted at all? That can cause the IP to change if it is being created from the router's DHCP server. Or if the phone line has disconnected itself without you realising.
Annoyingly here we still get odd powercuts and when I turn my download server back on it the IP has always changed, so I then have to edit the port forwarding on the router to match.
[Reply]
xpect 08:46 19th June 2009
Originally Posted by Harrison:
Annoyingly here we still get odd powercuts and when I turn my download server back on it the IP has always changed, so I then have to edit the port forwarding on the router to match.
Does your router support uPNP? If yes you should activate it because all major Torrent client support that feature and when your DHCP network ip changes the router automatically makes the port forwarding using the nPNP that the client sends.
If uPNP is not supported on your router, other solution is to use fixed ip for your torrent server. This way you're set to never have to re-config nothing again.
[Reply]
Demon Cleaner 12:38 19th June 2009
I have a fix IP, this is the first time it happens, and my PC was obviously rebooted more than once during that time.
[Reply]