Hi..
In windows xp, after executing c++ program,Doskey is not working further.
pls give me solution for that.
Thanking u,
--Smitha

I find this to be an interesting question, since I haven't used doskey since, well, DOS3.3. I didn't even know that they kept it around. Is the doskey that you are using WINDOWS\system32\doskey.exe? You are using cmd.exe for the command window (not command.com), right?

1. What are you using doskey for?

2. What do you mean 'not working further?' Had you defined macros that got lost? Does it lose its history? What?

3. What is the nature of the C++ file? (Where did it come from? What does it do? Was it compiled with a 16-bit compiler or what?)

4. Exactly what are you doing? (Example: open WINDOWS\system32\cmd.exe window, enter "doskey..." or some such thing on the command line, invoke the C++ compiled program from the command line, then what...)

Regards,

Dave

hi,
This s/w is related to Banking. cmd.exe and doskey.exe both are located in c:\windows\system32. We r working under sub directories(i.e. c:\src\sbmod>) created through our s/w. Our source code is in sbmod. Before executing any program here, doskey works but after executing any program/part of s/w, doskey does not work. for example, if v use execution of c++ command ie make filename.exe , then dos key was not working.

Thanks.....
Smitha

I am still curious as to what you are using doskey.exe for. Macros or what?


Since I didn't know you were using make.exe, I didn't know to ask where make.exe is (and where it came from). If you are using a 16-bit make.exe (from a 16-bit compiler like turboc 3.0) then it might screw up cmd.exe to the point where the doskey stuff doesn't work. One clue would be if you were in a directory, say c:\test (and your prompt is C:\test>) and then you executed \tc3\bin\make.exe you might find that your prompt becomes C:\TEST>

If this is the case, then there is no solution other than to get a newer compiler or at least get 32-bit make.exe from who-knows-where. Other 16-bit software can also screw up cmd.exe on Windows XP (at least it does for me --- sometimes).

Regards,

Dave