Re: [hatari-devel] Re: Feature request: allow to specify "-d" with autostart

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On 03/31/2017 02:56 PM, Miro Kropáček wrote:
> > Attached patch handles also that case.
>
>
> OK, this looks to do the right thing but there's a bug (I think). My
> configuration was TOS 2.06de, the ACSI image from Hatari download site, an
> AUTO + FOLD100.PRG on it and my gemdos hd files.
>
> hatari --acsi 0=hd80mb.image --gemdos-drive K .
>
> still works well. However if I do this:
>
> hatari --acsi 0=hd80mb.image --gemdos-drive K HDDRUTIL.APP


As you're not using "--auto" option, this means that you need
to be in the directory where the APP resides and it equals to
to "-d . --auto C:\HDDRUTIL.APP".


> HDDRUTIL.APP starts, true,

It starts, or TOS just shows that it's trying to start it?

> but the TOS spits at me an error message about missing object.

I assume this means that TOS didn't find the application
you gave.  Does your C: drive root in above case contain
that application?

"--trace gemdos" is your friend when checking what you
actually asked Hatari to do and why it fails.


> I click OK (so this is the first bug, it runs OK in the
> former scenario if I manually click on the APP), I'm back in desktop. Now
> if I click ALT+K (so I want to open K:), it bombs out!

TOS bombing out after *.INF autostart, isn't that strange,
old TOS versions seem to do that always.  I'm wondering
whether AHDI has any impact with your newer TOS version...


> Clicking on K: drive with mouse is ok. This happens with other apps too.

Does same happen if you use floppy image (with HDDRUTIL)
instead of ACSI image?


	- Eero