Bus Error w/Virtual Jaguar on OS X 10.3.2

[awarlock@eaglec]

Last login: Sun Mar 7 09:44:53 on ttyp1
Welcome to Darwin!
******-******-Computer:~ ******$ cd
******-******-Computer:~ ******$ /Users/llibal/Desktop/virtualjaguar/vj ./vj
Virtual Jaguar GCC/SDL Portable Jaguar Emulator v1.0.6
Based upon Virtual Jaguar core v1.0.0 by Cal2 of Potato emulation.
Written by Niels Wagenaar (Linux/WIN32), Caz (BeOS),
James L. Hammons (WIN32) and Adam Green (MacOS)
Contact: http://sdlemu.ngemu.com/ | sdlemu@ngemu.com

OpenGL driver information :

Vendor : ATI Technologies Inc.
Renderer : ATI Radeon 9800 OpenGL Engine
Version : 1.3 ATI-1.3.4
OpenGL drawmethod : GL_QUAD rendering

OpenGL filters : disabled
Bus error
******-******-Computer:~ ******$

I have been working with Virtual Jaguar v1.0.6 trying to get it work on OS X 10.3.2 with no success thus far. Admittedly, I have not used Terminal at all so it is new to me as well so please bear with me.

I have listed above the Terminal Window response and the problem that I am having. What I do first is doubleclick on the "vj" application to get Terminal to launch whereupon I get a Terminal Window that will not let me do anything. I close that Window down go to the top menu "File" and select "New Shell". I have replaced my name with "******" for privacy purposes. I type "cd" and hit "enter". I then drag and drop the "vj" application on the Terminal Window to establish the path. After that I type "./vj and hit "enter" whereupon a new Window opens up as if the program is trying to launch but after after a second or so, the program crashes and I get the typical Apple window which states: The application vj has unexpectedly quit. The system and other applications have not been affected. etc.

The Terminal Window indicates there is a "Bus error". Right?? I have the "jagboot.rom" in the Bios Folder. Shouldn't the "vj" application launch with a logo or something or do I have to launch a game at the same time.

Where do I place the game.rom files?? I have read that the .jag files need to be renamed to .j64 and have tried that as well. I have Zoop!.j64 and in the Terminal Window I typed ./vj [zoop] and the program tried to launch as described above and crashed again with a "Bus error". I tried ./vj [zoop!] and it didn't do anything at all. Are there specific names for each game file that have to be typed in?? I have an Alien vs Predator (1994).jag file which needs to be renamed .j64 but what do I type in the [**********] for a file like this??

But first I just need to get the program up and running and not crash!!

Any help would be appreciated!! I'm ready to play some Jaguar games on my Mac!! I do have an Atari Jaguar and Cart/CD's but it would be really neat to play AVP, Cybermorph, or Iron Soldier, etc. on my computer!!

Dual 2GHz G5w/512 Meg or Ram, w/ATI 9800 w/128 Meg, and OS X 10.3.2

[gameman733]

i havent used virtual jaguar so this may not be much of a help, but try this

Type in: cd /Users/llibal/Desktop/virtualjaguar/vj
then try: ./vj

if that doesnt work, instead of ./vj try
./vj zoop!.v64

Like i said, ive never used VJ so im probebly not much help. If its a problem with the command then that might fix it.

[Shamus]

Hmm. Did you set things up properly in your vj.cfg file? That's where paths to ROMs, etc. are placed (and it can use relative paths as well). Assuming all is set up properly, all you should have to do is double click on the icon and choose a file from the selector that VJ gives you.

Small side note: 1.0.6 doesn't recognize file formats properly, and I think this is a good reason to officially release 1.0.7 for now. Adam--let me know what needs to be added to CVS for it to be able to compile and run cleanly.

[awarlock@eaglec]

I have the "bios" folder, which contains "jagboot.rom" and "jagcd.rom". I did open the vj.cfg file with BBedit to take a look at it. I did rename the "rom" folder to "ROMs" as I believe it indicates in the ''config". The "ROMs" folder, the "bios" folder, and "vj" are all in the same folder which I named "virtual jaguar".

