| Re: [hatari-users] hatari-prg-args not working quite right |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-users Archives
]
Hi,
On 1.2.2024 23.58, Charles Curley wrote:
On Mon, 29 Jan 2024 01:03:37 +0200
Eero Tamminen <oak@xxxxxxxxxxxxxx> wrote:
Please make sure that TOS can launch the program when you give that
same program path to Hatari with the "--auto" option, before using
"hatari-prg-args" to provide command line arguments for the launched
program.
It does.
>
I neglected to mention that this all worked under Debian 12, Bullseye,
where the version was 2.3.1+dfsg-1
I do not see in trace output any attempt for TOS to launch given
program. Are you sure you used Hatari "--trace os_base" option?
I did not.
--trace-file, by the way, turned out to not work right. It creates the
file, but then fails to re-direct the output.
Works fine for me.
Or did you mean that _only_ trace output went to trace file?
(There's a separate "--log-file" option for Hatari log output, e.g. from
"--log-level debug".)
Easily fixed with a bit of redirection, of course.
If one wants all the output in correct order in same file, redirection
is indeed best (and reason why all those outputs were changed to go by
default to stderr).
> e.g.:
> hatari --trace-file ~/hatari.$(date +%Y.%m.%d-%H.%m.%S).txt -m \
> --auto 'C:\FF\FAST4TH.TTP' &
Please provide output from above too (with "--trace os_base --log-level
debug").
Anyway, I finally got a trace (attached) with this (wrapped) command
line:
hatari-prg-args -q -m --trace os_base -- 'C:\FF\FAST4TH.TTP' 3 load &>
~/hatari.args.prg.$(date +%Y.%m.%d-%H.%M.%S).txt
According to log:
* Hatari determined A: to be boot drive in your configuration, and
* It created virtual EMUDESK.INF on A: (for program given with "--auto"
argument)
* EmuTOS did not run program specified in that INF file
Exactly same should happen when giving "--auto" argument directly to
Hatari, that's why I want log of that too. Are you really sure you used
same Hatari version & config in both cases?
- Eero