Randy Schad wrote:
>
> Greg Goebel wrote...
>
> > When the OK button is waiting for input, VEE won't "hog" the
> > CPU -- that is, Windows will be able to do other things while
> > the VEE program is waiting for the user to do something.
>
> Uh huh... =]
>
> Considering that any instance of VEE I've ever seen automatically consumes
> 95% processor time, I fail to see how this could be the case.
Suggestion:
% Write the following program:
+-------+
| Until |
| Break +--+
+-------+ |
|
+--+--+ +---------+
| OK +--->| Counter |
+-----+ +---------+
% Run the Windows System Monitor (SYSMON.EXE) for Win95/98. There are
different but analogous tools on NT under "Administrative Tools". Select
"Kernel Processor Usage".
% Run the program. In absence of any other actions, kernel processor
usage goes to zero.
% As a control experiment, replace the OK button with a 1-second DELAY,
which is an infamous CPU hog. Run the program again. Kernel processor
usage is pegged.
[%%] regards -- gvg
> Randy Schad
> randy@oswegosw.com
>
> Oswego Software, Inc.
> http://www.oswegosw.com
> Phone : 630-554-3567
> Fax : 630-554-0200
--
Greg Goebel ftp://fcext3.external.hp.com/dist/mxd/index.html
HP MXD Marketing http://hpislsup.lvld.hp.com (HP only)
pctm@lvld.hp.com http://www.geocities.com/CapeCanaveral/Launchpad/6000
>
> Greg Goebel wrote...
>
> > When the OK button is waiting for input, VEE won't "hog" the
> > CPU -- that is, Windows will be able to do other things while
> > the VEE program is waiting for the user to do something.
>
> Uh huh... =]
>
> Considering that any instance of VEE I've ever seen automatically consumes
> 95% processor time, I fail to see how this could be the case.
Suggestion:
% Write the following program:
+-------+
| Until |
| Break +--+
+-------+ |
|
+--+--+ +---------+
| OK +--->| Counter |
+-----+ +---------+
% Run the Windows System Monitor (SYSMON.EXE) for Win95/98. There are
different but analogous tools on NT under "Administrative Tools". Select
"Kernel Processor Usage".
% Run the program. In absence of any other actions, kernel processor
usage goes to zero.
% As a control experiment, replace the OK button with a 1-second DELAY,
which is an infamous CPU hog. Run the program again. Kernel processor
usage is pegged.
[%%] regards -- gvg
> Randy Schad
> randy@oswegosw.com
>
> Oswego Software, Inc.
> http://www.oswegosw.com
> Phone : 630-554-3567
> Fax : 630-554-0200
--
Greg Goebel ftp://fcext3.external.hp.com/dist/mxd/index.html
HP MXD Marketing http://hpislsup.lvld.hp.com (HP only)
pctm@lvld.hp.com http://www.geocities.com/CapeCanaveral/Launchpad/6000
> When the OK button is waiting for input, VEE won't "hog" the
> CPU -- that is, Windows will be able to do other things while
> the VEE program is waiting for the user to do something.
Uh huh... =]
Considering that any instance of VEE I've ever seen automatically consumes
95% processor time, I fail to see how this could be the case.
Are there any tricks to reducing VEE's outrageous CPU usage?
Randy Schad
randy@oswegosw.com
Oswego Software, Inc.
http://www.oswegosw.com
Phone : 630-554-3567
Fax : 630-554-0200