mumbai

Many Sierra titles for the ColecoVision share this blue/white label variation. The non-foiled label versions seem less common, though any suggested relative distribution is likely guesswork.

No, it's legitimate as a production sample / review copy / loaner. It's not a prototype per se. It's not worth the asking price.

Blurriest photos ever attached to that listing, but that is the Collectorvision release. It is not from the '80s.

No. There's homebrew packaging for this game (among others) that uses the CBS style.

Yes: https://www.atarimax.com/colecosd/documentation/

This. 100%. Add Nice Ideas (France) to disprove the notion, even narrowly limited to just '80s ColecoVision software, that all notable game development houses were solely based in the United States. However, this whole subthread is veering off-topic (the only subthreads to which I respond, it seems).

Given how his post was written, I believe mr_me was speaking about future prospects, not past actions, w/r/t ordinary retail products. You answered your own question posed as to when, if ever, sale limitations were imposed on cartridges of any kind.

I've been pranked! May this day pass quickly.

Do you recall the ftp server from which this file came? Just curious.

You might have better luck posting this in the Wanted subforum of the Marketplace here.

One can shift the PNGs to grayscale and reoptimize to achieve the same visible output, with approximately 75% file size reduction on average. Individual files will report 72dpi rather than 600dpi, but the pixel dimensions are identical. See attached. Repro png (optimized grayscale).zip

The attached build appears to address the crash-on-load in all cases: forced integrated graphics, forced discrete graphics, and dynamic graphics switching. Interesting. Was able to idly generate an unrelated crash using "revert to saved" on Goonies. clocksignal-8bppstencial-revertosaved-crash.txt.zip

Addendum: If I force use of the integrated GPU only, no crash. If I force use of the discrete GPU, crash as reported. I guess this is why your MBA wins out. Not certain what's "wrong" with the GeForce that isn't with the Intel GPU w/r/t Clock Signal.

I'm on a mid-2012 Retina MBP, which I'd like to think outclasses a 2011 MBA. System profiler reports thus: Intel HD Graphics 4000: Chipset Model: Intel HD Graphics 4000 Type: GPU Bus: Built-In VRAM (Dynamic, Max): 1536 MB Vendor: Intel Device ID: 0x0166 Revision ID: 0x0009 Automatic Graphics Switching: Supported gMux Version: 3.2.19 [3.2.8] Metal: Supported, feature set macOS GPUFamily1 v3 Displays: Color LCD: Display Type: Built-In Retina LCD Resolution: 2880 x 1800 Retina Framebuffer Depth: 24-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Automatically Adjust Brightness: No NVIDIA GeForce GT 650M: Chipset Model: NVIDIA GeForce GT 650M Type: GPU Bus: PCIe PCIe Lane Width: x8 VRAM (Dynamic, Max): 1024 MB Vendor: NVIDIA (0x10de) Device ID: 0x0fd5 Revision ID: 0x00a2 ROM Revision: 3688 Automatic Graphics Switching: Supported gMux Version: 3.2.19 [3.2.8] Metal: Supported, feature set macOS GPUFamily1 v3 Crash occurs when plugged into the wall, so the latter GPU is in play, not the integrated Intel chipset.

I hate typing this, but the 20190303 release still crashes out on my laptop. Log attached. clocksignal-20190303-macos10.13.6-crashlog.txt.zip

Thanks for the attachment. Same behavior as before, though.

Beamrider crash attached, fwiw. clocksignal-crash-macos10.13.6.txt.zip

Funny, I tried two of those three titles, myself. Hmm ... I suppose I could attach a crash file in case someone wants to look. Not interested in migrating up to 10.14 just yet to see if lagging behind on 10.13 is the culprit. Thanks for providing at least one difference in use cases to explore, though.

And you're doing anything other than File>Open [rom file]? Which OS and version? If not, I guess the question becomes what's the source of the crash-on-load issue that's unavoidable for me.

Is there anything by way of documentation on how this should function? Opening ROMs (ColecoVision) from within the application immediately crashes out on macOS 10.13.6 ... I feel user error may be at fault, but it's not clear how to obtain what is demonstrated in the thumbnails above.

Cartridge availability mostly updated. Numerous additions, including: + 2010: The Graphic Action Game + Antarctic Adventure + Cabbage Patch Kids: Adventures in the Park + Defender + Dukes of Hazzard + Frogger + Front Line + James Bond 007 + Keystone Kapers + Miner 2049er + Montezuma's Revenge + Pitfall! + Pitfall! II + Zenji

Clearly Sydney had a hand in bringing Evolution to market, yet their role seems confined to that of a rights licensor (and potential co-developer) that handed the title off for material production and distribution by another party, at least in the case of the CV/A platform. I'd guess that deciding how far up the chain from final product one would count [co-]publisher status is a matter of opinion, but to me it looks like the weight in this case falls more heavily on Coleco (Canada) than Sydney. Nice find on that brief article. Good question. The write-up referenced by mr_me suggests the game began on the Apple platform. The packaging of the CV/A version of Evolution merely credits Sember and Mattrick as creators. The manual is altogether silent on any additional development specifics. It does declare Sydney to be a "major developer of computer games" etc., which is open to interpretation with respect to porting software they licensed, absent additional information.

And what actual distribution does that retail flyer match, though? The home computer systems as indicated? I was referring to the ColecoVision console, in which case I'm unaware of a self-distribution by Sydney.

I don't think Sydney "published" Evolution ... unless there's another distribution apart from Coleco (Canada)'s or, I guess, TeleGames's.

These are present for all the Activision gatefold boxes they produced for the ColecoVision: Decathlon, H.E.R.O, Pitfall ][, and Zenji. So you've listed them all. Not sure what the formal term would be (there must be one). I've always called them "secondary platform packaging", which is clumsy at best.