Jump to content

5-11under

+AtariAge Subscriber
  • Content Count

    3,715
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by 5-11under


  1. If you could change the way games are now made,would you go back to carts,or stay with CD disc? I for one,would go back to carts.I don't like paying $59.00 for say,a new xbox game,and then get a scratch that makes the game junk.(my halo 3)It just slipped out of my hand.Now Will not play!For one thing,you could always depend on a cart.I have found Atari games,well over 30 years old,that played like new.You did,have to clean the carts,that did not have the old dust covers.Now,I know that the CD'S do hold more infomation,but at what cost?I just don't think,games should be on a CD disc.Atari carts,just seemed to be so well built.(until they went to the open air carts)I thought that cd's were suopse to be real cheap to make,Well they sure are not cheap to buy.Does anyone know,what it cost Atari back in the day to make a cart?If so,what would it cost today?What do you guy think?

     

    I love carts... and so do my kids. I find scratched DVDs and CDs around the house :( , but the N64 carts that are lying around work just fine. :) .

    I'd like to see a console with some sort of flash memory cart (built into a decently sized, relatively indestructible case). You'd probably need some extra RAM in the console for speed, and there's still the fact that the retail price of 4GB flash memory is around $12, versus less than $1 for disc media, but maybe that's not too bad.

     

    Thanks,

    5-11under


  2. These systems with the nes/gen in one are based off of "NES-on-a-chip" and "genesis-on-a-chip" designs. I can't be quoted here, but I do not believe that there is a Colecovision or intellivision on a chip. Atari 2600 on a Chip, yes. That was used in the Atari Flashback 2. To create a "console on a chip" requires some ingenuity in chip design. Not to question the genius-ness of our members, I don't think anyone here has the money or the ability to do so.

     

    It doesn't have to be that difficult. Three boards (and three cartridge ports?) and some logic for controllers, output, power.

     

    Thanks,

    5-11under


  3. Hi jeremysart,

     

    I'm guessing the Intellivoice "I" sits too far forward in the Intellivison II, which is why the internals would require modification?

     

    For the molding, I'd consider doing it yourself... although it's going to be a lot of work... make your own mold, and cast the parts yourself. Probably not a project for the faint of heart. That grill on the top might need to changed... .

     

    Good luck,

    5-11under

     

    edit: I don't own an Intellivision anymore, but it sounds like a great idea.


  4. Hi Opcode,

     

    I've got a DE1 also, because it was really cheap at the time, and I've wanted to try the FPGA Arcade CV for a while now. Care to share, or am I going to have to try the conversion myself? :)

     

    Thanks,

    5-11under

     

    Do you want the pof file? The current implementation isn't very useful, as the ROM cartridge is placed inside the pof file, so you need to recompile the whole thing every time you want to change game. Furthermore, the way they implemented the thing limits the cartridge size to 16KB. Finally, the code I have here is a mess, so I will be doing my version from scratch... or almost..

    Anyway, if you want the pof file (with DK) let me know...

    BTW, good to know you also have a DE1. Perhaps you could help me in the future...

     

    Hi opcode,

     

    The pof file would be a start, to make sure everything is working. However, the source files as an addition would be best, or at least the files that are different from the FPGA Arcade version. I'm pretty green at vhdl, but this sounds like a good project to get my feet wet. Although it may be pretty complex, I guess if the building blocks are organized, it could be manageable.

     

    edit: so yes, I'm willing to help out as I'm able.

     

    Thanks,

    5-11under


  5. Hi Opcode,

     

    I'm curious how much RAM is required for your upcoming projects?

     

    Thanks,

    5-11under

     

    8KB I believe. But the OM offers 24KB, since it is cheaper to buy 32KB than 2 ICs of 8KB nowaday.

     

    Hi Opcode,

     

    Is the OM RAM part of the regular memory map? If so, are you only using the 16K from 0x2000 to 0x5FFF, or are you somehow going beyond that, into the space mapped out by the 1K internal RAM? I'm just wondering if there's bus contention issues (and how easy it is to access the OM RAM)?

     

    For those who would have to look it up, like I did, 0x0000-0x1FFF is BIOS ROM, 0x6000 to 0X7FFF is the 1K RAM mirrored a total of 8 times, and 0x8000 to 0xFFFF is cartridge ROM.

     

    Thanks,

    5-11under


  6. I agree that Defender was tough. I never got the hang of all the buttons. Two friends of mine used to play together, one person doing the flying, the other doing most of the rest.

     

    Starcastle wasn't too bad, in my opinion. It definitely got tougher, but after a few rounds, I mostly flew vertically, on one side of the screen, and every cycle up, if the shields looked good, I'd rotate my ship temporarily, fire a few rounds, then rotate straight up again, and accelerate.

     

    Thanks,

    5-11under


  7. Hi Pixelboy,

     

    Me again. Looking at figures 4 and 5 from post #2, I just want to be clear on a couple of things...

     

    1. The PCB sits on top of the red lines, right? So these are keep-away zones for components, but no routed slots in the PCB are required.

     

    2. The blue line would directly interfere with the PCB, and absolutely require a routed slot in the PCB in that area?

     

    Thanks,

    5-11under


  8. Next questions...

     

    When using a CPLD or FPGA to control a serial EEPROM, what is the typical method to access the memory, from the homebrewer's perspective? Is there a lot of overhead required, or is it a simple task to access? The reason I'm asking is because...

     

    A fairly simple way (for someone like me, who doesn't fully understand FPGAs and CPLDs) to add memory would be to add a parallel EEPROM, and "chip-select" it into the upper portion of memory. Access to the memory should be easy, but it would reduce the available ROM space by the amount of space allocated to the EEPROM. I might have to try this... .

     

    Thanks,

    5-11under


  9. You can get a decent caliper from Canadian Tire (or your local big-box hardware store) for about $15 if they're on sale ($30 if they're not on sale). The digital readout is easy to read. Just measure the existing PCB, including the location of the half holes, and the hole size from the case. Make adjustments if you think the existing board is too tight or too loose. Measure >2 times, and all should be fine.

     

    Pixelboy or Albert, give me a PM if you want me to do any of the following: layout the PCB, order some PCBs, assemble the logic chip. I've done this for the regular Coleco casing, using it for my Squares! game, as well as providing >500 to other customers. Price will be low, especially if you want to order decent quantities.

     

    Thanks,

    5-11under


  10. Hi Pixelboy,

     

    For basic 32K cartridges, I'd go with the PCB in figure 2, rather than figure 3 (of post #2). The 74LS21 chip (or whatever is chosen) can go on the back (soldered first, with the leads bent inward before soldering). That's what my board does. With the Activision layout, it looks like the PCB can be even smaller than the Coleco layout. The PCB and logic chip might end up costing less than $1.25 each, in quantities of several hundred.

     

    Thanks,

    5-11under


  11. Hi yurkie... :)

     

    I will say this, that it is much harder than I had imagined.

     

    So far I have not over 3000 points yet.

     

    On the emulator I could never get through that desert after Las Vegas.

     

    In the arcade, I used to be able to go through several rounds. Now, in MAME, I can't finish the first round. :(

    5-11under


  12. Hi Al,

     

    At some point, I suggest a poll, asking people how much they would be willing to pay for whichever benefits would be provided. That can help estimate how much money could be brought in. I'd hope it would end up with a high-volume, low cost solution, something like $20 per year times 250 subscribers.

     

    The only features I'm interested in, besides no advertising, is perhaps a regularly scheduled draw (or contest) for some free stuff. I'd consider it mostly a donation.

     

    Thanks,

    5-11under


  13. Doubledown, it looks like you're using a different BIOS than the popular intro skip BIOS out there (the one I linked above). I've got only a crappy hex editor here, but the only difference I'm seeing between the regular BIOS and the popular intro skip BIOS is a section with an "I" (plus an accent), followed by an "h" and a "19" replaced by a "0", "0", "0". I'm guessing the call to the ~10 second delay is merely cut for the popular intro skip BIOS.

     

    As an alternative, attached is the BIOS I'll be using for any future work I do. It has a 2-3 second delay, instead of ~10 seconds. Long enough to have a peek at the game title, etc., but not too long that you're waiting for what seems forever. There is no option to skip the BIOS with the press of a fire button in this version. What I've done is change the outside delay loop from 17h to 05h (location 0x196A, I think).

     

    Thanks,

    5-11under

     

    edit: made things a bit more clear.

     

    If I am understanding you right 5-11under. This file would be burned on a eprom chip, Original BIOS IC would be removed and the eprom would be put in it's place?

     

    I love the idea of a 2-3 second delay with no fire button skip feature. I had read somewhere that a delay was needed for some games to load properly. Does your 2-3 second delay allow for all games to load properly... or have I got some misinformation about games not loading with a delay skip?

     

    Hi Yurkie,

     

    The 2-3 second delay shouldn't have any adverse effect to any games. Looking at the BIOS code, a game could conceivably call the delay, but I'm almost 100% sure there aren't any.

     

    Thanks,

    5-11under


  14. Doubledown, it looks like you're using a different BIOS than the popular intro skip BIOS out there (the one I linked above). I've got only a crappy hex editor here, but the only difference I'm seeing between the regular BIOS and the popular intro skip BIOS is a section with an "I" (plus an accent), followed by an "h" and a "19" replaced by a "0", "0", "0". I'm guessing the call to the ~10 second delay is merely cut for the popular intro skip BIOS.

     

    As an alternative, attached is the BIOS I'll be using for any future work I do. It has a 2-3 second delay, instead of ~10 seconds. Long enough to have a peek at the game title, etc., but not too long that you're waiting for what seems forever. There is no option to skip the BIOS with the press of a fire button in this version. What I've done is change the outside delay loop from 17h to 05h (location 0x196A, I think).

     

    Thanks,

    5-11under

     

    edit: made things a bit more clear.

    COLECO_SHORT_DELAY.zip

    • Like 1

  15. Hi Trebor,

     

    It's a ColecoVision. Besides black, white, grey and see-through, there's only 12 other fixed colours available... unless this game is linked with the planned opgrade module.

     

    Thanks,

    5-11under

     

    edit: looks like Pixelboy beat me to it.

×
×
  • Create New...