belboz

SubQ doesn't support the -y switch yet. I believe it is on his list.

I was referring to the original source to madmac posted by the ex Atari developer. If Allan downloads that source from that ex Atari guys website he can just rebuild it and have madmac that supports the 68K and 6502. Here is the Atari developers post about madmac and source http://www.dadhacker.com/blog/?p=1049

SubQ wanted me to post binaries for Linux and OS X users. Attached to this message are the binaries for Linux users. These were compiled with an Ubuntu 8.04 machine. You can use these in conjunction with the Atari made Linux dev tools. The Atari made mac and aln bundled with their linux tools suite function well with Linux, but with smac you gain the gpu main code feature and bug fixes SubQ has made to the original code base. I will build an OS X set of Universal binaries tonight and post. sln_0.1.4.tar.gz smac_1.0.12.tar.gz

The original developer of MadMac posted the source to it. This is pre Jaguar time, but it has the support for 6502 in it. You could simply rebuild if you want a madmac that works on modern OS's. It just won't support the Jaguar.

I can tell you that SubQ has done an awesome job with his work on this. The assembler and linker have worked very well for me with my old projects. Everything assembled and linked beautifully. This coupled with Tursi and kskunks skunkboard have allowed me to do something pretty unheard of for Jag development. I was able to compile, assemble and link my various Jag projects on an OS X machine (PPC one, although Intel based works too obviously). I was also able to download the resulting binary to the Jag with the skunkboard. All done on OS X. Of course everything works beautifully with Windows XP, Vista, 2000,etc. Linux of course also. For Linux and OS X users who want a working C compiler I recommend going to Seb's site. OS X users can use his compiler build script to get a working gcc for the 68K. Linux users can either use the script to build their own or download the prebuilt version. Seb's prebuilt version has binaries for Linux and Windows (using Cygwin). Seb's site is... http://removers.free.fr/softs/download.php Congrats again SubQ on the excellent work!

Another Vista user reported that the dev tools work under Vista. Only issue is things like the BJL loader, or alpine software which talk directly to the printer port. If they don't work under Vista your current alternatives are. Run the tools under Dosbox, use a Virtual Machine to run Windows 9X/Dos and use the tools under that. Dual boot Windows 9X/Dos and use the tools there. Run the Linux tools under your favorite Linux OS. Or use the Atari tools on an Atari machine. I have the DOS based dev tools on my site if you haven't got them yet. http://www.hillsoftware.com So your goal is to make a new Pitfall and Flashback cartridge an bundle it with an enhanced CD? Cause you can't boot a JagCD with any "standard" game cart in the Jaguar. So the only way your going to to do this with a standard Jag would be to make a new cart that accesses your extra content CD.

On my schematics for the Mega ST (not a Mega STE, but they are probably very similar) I see the signals for transmit and receive from the 6850 goes through an inductor (L9 on the Mega STE). There is a chance that is blown. There are also a pull up resistor and some caps on the signals coming out of the 6850. Pin 6 is the transmit pin from the 6850 and pin 2 is the receive pin. The troubleshooting section of the manual says that a keyboard not responding is generally related to the 6850 or the MFP chip. You can also verify the signals on the 6 pin keyboard connector. On the schematic it says. Pin 1 = +5 Pin 2 = +5 Pin 3 = TX Pin 4 = RX Pin 5 = GND Pin 6 = GND

Weren't there two 6850 UARTS used in the ST's. One for midi port, the other to communicate with the keyboard? Pretty sure that is what was used. Don't have any schematics handy, but it could be the 6850 used to communicate with the keyboard controller is dead. Pretty sure the picture below shows them. One is directly to the right of the keyboard connector, the other above it. http://www.maedicke.de/atari/hardware/pictures/megaste_5.jpg

