[hatari-devel] Executing program with Hatari (was: [Bug #17567] ...)

Miro Kropacek miro.kropacek at gmail.com
Tue Oct 5 22:44:17 CEST 2010


Hi,


> So I think GEMDOS emulation is better solution.  You can check Hatari's
>
your arguments are very good, I tend to agree with you now.

I meant that the OS needs to boot before program can be run.
> Programs may need OS services (e.g. GEM) to work.
>
Sure, TOS would be needed, that's no question. GEM -- yeah, that's a
problem. But for a GEM stuff, one can use Aranym with far better chances for
easy development.

I was thinking that if Hatari could create the INF file virtually, then
> the program could be in a read-only directory, e.g. on CD.
>
Yes, this respects my wish of not bothering user with some crappy
DESKTOP.INF file, as it's created virtually. With this feature, I mark this
feature request as perfectly done ;) You can do it as following: take
current emulated GEMDOS HDD, look for desktop.inf/newdesk.inf, if present,
do nothing (or make it optional, what to do). If not present, look for
command line argument if there isn't something to run, if so, create virtual
inf file and slide it to GEMDOS HDD. Shouldn't be so hard or?

Hatari package for Linux distros could then even register a Linux
> binfmt_misc handler that invokes Hatari automatically when one clicks on
> an Atari binary.  (Like some people have done with Wine and Window programs
> or Java VM and Java programs.)
>
Holy crap, this would be awesome !!!

> This isn't that critical. Can be added later, if needed at all.
>
> It might be nice for the cases when the messages disappear too fast to read
> them.  Unfortunately it seems that e.g. EmuTOS messages cannot be catched
> this way[1].
>
I meant, this particular feature of re-interpreting escape codes isn't that
critical, the feature as whole is something I miss badly ;-) I don't care
about OS stuff (one can use much better techniques provided by excellent
Hatari debugger), this is about application level, it's so boring to
implement "press a key to exit" for TOS programs, prey text will fit into
console size and wont scroll away etc... (esp. for demos where graphics,
i.e. non-console screen is used I have no other options for logs than
postponed screen output of files, what is quite inconvenient).


-- 
MiKRO / Mystic Bytes
http://mikro.atari.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.berlios.de/pipermail/hatari-devel/attachments/20101005/69c185bf/attachment.html>


More information about the hatari-devel mailing list