Member Avatar for buddyb

I'm actually fine in the auto IP dept, but I wanted to look and see the set-up. When I tried to execute cmd from Run, but no deal. I got the requester that states this app is not suitable for DOS applications. I know that you can do this from some XP machines. Does this mean that maybe you can do this from XP Home and not XP Pro? I believe there's a release/renew command from Windows, but haven't located it yet. Any input appreciated.
Thanks, BuddyB

  • 4 Contributors
  • 12 Replies
  • 288 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by gemini4

Dani AI

Generated

Short practical summary and where this thread left off: was correct that the usual way to do a DHCP release/renew is from a command prompt, but the error reported by (the AUTOEXEC.NT message) prevents opening the DOS/16‑bit subsystem so cmd will not stay open. ’s GUI “Repair” route is the quickest workaround when a prompt is unavailable; was also right to call out a damaged/missing MSDOS‑subsystem file as the likely root cause.

Why the AUTOEXEC.NT message appears and a safe fix: Windows shows that message when one or more of the 16‑bit subsystem files (Autoexec.nt, Config.nt, Command.com) are missing or damaged. The simplest, non‑command‑line repair is to use Explorer: open C:\Windows\Repair, copy Autoexec.nt and Config.nt into C:\Windows\System32, set their Properties to Read‑only, and reboot. If the Repair folder doesn’t contain them, extract the originals from the XP install media or use the recovery/repair options on the CD. This is the procedure documented by Microsoft and documented in community references.
. (users.cs.jmu.edu)

Immediate networking workaround and checks: if a prompt cannot be used right now, use Network Connections → right‑click the adapter → Status → Support → Repair; that automated Repair performs the same release/renew and related steps the command line would run. Also confirm the OS bitness: 64‑bit Windows does not include the NTVDM 16‑bit subsystem, so restoring AUTOEXEC.NT won’t help on x64 systems. (answers.microsoft.com)

Cautions and next steps: avoid permanent DEP changes as a general cure — that’s rarely needed and can cause other problems. If the Repair‑folder copy is unsuccessful or files reappear missing, treat the system as possibly compromised (run an updated antivirus/antimalware scan) and follow ’s suggestion about collecting a HijackThis/diagnostic log before doing an in‑place repair of XP. Once the subsystem files are restored, the command prompt should remain open and the normal IP troubleshooting commands will work again. (users.cs.jmu.edu)

Recommended Answers

All 12 Replies

Member Avatar for BinaryMayhem

yea, its called ipconfig

start > run > cmd
type in ipconfig /all

that will list all the IP info
ipconfig /release -> will let the IP lease expire
ipconfig /renew -> will try to grab a new one from the dhcp server

Member Avatar for buddyb

Windows on my machine will not run the DOS box; says the op system is not suitable for running DOS; ideas?
Thanks, BuddyB

Member Avatar for rasputinj

try from the run line "cmd /k ipconfig/release" "cmd /k ipconfig/renew" , now to do it from a giu, go to control panel, then go to networking, double click on the Lan connection to to support then details you can click repair which should do the release and renew.

Member Avatar for buddyb

I've tried all those commands and my system will not allow the DOS box; keep getting the error message, "System not compatible with DOS".
BuddyB

Member Avatar for rasputinj

to get to a cmd prompt are you going to run then enter cmd, then enter the command. I can nor remember a XP machine where I could not do that.

Member Avatar for buddyb

When I go to run and type in "cmd" this is what the computer returns:
"C:\windows\system32\autoexec.nt. The system file is not suitable for running MSDOS & Microsoft Windows applications. Choose 'Close' to terminate the application." Then I have the choice of 'Close' or 'Ignore'. Whichever I choose it closes the box.
Thanks, BuddyB

Member Avatar for gemini4

Your file got corrupt. No worries follow this article:

Member Avatar for rasputinj

Your file got corrupt. No worries follow this article:

Good info to know thanks.

commented: A most helpful person +3
Member Avatar for buddyb

I can see where this would be good to utilize. I did no.1 and could find no system32. I downloaded xp_fix.exe and that didn't work. It didn't give me the return error, but the DOS box came up empty and then went away. On the Data Execution Prevention Error I went to AlwaysOff. The only change there is that now I come up with the DOS boot screen that gives you options if you're running multiple op systems.
BuddyB

Member Avatar for gemini4

I can see where this would be good to utilize. I did no.1 and could find no system32. I downloaded xp_fix.exe and that didn't work. It didn't give me the return error, but the DOS box came up empty and then went away

That is perfectly normal. What you have to do now is click start run cmd. Then type ipconfig and it will stay

. On the Data Execution Prevention Error I went to AlwaysOff. The only change there is that now I come up with the DOS boot screen that gives you options if you're running multiple op systems.
BuddyB

There was not need for the data execution prevention fix. That was for a different problem. For the DOS Boot screen that you now have click start choose run type in there msconfig and click Boot.Ini on the top. Then click Check all boot paths and click Y Yes then Ok and then Restart.

So now that you don't get the error message anymore your problem should be solved. The window will not stay because ipconfig executes and terminates. You have to run it from inside cmd.

Member Avatar for buddyb

I know you're correct about this. However, I go to run, type in cmd, the DOS box comes up, but terminates before I can do anything. It also doesn't have any info in the box anywhere, and no blinking cursor to input from.
BuddyB

Member Avatar for gemini4

How about if you try command instead of cmd?

I have to say even if command works I think cmd was replaced by something else on your system. I would advise you to post a Hijackthis log in the Spyware and Virus Section

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.