Programmers Workbench Question

  • Thread starter Thread starter Jim Carlock
  • Start date Start date
J

Jim Carlock

Two questions:

(1)
When I start up a command prompt (cmd.exe /K) and then start
Programmers Workbench up inside of it, the CPU useage goes
up to 99-100% and stays there.

Is there a way around this ? NTVDM.EXE shows up as doing
all the processor work and everything else in Windows becomes
sluggish.

(2)
How do I get the mouse to work inside the command prompt ?
In the older Windows version, I used to have to load a mouse
driver up via either config.sys or autoexec.bat. What is the
recommended way to do this inside XP ?

Thanks for any and all answers.
 
Hi Kelly,

Ahh, I was going to say something, but I see that I had to take
the checkmark out of QuickEdit, so, I will instead say that taking
the check mark out of QuickEdit did the trick.

I don't know what happened earlier. I was just starting up a
cmd.exe and then starting Programmers Workbench up from
within it, by typing PWB (it's in the Path). ntvdm.exe was jumping
up to 99% / 100% useage. It seems to have stopped for the
time being. Strange. The CPU useage was taching out. All I've
done since then, is to run a few DOS command prompts and close
them down and I've shut down several other programs as well.

Now... sometimes ntvdm.exe jumps up to 100% and sometimes
it stays at 0%. This is very wierd.

Thanks.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


:
Hi Jim,

2. Depending on how much of a mouse you need, use the Quick Edit Mode.
Automated on line 40:
http://www.kellys-korner-xp.com/xp_tweaks.htm
 
Jim said:
When I start up a command prompt (cmd.exe /K) and then start
Programmers Workbench up inside of it, the CPU useage goes
up to 99-100% and stays there.

Is there a way around this ? NTVDM.EXE shows up as doing
all the processor work and everything else in Windows becomes
sluggish.

The environment there is an emulation, and consequently things run in it
run slower. My guess would be that PWB has some sort of loop it runs
round while awaiting attention, and that is soaking CPU. It may be
trying to process input about the mouse direct, hence it dropping back
once you got QuickEdit working
 
I seemed to have done something with a switch in the command
prompt (cmd.exe) that I started up yesterday. I can't get rid of
the of 100% CPU problem now. If someone thinks of something
let me know...

I've tried the following things:

cmd /c pwb.exe
pwb.exe
pwb
cmd /k pwb.exe

I was playing around with some of the other switches yesterday,
using the start command, ie:

start pwb.exe
start command.com
start cmd.exe

.... I was looking for a way to start a couple programs up in different
DOS windows, from a single DOS command prompt. The START
command accomplished this quite well... and that's when I noticed
my CPU useage going up when starting Programmer's Workbench
( PWB.EXE ) which is an old DOS Assembly Language Editor that
Microsoft gave out with MASM and continues to give out with
MASM. It predates 1994.

But that is NOT the only program that causes ntvdm.exe to jump
to 100% CPU useage. The DOS EDIT command does it as well.
So it's happening with DOS programs supplied with XP as well.

Changing the QuickEdit does NOT seem to have any effect upon
it.

Wierd...

Okay, I just found a fix... I'm wondering if you guys can duplicate
this by:
1) running cmd.exe
2) typing edit at the command line and pressing [enter] and respond
by telling me what your CPU is doing.
3) type, inside the cmd.exe prompt:
start command.com
4) inside the new command.com window, start up edit there and let
me know what your CPU is doing.

Just want to know if others are experiencing this as well. Thanks.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


Jim said:
When I start up a command prompt (cmd.exe /K) and then start
Programmers Workbench up inside of it, the CPU useage goes
up to 99-100% and stays there.

Is there a way around this ? NTVDM.EXE shows up as doing
all the processor work and everything else in Windows becomes
sluggish.

The environment there is an emulation, and consequently things run in it
run slower. My guess would be that PWB has some sort of loop it runs
round while awaiting attention, and that is soaking CPU. It may be
trying to process input about the mouse direct, hence it dropping back
once you got QuickEdit working
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top