Floppy keeps spinning after fread

[Csoft]

Hello all,

I'm developing a game in C, in my code I load assets from floppy with fread/fclose functions, it works, but the floppy keeps spinning even after the load is completed.

How can I solve it?

Thank you in advance,

Lorenzo

[Galahad/FLT]

Originally Posted by Csoft

Hello all,

I'm developing a game in C, in my code I load assets from floppy with fread/fclose functions, it works, but the floppy keeps spinning even after the load is completed.

How can I solve it?

Thank you in advance,

Lorenzo

Are you shutting down the system after loading files or stopping multitasking with Forbid?

[Csoft]

Originally Posted by Galahad/FLT

Are you shutting down the system after loading files or stopping multitasking with Forbid?

No, I'm not shutting down the system at all. I'm trying to keep everything OS friendly.

[alkis]

what's the flow?
fopen/fread/fclose? (c library)
Open/Read/Close? (OS)

[phx]

Originally Posted by Csoft

No, I'm not shutting down the system at all. I'm trying to keep everything OS friendly.

Then there is no reason it could ever happen. And it should be easy to isolate the problem with some test code doing fopen/fread/fclose.

Is it some strange file system? Or standard FFS?
Note, that a running motor for a few seconds after the last access is normal.

[Csoft]

Originally Posted by phx

Then there is no reason it could ever happen. And it should be easy to isolate the problem with some test code doing fopen/fread/fclose.

Is it some strange file system? Or standard FFS?
Note, that a running motor for a few seconds after the last access is normal.

Simply this, with standard Amiga FFS, it keeps spinning forever:

FILE *fp = fopen(filename, "rb");
    if (fp) {
        fread(dest, sizeof(unsigned char), size, fp);
    } else {
        printf("error: file '%s' not found\n", filename);
    }
    fclose(fp);

[Thomas Richter]

Please post a complete source. For example, you could run into a buffer overrun here, overwriting some Os variables if "dest" is smaller than "size" bytes. Thus, what is "dest", and "size", and how are they allocated? A standard "fread" (or an underlying Read()) will not cause this.

[Asman]

Originally Posted by Csoft

Simply this, with standard Amiga FFS, it keeps spinning forever:

FILE *fp = fopen(filename, "rb");
    if (fp) {
        fread(dest, sizeof(unsigned char), size, fp);
    } else {
        printf("error: file '%s' not found\n", filename);
    }
    fclose(fp);

What about such code, it still keeps spinning forever ?

FILE *fp = fopen(filename, "rb");

if (fp)
{
    fread(dest, sizeof(unsigned char), size, fp);
    fclose(fp);
}
else
{
    printf("error: file '%s' not found\n", filename);
}

Furthermore you can also print value from fclose, should be 0.

[Olaf Barthel]

Originally Posted by Csoft

Hello all,

I'm developing a game in C, in my code I load assets from floppy with fread/fclose functions, it works, but the floppy keeps spinning even after the load is completed.

Which operating system version are you developing and testing your game on? Are you using timer.device I/O requests in your game? Any chance you might be using a vertical blanking interrupt handler in your game?

It's the job of the file system to tell the floppy disk drive to spin down and give it a rest. This should happen within 3-4 seconds of no file system activity taking place, such as the last read or write operation. Because the file system uses timer.device to schedule periodic tests for activity, accidentally knocking out timer.device processing may cause the spindown never to take place (trackdisk.device does not spin down on its own accord).

Question is whether your game code might be responsible for that.

[Csoft]

Originally Posted by Olaf Barthel

Which operating system version are you developing and testing your game on? Are you using timer.device I/O requests in your game? Any chance you might be using a vertical blanking interrupt handler in your game?

It's the job of the file system to tell the floppy disk drive to spin down and give it a rest. This should happen within 3-4 seconds of no file system activity taking place, such as the last read or write operation. Because the file system uses timer.device to schedule periodic tests for activity, accidentally knocking out timer.device processing may cause the spindown never to take place (trackdisk.device does not spin down on its own accord).

Question is whether your game code might be responsible for that.

I'm working on 3.0. No use of timer.device, but I DO use a vblank interrupt, yes. Could be this the source of the problem?

[Thomas Richter]

If the system timer is not run, yes. What is the return code of your code? Note, in particular, that your code shall return with Z flag set as otherwise the exec interrupt handler assumes that your code handled the interrupt completely, and will not call the remaining system interrupt handlers, including the one of the timer.device.