Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Sudden problem with old batch files

Sudden problem with old batch files

Sudden problem with old batch files


I have a collection of batch files which have been proven, and all had worked until lately (I'm suspecting a windows update may be the source of my problem, but have not been able to find a solution.)

Problem: When executed a batch file will not properly execute calls/commands for the "local" directory - that is where the [Drive:][\Path\] don't exist.
eg. Del myfile.txt
Call myprog.exe

I can see that the command prompt ALWAYS defaults to C:\Windows\system32\ as of late.

If I open the command prompt directly I get a mesage indicating that "UNC paths are not supported" - and again the prompt defaults to C:\Windows\system32\

Anyone know a quick work-around?

Appreciate the help. Thanks.

RE: Sudden problem with old batch files

del .\myfile.txt
call .\myprog.exe

[ I'm working from memory; I hardly ever use DOS or Windows anymore. ]

Mike Halloran
Pembroke Pines, FL, USA

RE: Sudden problem with old batch files

IRstuff -

To some of my files - sure that would certainly fix the problem, but many of them are used in conjuction with inhouse programs and the working directory for them is not always known (for example some of these batch files can perform the same task in any directory which they reside).

These batch files had all been tested - this problem only surfaced recently. As I stated earlier, I believe a Windows update may have changed the way the CMD prompt functions.


RE: Sudden problem with old batch files

Resolved.  Thanks for any responses.

Turns out the IT department associated a new registy entry with everyones login script.  This was done to facilitate a certain software upgrade, and forced the command prompt to C:\Windows\system32 when run.  If anyone ever has the problem in the future - look for a registry entry called "AUTORUN" within the command prompt registry folder, and delete it.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members! Already a Member? Login


Design for Additive Manufacturing (DfAM)
Examine how the principles of DfAM upend many of the long-standing rules around manufacturability - allowing engineers and designers to place a part’s function at the center of their design considerations. Download Now
Taking Control of Engineering Documents
This ebook covers tips for creating and managing workflows, security best practices and protection of intellectual property, Cloud vs. on-premise software solutions, CAD file management, compliance, and more. Download Now

Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close