obj/sdlemu_config.o \
obj/sdlemu_opengl.o \
obj/settings.o \
+ obj/state.o \
obj/tom.o \
obj/unzip.o \
obj/video.o \
REQUIREMENTS:
-------------
-To compile Virtual Jaguar you need to check if you have the minimum
-requirements for compiling the sources:
-
-- GCC v4.3.x or higher
-- SDL v1.2.13 or higher
-- ZLIB v1.2.3
-- libcdio v0.80 or higher
-- OpenGL libraries
-- supported OS (BeOS, Linux, FreeBSD and WIN32 through mingw, MacOS); other OSs
- may work to but you may need to change some items in the Makefile.
-
-Optionally you need a Atari Jaguar boot ROM (and/or CD boot ROM) which is
+The minimum requirements for compiling Virtual Jaguar from source are:
+
+ o GCC v4.3.x or higher
+ o SDL v1.2.13 or higher
+ o zlib v1.2.3
+ o libcdio v0.80 or higher
+ o OpenGL libraries
+ o supported OS (BeOS, Linux, FreeBSD and WIN32 through mingw, MacOS); other
+ OSs may work to but you may need to change some items in the Makefile.
+
+Optionally you'll need an Atari Jaguar boot ROM (and/or CD boot ROM) which is
available on the Internet. We can't include the boot ROM since it's still
copyrighted.
COMPILING:
----------
-If you sure you have the minimum software requirements, you can compile
+Assuming that you meet the minimum software requirements, you can compile
Virtual Jaguar by issuing the following command in the directory where you
decompressed the source:
upx in your path somewhere, you can uncomment the line in the makefile that
executes upx so that you'll end up with a somewhat smaller binary.
-That's it! You're done! You can now start the emulator with ./vj. See the
-output for more details or consult the README file for more info.
+That's it! You can now start the emulator with ./vj. See the output for more
+details (or stdout.txt on Win32) or consult the README file for more info.
For even more info, go to http://sdlemu.ngemu.com or send use an e-mail to the
following e-mail address: sdlemu AT ngemu DOT com.
consult the INSTALL file for more information about supported OS's and
software requirements.
-The use of this software is entirely at your own risk. We can't be held
-responsible for damage done to you hardware and/or software. While it won't
-rape your dog, it might do other nasty things. You have been warned. This
-software requires the use of the Atari Jaguar (CD) boot ROM and/or Commercial
+The use of this software is entirely at your own risk. While it won't rape
+your dog, it might do other nasty things. We can't be held responsible for
+damage done to you hardware and/or software. You have been warned! This
+software may require the use of the Atari Jaguar boot ROMs and/or Commercial
ROM images. You may only use the ROM images if you own the cartridges itself.
The use of Commercial ROMs without owning the original cartridge is illegal in
most countries and could result in fines and/or legal actions.
source code to the public and send the changes you made to the original
authors.
-The products and brands used in these documents and/or sourcecode are owned by
-their respective companies and/or successors in interest.
+The products, trademarks and/or brands used in these documents and/or
+sourcecode are owned by their respective companies and/or successors in
+interest.
----------------------------------------------------------------
- IMPORTANT NOTE ABOUT JAGUAR FILE FORMATS--READ THIS OR ELSE! -
Potato Emulation [http://potato.emu-france.com] and was released under the GPL
on 25 June 2003.
-Virtual Jaguar GCC/SDL is not only a port of the MS Visual C++/SDL sourcecode
+Virtual Jaguar GCC/SDL is not just a port of the MS Visual C++/SDL sourcecode
but has also been extended and rewritten so that we can enjoy Atari Jaguar
-emulation on every platform which uses the GCC compiler and that can make use
-of the Simple Directmedia Layer library (SDL).
+emulation on every platform that has a GCC compiler and a port of the Simple
+Directmedia Layer library (SDL).
Currently Virtual Jaguar GCC/SDL compiles on WIN32 using mingw, and several
-UN*X based systems (BeOS, Linux and FreeBSD). It may run on other systems
-as well but we can not guarantee that.
+UN*X based systems (BeOS, Linux, FreeBSD and MacOS). It may run on other
+systems as well but we can not guarantee that.
The port was done by the SDLEMU crew (http://sdlemu.ngemu.com) and especially
by Niels Wagenaar and Carwin Jones. A major portion of the rewrite was done by
message on the SDLEMU Official Forum (see the website). Patches and bugfixes
are particularly welcome! :)
-More information about SDL can be found at http://www.libsdl.org.
+More information about the incredible SDL libraries can be found at
+http://www.libsdl.org. Thanks Sam--you rock! :)
--------------------------------
- Using Virtual Jaguar GCC/SDL -
After compiling the binary (see INSTALL) you can now run original Atari Jaguar
games. These games are distributed on cartridges and can therefore cannot be
used on a PC (we're still waiting for that Jaguar-on-a-PCI-card that you plug
-into your late model PC, complete with cartridge slot ;-). To use these games
-on Virtual Jaguar GCC/SDL you need to get ROM images. Besides the ROM images
-from commercial games you must also obtain the Atari Jaguar (CD) boot ROM
-which you must copy to the BIOS directory. For legal issues concerning ROM
-images please consult the DISCLAIMER at the beginning of this file.
-
-After obtaining the Atari Jaguar (CD) boot ROM and several ROMs you can now
-use Virtual Jaguar using the following command:
+into your late model PC, complete with cartridge slot and controller connectors
+;-). To use these games on Virtual Jaguar GCC/SDL you need to get ROM images.
+Besides the ROM images from commercial games, you may also need to obtain the
+Atari Jaguar boot ROM (and/or CD boot ROM) which you must copy to the BIOS
+directory. For legal issues concerning ROM images please consult the DISCLAIMER
+at the beginning of this file.
+
+After obtaining the Atari Jaguar boot ROM (and/or CD boot ROM) and several game
+ROMs you can now use Virtual Jaguar using the following command:
./vj [romfile] [-switches]
//void OPWriteByte(uint32, uint8, uint32 who = UNKNOWN);
//void OPWriteWord(uint32, uint16, uint32 who = UNKNOWN);
+// Exported variables
+
+extern uint8 objectp_running;
+
#endif // __OBJECTP_H__
--- /dev/null
+//
+// state.cpp: VJ machine state save/load support
+//
+// by James L. Hammons
+//
+
+#include "state.h"
+
+bool SaveState(void)
+{
+}
+
+bool LoadState(void)
+{
+}
+
--- /dev/null
+//
+// state.h: Machine state save/load support
+//
+// by James L. Hammons
+//
+
+#ifndef __STATE_H__
+#define __STATE_H__
+
+//#include <stdio.h>
+
+//#ifdef __cplusplus
+//extern "C" {
+//#endif
+
+//int LogInit(const char *);
+//FILE * LogGet(void);
+//void LogDone(void);
+//void WriteLog(const char * text, ...);
+
+//#ifdef __cplusplus
+//}
+//#endif
+
+bool SaveState(void);
+bool LoadState(void);
+
+#endif // __STATE_H__
//(It's easier to do it here, though...)
//#define TOM_DEBUG
-extern uint8 objectp_running;
-
uint8 tomRam8[0x4000];
uint32 tomWidth, tomHeight;
static uint32 tom_timer_prescaler;
if (inActiveDisplayArea)
{
//NOTE: The following doesn't put BORDER color on the sides... !!! FIX !!!
+#warning The following doesn't put BORDER color on the sides... !!! FIX !!!
if (vjs.renderType == RT_NORMAL)
scanline_render[TOMGetVideoMode()](TOMBackbuffer);
else//TV type render
uint8 pwidth = ((GET16(tomRam8, VMODE) & PWIDTH) >> 9) + 1;
uint8 mode = ((GET16(tomRam8, VMODE) & MODE) >> 1);
bool varmod = GET16(tomRam8, VMODE) & VARMOD;
-//The video texture line buffer ranges from 0 to 1279, with its left edge starting at LEFT_VISIBLE_HC.
-//So, we need to start writing into the backbuffer at HDB1, using pwidth as our scaling factor. The
-//way it generates its image on a real TV!
+//The video texture line buffer ranges from 0 to 1279, with its left edge starting at
+//LEFT_VISIBLE_HC. So, we need to start writing into the backbuffer at HDB1, using pwidth
+//as our scaling factor. The way it generates its image on a real TV!
+
+//So, for example, if HDB1 is less than LEFT_VISIBLE_HC, then we have to figure out where
+//in the VTLB that we start writing pixels from the Jaguar line buffer (VTLB start=0,
+//JLB=something).
+#if 0
+//
+// 24 BPP mode rendering
+//
+void tom_render_24bpp_scanline(uint32 * backbuffer)
+{
+//CHANGED TO 32BPP RENDERING
+ uint16 width = tomWidth;
+ uint8 * current_line_buffer = (uint8 *)&tomRam8[0x1800];
+
+ //New stuff--restrict our drawing...
+ uint8 pwidth = ((GET16(tomRam8, VMODE) & PWIDTH) >> 9) + 1;
+ //NOTE: May have to check HDB2 as well!
+ int16 startPos = GET16(tomRam8, HDB1) - (vjs.hardwareTypeNTSC ? LEFT_VISIBLE_HC : LEFT_VISIBLE_HC_PAL); // Get start position in HC ticks
+ startPos /= pwidth;
+ if (startPos < 0)
+ current_line_buffer += 4 * -startPos;
+ else
+//This should likely be 4 instead of 2 (?--not sure)
+ backbuffer += 2 * startPos, width -= startPos;
-//So, for example, if HDB1 is less than LEFT_VISIBLE_HC, then we have to figure out where in the VTLB
-//that we start writing pixels from the Jaguar line buffer (VTLB start=0, JLB=something).
+ while (width)
+ {
+ uint32 g = *current_line_buffer++;
+ uint32 r = *current_line_buffer++;
+ current_line_buffer++;
+ uint32 b = *current_line_buffer++;
+ *backbuffer++ = 0xFF000000 | (b << 16) | (g << 8) | r;
+ width--;
+ }
+}
+#endif
}
}
else
{
// If outside of VDB & VDE, then display the border color
-/* int16 * currentLineBuffer = TOMBackbuffer;
- uint8 g = tomRam8[BORD1], r = tomRam8[BORD1 + 1], b = tomRam8[BORD2 + 1];
- uint16 pixel = ((r & 0xF8) << 7) | ((g & 0xF8) << 2) | (b >> 3);//*/
uint32 * currentLineBuffer = TOMBackbuffer;
uint8 g = tomRam8[BORD1], r = tomRam8[BORD1 + 1], b = tomRam8[BORD2 + 1];
uint32 pixel = 0xFF000000 | (b << 16) | (g << 8) | r;
*currentLineBuffer++ = pixel;
}
-// TOMBackbuffer += GetSDLScreenPitch() / 2; // Returns bytes, but we need words
TOMBackbuffer += GetSDLScreenWidthInPixels();
}
}
hardwareTypeNTSC = 1
+# Render type (experimental): 0 - regular/OpenGL, 1 - TV style
+
+renderType = 0
+
# DSP options: 1 - use, 0 - don't use
DSPEnabled = 0
projects / virtualjaguar / commitdiff