ZSNES board

xamenus wrote:Aerdan, do you think you could update your first post in this thread? The links in it are broken.

I don't have the tools involved any more [hard drive failure & pagefault decided he didn't want me on his server any more, either], so...

Use the makefile, Luke.

Eternal Lands.

OpenAL is a mess.

OpenGL, on the other hand, isn't all that hard to deal with; all we really need to do is add a Windows SDL port.

[EDIT: Not to mention the fact that OpenAL has a tendency to change its implementation just to break some games. OpenGL doesn't have this problem, however. ]

Unless you have a resolution request. Please.

If by 'simpler' you mean 'stupider', then yes. Hardcoding installation paths ==

I KILL YOU. WIF A BFG10K.

:looks at "Godslayer"'s avatar.

Nicholas D. Wolfwood is cool. You are not. Cease using that avatar immediately.

And post NSRT information, while you're at it. Use 3.3-RC3 plus the frontend if you can't figure out how to use the command line.

apt-get install build-essential
apt-get install libsdl12-dev
apt-get install nasm
apt-get install libpng-dev
apt-get install zlib-dev

additionally, Ubuntu does *not* have 'gmake'; just use 'make'.

Except, um, not. Most people who use ZSNES don't encounter this problem because they don't have ancient hardware that would take except to D modes. That being said, making any sort of video mode changes at this point in time would be pointless, as grinvader is currently working on killing off the ha...

What creaothceann said, plus 512x448 is the best resolution for supporting all possible SNES ROMs. Anything less just won't work.

Not on your life.

I refuse to support hardware that can't tolerate 512x448, on the grounds that said hardware also isn't likely to support anything that uses any of the high-resolution effects that depend on being able to use 512x448.

Windows XP-64 is rather stupid, anyhow. If you want to make the most of your system, you really can't consider Windows until Vista comes out, bare minimum.

Probably.

ZSNES sources shouldn't include one, as they're not completely platform-independent.

Nach would've said something if he minded.

It is not nasm's fault that gcc breaks on initc.c.

Anyhow, yasm is broken in Linux, please don't try to use it.

Agozer wrote:Shut the hell up Aerdan. Since when was it wrong to congratulate someone for a work well done?

You missed the irony in the post, apparently.

Go reread the last line.

Please to be shutting up with the suckup posts already.

They sicken me.

Go find something more constructive to do with your time, like playing games and/or actually using the features our local representative of God gave you.

If you're using GCC 3.4, please don't use -O3 when compiling, unless you also specify -fno-web.

-fweb is included in -O3 and, in GCC 3.4 at least, removes live code.

This may or may not fix the issue with 'recently played ROMs' being [and staying] blank.

Go ahead and post it here.

I have a repeatable crash (or, rather, freeze) bug to report, but before I do, I'd like to make certain it's appropriate. The "properly reporting a bug" announcement topic says to only report bugs on the latest WIP version, and as a member (albeit not a coding member) of an unrelated open...

, then.

See Input Device #1.

Read the fucking documentation.

HT(N)H, HAN(oS;IDCW)D.