S
sean
I'm trying to change my applications priority to something besides the
basic highest, above average, etc. I'm developing for an embedded
processor (Windows CE 4.2), thus I'm using evc++ in conjunction with
vb.net. Now I can make a CeSetThreadPriority call using a C dll (from
the VB app), which does allow me to change the process priority to
something other than the 'supposed' allowed priorities (which are
251-255 for those who are wondering, 251 being the 'highest', and 255
being the 'lowest', and fyi 255 is the lowest priority a thread can
have in an embedded application, period). Now making this C call thru
a dll works (succeeds), however, the priority REALLY doesnt change, i
know this because high-impact C threads running at a priority of 250
(or higher) kill the vb.net application. I'm attributing this to the
fact that any vb.net embedded application is actually running 5 threads
for one application (instead of one as you would assume), and the other
threads priorities probably aren't getting changed when you call
CeSetThreadPriority. So I guess my question is... what are these
background threads? Can you change their priority? I dislike VB for
these types of situations, although its ease of use for graphics is
amazing. Any help would be greatly appreciated, thanks.
basic highest, above average, etc. I'm developing for an embedded
processor (Windows CE 4.2), thus I'm using evc++ in conjunction with
vb.net. Now I can make a CeSetThreadPriority call using a C dll (from
the VB app), which does allow me to change the process priority to
something other than the 'supposed' allowed priorities (which are
251-255 for those who are wondering, 251 being the 'highest', and 255
being the 'lowest', and fyi 255 is the lowest priority a thread can
have in an embedded application, period). Now making this C call thru
a dll works (succeeds), however, the priority REALLY doesnt change, i
know this because high-impact C threads running at a priority of 250
(or higher) kill the vb.net application. I'm attributing this to the
fact that any vb.net embedded application is actually running 5 threads
for one application (instead of one as you would assume), and the other
threads priorities probably aren't getting changed when you call
CeSetThreadPriority. So I guess my question is... what are these
background threads? Can you change their priority? I dislike VB for
these types of situations, although its ease of use for graphics is
amazing. Any help would be greatly appreciated, thanks.