[Coco] Mess is a mess.... again....

[Bill Pierce]

John, why bother? I'm not planning on using it. I just needed to run the debugger for about 5 minutes, so I loaded a "known working version" (very old) and did what I needed. By the time it gets fixed, I will have moved on from what I needed it for anyway.
What I can't understand is that it's been like this since before v1.56 (now 1.70) and no one has noticed it ????
Besides, they'll just break something else on the next revision, even if they fix the floppy drives.

Mark, yes, I understand the whole concept behind Mame/Mess, and I applaude their efforts... But I need consistancy when I crank up the emulator. I'm usually developing software and I don't have time to "fix the tools before I work on the car", so to speak.

I guess that's why I do like VCC... it's a Coco3 and that's all I want. And it's just getting better... :-)

 

 


Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
Global Moderator for TRS-80/Tandy Color Computer Forums
http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo at aol.com


 

 

-----Original Message-----
From: Mark McDougall <msmcdoug at iinet.net.au>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Tue, Feb 23, 2016 9:43 pm
Subject: Re: [Coco] Mess is a mess.... again....

On 24/02/2016 1:27 PM, Bill Pierce via Coco wrote:> In doing some experiments, I needed to use Mess, and wanting the> latest build, I just downloaded v1.70. The last version I "messed"> with was v1.56 & v1.65. Somewhere between 156 and 165, someone> changed the floppy system to "5.25' Quad Density Floppy Drives". Now,> absolutely no floppy disk image in the Coco archives will load!!!> Mess gives a "File format not recognized" error on every disk. I> tried a couple of tricks (like removing the 2 header bytes that VCC> creates when creating a disk) and it just completely crashed Mess.I don't have an issue with v0.166.> This is the very reason I switched to VCC years ago and have> continued to use VCC through the years. Every time I try a new> version of Mess, something else is broken (and usually it worked> before). There is no consistancy from one version to another.It's a double-edged sword. People working on VCC are working on a single emulator for a single platform - the Coco. Those working on MAME/MESS are working a framework that enables emulation of literally thousands of systems and the almost infinite variety of hardware that entails. It's inevitable that changes to the core will break some emulations, or human error when editing by someone trying to update/fix two dozens platforms at once, and it probably won't get fixed until someone shouts loud enough. But on the flip side you get the benefit of the advances made in the rest of the framework. You can't have your cake and eat it too...I don't consider _any_ emulator as an all-encompassing solution.Regards,-- |        Mark McDougall              | "Electrical Engineers do it|  <http://members.iinet.net.au/~msmcdoug> |   with less resistance!"-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco