Re: [ros-kernel] dflat and drivers

[Eric K. <ek...@rz...>]

"Robert K." <ro...@ko...> wrote:

Hello Robert!

> Hi,
> I plan to make a driver start and stop applet.
> So, does souch a thing already exist?

Services.exe should start and stop drivers. But at present it is still far
from being able to handle this task. Any 'driver start and stop applet' (aka
'Service Control Program' or 'SCP') should instruct services.exe (aka
'Service Control Manager' or 'SCM') to start or stop a driver. So the short
answer to your question is: No!

> I plan to use plain c with WindowProc etc. pp = simple and efficient.
> What is dflat for. Is it possible to write dualmode applications with
> that lib, or
> is it at least possible to have either a textmode app or an win app?
> Are the apis mostly compatible?

Dflat32 was planned to become a universal textmode user interface library to
support the development of powerful console mode applications. But because
there was a much stronger demand for low-level improvements my focus moved
to the kernel-mode side of the project.

Dual-mode applications are *not* supported because console-mode and gui-mode
differ in too many ways. The APIs were designed to be almost compatible with
the win32 APIs. One major problem is the good chance of stumbling upon
name-collisions caused by Dflat32. All Dflat32-APIs should use a 'Df'-prefix
to prevent these collisions.

> And what is the Systemcall to load a driver?
The function to load a driver is NtLoadDriver(). To unload a driver call
NtUnloadDriver(). NtUnloadDriver() is not implemented yet!

Eric