I have following problem with Warp 4.
When booting the system, startup.cmd is in foreground until the desktop
is setting up. Once the desktop is up, startup.cmd looses the focus.
This is a problem for me, because i use startup.cmd to load several
processes and an application which has to be in the foreground
Even if i lounch my application with /f option, it doesn't get the focus.
With OS/2 2.11, startup.cmd was always in the foreground.
Is there a way to keep startup.cmd in the foreground during the whole
boot sequence ? Maybe a setting in the config.sys ?
Thanks for your help,