|[hatari-devel] Fastload from GEMDOS drive emulation|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] Fastload from GEMDOS drive emulation
- From: Vincent Rivière <vincent.riviere@xxxxxxxxxxx>
- Date: Mon, 10 Jun 2019 00:56:54 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:subject:to:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=oKIGg9PJDFNETUDsrD9mz5KeqhcjEQ2/bRg01XOXmUI=; b=uLr0s28X3C+MTTZ4ZkRcQDzF6GzjAERHYFDtyppF4BBT5MODBC1ETJIdVR3OwDgFft +C6NgXfa2YLw1157zG4hjZCWmYo0NGBlEjdpI3+UwVPxw4DY9LWuvtKTvder2vxbqjA6 vfj/sH6VHBheyAJTWisX1ouElbpQtlaHyIGRNmy9zdc64Nf3gzSh35tliDmxPV5gn4Qs MMlK8A+o5jIbXW8xvv0SR86yKO4+r8GlwDE/0cPo3JN7EPV15OhUf8Zbjou7TVjrbFh0 gaglCMJGg9nEy0gps1j8BEgxtcWRxt0i1n3w3ehRwMzgTMIOxQAr6jzwmjO3vC8Ca38O p/sw==
It seems that Hatari GEMDOS drive emulation forces the Fastload behaviour.
Am I right? And is this expected behaviour?
For example, if I put a program *without Fastload bit set* on floppy, its
startup time takes more time when there is a lot of RAM in the system. This
is very visible with 14 MB of ST-RAM, there is a pause of at least 3 seconds
after the program has loaded. This does not happen when the Fastload bit is
set, as expected.
But this does not happen either from emulated C:, even if the Fastload bit
is not set.
Bug or feature?