Creating a Jaguar CD image without burning to CD?

[cdoty]

Is it possible to create a Jaguar CD image without burning it to CD?

 

I would like to test out my game, in an emulator, without burning a CD for each test.

 

It seems like Project Tempest can play a few Jaguar CDs. It works with Baldies and Primal Rage at least.

Edited May 10, 2005 by cdoty

[justclaws]

Hello,

 

Is it possible to create a Jaguar CD image without burning it to CD?

I would like to test out my game, in an emulator, without burning a CD for each test.

It seems like Project Tempest can play a few Jaguar CDs. It works with Baldies and Primal Rage at least.

Maybe ask Atarifan49, or JagMod, or maybe Matthias or StarCat.

I have only created real CD's, because normally Jaguar code which loads to

RAM can already be tested adequately using the BJL loader, without even an

Alpine, as all the JagCD code has to load into RAM just as most homebrews do.

Thus, a CD only gets written for distribution purposes normally, unless of course

you're using Quicktime, or loading sections from CD. Why do that for FrogBog?

Cheers,

JustClaws.

[Matthias]

Hi!

 

Is it possible to create a Jaguar CD image without burning it to CD?

Maybe ask Atarifan49, or JagMod, or maybe Matthias or StarCat.

853471[/snapback]

 

Sorry, but if i would know an answer i would have replied already.

 

I think we all use CDRECORD to create our CD-based games, so a look into the CDRECORD-manual might help, but at the moment i don't know if it offers such a "create CD-image only" option.

 

Regards

Matthias

[cdoty]

Thus, a CD only gets written for distribution purposes normally, unless of course

you're using Quicktime, or loading sections from CD. Why do that for FrogBog?

 

It'll be a single load. I'm just trying to cut down on the number of CDs I burn. I may have to burn to CD-RW, and create an image from that..

[Matthias]

Hello!

 

Thus, a CD only gets written for distribution purposes normally, unless of course

you're using Quicktime, or loading sections from CD. Why do that for FrogBog?

 

It'll be a single load. I'm just trying to cut down on the number of CDs I burn. I may have to burn to CD-RW, and create an image from that..

853668[/snapback]

 

So if it is just a single programfile which includes all the graphics and sounds and leveldata you can ignore the fact that you intent to spread it on CD later.

 

Regards

Matthias

[cdoty]

So if it is just a single programfile which includes all the graphics and sounds and leveldata you can ignore the fact that you intent to spread it on CD later.

 

I was reading in the manual yesterday about the boot track.

 

The manual said the track could contain more than 64k, but only the first 64k could be loaded, and the rest would have to be loaded by the code.

 

Is there an easy way to do this, by resuming where that last cd_read left off or something?

 

Also, if a marker is used, is it also read into the buffer (using cd_initm)?

 

If the marker is read into the buffer, the program could be compiled as one big track, and the marker would indicate where to start loading the rest of the track into memory. The program would only need to have cd_initm, cd_read, and cd_ack added to it (plus a small amount of support code). Once the rest of the track was loaded, the program would run the same as the BJL version.

 

Am I missing something? In theory, it sound fairly easy. Granted, you would have to pad out the data before the marker to a sector boundary, but that's not too difficult.

Edited May 12, 2005 by cdoty

[belboz]

The 64K limitation seems to be bogus. You can load as large a boot track as you want.

[cdoty]

The 64K limitation seems to be bogus.  You can load as large a boot track as you want.

 

Didn't know that, that makes things a lot easier then.

 

Maybe that was an issue with an earlier version of the bios.

[cdoty]

The 64K limitation seems to be bogus.  You can load as large a boot track as you want.

 

So, is Track 2 of the BJL Loader CD a dummy track?

[belboz]

Yep that is a dummy track. I talked with Glenn about this when I first started messing with encrypted CD's. It looks like two tracks are needed (not counting the hash table track) for the Jaguar cd encryption to actually work.

 

In the case of my BJL cd track 2 is just the default.wav file copied with the proper header and tail on it.

[cdoty]

I finally got some of the issues with the Atari Jaguar CD version sorted out. For some reason clearing the BSS is causing a problem. I also have some random lock ups and stuff. I'll have to look into this deeper.

 

The good news is, the flickering and corrupt sprite problem has magically vanished.

 

I also created a cdi image that works under Project Tempest. (Obviously Project Tempest bypasses the CD validation.)

Edited May 14, 2005 by cdoty