The "ROMs" folder has avp.j64 and zoop.j64.

What else do I need to do with the "vj.cfj" file? The config file in part says this:

#
# Virtual Jaguar configuration file
#

# Jaguar BIOS options: 1 - use, 0 - don't use

useJaguarBIOS = 0

# Jaguar ROM paths

JagBootROM = ./bios/jagboot.rom
CDBootROM = ./bios/jagcd.rom
EEPROMs = ./eeproms
ROMs = ./ROMs

(I did not include all of the settings from the config file but they are still there.)

When I double click on the "vj" this is the "window" that I get:
Last login: Thu Mar 11 06:08:45 on ttyp1
Welcome to Darwin!
******-******-Computer:~ ******$ /Users/******/Desktop/Emulation/virtualjaguar/vj; exit
Virtual Jaguar GCC/SDL Portable Jaguar Emulator v1.0.6
Based upon Virtual Jaguar core v1.0.0 by Cal2 of Potato emulation.
Written by Niels Wagenaar (Linux/WIN32), Caz (BeOS),
James L. Hammons (WIN32) and Adam Green (MacOS)
Contact: http://sdlemu.ngemu.com/ | sdlemu@ngemu.com

OpenGL driver information :

Vendor : ATI Technologies Inc.
Renderer : ATI Radeon 9800 OpenGL Engine
Version : 1.3 ATI-1.3.4
OpenGL drawmethod : GL_QUAD rendering

OpenGL filters : disabled
logout
[Process completed]

That's all that it does. I cannot access the above window. Is there something in the "vj.cfg" file that I need to change??

Thanks.

[Shamus]

Yeah, what's needed is a 1.0.7 release and for that I need Adam on board since he's our Apple guy. Like I said above, in 1.0.6 file format handling is broken and at this point I think it's important to get that fix out (which is in 1.0.7) and let everything else wait for 1.0.8...

Adam: Once CVS is in a good state for building on the Mac, let me know so I can tag it and do an official release.

[awarlock@eaglec]

Thanks for the help and reply! I really appreciate it!! I'll wait for the next version to come out!!

[Adam Green]

Ok, here's the binary: http://victoly.com/~adam/vj.tgz

Here's a makefile for OS X. Feel free to put this in cvs for others:

#
# Makefile for Virtual Jaguar GCC/SDL Portable Jaguar Emulator
#

# Uncomment the following lines to compile for Win32

#SYSTYPE   = __GCCWIN32__
#EXESUFFIX = .exe
#GLLIB     = opengl32
#ICON      = vj-ico.o

# Uncomment the following lines to compile for Mac OS X

SYSTYPE   = __GCCUNIX__ -D_OSX_
EXESUFFIX =
GLLIB     =
ICON      =

CC        = gcc
LD        = gcc
TARGET    = vj

CFLAGS = -Wall -Wno-switch -O3 -D$(SYSTYPE) -Dstricmp="strcasecmp" \
		-fomit-frame-pointer `sdl-config --cflags`

LDFLAGS = $(CFLAGS)

LIBS = -L/usr/local/lib -L/usr/lib `sdl-config --static-libs` -lstdc++ -lz

INCS = -I. -Isrc -Isrc/include -I/usr/local/include -I/usr/include

THECC = $(CC) $(CFLAGS) $(INCS)

OBJS = \
	obj/anajoy.o \
	obj/blitter.o \
	obj/cdbios.o \
	obj/cdi.o \
	obj/cdrom.o \
	obj/clock.o \
	obj/crc32.o \
	obj/dac.o \
	obj/dsp.o \
	obj/eeprom.o \
	obj/gpu.o \
	obj/gui.o \
	obj/jagdasm.o \
	obj/jaguar.o \
	obj/jerry.o \
	obj/joystick.o \
	obj/log.o \
	obj/m68kcpu.o obj/m68kops.o obj/m68kopac.o obj/m68kopdm.o obj/m68kopnz.o \
	obj/m68kdasm.o \
	obj/memory.o \
	obj/objectp.o \
	obj/sdlemu_config.o \
	obj/sdlemu_opengl.o \
	obj/settings.o \
	obj/tom.o \
	obj/unzip.o \
	obj/version.o \
	obj/video.o \
	obj/vj.o \
	$(ICON)

