cmd - only momentary access on xp

In doing Start-Run-cmd, I get into DOS momentarily, then the system reverts back to windows. My first clue that something was 'different' was when I did Start-Run, the default command was %SYSTEMROOT%\SYSTEM32\CMD.EXE. I have never entered the command this way. I'm guessing someone or something took control of my computer and did something bad. Any suggestions on how to remedy my situation? In looking at the processes running in task manager I see 'cmd.exe' is running. Is that the source of my problem? There is a 'cmd.exe' for each try to get into DOS. Also, yesterday I saw a '(space)wowexec.exe session running, with no further file description (it didn't repeat after I deleted it).
I've tried running cmd from c:\windows\servicepackfiles\i386, with the same result. I get into DOS for about two seconds, then it reverts back to windows.
I've run Spybot Search'n Destroy. It found nothing.

 

I still have my initial problem: I can't get into DOS. When I hit Start-Run-cmd, I see the DOS screen for about 2 seconds, then the system reverts back to Windows. (I've tried to run the cmd.exe file in c:\windows\servicepackfiles, with the same result.) I've also tried the cmd.exe file from another xp computer.
I've done the "Read and Run Me First" procedure. Attached are the resultant files. (Note that initially I hadn't unchecked TeaTimer. I've since unloaded it.) Also, I may have had Trend Micro Corporate antivirus running for the initial parts.
I'm unable to find 'saslog.txt', although it did find about 80 'issues' which it looked after.
Thank you for your help.

 

Is this better? (The DOS screen disappears very quickly, which is my problem. But I think this one has more content. Thanks!

 

No luck yet. I've removed Hydravision, and run sfc / scannow twice.
Whether I click on the command prompt, or do run-cmd, I get the black DOS screen for about 2 seconds, then it reverts back to Windows.
This is a business computer on a Small Business Server 2000 domain.
This is obviously not an urgent problem (... until I need to do some heavy duty DOS commands, etc.)

 

I didn't but I've loaded it, rebooted, updated, rebooted - problem still persists.