Hi,
On 27.6.2022 13.16, Paweł Góralski wrote:
I've made a check on second machine and result is the same. Maybe
it's a fault of NF_AHCC.TOS I've downloaded from repo
(https://git.tuxfamily.org/hatari/hatari.git/tree/tests/natfeats)?
No, the binary in repo works fine (I tested downloading and trying the
latest one).
W dniu 27.06.2022 o 11:44, Paweł Góralski pisze:
Hi it was me, I didn't answer, because there was nothing to answer
to. NATFS doesn't work for me. Tested same same build
(hatari-win64-ce8058b.zip) later by Czietz, but it works same as
earlier (NF_AHCC.TOS program quits, there's nothing in the logs
related to NATFS, debugger isn't triggered). I've checked both debug
and release builds.
I will check it on another machine and see what happens.
It's really odd that:
* Same Hatari Windows snapshot works fine for Christian, but not for you
* Trace output works for you, but NatFeats does not
NatFeats NF_STDERR explicitly outputs to "stderr" and both log & trace
outputs default also to "stderr". So when using Hatari defaults,
there should be no difference whether you see trace or NF output.
If you use:
--------------------------
hatari -W --natfeats on --log-level debug nf_ahcc.tos
--------------------------
What debug output you see?
The output should look something like this:
--------------------------
DEBUG: Native Features enabled.
DEBUG: ARG = autostart program: nf_ahcc.tos
...
DEBUG: Virtual INF file 'C:\EMUDESK.INF' matched.
DEBUG: Virtual INF file removed.
VDI video mode = 320x200 4-plane
Emulator name:
Hatari v2.4.0-devel (Jul 1 2022)
Invoking debugger...
--------------------------
- Eero
W dniu 27.06.2022 o 11:03, Nicolas Pomarède pisze:
Le 20/06/2022 à 23:33, Eero Tamminen a écrit :
Hi,
On 20.6.2022 20.48, Nicolas Pomarède wrote:
with the work done recently by everyone, what are the open /
blocking issue ?
On my side, falcon's sound is fixed and I don't see any urgent
fix to be done.
>
Laurent will have a look at the DSP change and maybe fix it (or
revert it).
what do other need to push ?
I have nothing that could not wait until after the release.
There's this one issue at atari-forum that would be good to be
verified that it's the same issue that Thomas already fixed,
before release.
I think all the Hatari docs can be updated to 2.4 while waiting
couple of days for the user to answer.
Btw. There have also been few issues on atari-forum where it seems
like Hatari boolean options do not work (enabling NatFeats in one
case, selecting ext disassembly output in another), but I think in
both case it's under Windows, i.e. out of our hands.
hi
it seems the user didn't answer so far, so I think I will not wait
too long.
Unless someone needs to push urgent things to the repo, I ask to
not commit anything after tomorrow (tuesday 28/6), then I think I
can work on the release in the next days.
Nicolas