all: obj $(TARGET)

clean:
	rm -rf obj
	rm -f ./vj$(EXESUFFIX)

obj:
	mkdir obj

obj/%.o: src/%.c
	$(THECC) -c $< -o $@

obj/%.o: src/%.cpp
	$(THECC) -c $< -o $@

vj: $(OBJS)
	$(LD) $(LDFLAGS) -o $@ $(OBJS) $(LIBS)
#	strip --strip-all vj$(EXESUFFIX)
#	upx -9 vj$(EXESUFFIX)

# Other stuff that has unusual dependencies

obj/gui.o: src/gui.cpp src/include/gui.h src/include/font1.h
	$(THECC) -c src/gui.cpp -o obj/gui.o

#
# Musashi specific stuffola
#

obj/m68kcpu.o: obj/m68kops.h src/m68k.h src/m68kconf.h
	$(CC) $(CFLAGS) -Iobj -c src/m68kcpu.c -o obj/m68kcpu.o

obj/m68kops.o: obj/m68kmake$(EXESUFFIX) obj/m68kops.h obj/m68kops.c src/m68k.h src/m68kconf.h
	$(CC) $(CFLAGS) -Isrc -c obj/m68kops.c -o obj/m68kops.o

obj/m68kopac.o: obj/m68kmake$(EXESUFFIX) obj/m68kops.h obj/m68kopac.c src/m68k.h src/m68kconf.h
	$(CC) $(CFLAGS) -Isrc -c obj/m68kopac.c -o obj/m68kopac.o

obj/m68kopdm.o: obj/m68kmake$(EXESUFFIX) obj/m68kops.h obj/m68kopdm.c src/m68k.h src/m68kconf.h
	$(CC) $(CFLAGS) -Isrc -c obj/m68kopdm.c -o obj/m68kopdm.o

obj/m68kopnz.o: obj/m68kmake$(EXESUFFIX) obj/m68kops.h obj/m68kopnz.c src/m68k.h src/m68kconf.h
	$(CC) $(CFLAGS) -Isrc -c obj/m68kopnz.c -o obj/m68kopnz.o

obj/m68kdasm.o: src/m68kdasm.c src/m68k.h src/m68kconf.h
	$(CC) $(CFLAGS) -Isrc -c src/m68kdasm.c -o obj/m68kdasm.o

obj/m68kops.h: obj/m68kmake$(EXESUFFIX)
	obj/m68kmake obj src/m68k_in.c

obj/m68kmake$(EXESUFFIX): src/m68kmake.c src/m68k_in.c
	$(CC) $(WARNINGS) src/m68kmake.c -o obj/m68kmake$(EXESUFFIX)

Also, a small change to deal with reversed Y-coordinates in OpenGL on OS X:
In gui.cpp

else if (event.type == SDL_MOUSEMOTION)
			{
				mouseX = event.motion.x, mouseY = event.motion.y;

				if (vjs.useOpenGL)
				#ifdef _OSX_
					mouseX /= 2, mouseY = (480 - mouseY) / 2;
				#else
					mouseX /= 2, mouseY /= 2;
				#endif

				if (mainWindow)
					mainWindow->HandleMouseMove(mouseX, mouseY);
				else
					mainMenu.HandleMouseMove(mouseX, mouseY);
			}

[awarlock@eaglec]

OK, that definitely got me a little further.

I just have to download the binary file, right? I moved my jagboot.rom and jagcd.rom to the Bios folder and I moved my roms to the Roms Folder. The roms were renamed from .jag to .j64.

I double click vj, now, and I do get a window with File, Settings,and Info. I got to File and choose Load and there is nothing there to choose from. I assume vj is going to the ROMs folder to get titles. Do the games have to have a specific name or is just renaming them from .jag to .j64 all that I need to do? I mean a Jag rom titled Alien vs Predator (1994).j64 or avp.j64 should work? And I do own the actual cartridge as well.

Is my jagboot.rom screwed or are my roms screwed??

