Stone

I have to agree with the others here. If I've understood right (which I hope I have) what you want to do is: 1) Rewrite the JagCD encryption tools so they work on a PC with no Jag involved 2) Encrypt and burn CDs for every code change you make Is that right? Other than the obvious time and cost penalty (OK, so blank CDs don't cost that much, but they'll of necessity take a while to encrypt and burn for each iteration), I'm still completely baffed as to why you'd want to reinvent so much stuff when perfectly viable alternatives exist already. Also, Tyrant's not being completely accurate about games developed via BJL, in his response to when you said: Fact is, when you're writing code on a BJL your only restriction is that you have to contain the code in RAM as well as using it as scratch space - you obviously can't leave the code on the CD/cart because you've not got one BUT there's no problem at all with taking a finished BJL program and making it run off a CD or off a cart (Tyrant's error). There already exists a 'loader' program which allows you to append a BJL-compatible program to it and run it from cartspace - all that happens is that when the cart's booted, the loader program copies the BJL program to the correct location in RAM and then shifts control over to it. Likewise, you can put a BJL program on a CD's boot track - when run the Jag will automatically load the BJL program to the specified RAM address and run it. Unless you genuinely need 2/4MB of storage space and 2MB of RAM for scratch space, there is no reason at all why you can't develop a game for cart or for CD on a BJL setup. In short, I can't see any reason why BJL is a solution you should shrug off so easily, and I know for sure I'd rather see a coder who appears as competent as yourself get straight to work on some democoding rather than spend weeks or months in unnecessary duplication of effort HTH Stone

Surely surface-mount resistors are easier to remove than through-hole ones? Heat one end, heat the other end, repeat until it comes off Stone

Bear in mind you'd likely get much more by putting in the extra effort to sell things seperately, however. Stone

The Jag can happily emulate Paula, at least - there's a nice sound demo of the Jag running an Amiga MOD which exists. Having (for example) the Lynx hardware on a cart and having the Jag simply display it is a nice idea, but I can't think of any easy way to get the video output from the Lynx into the Jag - there's certainly no 'video input' facility on the cart slot that I know of. One possibility might be to have the Lynx's video memory mapped to a region of cartspace that could be polled, but I don't know anything about the Lynx hardware so I don't even know if it works this way Another potential problem would be whether the Jag had enough bandwidth available to the cart to maintain a 60Hz display, but I guess this could be tested easily enough. How you'd get sound to work is beyond me though Stone

I heard way back that Creature Shock was in-dev, but all the stuff got trashed when Atari told them to. Jack Niklaus Cyber Golf has a physics engine and a concept demo. Nothing about any of the others springs to mind... Bear in mind the majority of these won't even have had development started - Atari would announce new games (and most of these were only announced to dealers anyway) with virtually no justification Stone

Whoops. Ta for that, it is kinda outdated There's plenty of other instructions on the Net for the mod itself though - Linkovitch has some, and the original ones by Bastian and Starcat are perfectly adequate. Stone

Oh, and this is a good place to pimp my BJL FAQ Stone

To start up the BJL loader, hold 4(4-bit loader) or 8(8-bit loader) as you turn on the Jag with the P:SE cart plugged in. This gives you a small routine which accepts input from a PC parallel port via a BJL cable to the second Jag joypad port, loads the data to RAM and then runs it. The limitations...well, there aren't many, really. You have to store the program in RAM (so you can't use the whole 2MB for scratch calculations, and large uncompressed textures etc are a no-no). You also get very limited debug info (none at all in the Protector SE cart as it only includes the loaders - with a hardware BJL mod you get 68K error codes and a registerdump of the 68K, GPU and DSP). In the hardware version some extra functionality is available if you're using an ST or Falcon, IIRC, but I don't have either so I can't test this. Only being able to run from RAM is the main issue - otherwise you have pretty much free rein. 2MB is easily enough for most simple games anyway Stone

But what exactly were you going to be doing that was such effort? I don't see how burning an EPROM and selling it with a socket is anything particularly original Stone

