[Coco] MAME FDC Issue that can cause corruption

[Salvador Garcia]

"I just wonder if this was introduced when the floppy access sounds wereadded?"

I would say it is plausible. This issue has the trademark of multi-threading gone wrong, assuming that this is even used for this functionality.

Salvador

On Tuesday, August 1, 2017, 11:08:55 AM CDT, Ron Klein <ron at kdomain.org> wrote:

The issue is being actively looked at.

I just wonder if this was introduced when the floppy access sounds were
added?



On Tue, Aug 1, 2017 at 11:02 AM, David Ladd <davidwladd at gmail.com> wrote:

> Barry,
>
> That would be good to test on version 0.188 on the Mac.  So far my current
> tests were done using the Official 32bit & 64bit Windows Binaries for
> version 0.188
>
>
> +-----------------------------------------------------------------------+
> | David Ladd a.k.a. PacoOtaktay a.k.a. Drencor                          |
> | YouTube: http://www.youtube.com/user/PacoOtaktay                     |
> | YouTube Gaming Live: https://gaming.youtube.com/user/PacoOtaktay/live |
> | Websites: http://dwladd.com     &    http://www.theterrorzone.com   |
> | G+:  https://plus.google.com/113262444659438038657                   |
> | G+:  https://plus.google.com/+DavidLaddPacoOtaktay                   |
> |                                                                      |
> | Do you have your CoCo 3 yet?                                          |
> +-----------------------------------------------------------------------+
>
>
> On Tue, Aug 1, 2017 at 10:53 AM, Barry Nelson <
> barry.nelson at amobiledevice.com> wrote:
>
> > I was also able to reproduce this with the DIR commands on separate lines
> > when I was able to type in the second DIR fast enough. When I have time I
> > will try to build 0.188 (or later) and see if the issue persists. This
> may
> > take some time. There were no special disk images needed to reproduce
> this
> > issue, I created two blank JVC images and formatted them as described
> below.
> >
> > > On Aug 1, 2017, at 4:30 AM, Barry Nelson <barry.nelson at amobiledevice.
> com>
> > wrote:
> > >
> > > I have confirmed this issue on my Macintosh build of MAME as of version
> > 0.186 and later. David, have you filed a bug report?
> > >
> > >> David Ladd davidwladd at gmail.com  <mailto:coco%40maltedmedia.com
> > ?Subject=Re%3A%20%5BCoco%5D%20%5BCOCO%5D%20MAME%20FDC%
> > 20Issue%20that%20can%20cause%20corruption&In-Reply-To=%
> > 3CCAHW2jkD0ehDiQ7H--G5TxgskT4X3pWxnUuy-XEtkdOd56gMY1Q%40mail.gmail.com
> %3E>
> > >> Tue Aug 1 01:50:32 EDT 2017
> > >>
> > >> If you want to try it out the simplest way to show this off is to do
> > this:
> > >> Startup CoCo 2 or CoCo3 emulation
> > >> Create a new disk image in drive 0
> > >> Create a new disk image in drive 1
> > >> DSKINI 0
> > >> DSKINI 1
> > >> Enter a quick basic program like this and save it to disk:
> > >> 10 PRINT "DIR 0"
> > >> 20 DIR 0
> > >> 30 PRINT "DIR 1"
> > >> 40 DIR 1
> > >> 50 GOTO 10
> > >> SAVE"TEST1.BAS"
> > >>
> > >> Then all you have to do to see the problem is to:
> > >> DIR 0:DIR 1
> >
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > https://pairlist5.pair.net/mailman/listinfo/coco
> >
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>

-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco