Re: Eagle (Was: GEMDOS from VBL)

[Jo Even Skarstein <joska@nuts.edu>]

On Sun, 21 Jun 1998, Petr Stehlik wrote:

> Actually Eric already answered it some months back. He said everything
> but device drivers should/could be started after MiNT. But has anyone
> tried it already? To put NVDI and all these AES/VDI patches after MiNT?

NVDI doesn't work when started after MiNT.

> BTW, MiNT used to be designed to run automatically all programs that
> were placed after MiNT in AUTO folder. This feature had been lost in some
> versions between 1.0x and 1.12 and that's why probably people got to put

This is not correct, MiNT was initially designed *not* to run programs
in AUTO. When MultiTOS came along this was changed, and all versions
since then is able to do this. I'm running 1.15.4 with some programs
after MiNT in AUTO myself. Perhaps you're running a kernel without
MultiTOS-support (-DMULTITOS iirc)?

> Now, when the feature is back, it should be easy to place MiNT.PRG
> freely and find all those programs that are not able to be started after
> MiNT. HSMODEM is the first example.

I normally run MiNT last in the auto-folder, unless there are TSRs
that *must* run after (like Videlity or 68882.prg), just because I
don't want MiNT's process- and memory-manager to know about them. 


/*
** Jo Even Skarstein    http://www.stud.ntnu.no/~josk/
**
**    beer - maria mckee - atari falcon - babylon 5
*/