Upload-based dev solutions are really the only way to get anywhere in Jag dev, imho. Sure, you could keep burning FlashROMs or EPROMs with your program, but I guarantee you'd soon get tired of spending ages burning 4 chips (coupla minutes or so each) for your cart, and then having to wait for 30 minutes while they erase before you can try again. In the same vein, you could create a flash-based cart emulator, but there's not really much point in duplicating effort that's already been expended. The BJL kit is pretty trivial to arrange, and since you're happy without any debug info you could easily use the Protector:SE solution (no internal mods to the Jag at all, you just need to make up a cable) which would suit you far better, I think. Just some ideas Stone

I did this early last year, works great The only thing to watch is that A17 and A18 are hardwired to Vcc on the PCB, so you need either to cut those traces (both between A17 and A18, and between A18 and Vcc) or put another socket in the existing socket with the pins bent up so they don't touch. A18 shorts on mine so it'll only boot the top two BIOSes, but I don't mind cos they're Stub94 and BJL Stone

What video hookup are you using, or does it apply to all of them? Sounds like a pixel clock error...been ages since I generated one though, so I can't be sure Stone

None. The average Jag cart doesn't use EPROMs, so none But for 2MB carts a suitable drop-in replacement is the 27C800 (16-bit 1MB, 2 pieces) and for 4MB carts two 27C160s will do the trick, IIRC. Stone

I can't see anything wrong with using 4x27C080 to make a 4MB cart. Mind you, they cost about $12 each and you'd have to design and make your own PCB to hold them... Stone

The burner you'll need is determined by the chips you want to burn, which is determined by what you're going to use them for in the Jag context. How about you tell us what you want to do, and we'll be able to give an answer Stone

Jaglink stuff is here. You'd have to ask Jay for everything else, he owns them all Stone

It's going to be a cart release...no idea when though. 'When it's done' I guess Stone

If I had somewhere to put it...:'( Stone

Real ones or Ikea ones? Stone

What Curt said. Also only the first run of the K-series contained the internal ADC for use with analog controllers. Stone

Well, congratulations to JustClaws on winning that auction Stone

With regards that auction, I must say I'm surprised to see Tbird bidding. Without putting too fine a point on it, he does have quite a few Alpines already, for someone who claimed to be leaving Jag development Stone

I assume you mean a Genesis pad, in which case it's easy (assuming you don't want to use any buttons other than left and right on the Genesis pad...). Pin 4 on the Jag (pause/A/left/right/up/down) connects to pin 8 on the Genesis pad (ground). Jaguar pin 11 (left/1/2/3) connects to Genesis pin 3 (Left). Jaguar pin 12 (right/4/5/6) connects to Genesis pin 4 (Right). That should give you a Jaguar pad that only responds to left and right...you should then be able to piggyback a high-density 15-pin socket on the connections to plug a standard Jag pad into. Obviously I take no responsibility if you blow everything up (your Jag, your pad, your Jagpad, your house, your cat, your girlfriend) since I've never taken a Genesis pad apart, but I'd be confident enough that it'd wrk to try it myself, if I wanted to do such a thing. I still don't think it's a great idea, but that's how I'd do it If it's a Master System pad the principle's the same, but with different pins. Stone

Or, you could let a developer buy it. Why people insist on buying stuff 'because it's rare' and then locking it away under glass so nobody gets the chance to use it is beyond me Stone

It's much easier to convert pads from a different system to work on the Jaguar, to be honest. Jag pads work on a matrix system, whereas Genesis pads have a pair of 'pages' containing button inputs that have to be pulled low to activate them. Unless I'm missing something really obvious you'd need to add a circuit constantly flick between the pages really fast to get all the buttons. Otherwise you could just use some transistors to connect the right row and column together on the Jag pad and it'll work. Not an overly elegant solution...I know it works though, since I've found all the fancy circuitry in your standard Jag controller to be largely unnecessary As for the tracking, digital tracking using the controllers would most likely be ugly as hell, but feel free to try it...the fact remains MC3D is designed for the (complicated!) JagVR and using anything else is unlikely to give nice results. By all means try it and see though Stone