startup.cmd

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
automatically.
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.
My question:
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,
um95Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sbuftonCommented:
I don't believe that there is any way for you to specify that startup.cmd should be kept in the foreground. What is worth checking, though, is whether you have anything in your Startup folder (inside OS/2 System on the desktop); startup.cmd starts first, then the programs in the startup folder, and each program in the startup folder snatches focus away from the previous program.

I can only think of two ways you could try to make your program come up in the foreground: start it as the last item in startup.cmd *after a pause* long enough to make sure that the desktop has completely started, or move the call to start it out of startup.cmd and put a shadow of the program into the Startup folder, again as the last item.
At the moment, I can't think of a way for you to put a pause in the startup.cmd, though. Perhaps there is some free- or shareware program which would do that.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
um95Author Commented:
In fact, the real problem after some more tests is:
Even if you launch a program with /f option from startup.cmd after the desktop is up, the /f has no effect.
It seems to be impossible, to launch a program in foreground from startup.cmd after the desktop is up.
0
sbuftonCommented:
I guess the problem is that as the desktop starts, the WarpCenter (in Warp 4) and the Launchpad (in Warp 3) get started, snatching the focus away from other programs which were started before.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Operating Systems

From novice to tech pro — start learning today.