The removers library are not really dev tools. It is a library of routines to help a person write a game. Its a very nice library and Seb should be commended for putting it out there. You still need Atari's assembler, linker,etc. Seb does have a script to let Unix users build their own GCC targeted for the Atari to run under their OS. It downloads the source code to GCC from the GNU website and then compiles and installs the GCC compiler under their OS. Maybe Seb will chime in if anyone has used his Library under a Windows dev system. As for using the dev tools in XP with userport. Userport is only for programs that need the parallel port for communication. So that is wdb/rdbjag for Alpine users, or BJL loaders for BJL users. Even Vista users need userport or a similar program to be able to use parallel port access programs. XP does not work with the assembler mac, or the linker aln. userport doesn't help with that. I tried the dev tools on my Vista Home laptop (which now happily runs Linux) and they didn't work for me.

I have a tutorial on my website for setting up the dev tools on Windows 98. I also have the DOS/Windows dev tools for download on my site also. http://www.hillsoftware.com/downloads/index.html For DOSBox it should be similar to what my Video does. Just going from memory I would do this. (No guarantees this will work as I don't really use DOSBox for Jaguar development. I have gone the Linux route mainly and also used Windows 98 under a virtual machine. I also have a Jaguar test program and Hello World program. Either would be a nice candidate to test your development environment with. 1) Install DOSBox 2) Inside your folder that is going to be your "C" drive for DOSBox create an autoexec.bat file and put in the environmental variables as I show in my video 3) copy the contents of jagdev.zip into a folder called "jaguar" and place it inside your DOSBox "C" drive folder. 4) Put any projects you want to build or work on inside your DOSBox C drive. 5) Run DOSBox and change to your project directory and try to build it. 6) There are a lot of Jaguar development info over on JSII. So you might want to visit there too. I know a couple people on there are using DOSBox for their development. I believe some are using a special version of DOSBox on the web that has been hacked to allow parallel port access. Nice for doing BJL downloads or communicating with an Alpine development board,etc.

Nope. Some things work, most don't. Best bet is to either dual boot 98, or use a Virtual machine for 98. Or use DOSBox. Basically the dev tools work great under 98, Linux, and on the Atari ST line.

If anyone with a Mac who knows their way around the command line wants to test some OSX SIO2PC software I wrote that is compatible with USB->Serial FTDI based chipsets, drop me a PM. I have yet to finish the software but it works now, and I also want to toss a GUI on it at some point. Goal is to release it for free.

I have the dev tools on my website. http://www.hillsoftware.com Just go to the downloads section. I also have a few simple examples and a video where I show how to setup the dev tools on your PC. As for source code. JS II has some in their download sections. Painter source, Native, and Doom I believe.

I have a full developers unit from an ex-atari developer. The CD unit has a gray cable coming out of it that goes to a little PCB that has 3 connectors on it. You have to have it plugged into one specific connector when you just want to use the JagCD as a normal JagCD (obviously it still has the dev bios in it so it will boot unencrypted cd's). Without this cable being plugged in you get the power issue your seeing. The pcb has two connectors going straight up and one at a right angle. The right angle is for connecting to the Falcon. The straight up connector on the other end is for normal JagCD usage. The middle straight up connector is for when you have the Falcon connected to the other cable.

I have been able to get B2K to build successfully. Has a few graphical glitches which I believe are because I had to use tga2cry because of the lack of tga__cry.

Matthias, I sent you a PM with some of my finding on building B2K.

I don't think this is for the Jag.

Thanks Curt! Great stuff as always!

Oops. Double post. So I will just thank Curt again! Thanks!

Great find Curt! Thanks for posting it!

I think Christos is on to something. How about booting from a blank floppy (holding alternate at boot) and skipping the HD completely. Make sure the floppy is not a bootsector game, or have an auto folder or accessories. Then just try switching the resolution from the desktop on that clean boot. If it still crashes you might have a chip loose, or possibly a worse hardware problem.

There is a reference card in a thread on here. http://www.atariage.com/forums/index.php?showtopic=119598

Never enough time is there?

Yeah that wouldn't be too hard. But do people really love the Jag controller that much? Lots of good USB game pads for the PC.

Glad to hear it worked for you.