MDI and FDI device driver updates

[Martin_Head]

I noticed a problem with my Microdrive and Floppy disk image drivers.

The MDI_FILE$ and FDI_FILE$ functions were damaging the maths stack. Leaving time bombs behind, that go off unexpectedly.

The forum software would not let me attach all the files in one message, So here's the FDI ones.

[Martin_Head]

And here's the MDI ones.

[Derek_Stewart]

Hi Martin,

Thanks for the update.

I use FDI and MDI on the Q68,, I had not noticed any problems.

[Martin_Head]

Hi Martin,

Thanks for the update.

I use FDI and MDI on the Q68,, I had not noticed any problems.

If you don't use the MDI_FILE$, or FDI_FILE$ functions, and I don't expect many people do. Then you won't see a problem. Even if you do use it, you may not see a problem. Or something strange will happen later.

For example, The way I noticed it, was that I had a Procedure that used FDI_FILE$ to read the mounted image names into an array.
Later a Function, that had nothing to do with FDI_FILE$, or the array. Would fall over on the RETurn line, saying the Procedure or Function had no RETurn.

[Derek_Stewart]

Hi Martin,

I was looking at those functions to develop a software distribution for the Q68 using FDI or MDI images.

[Martin_Head]

Hi Martin,

I was looking at those functions to develop a software distribution for the Q68 using FDI or MDI images.

I'm currently tinkering with a MDI/FDI image manager program based on what I was doing here viewtopic.php?f=3&t=4182&start=10#p47955

But using menu_rext to select the images, instead of an external Windows program.

That's where I hit the bug. One day, I only saw the problem when I mounted one particular image file. But the next day it did it on all the image files.