Or is there something else that I need to do? Sorry to bother.

[ZildjianKX]

I just downloaded and tried it for the first time with OS 10.3.3.

Double clicking on the application just brings up a terminal and a window flashes and quits.

If you run the program manually at the command line by typing ./vj romname.jag it launches and runs fine for me... so try that.

Make sure there are no spaces or special characters in the rom name... I got a bus error when it did.

[Shamus]

else if (event.type == SDL_MOUSEMOTION)
{
    mouseX = event.motion.x, mouseY = event.motion.y;

    if (vjs.useOpenGL)
#ifdef _OSX_
        mouseX /= 2, mouseY = (480 - mouseY) / 2;
#else
        mouseX /= 2, mouseY /= 2;
#endif
...

I'm a little curious and concerned about this--Adam, do you know why the mouse coords are being reversed with OpenGL? Is this an SDL bug? Also:

LIBS = -L/usr/local/lib -L/usr/lib `sdl-config --static-libs` -lstdc++ -lz

Is there an advantage to linking SDL statically on OSX instead of using shared libs?

Awarlock: As long as the ROM file itself isn't zipped and has the extension of .j64 AND it's in the folder pointed to by the vj.cfg file, then it should find it. One thing you might check is to see that the case of the actual folder and the case in the vj.cfg file match--I'm pretty sure that OSX (being derived from UNIX) is case sensitive when it comes to filenames.

[_Em]

Shamus: in reverse order:
OS X both is and isn't case sensitive when it comes to filenames -- it all depends on what method you use to work with files. Using MacOS traditional file calls, case doesn't matter -- using POSIX compliant calls, I'm pretty sure it does.

Static linking ot SDL is generally better on OS X as different programs use different versions of the SDL libraries, and installing the libraries can be difficult if you don't know anything about unix and/or coding.

My guess for the reversed coords is that it has to do with where position 0,0 is on a Mac -- upper left hand corner. My guess is that some bit of code (either in vj, SDL or OpenGL) fails to deal with this. As all other SDL apps I've used handle this well, I can only guess.

Also, for people who want a quick and dirty front end to vj on OS X, try http://www.versiontracker.com/dyn/moreinfo/macosx/10459 -- DropScript. If you set it up right, all the files can be inside the application bundle, and you just need to drag jag roms onto it to play them. You can also set up a j64 file extension for the app in the plist table so that all you have to do is double click the roms in the Finder to play them.

[The U-Man]

Just a few words !

I want you to know that I have the same problem that awarlock[b] has !
On my PowerMac G5 bi-2Ghz with Mac OS 10.3.3

It works only when I place the file "vj.cfg" in my user folder !!!

second thing: I don't believe it's a good thing to use reversed coords for your gui !
when you choose the first file for load it's the last one who is select !!!

just hope it can help someone for make this emu going even better !

Is it normal that so few games work with this version ?
Only AvP works good ; Tempest 2000 won't works anymore (it does in 1.06)

And sound ? Anytime ?

Last word : I want to thank you for the great works you do in this emu and for support Mac OS X ! Thanks !!! :-)

[Adam Green]

The reversed coordinate system is "the way it is supposed to be" from what I've seen on the mailing lists, it's not considered a bug and no "fixes" will be accepted for it, so consider it a corner case People may want to try to decompress their roms before they run virtual jaguar, as sometimes Mac OS X will hide the .gz extension and that will not allow the file to be recognized (maybe we should parse for .gz?). Static linking is necessary on OS X because, like Em said, it's not really acceptable to have people install libs before they use it on the Mac side.

[The U-Man]

Ok more games run when I rename the extension .j64 (.Jag before)

I also have "some" sound.... when I activate DSP ;-)
But I was a little disapointed of the speed of the emulation (the sound is very bad !) I run on a Bi G5 2MHz !!!

I run a version of an other Jaguar emulator on top of Virtual PC on my old Bi G4 1GHz and I have a very good sound ???

For the gui, I don't understand why when I select with my mouse the first file in the loading list it is the last (on the opposite side of the screen) who is selected (highlited ?)

In the futur, can we hope a better sound emulation ? (speed)

Last question: G5 = 64bit processor Right ! (like Jaguar blitter and other coprocessor)
and it is more simple to emulate 68000 processor on RISC processor (like G4 or G5) than on the CISC processor like Pentium !
So why the speed of the emulation is not more efficient on the Mac side ?????

[ZildjianKX]

Originally Posted by _Em

Also, for people who want a quick and dirty front end to vj on OS X, try http://www.versiontracker.com/dyn/moreinfo/macosx/10459 -- DropScript. If you set it up right, all the files can be inside the application bundle, and you just need to drag jag roms onto it to play them. You can also set up a j64 file extension for the app in the plist table so that all you have to do is double click the roms in the Finder to play them.

Umm... how exactly do you setup all the files to be inside the application bundle? I've been messing with it, but didn't see any documentation on it... thanks!

[Shamus]

How bizarre that the SDL guys think that mapping the mouse Y inversely in OpenGL to the way the rest of the world does in every other context is 'the right way to do it.' I guess I'll have to look over the mailing list archives to see if I can figure out their logic, 'cause it doesn't make any sense to me.

Adam: I've finally figured out how to unify the Makefile, but I need to know what the output of

echo $OSTYPE

returns before I can commit this to CVS.

[awarlock@eaglec]

I just downloaded the file that was put up yesterday or day before and dropped my roms in the ROMs folder and put my jagboot.rom and the jagcd.rom in the bios folder. I have not renamed anything except some of the actual game roms. I renamed "Alien vs Predator (1995).jag to "avp.j64" as an example and put it in the ROMs folder.

I looked at the config file again and I do not see anything wrong with the path.

I tried moving the vj.cfg file to my user folder as suggested and when I clicked on File in the window to get to Load that just crashed the program repeatedly. I moved it back to the folder that vj is in.

I tried launching Terminal manually and after establishing a path to the vj application, typed ./vj avp.j64. VJ launched but I just ended up with the screen with File, Settings, Info. I clicked on File and then Load and there was nothing there to select.

I tried using the Dropscript suggestion and got nowhere with that as well.

Is there anyway to check the jagboot.rom to see if it is legit. I mean I downloaded it from somewhere. I have never had any of this working before so I cannot verify whether or not the jagboot or the roms are OK.

Is there any freeware (legally available) jag rom out there that I can test with?

Can somebody paste a working config file so that I can look at it?? I'm sure its just me but I can't get vj to see any roms. When I go to Load, there is nothing there. Does this suggest the jagboot is OK but the rom is bad or vice versa?

I appreciate the help!! Still VJ/Jagless.

[Shamus]

Here's the stock vj.cfg that comes with the standard VJ distro (1.0.7):

#
# Virtual Jaguar configuration file
#

# Jaguar BIOS options: 1 - use, 0 - don't use

useJaguarBIOS = 0

# Jaguar ROM paths

JagBootROM = ./bios/jagboot.rom
CDBootROM = ./bios/jagcd.rom
EEPROMs = ./eeproms
ROMs = ./ROMs

# OpenGL options: 1 - use OpenGL rendering, 0 - use old style rendering

useOpenGL = 1

# OpenGL filtering type: 1 - blurry, 0 - sharp

glFilterType = 0

# Display options: 1 - fullscreen, 0 - windowed

fullscreen = 0

# NTSC/PAL options: 1 - NTSC, 0 - PAL

hardwareTypeNTSC = 1

# DSP options: 1 - use, 0 - don't use

DSPEnabled = 0

# If DSP enabled, set whether or not to use the pipelined core: 1 - use, 0 - don't use

usePipelinedDSP = 0

# Joystick options: 1 - use joystick, 0 - don't use

useJoystick = 0

# Joyport option: If joystick is enabled above, set the port (0 - 3) here 

joyport = 0

# Jaguar joypad key assignments
# Note: It would be nicer to be able to have a single left side to store all this in...
# E.g. p1keys = 34, 32, 22, etc. instead of what we have here...

