Re: [hatari-devel] NatFeats on Windows (was: Preparing for next release 2.4) |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] NatFeats on Windows (was: Preparing for next release 2.4)
- From: Christian Zietz <czietz@xxxxxxx>
- Date: Sun, 3 Jul 2022 17:02:55 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1656860576; bh=pHmxr2oVbvUsMoMnGJMtJk4AJwowa1Qvi5LfGzb1YG4=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=MPqv0jBGGNvzxpPZfyHnKg9Qx2bOXfWQKRVQeWVC2GL5OisCga+1u4rc2H/crt68Z y0tRtibYoQst/B67Xftot1iTA1/7furI9UxLQ2sL/ai3npmQQhEllVXqc4+Io9DMog IL1j+SECJO3OlLhPTT9vTBjhL0FqR24q+ORubKmY=
Paweł Góralski schrieb:
As a follow up to my previous mail I can confirm that natfeats logging
started to work in my application too, when I've used modified binary
and launched hatari from cmd. But I'm using only logging right now, no
other features.
That's frankly a bit weird. What this change does: It changes the
so-called "subsystem" in the PE executable header from GUI (02) to
Console (03). This means that the standard handles are directed to the
console from where you launched Hatari. Otherwise, there is no console
attached and, as you know, you therefore need the "-W" switch to open a
separate console window.
But for me Natfeats output and other Natfeats calls work in either case.
I don't recall: If you use the original binary (i.e, subsystem set to
02), you don't see any Natfeats logging from your application in the
separate window, right?
Regards
Christian
--
Christian Zietz - CHZ-Soft - czietz@xxxxxxx
WWW: https://www.chzsoft.de/
PGP/GnuPG-Key-ID: 0x52CB97F66DA025CA / 0x6DA025CA