cmd.exe only works for internal commands, not external commands.
Results 1 to 8 of 8

Thread: cmd.exe only works for internal commands, not external commands.

Hybrid View

  1. #1
    Registered User Niclo Iste's Avatar
    Join Date
    Oct 2007
    Location
    Pgh, PA
    Posts
    2,051
    Quote Originally Posted by jake21 View Post
    I think that this problem isn't connected with the program that you have installed. It seems that some problem connected with system drivers appeared.
    Drivers to run the CMD or a batch file? Is that like downloading more RAM? Or buying more Ghz to install on your processor?

    The command prompt and functions of programs are more likely affected by file structure changes, file association changes, or the registry and less likely by drivers unless the batch is calling on a process that specifically uses the drivers, additionally you don't need drivers to use the CMD.
    One Script to rule them all.
    One Script to find them.
    One Script to bring them all,
    and clean up after itself.

  2. #2
    Registered User
    Join Date
    Mar 2013
    Location
    Catheys Valley, CA
    Posts
    3
    Thanks for your comment jake21, but Bravo to Niclo! Good sense of humor too.
    The batch files I referred to are very simpleminded -- they just change to a different directory and run a .exe program. It was quicker than changing the path at the time.
    There are some strange things in the registry, like "inst imposta ayarla felrak eviewset", but I'm hesitant to change anything until I fully understand what I'm changing. I've changed things in the registry with good results before, but not without fully researching and understanding what I was doing.

    The problem seems to be with ntvdm.exe, and I'm thinking that nero installed a modified version of it as I know they use a lot of system calls to burn CD's. The internal cmd.exe command work in cmd.exe because ntvdm.exe does not load when cmd.exe loads. Ntvdm.exe is only loaded by cmd.exe when you try to run an external program and that's when it hangs. When I run command.com instead of cmd.exe, ntvdm.exe loads with command.com and it hangs too. A blinking cursor only, no prompt, and it's hung too.

    I ran sfc.exe /scannow and after several seconds of scanning it asked for the original CD, so I presume it found something wrong. I don't have the original CD but I do have the Product Key, thanks to Belarc Advisor, so I'm going to find an xp pro sp3 CD and run the Recovery Console to see if that fixes the problem. A new adventure.

    Thanks for everyones help.

Similar Threads

  1. cmd commands
    By shock1 in forum DOS
    Replies: 2
    Last Post: March 8th, 2004, 08:56 AM
  2. DOS Commands
    By jfesler in forum Tech-To-Tech
    Replies: 6
    Last Post: February 4th, 2004, 10:51 PM
  3. CMD commands
    By qwicker in forum Programming And Web Design
    Replies: 6
    Last Post: January 7th, 2004, 12:54 PM
  4. Dos Commands
    By blue_screen in forum Tech-To-Tech
    Replies: 7
    Last Post: June 18th, 2001, 11:25 PM
  5. at commands with NT
    By jmlozan in forum Tech-To-Tech
    Replies: 1
    Last Post: November 1st, 2000, 02:22 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •