Just in case you have an Android Smart-phone with a 1Ghz processor or better, you maybe interested to know that MAME has landed with a bang all be it 0.37.
It's the same one on iOS iPhone but now ported to Android.
While current MAME can be built on Android if you aren't stupid, this is not that. This is 0.37 from 10 years ago with some lipstick applied. Keep your expectations low and you'll probably have a good time (at least on devices with hardware buttons - on a touchscreen, this is basically useless). Just don't even think about asking for support for it here or on MAMETesters.
> Good but this is 0.37 from 10 years ago so I will skip it. Buy laptop instead of this > not quite powerful Android.
I don't want to discourage people from trying it - if you have a capable device, you oughta see if it does what you want. 0.37 didn't suck exactly, it's just much older than I'd use as a base to target 1 GHz devices (somewhere in the 0.8x range was probably the sweet spot for 1 GHz PCs).
> For whatever reason it is, it seems for many portable devices, the only choice is a > 0.3X version only.
It's called "laziness". On the GP32/GP2X, yes, you needed a 0.37 version as those were 150/200 MHz devices. On 1 GHz devices, rebasing is a better idea, but instead everyone's just porting the GP2X version around.
> The new wave of NVIDIA® Tegra™ 2 based tablets and now phone devices with the same > chips are very powerful.
That's GPU power, not CPU. If someone backports HLSL to this thing, that'll be relevant (or you can play on a "PenTile" device where they don't have all 3 subpixels for each pixel and get a similar effect for free ;-) Otherwise, the Tegra 2 isn't all that interesting on CPU loads. Kal-El might be.
Sweet- 10 tokens for a buck! Just a dime per credit... Seriously, speaking of credit, I give them some to try and give the arcade experience, but I would rather just pay the $1-3 outright for the game and infinite credits.
I would need a proper game controller though- playing by touch-screen is just not fun.
Is it just me, or are these 'phone MAME' builds a complete waste of time? Interesting from a technical standpoint, but totally not worth it from the age of the source code they use, and the platform it's on.
When will people finally outgrow the smartphone fad? Aside from sending/receiving calls (e.g. the actual design principal of a mobile phone), they are just pointless, expensive, poor quality computing devices with no future and are obsolete after 2 weeks. If it wasn't for today's youth continually buying them there would be no mobile telecommunications companies left out there to keep ripping people off with 1995-standard download rates (compared to modern broadband which is generally unlimited or 20GB+). I'm shocked how they still even charge for texts (SMS etc), considering there have been completely free PC messaging programs like MSN for almost 2 decades, then you also have vendor lock-in (e.g. giving free or discounted texts only to people who are using the same company, or the inability to switch companies without a stupid contract or $$$$). The sooner everyone throws them out for good, the better.
Same with the Apple 'i' fads, the iPad is an all-in-one system, yet it completely lacks the most needed item for computing, a decent input device (yet, people insist on putting games on it, then complain that the emulator is uncontrollable so they blame the devs for not making it iPad/iPhone compatible from the beginning).
Now... why can't I run brand new PS3 games at full speed on an iPhone, people? Whilst running them in full 1080p despite having a 3 inch screen with about 20% of the total pixels available.
> > The new wave of NVIDIA® Tegra™ 2 based tablets and now phone devices with the same > > chips are very powerful. > > That's GPU power, not CPU. If someone backports HLSL to this thing, that'll be > relevant (or you can play on a "PenTile" device where they don't have all 3 subpixels > for each pixel and get a similar effect for free ;-) Otherwise, the Tegra 2 isn't all > that interesting on CPU loads. Kal-El might be.
I'm interested to see what can be done with the dual core processor machines with NVIDIA® Tegra™ 2. I'm buying an ASUS Transformer tablet soon for that very reason and maybe my next mobile phone when they come to market.
I'm sure there is enough power there to do most things I personally love to play in MAME. Of course Model 2 would be awesome, but at the moment playing Mr Do, Donkey Kong, Pac-Man, Joust, Popeye, New Zealand Story and many other true classic machines from the 80's, I'm loving it.
For me, they are the best time wasters that have simple game-play you can play on the train/bus stop on the way to work and back.
Most people that get a smart phone have unlimited text/picture message/video messaging on their contract. Alot of people even have unlimited data. As for the contract, I'd rather sign a 2yr contract and pay $150-200 for the phone instead of flat out buying it for $600+, it's not like I plan on changing companies all the time.
And they aren't going anywhere. It's very handy to have a internet capable device everywhere you go. Kids are growing up with them now, so they will continue to want them.
As for the touch screen, it's all dependant on what you are using it for. For alot of the stuff I play on my phone, it's the best input method I could think of. Trackballs are horrible inputs for some games, but essential for others, the same concept applies to touch screens.
Alot of newer phones are 960x540 resolution with 1GHz dual core processors, it may not be HD, but it's far above most portable gaming systems. And on Android you can get an app to connect a PS3 controller to your phone via bluetooth for better gaming support
> I'm interested to see what can be done with the dual core processor machines with > NVIDIA® Tegra™ 2.
Helpful tip: don't buy a T2 device now - wait for the quad-core Nvidia Kal-El in about 6-8 weeks. *That* should be a chip worth remembering how to type circle-R for.
Yup. Pretty much anything that has or could reasonably use a touchscreen is going to be taken over by phones/tablets. When Korg, Moog, Yamaha, Fairlight, and Native Instruments all make pro-quality iOS synth and drum machine apps it's definitely not a fad.
I'm kind of surprised by some of the attitudes expressed on this thread. Too many points to make, so I'll try to summarize.
Sometimes building a program on a platform isn't about whether it's worthwhile or not, sometimes it's just about discovering whether it can be done. Sometimes it's even just about personal accomplishment.
Yes, it's based on 0.37 like all the other MAMEforAll builds. MAMEforAll is a fork of MAME, maintained for it's portability. Just because it's "old" doesn't mean it's "bad". Lots of emulators get ported in this fashion (e.g. FCEU, SNES9x, etc.)
Yes, mobile gaming still leaves a lot to be desired. But that's why I bought the Xperia Play. I fricken love this thing, and now that MAME is available for it, that's the final nail in the coffin for my GP2X. Even without the gamepad controls, the 80s games that this MAME faithfully emulates are not so complicated that an on-screen control pad can't suffice.
Convergence is the name of the game. PCs, phone, tablets... they're all converging into one ubiquitous device. Sure, phones are bit on the slow side compared to PCs today, but don't bet on that being true in less than a decade.
It just seems like a lot of people are expressing the thought that if they don't think it's worthwhile, it should never be attempted. And to me, that sort of flies in the face of MAME's philosophy.
> Yes, it's based on 0.37 like all the other MAMEforAll builds. MAMEforAll is a fork > of MAME, maintained for it's portability. Just because it's "old" doesn't mean it's > "bad".
No, it just means Donkey Kong has wrong colors, incorrect sound, a few pixel-off glitches, and a slightly incorrect gameplay speed. Most people probably won't notice, but you don't want to train to beat Steve Wiebe on it either. MAMEdev has not sat still on "the true classics" in the last 10 years. In that time nearly all the major classics have been improved in some way or another: Pac-Man, DK, Space Invaders, Galaga, Gyruss, Mappy, just to name a few, have all improved.
And for the record, I am fine with MAME4All on the GP2X. That machine has CPU power roughly equivalent to the average PC when MAME 0.37 was a going concern. I just think that faster devices (1.5 GHz quad core phones by the end of the year) deserve a newer, more accurate MAME. To the extent that people unfamiliar with desktop MAME are going to play this on their phones, it's damaging our reputation a little.
> Yes, it's based on 0.37 like all the other MAMEforAll builds. MAMEforAll is a fork > of MAME, maintained for it's portability. Just because it's "old" doesn't mean it's > "bad". Lots of emulators get ported in this fashion (e.g. FCEU, SNES9x, etc.)
It's not that it's old, it's more on the prehistoric side. It would be like porting Windows 3.1 to a device simply because it has less overhead than a later GUI system, or it's simply easier to do (not that the actual source code is available, just an example though). If the iMAME4all group had another look at later versions, they would be amazed to find how some of them would still run at a reasonable speed on modern devices.
With those 1980s games you mention, just about every game since 0.37 has been significantly improved in terms of emulation, for example Bubble Bobble's gameplay fixed after its MCU code was extracted via decapping, discrete sound emulation instead of simulation using recorded samples, hundreds of PALs, GALs, PICs and MCUs dumped/decapped, original versions which may have only been available as bootlegs in 0.37 (or not working due to encryption/protection, or just in the too hard basket at the time), and games which were simply not dumped or acquired when the 0.37 BETA cycle was out 11 years ago.
I would imagine it would actually be more difficult to maintain or update such an old release these days, especially when it comes to adding games or bug fixes from much later versions of MAME - the core and source design has been changed many times in the past decade, for example the move to Win32 instead of pure MS-DOS, the 0.107 video update, two evolutions of the cheat system (0.60 32-bit DAT and 0.126 XML), the recent jump to C++ code (and MESS-in-MAME, half a million shoddy gambling games...)
"Same with the Apple 'i' fads, the iPad is an all-in-one system, yet it completely lacks the most needed item for computing, a decent input device (yet, people insist on putting games on it, then complain that the emulator is uncontrollable so they blame the devs for not making it iPad/iPhone compatible from the beginning).
Now... why can't I run brand new PS3 games at full speed on an iPhone, people? Whilst running them in full 1080p despite having a 3 inch screen with about 20% of the total pixels available."
Well, this might be just what your looking for. Pre-loaded up with some PS3 games! And check out the controller.
> Do you know if there is a config file or any way to point it to other folders for > roms? > > \ROMs\MAME4all\roms is currently the only place it will look.
It's been requested, but the application is created for use for MAME noobs as well as veterans. It also creates the other directories like MAME should like Artwork, Samples etc. In fact MAME4droid is the only current MAME emulator to my knowledge on Android that uses the Samples and other aspects of external files.
Btw, version 1.1.1 was released the other day with performance enhancements for low end devices.
> No, it just means Donkey Kong has wrong colors, incorrect sound, a few pixel-off > glitches, and a slightly incorrect gameplay speed. Most people probably won't notice, > but you don't want to train to beat Steve Wiebe on it either. MAMEdev has not sat > still on "the true classics" in the last 10 years. In that time nearly all the major > classics have been improved in some way or another: Pac-Man, DK, Space Invaders, > Galaga, Gyruss, Mappy, just to name a few, have all improved.
I'm curious RB. My understanding of the MAME code base is very limited, but I understand enough to know that the drivers have undergone many architecture revisions. Nevertheless, I could still be talking completely out of my ass here... Would I be correct in assuming that you can't take (for example) the current Donkey Kong driver and replace the one in the 0.37b5 source, and expect it to compile, much less work? I think part of what prevents MAME4All from adopting the improvements may be a lack of understanding on how to take the drivers in their current form, and retro them back to 0.37. As for why someone doesn't take 0.143 source code and adapt it to Android, would I again be correct in assuming that MAME was more portable (in the compiler sense) back in 0.37 than it is today? I thought modern MAME leverages x86 and x64 architecture much more so today than it did in the past.
> > No, it just means Donkey Kong has wrong colors, incorrect sound, a few pixel-off > > glitches, and a slightly incorrect gameplay speed. Most people probably won't > notice, > > but you don't want to train to beat Steve Wiebe on it either. MAMEdev has not sat > > still on "the true classics" in the last 10 years. In that time nearly all the > major > > classics have been improved in some way or another: Pac-Man, DK, Space Invaders, > > Galaga, Gyruss, Mappy, just to name a few, have all improved. > > I'm curious RB. My understanding of the MAME code base is very limited, but I > understand enough to know that the drivers have undergone many architecture > revisions. Nevertheless, I could still be talking completely out of my ass here... > Would I be correct in assuming that you can't take (for example) the current Donkey > Kong driver and replace the one in the 0.37b5 source, and expect it to compile, much > less work? I think part of what prevents MAME4All from adopting the improvements may > be a lack of understanding on how to take the drivers in their current form, and > retro them back to 0.37. As for why someone doesn't take 0.143 source code and adapt > it to Android, would I again be correct in assuming that MAME was more portable (in > the compiler sense) back in 0.37 than it is today? I thought modern MAME leverages > x86 and x64 architecture much more so today than it did in the past.
... Last I checked, modern (SDL) MAME still built and ran on PowerPC chips and even PS3's...
Nope, that's just the 4G version of the Xperia Play, I've got the 3G one here, it does PS1 emulation only.
Luckily someone discovered (search for PSXperia) how to rebuild any PS1 game into the existing Crash Bandicoot game that comes with it, so now many PS1 games can be run on the device (until Sony does something to stop it!).
> Helpful tip: don't buy a T2 device now - wait for the quad-core Nvidia Kal-El in > about 6-8 weeks. *That* should be a chip worth remembering how to type circle-R for.
Thanks for the heads up!
I've just Google'd it and the specs are amazing for a mobile device:-
Quad-core ARM Cortex-A9 MPCore, up to 1.5 GHz Ultra Low Power GPU mode 40 nm technology Video output up to 2560×1600 NEON instruction sets from ARM 1080p H.264 High Profile video decode 12-Core Nvidia GPU with support for 3D stereo (12 unified shaders)
> Fair warning: > > While current MAME can be built on Android if you aren't stupid, this is not that. > This is 0.37 from 10 years ago with some lipstick applied. Keep your expectations low > and you'll probably have a good time (at least on devices with hardware buttons - on > a touchscreen, this is basically useless). Just don't even think about asking for > support for it here or on MAMETesters.
For the record, the current MAME can't be built on Android for a number of reasons:
1) Android NDK doesn't support GNU Makefiles, you have to use their makefile system 2) The android makefile system doesn't support making archives which aren't static libraries 3) The naive approach of making a single Android.mk file with all of the MAME source in it does not work because the android build system has a hard limit on the number of objects in a library/executable. 4) The android build system uses file extension exclusively to determine whether code is C or C++, and MAME violates this by putting C++ code in .c files.
> yup. And since pretty much all phone CPU's use ARM architecture (neither x86 nor > x64), I'm not sure what the point of that was anyway
Point is, current MAME is more portable than old-skool MAME - it runs on anything, including esoteric x86 OSen like OS/2, and *NIX on RISC CPUs (Solaris/SPARC, Linux/PPC, etc.).
It's easier to carry a phone around (and the fact that I would be carying a phone anyway)than a laptop or something. Internet-on-demand has a plethora of uses. Not to mention GPS, improving picture/video quality, app functionality... I could go on and on.
I've spent a few months shy of HALF OF MY LIFE in the Navy and I go to sea a lot. Watching movies on a tiny screen is a turn-off for most, but convenient for me. I can just roll over and go to sleep with it still in my rack (and it duals as an alarm clock). Can't do that with a laptop or I'd break the LCD in my sleep.
Not that I own an iPad, but it actually does have *decent* input devices. A keyboard dock, for one, and a controller-like gizmo that you can 'stick' to the screen.
> and you'll probably have a good time (at least on devices with hardware buttons - on > a touchscreen, this is basically useless). Just don't even think about asking for > support for it here or on MAMETesters.
RB,
Have you seen this?
I'm sure an Android tablet version won't be too far behind.
> That wasn't in regards to Stiletto's post but > I thought modern MAME leverages x86 and > x64 architecture much more so today than it did in the past.
Well it does leverage x86 - we have x86 DRCs for PPC, MIPS, SH2, etc. and there's a bunch of SSE code for bilinear filter, etc. but none of this has been done at the expense of portability.
> RB, > > Have you seen this? > > > I'm sure an Android tablet version won't be too far behind.
It might be something I would be willing to display on the mantle next to picture frames, but I would never game on that.
When I'm on the go it's because I'm busy and there is crap to be done, no time for playing games. When those tasks are finished nothing beats MAME in my PC environment, where I can be comfortable, except standing up at a custom built cab
> > That wasn't in regards to Stiletto's post but > > I thought modern MAME leverages x86 and > > x64 architecture much more so today than it did in the past. > > Well it does leverage x86 - we have x86 DRCs for PPC, MIPS, SH2, etc. and there's a > bunch of SSE code for bilinear filter, etc. but none of this has been done at the > expense of portability.
Yes. MAME out-of-the-box supports more OSes and more architectures than it ever has, and there's a "NOASM=1" flag that should completely disable all CPU-specific code. At that point you just need a reasonable C++ compiler and SDL. I expect ARM to get explicit support in the future with both Windows 8 and major Linux distros promoting it to tier-1 support.
> Thanks for the heads up! > > I've just Google'd it and the specs are amazing for a mobile device:-
Yup. And they've just shown Windows 8 running on it this week. Nvidia believes it has enough power to support nearly direct ports of high-end PC games circa 2009. If the power consumption stays reasonable that's going to be amazing.
> > and you'll probably have a good time (at least on devices with hardware buttons - > on > > a touchscreen, this is basically useless). Just don't even think about asking for > > support for it here or on MAMETesters. > > RB, > > Have you seen this?
> Fair warning: > > While current MAME can be built on Android if you aren't stupid, this is not that. > This is 0.37 from 10 years ago with some lipstick applied. Keep your expectations low > and you'll probably have a good time (at least on devices with hardware buttons - on > a touchscreen, this is basically useless). Just don't even think about asking for > support for it here or on MAMETesters.
This is from .37 10 years ago when you didn't need a quad core pc to play donkey kong. Yes Mr. Belmont we know. We also know that it isn't made from the recent SDLMame, otherwise the comment "stupid" would not appear.
It works Mr. Belmont, the same could be said for the Dreamcast Port, or the PSP port, as well as the Arm 200 port. My goodness and we can play donkey kong on the bus or waiting in some god forsaken line at the supermarket.
Now if you just removed all the mahjong games and other ***** on the current build optimized for Android, it might run donkey kong in 30 years time. Just kidding, maybe in 5 years. We should have eight cores by then.
I'm just glad there is a port for the Android Platform, on a build that was created by so many talented programmers, including the talented work of a person I cannot unfortunately mention here.
If you have a Android capable of running MAME4Droid - get yourself a Zeemote. They are cheap enough.
Has anyone managed to get it working on the Hannspad with a cooked 3.0 OS yet?
> For the record, the current MAME can't be built on Android for a number of reasons:
And yet, by my count half a dozen people have done it, not including yourself.
Less interference with my simplifying things for end users and more .diffs to fix those problems, please. I like that you try to do things the right way. That's rare in hobbyist emulation.
> > Thanks for the heads up! > > > > I've just Google'd it and the specs are amazing for a mobile device:- > > > Yup. And they've just shown Windows 8 running on it this week. Nvidia believes it has > enough power to support nearly direct ports of high-end PC games circa 2009. If the > power consumption stays reasonable that's going to be amazing.
It should burn a hole in your pocket when it comes out, and probably burn your hands running the games. The snapdragon runs hot for just a 20 minute HD video and that is through the leather case. I have lost two memory cards to it already.
Good luck with that new gen tablet. You have a link to that Windows 8 tidbit? M$ just said it would not support ARM in any near future.
> Now if you just removed all the mahjong games and other ***** on the current build > optimized for Android, it might run donkey kong in 30 years time.
You really have learned nothing I've tried to teach you. I hope you don't retain this poorly on your coursework. (I'm not angry, just sad. I want people to understand why things are and how they work).
> Good luck with that new gen tablet. You have a link to that Windows 8 tidbit? M$ just > said it would not support ARM in any near future. How things change.
Recently? MS announced nearly a year ago that they had ported to ARM, and it's the big excitement at this week's BUILD conference.
Here's one video of Windows 8 on Kal-El, you can find many more
> Good luck with that new gen tablet. You have a link to that Windows 8 tidbit? M$ just > said it would not support ARM in any near future. How things change.
Why do people refer to Microsoft as M$? Are you jealous that they are a company that makes money with products people freely buy? Seems juvenile to me. Gotta run. I have to go fill the car with GA$ before the jackoffs raise the price again!
> > Thanks for the heads up! > > > > I've just Google'd it and the specs are amazing for a mobile device:- > > > Yup. And they've just shown Windows 8 running on it this week. Nvidia believes it has > enough power to support nearly direct ports of high-end PC games circa 2009. If the > power consumption stays reasonable that's going to be amazing.
You do realize that you can download the Developer's Build from Microsoft if you want, and try Metro. I downloaded it, and then found out I didn't have any blank DVDs, need to pick some up. You do need a blank hard drive, since it wants to have a clean install, also you can't uninstall it.
> > > Thanks for the heads up! > > > > > > I've just Google'd it and the specs are amazing for a mobile device:- > > > > > > Yup. And they've just shown Windows 8 running on it this week. Nvidia believes it > has > > enough power to support nearly direct ports of high-end PC games circa 2009. If the > > power consumption stays reasonable that's going to be amazing. > > You do realize that you can download the Developer's Build from Microsoft if you > want, and try Metro. I downloaded it, and then found out I didn't have any blank > DVDs, need to pick some up. You do need a blank hard drive, since it wants to have a > clean install, also you can't uninstall it.
Sounds perfect to install in a virtual machine! I might give it a try later.
> You do realize that you can download the Developer's Build from Microsoft if you > want, and try Metro. I downloaded it, and then found out I didn't have any blank > DVDs, need to pick some up. You do need a blank hard drive, since it wants to have a > clean install, also you can't uninstall it.
> > You do realize that you can download the Developer's Build from Microsoft if you > > want, and try Metro. I downloaded it, and then found out I didn't have any blank > > DVDs, need to pick some up. You do need a blank hard drive, since it wants to have > a > > clean install, also you can't uninstall it. > > The public developer release doesn't support ARM.
True, but there isn't much you could run, if it did support ARM, since x86 code doesn't run on the ARM version.
> > Good luck with that new gen tablet. You have a link to that Windows 8 tidbit? M$ > just > > said it would not support ARM in any near future. How things change. > > Why do people refer to Microsoft as M$? Are you jealous that they are a company that > makes money with products people freely buy? Seems juvenile to me. Gotta run. I have > to go fill the car with GA$ before the jackoffs raise the price again!
I use M$ due to the $upport cost$ Micro$oft like$ to charge.
We get a patch and our application goe$ tit$up. We do control te$t it fir$t but when it$ an unexpected i$$ue...
I will have to tell our QA guy$ it'$ childi$h to use that name. I'm $ure I'll get $ome laugh$ from that.
Quote: To the extent that people unfamiliar with desktop MAME are going to play this on their phones, it's damaging our reputation a little.
Why would it damaging your reputation? Are you implying that the developers merits on Pre .37 builds are somewhat inferior to the current caretakers of Mame?
Should we not celebrate the efforts of the developers such as Neil Bradley, Zonn Moore and the father of the project, Nicola Salmoria to the new and future contributors of Mame?
Did you work on Mame during this period Mr. Belmont? Is that where you draw on that reflection? Or is it due to all those fancy additions like HLSL that makes the current Mame more superior for the mass audience?
> True, but there isn't much you could run, if it did support ARM, since x86 code > doesn't run on the ARM version.
It's the *developer's release*. The point of posting it is exactly to kickstart that porting.
Of course, Metro-style C# apps made in the DR will also run on ARM, but this doesn't do much for conventional Win32/Win64 apps that might want to run on Win8 ARM.
Back here in real life, I was implying that later version numbers of software are generally improved compared to earlier ones. I had no idea this was controversial - is there some secret society claiming Windows 1.0 is better than Windows 7? Is it insulting to the Windows 1.0 programmers to say so?
Quote: > Back here in real life, I was implying that later version numbers of software are > generally improved compared to earlier ones.
No you didn't. You implied that the previous MAME versions were inferior and could threaten your reputation when adopted through other channels. Like Android ports.
I can understand that, but it implied embarrassment on your part. Then you go off and make that reply.
Windows 1.0 and Windows 7? Another gem from Mr. Belmont.
What would be more apt? OS2 and NT3x? Secret Society for Windows 1.0? A Gem (sic) conspiracy, no doubt.
We never left real life Mr. Belmont. I would instead feel proud to be working on such a project that is challenging and suited to all programming talents. I'm sure that is what you meant.
Your reputation is at peril because of an earlier work, which you base your future and improved work on. Due to its availability on several mass produced platforms.
The previous MAME versions ARE inferior. The emulation is far less accurate back then compared to now. His comparison makes complete sense. People that don't follow MAME don't know that its based on a decade+ old version of MAME, and can get the idea that the PC version is the same.
> No you didn't. You implied that the previous MAME versions were inferior and could > threaten your reputation when adopted through other channels. Like Android ports.
> I can understand that, but it implied embarrassment on your part. Then you go off and > make that reply.
There is no embarrassment. There is simply the fact that MAME emulates nearly every game that was in 0.37 more correctly in at least one aspect now than it did 10 years ago. 0.37 was a state-of-the-art piece of software in 2001. It's not in 2011, and it is not an accurate or correct representation of the current state of MAME or of hobbyist emulation in general. WinUAE also got a lot better since 2001, for instance. But the WinUAE Android port is based on recent code (I have it on my EVO 4G to run demos - trying to play games is of course not happening on the touchscreen).
> What would be more apt? OS2 and NT3x? Secret Society for Windows 1.0? A Gem (sic) > conspiracy, no doubt.
On a 10 year time scale, I like Windows 3.0 (the best available in 1991) vs. Windows XP (the best available in 2001). MAME's evolution is not quite as obvious to end users (although the on-screen display UI has changed significantly), but internally it's every bit as drastic as going from segmented DOS-based Win16 to flat-model NT kernel Win32.
> Your reputation is at peril because of an earlier work, which you base your future > and improved work on. Due to its availability on several mass produced platforms.
You're trying to insert drama where there is none. Iterative products improve over time. It's as true for software as it is for hardware.
You can always install to a VHD, like I did. I've hit a few interesting bugs in Win8 already, though I'm going to keep working with it. The Metro dev system feels unpleasantly like the existing layout scheme used in pre-tablet Android when you add new form factors like tablets. I'm not sure how I feel about this.
I'm thinking that if it were implemented, it'd have to be yet another configuration option to toggle how keyboards were handled-- which would then lead to people turning it on blindly and asking all sorts of support questions about why other keyboard-sending joystick devices or keyboards were no longer working as they should.
That reason alone makes me think it should be handled outside MAME or as perhaps a platform-specific option as compared to core.
That assuming that anyone wants to code it. I'll be waaaaay over here not writing code for that puppy, myself. I don't even have one to test with, anyway.
Heads-up, a lot of people are having problems getting 8 to run in a VM. Some reports claim that one cause is not having VM extensions turned on for your CPU, but the reports are scattered enough that there could be other reasons too.
I swear, you're always LOOKING for a false controversy to turn into a fight, aren't you?
No I do not consider my comments in any way combative with regards to Mr. Belmont. If any Moderator notices comments which are abusive in this or any message board you run the risk of being banned, and rightly so. I do get the odd warning though.
I believe Mr. Belmont has enough patience to allow for my questioning, and his responses are always worth the effort. There has been a time when I have been completely wrong, and given Mr. Belmont his due credit.
So in answer to your comment. No.
In the short space of time, I have come to respect Mr Belmont's responses to my posts, but there are times when he slips out of those odd gems, that simply captivates, and requires additional attention.
The build .35 (I think that is the set being used for the Mame4All forks) works, and plays the games that a 14 year old would enjoy, or a 40 year old would remember on his phone. Maybe it is a message to the Mamedevs?
> The build .35 (I think that is the set being used for the Mame4All forks) works, and > plays the games that a 14 year old would enjoy, or a 40 year old would remember on > his phone. Maybe it is a message to the Mamedevs?
My dear Troll, It says 0.37 in the first sentence of this thread.
I don't know much about these phones and such, but the Mame4All port on the PSP is horrible, and pretty much unplayable. Then again, what can you really expect from a 333 MhZ CPU.
I think the concerns about this port have been already spoken about in this thread. Why is it necessary for you to continue arguing about it?
> My dear Troll, > It says 0.37 in the first sentence of this thread. > > I don't know much about these phones and such, but the Mame4All port on the PSP is > horrible, and pretty much unplayable. Then again, what can you really expect from a > 333 MhZ CPU. > > I think the concerns about this port have been already spoken about in this thread. > Why is it necessary for you to continue arguing about it?
Because, like you said, he is a fucking Troll. I wish he would get banned. I'll bet he is a real mother fucker to be around with his combative attitude and all.
Index 
Threaded 
MAME4droid - v1.02 - MAME Emulator on Android
Reply
[Re: 
