ZSNES 64Bit stuff

Kushan · Post by **Kushan** » Sat Nov 13, 2004 1:51 am

Hey all.
I recently built meself a nice new system.

Specs
1Gb of RAM
Radeon 9800 (256Mb)
200GB SATA
and most importantly....
Athlon 64 3400+

I noticed that ZSNES has a release designed for 64bit CPU's and I'd like to test it out a fair bit since nobody else here seems to have (or at least I can't find ANY threads on the subject here).
Thing is though, I'm not quite sure how I should go about Benchmarking ZSNES 64 or how to properly compare it to the 32bit version. Anyone here got any suggestions or pointers on how I should go about it?
Thanks in advance!

EDIT: I should probably mention I have XP x-64 installed on a seperate HDD, and installed whatever drivers and stuff I could find, so I have sound and stuff.

ipher · Post by **ipher** » Mon Nov 15, 2004 1:06 am

Well, the 64-bit version is just supposed to be compatible with 64-bit processors. Pagefault said somthing about NASM-compiled programs (ZSNES) not working right with them, so the 64-bit version is compiled using YASM. There shouldn't be any real speed improvements since no new code was added.

Do the regular WIPs work with your computer?

michael flatley · Post by **michael flatley** » Mon Nov 15, 2004 3:49 am

OMG!!! Overbloated system alert! Sound the alarms! Quick, everyone post on how they have a 100MHz processor and anything more is overbloated!

Sorry about the sarcasm... Anyway, the good news is that it shouldn't really matter if you are getting the 64-bit enhancements or not. For SNES emulation your system is running the emulator as fast as it will go with or without 64-bits.

ThunderClaw · Post by **ThunderClaw** » Mon Nov 15, 2004 3:55 am

michael flatley wrote:OMG!!! Overbloated system alert! Sound the alarms! Quick, everyone post on how they have a 100MHz processor and anything more is overbloated!

I would like to note here how he didn't brag about his watercooled epenis and pointless hard drive access times, among other things.

Joe Camacho · Post by **Joe Camacho** » Mon Nov 15, 2004 4:00 am

ThunderClaw wrote:
michael flatley wrote:OMG!!! Overbloated system alert! Sound the alarms! Quick, everyone post on how they have a 100MHz processor and anything more is overbloated!
I would like to note here how he didn't brag about his watercooled epenis and pointless hard drive access times, among other things.

Also, at least he is willing to help with the development of zsnes, instead of bitching about specific requests.

Kushan · Post by **Kushan** » Mon Nov 15, 2004 4:39 am

Both the latest WIP (October 24) and the 64bit version work fine on my system, in fact they're identical in how they work.
I tested The Legend of Zelda (Simply cuz it's my favorite game), Star Fox (For the SuperFX) and Mario Kart (Because of MODE7) and they all performed identically on both versions at different resolutions and video settings (with and without 2XSAI and stuff) and I couldn't detect any difference in either build.
Admittadly I only did a quick test, but as far as I could tell they're both the same.

Incidently, both versions work the same when on regular Windows XP AND when on XP x64.

Oh and as for bragging, I used a 700Celeron with 256Mb of RAM and a Geforce2Mx PCI for years and knew what it was like when people bragged about their Uber systems, hence I don't do it

Hope that's some help to you guys ^_^

EDIT: Oh yeah, since I don't know the diffference between YASM and NASM (I aint no programmer), this might sound a little dumb, but I'm slightly confused about exactly what the 64bit version is meant to be.
What I mean is, is it coded in a different way so that it works on both 32bit and 64bit CPU's or is it 64bit ONLY or what? Just the readme isn't very clear and the Help>about panel in the 64bit version still says Win32, plus it still runs on regular XP...

illegal eagle · Post by **illegal eagle** » Mon Nov 15, 2004 12:36 pm

It would be nice if there'd be a FPS counter that works when "auto frame rate" is disabled... would allow benchmarking.

ipher · Post by **ipher** » Wed Nov 17, 2004 2:20 pm

Kushan wrote:EDIT: Oh yeah, since I don't know the diffference between YASM and NASM (I aint no programmer), this might sound a little dumb, but I'm slightly confused about exactly what the 64bit version is meant to be.
What I mean is, is it coded in a different way so that it works on both 32bit and 64bit CPU's or is it 64bit ONLY or what? Just the readme isn't very clear and the Help>about panel in the 64bit version still says Win32, plus it still runs on regular XP...

Well, basically pagefault got (apparently incorrect) information that programs compiled with NASM (the assembler we use) won't work on 64-bit processors. So we tried a differant one (YASM) that is known to be compatible.

We did have a topic dedicated to the two experimental releases (Super-Optimized and 64-bit Compatible), unfortunately, i don't think anybody had an Athlon 64 yet as they were still pretty new. Its nice to know that the original releases work on it, so we don't need to mess with YASM anymore.

illegal eagle wrote:It would be nice if there'd be a FPS counter that works when "auto frame rate" is disabled... would allow benchmarking.

From what i remember, the FPS counter is directly tied to the Auto Frame Rate code. There used to be a bug to enable the FPS counter without AFR on (me and another user reported the FPS counter looping past FF), and while the FPS seemed to be at least partially correct (higher res, more filters, ect made the numbers "smaller"), the devs assured us that it could not be trusted. Somthing to look into tho (i forgot all about that until this post

)
-ipher

kieran_ · Post by **kieran_** » Wed Nov 17, 2004 6:27 pm

ThunderClaw wrote: his watercooled epenis .

Hah! I actually laughed out loud at that!

Michael Flatley: You are a fucking idiot.

Kushan · Post by **Kushan** » Wed Nov 17, 2004 6:32 pm

Ooooo, flame war ahoy!

Well I've certainly had no problems running ZSNES of either builds, but don't forget my CPU is 32 and 64bit compattible anyway, a fully 64Bit CPU may have problems, but since the WIP builds seem to work on XP x-64 (Where I believe the CPU runs only in 64bit mode) I'd say it's a good guess that you don't need to worry about YASM.

adventure_of_link · Post by **adventure_of_link** » Wed Nov 17, 2004 7:42 pm

Kushan wrote:Ooooo, flame war ahoy!

*cough*lock the thread*cough*
J/K, LoL

cdbsi · Post by **cdbsi** » Thu Nov 18, 2004 6:39 am

michael flatley wrote:OMG!!! Overbloated system alert! Sound the alarms! Quick, everyone post on how they have a 100MHz processor and anything more is overbloated!

Sorry about the sarcasm... Anyway, the good news is that it shouldn't really matter if you are getting the 64-bit enhancements or not. For SNES emulation your system is running the emulator as fast as it will go with or without 64-bits.

The only thing in his computer that could be considered bloat would be his RAM, but how are you to know if he doesn't work with rendering programs or anything.

I actually recently built a similar system. Here are the specs:

AMD Mobile Athlon-XP 2600+ Barton IQYHA-0434APAW @ 236x11 [2600MHz ~ 3800+ Equivalent]
MSI K7N Delta2 Platinum nForce2 Ultra 400 Mobo
Corsair VS512MB400 Value Select 184 Pin 512MB DDR PC-3200 CL2.5
Samsung SyncMaster 955DF 19-Inch FlatScreen Two-Tone Monitor
MSI RX9800PRO-TD128SP, ATI Radeon 9800 Pro Video Card, 128MB DDR, 256-bit, DVI S-Video, 8X AGP
Seagate ST3200822A 200GB 7200RPM IDE Hard Drive
Black Lite-On SOHW-1633S 16X DVD Burner [Dual Layer]
Speeze 5F263B1M3G WhisperRock II CPU Cooler
Black LITE-ON SK-1688A-B Standard Keyboard
Black Microsoft IntelliMouse Optical

Black Enlight Case EN-7250AZ
Logitech Z-2200 THX-Certified Speaker System - 200Watts

I love my new computer.

Post by **badinsults** » Thu Nov 18, 2004 6:47 am

Please stay on topic, kids.

ipher · Post by **ipher** » Thu Nov 18, 2004 10:31 pm

The topic is resolved, so there doesn't need to be any other posts in here unless someone has something useful to add.

Noxious Ninja · Post by **Noxious Ninja** » Thu Nov 18, 2004 10:49 pm

cdbsi wrote:AMD Mobile Athlon-XP 2600+ Barton IQYHA-0434APAW @ 236x11 [2600MHz ~ 3800+ Equivalent]

/me bows before your l33t overclocking skillz

ipher · Post by **ipher** » Sat Nov 20, 2004 1:36 am

actually, AXP Mobile 2600+'s are known to be very overclockable, like, insanely overclockable. Thats prolly how he got those speeds

Noxious Ninja · Post by **Noxious Ninja** » Sat Nov 20, 2004 2:51 am

I know, but that's still extremely good. My 2400+ barely hits 2.4, and can only do 2.33 stable.

Kushan · Post by **Kushan** » Sat Nov 20, 2004 3:26 am

ipher wrote:The topic is resolved, so there doesn't need to be any other posts in here unless someone has something useful to add.

Well Since I seem to be like...the one and only person here who seems to have tested ZSNES on a 64bit system, feel free to drop me an email or whatever at t3h.kitteh@gmail.com if you ever need anything else tested on a 64bit platform, I'm happy to help ^_^

Fentekreel · Post by **Fentekreel** » Sat Nov 20, 2004 5:57 am

I'm running Fedora Core 3 x86-64 and when i compile the source code for the wip pre 1.4 oct 24 i get the following errors:

Generating build information using aclocal and autoconf...
acinclude.m4:10: warning: underquoted definition of AM_PATH_ZLIB
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/auto ... ng-aclocal
acinclude.m4:121: warning: underquoted definition of AM_PATH_LIBPNG
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu

......................and
/usr/bin/ld: skipping incompatible /usr/lib/libz.so when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/libz.a when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.a when searching for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libm.a when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
/usr/bin/ld: skipping incompatible /usr/lib/libc.a when searching for -lc
/usr/bin/ld: warning: i386 architecture of input file `chips/sfxproc.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/fxemu2.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/dsp1proc.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/fxemu2b.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/fxemu2c.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/fxtable.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/sa1proc.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/sa1regs.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/st10proc.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `chips/dsp2proc.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/addrni.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/dma.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/dsp.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/dspproc.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/execute.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/irq.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/memory.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/spc700.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/stable.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/table.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/tableb.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cpu/tablec.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `linux/copyvwin.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `linux/sdlintrf.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `dos/debug.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `dos/joy.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `dos/modemrtn.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `dos/vesa2.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `dos/initvid.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `dos/sw.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `dos/gppro.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `dos/vesa12.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `gui/gui.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `gui/menu.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/makev16b.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/makev16t.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/makevid.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/mode716.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/mode716b.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/mode716d.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/mode716e.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/mode716t.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/mode7.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/mode7ext.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/mv16tms.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/newg162.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/newgfx16.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/newgfx2.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/newgfx.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/m716text.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/2xsaiw.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/procvid.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/sw_draw.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/hq2x16.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/hq2x32.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/hq3x16.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/hq3x32.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/hq4x16.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `video/hq4x32.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `cfgload.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `endmem.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `init.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `ui.o' is incompatible with i386:x86-64 output
/usr/bin/ld: warning: i386 architecture of input file `vcache.o' is incompatible with i386:x86-64 output
rm -f version.o
i'm not really sure what to do ....i notice that the 64 bit version is available for windoze but not for linux?

Thank in advance...

ipher · Post by **ipher** » Sun Nov 21, 2004 5:27 pm

ahh, so i guess its only when compiling that NASM sucks on 64-bit procs...

Try to get YASM and try it with that. I haven't played around with Linux yet, so im not sure how you would have to change the configure stuff. If you feel really crazy, and don't want to mess with config files, you COULD rename YASM to NASM, and see if it'll work (just don't blame me if it somehow screws up your system, remember, i don't use Linux).

Maybe in the future the configure script will be able to detect 64-bit procs and use YASM instead of NASM.

Kushan · Post by **Kushan** » Sun Nov 21, 2004 9:37 pm

Out of curiosity, does YASM not work on 32bit systems or something?

ipher · Post by **ipher** » Sun Nov 21, 2004 10:46 pm

It works fine on 32-bit systems. How else could i use it?

Kushan · Post by **Kushan** » Sun Nov 21, 2004 10:51 pm

So then...why not just use YASM from now on since it's fine on 32bit systems?

Post by **Nach** » Sun Nov 21, 2004 11:46 pm

Kushan wrote:So then...why not just use YASM from now on since it's fine on 32bit systems?

Because it's a change.

ipher · Post by **ipher** » Sun Nov 21, 2004 11:55 pm

YASM doesn't have all of the optimization flags that NASM has (no Super Optimized versions with YASM!), plus NASM is MUCH more popular

ZSNES board

ZSNES 64Bit stuff

ZSNES 64Bit stuff

Install problems....