Project 64 Roms

[Zee Petty]

Priorto CCS version 6, if you wanted to create a hex file output, you had to use the post build steps to call your hex build utility. In my case I called hex6x and I passed it a file that contained all the settings and the ROMS directive.

"most" is the keyword here. It does not provide any way to specify the ROMS directive. When you specify the -zero option, you'll get a warning that the -image option is also required. When you enable -image, you'll get an error that says a ROMS directive is required. I looked 3-4 times within the "C6000 Hex Utility" setting pages to see where the ROMS directive could be set. I searched the CCS help and found only information about the ROMS directive but nothing about how to enter it into the CCS project properties. I searched these forums and found a few discussions about the ROMS directive, but nothing about setup in CCS.

Toward the bottom it says that CCS currently doesn't have the ability to specify a ROMS directive and you have to add it as external file by specifying the filename in the command. So I took my old settings file, stripped out everything except the ROMS directive, and listed that file at the end of the "Command line pattern". It works.

One thing to note is that the wiki page shows an example using a file called "hex.cmd". I tried renaming my file to that filename (a nice simple file name), but when I went to build the project, the link failed because it was trying to use this .cmd file for linker settings. My hex.cmd file wasn't even in the main project directory. CCS must search through all directories for all .cmd files and assume they are linker settings files. Well, I renamed it to hex.dat, changed the "Command line pattern" setting to match, and voila (wah-lah here in America), it works.

I thought I'd pass this along since it took me a good 3-4 hours to track this down. The wiki page didn't initially show up in a search because it doesn't have the words "ROMS directive" together on the page...though it does have "ROMS and SECTIONS directive".

When taking on a new initiative, the first step is securing buy-in. Executive leaders and external stakeholders must know whether the project is feasible with the resources, budgeting, and timeline available.

Managers might also conduct a ROM to quickly review various initiative scopes to determine which one they think is most worthwhile. They can then choose the most feasible ones and run these by upper management before initiating project work.

While a ROM proposal provides a broad overview with less precision, a definitive estimate goes into detail, offering increased accuracy. Managers often use the former when choosing between initiatives to quickly gain a scope overview and the latter when asking for project approval. But you might stick with a ROM in both cases, since definitive estimates take more time and effort.

Programs like Google Sheets and Excel often have templates available, or you can replicate one you find online, creating it yourself in your preferred spreadsheet platform. And your preferred project management software might also have a template you can use to keep everything central.

Take your broad estimates to teammates who might have an even better understanding of how project work will go down. You might even chat with a business process reengineering professional to determine how you can streamline project processes to lower resource use.

This high-level estimate is a foundational guide for project execution, providing an initial framework that shapes how you implement your project strategy. Use this data to create more robust planning documents, like a roadmap and comprehensive resource allocation plan.

A PERT chart is a statistical tool that helps identify the probable outcomes based on three estimates: optimistic, most likely, and pessimistic. These estimates account for uncertainty and risk and provide a range of possible durations or costs.

COCOMO is an empirical model used for software cost estimation. It uses a mathematical formula to estimate the effort and duration required based on lines of code or function points. The model consists of several formulas depending on the version (basic, intermediate, or detailed).

The calculation involves classifying and weighing different functionalities. Once you have the total unadjusted function points (UFP), you can convert these into effort or cost using historical data or productivity factors. The formula itself depends on the specific values and weightings used.

Three-point estimating is analogous in principle to PERT but used in more straightforward contexts. It involves making optimistic, most likely, and pessimistic estimates. You can then use these three data points to determine an expected value, often focusing on calculating the range of uncertainty around the most likely estimate.

Historical data involves using information and metrics from completed projects to inform estimates for new projects. If a team has undertaken similar initiatives (which is likely), they can use the actual cost, time, and effort data from those projects to provide a ROM estimate for a new project.

Example: A software company knows a previous mobile app development project of similar scope and features took five months and cost $50,000. They use these figures as a starting point for a new mobile app project estimate, adjusting for any known differences between past projects and this one and accounting for external changes, like market and user behavior fluctuations and technological advancements.

First-hand experience refers to the personal knowledge and insights of individuals directly involved in similar projects or tasks. Someone who has repeatedly worked on similar jobs will have an innate sense of the challenges, timelines, and resources required.

This approach is related to first-hand experience but extends to seeking the opinions of experts who might not have direct experience with the specific project at hand. Companies might consult industry experts, senior professionals, or specialists for their opinion on the estimated resources and process improvement methodologies.

Introduction

It is a known fact that many of the ColecoVision ROM files and ROM file collections available in the public domain are a mess and include major inconsistencies, multiple incorrect versions, missing versions, bad dumps, overdumps, underdumps, etc. This project seeks to rectify this situation by compiling the definitive ColecoVision ROM package for all titles that were commercially released throughout the 1980s.

The objective of this project is to compile a complete and clean set of ROM files for all of the titles commercially released for the ColecoVision from inception through to, and including, the 1980s Telegames releases. This project specifically excludes all non-commercial and unofficial releases such as demos, prototypes, hacks, bootlegs and test cartridges, but does include reproductions where they were commercially released as well as fixes to ROMS with known issues. The intent being to provide the definitive go-to commercial releases ROM set.

Update

Following the release of the first public version of this ROM package (v1.1), a subsequent v1.2 release way back in 2014 and significant update in 2019, I am now pleased to announce a further update (v2.1). This update includes the addition of a new ROM for Moonsweeper which fixes a number of graphical glitches that were present in the original cartridge release. Thanks to AtariAge member pearsoe for this fix.

Due to the size and complexity of this project I cannot guarantee that I have not made any errors in its compilation. That said, I have done my level best to be careful and diligent throughout and honestly believe that if there are any errors they are likely to be minor in nature (e.g. incorrect name). Nevertheless, if you do spot any errors or problems then please let me know. As mentioned above, I would like for this ROM collection to become the definitive package and as such your help in correcting any problems is essential.

Included in the attached download is a Wanted List. This is a list of cartridges that are known to exist but I have been unable to source for dumping. If you have any of these cartridges then please let me know. I'm willing to pay for shipping to have the cart(s) sent to me for dumping and returned to you. Alternatively, if you are able to dump the ROM from the cartridge then please follow these requirements:

I have now finished adding all your re-dumped ROMs not already included in TOSEC, as well as marking all the newly identified bad/hacked images as such. I also took the opportunity to re-structure the whole ColecoVision hierarchy somewhat, as well as adding some new hacks and homebrews.

I am trying to use bluemsx as the emulator and it does not seem to want to run .bin files...... what roms do people use when using bluemsx for Colecovision? Or is there some setting to use to allow for .bin files to run? I'm confused.

A project manager can help to prepare more accurate estimates; to begin with, it is vital to get all of the inputs correct when calculating the cost. Some project managers use historical data when calculating the cost of a project; although this can work in certain situations, over the long term this will lead to higher variations in estimated and final costs.

There are essentially two ways to estimate the cost of a project. One of the most commonly used techniques is the ROM estimate or Rough Order of Magnitude estimate. Another way to estimate the cost of a project is by using a definitive estimate.

The way the costs are estimated is different in both methods, and it is important for any project management professional to understand how both these estimations work. Depending on the method used, a company will have more or less tolerance for variation from the estimate.

3a8082e126