p1k_up = 273		# SDLK_UP
p1k_down = 274		# SDLK_DOWN
p1k_left = 276		# SDLK_LEFT
p1k_right = 275		# SDLK_RIGHT
p1k_c = 122			# SDLK_z
p1k_b = 120			# SDLK_x
p1k_a = 99			# SDLK_c
p1k_option = 39		# SDLK_QUOTE
p1k_pause = 13		# SDLK_RETURN
p1k_0 = 256			# SDLK_KP0
p1k_1 = 257			# SDLK_KP1
p1k_2 = 258			# SDLK_KP2
p1k_3 = 259			# SDLK_KP3
p1k_4 = 260			# SDLK_KP4
p1k_5 = 261			# SDLK_KP5
p1k_6 = 262			# SDLK_KP6
p1k_7 = 263			# SDLK_KP7
p1k_8 = 264			# SDLK_KP8
p1k_9 = 265			# SDLK_KP9
p1k_pound = 267		# SDLK_KP_DIVIDE
p1k_star = 268		# SDLK_KP_MULTIPLY

p2k_up = 273		# SDLK_UP
p2k_down = 274		# SDLK_DOWN
p2k_left = 276		# SDLK_LEFT
p2k_right = 275		# SDLK_RIGHT
p2k_c = 122			# SDLK_z
p2k_b = 120			# SDLK_x
p2k_a = 99			# SDLK_c
p2k_option = 39		# SDLK_QUOTE
p2k_pause = 13		# SDLK_RETURN
p2k_0 = 256			# SDLK_KP0
p2k_1 = 257			# SDLK_KP1
p2k_2 = 258			# SDLK_KP2
p2k_3 = 259			# SDLK_KP3
p2k_4 = 260			# SDLK_KP4
p2k_5 = 261			# SDLK_KP5
p2k_6 = 262			# SDLK_KP6
p2k_7 = 263			# SDLK_KP7
p2k_8 = 264			# SDLK_KP8
p2k_9 = 265			# SDLK_KP9
p2k_pound = 267		# SDLK_KP_DIVIDE
p2k_star = 268		# SDLK_KP_MULTIPLY

Note that you don't need the Jaguar BIOS to use VJ--the default is not to use it. Also, note the ./ in front of the various paths. If it's not there, then you *must* use a fully qualified path to where the various goodies live. Also note that at present 1.0.7 doesn't honor loading of ROMs from the command line (it's on the fix list), so you have to set up your vj.cfg file correctly in order to use it!

So the short answer is yes, if you set up your config file correctly and call the uncompressed ROM avp.j64 (contrary to what another poster said, it can contain spaces, you just have to enclose the filename in quotes if you're passing it on the command line) it should work.

[The U-Man]

For awarlock : (here is the solution ! (I hope ?))

Place the file "vj.cfg" in your user folder (on Mac OS X)
Copy your folder "virtualjaguar-macosx" witch contain the laste release post before in this forum.

And here is the modification on the config file I made :

#
# Virtual Jaguar configuration file
#

# Jaguar BIOS options: 1 - use, 0 - don't use

useJaguarBIOS = 0

# Jaguar ROM paths

JagBootROM = ./virtualjaguar-macosx/bios/jagboot.rom
CDBootROM = ./virtualjaguar-macosx/bios/jagcd.rom
EEPROMs = ./virtualjaguar-macosx/eeproms
ROMs = ./virtualjaguar-macosx/ROMs

And That works for me !

I suppose this version is an non official one so the Bug is that It search the config file in the User Folder and not in other place (the program folder like before)....

[awarlock@eaglec]

I'll try this in the AM.

The U-Man: You say (Copy your folder "virtualjaguar-macosx"). Where do I place the "virtualjaguar-macosx" Folder? On the desktop or where? I have (2) hard drives. The first is named "Macintosh HD" and the other hard drive is named "Macintosh HD 2".

I realize that my problem may be trying to establish the proper path in the config file and so far I have tried all sorts of things and have still got no where with getting vj to run.

I appreciate the responses and the help. I am usually a quick learner or can usually figure this stuff out on my own but this one has me puzzled. I am sure it is easy and will feel really when I get vj to run that I didn't figure it out sooner.

Thanks to everyone for their support!!