Nt port driver could not start

Do this for both boards and you'll be basically back to scratch. Probably worth a reboot to ensure windows is not holding anything, then try re-installing. Please note down every step you do if possible. Phil suggested it could be that windows is trying to allocate it to a COM port that is already in use. That would cause it to fail with Code It seems sometimes Windows gets an inconsistency in it's registration of what has already been allocated.

Note that windows marks some as in use , but don't count this as exhaustive for the same reason as this problem may exist! Try changing it to a few different unused COM ports and see if this has an impact.

If not, we'll dive deeper to see what windows is reporting. Device manager showed them both as registered to COM1. I then unpluged-replugged, and got:. It always assigned the mbed to COM I then tried to run a program that writes out to the port.

I tried my LPC mbed. It works fine. LPC works fine LPC does not. Quite curious. Next thing to try is maybe another USB port. I realize COM port number will change. I'll let you know. Sounds like the LPC on XP is still coming in on some low numbered port, and I'm worried there may be a clash still if windows is confused. COM25 or some other higher one. Then unplug-replug and check it comes in OK i. Then re start teraterm and see if you get life!

If not, this is very strange. Can you list the exact hardware, OS specs? Maybe you can find another XP machine to try just to really narrow it down to that machine? For sanity, it might also be worth ensuring the program on the mbed really is running - e. This would confirm e.

But as you have had the board working with Vista, it is unlikely to be this. And checking teraterm is restarted. Actually, I did have other code running to flash some LEDs. It would not be the first time I had the wrong compiler selected The good news is I have it working. I finally chose COM9, and it works fine now. I am not sure why. At this point, I am not sure where the problem lies, but I am suspecting it might have to do with the PC I am running on. I would not worry about it being any other issue.

Thanks to you and all who tried to help. I am really quite impressed with the quick reponses and good information here.

It may be worth seeing if you are on the newest version of Teraterm. Though these are small things we cannot avoid them. For the valid hostname and port number, you can check the Listener.

In case of Listener. And if you are using TNSnames. Now try connecting. If this solves your problem then you can avoid the next step. To check whether Listener is up and running or not, simply open up your command prompt with Administrative privileges and Write. This command will show you the status of your listener.

If the output of this command looks like the one shown in the picture below then it clearly means your listener is not running thus next what you have to do is to start the listener. Error The specified service is disabled and cannot be started. When you attempt to start the Server service from a command prompt, you may receive the following error message:.

System error has occurred. The specified service is disabled and cannot be started. When you attempt to enable the Server service for the current hardware profile, the current hardware profile may be missing from the list of profiles or the Enable button may be unavailable.

Contact Dell Computer Corp. For more information about hardware and software vendor contact information, visit the following Microsoft Web site: -. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Note that you should back up the registry before you edit it. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

This issue occurs only on computers with the integrated Yamaha Sound System installed and is known to occur with the following computers:. When you attempt to start the Server service from a command prompt, you may receive the following error message: System error has occurred.