MS-DOS Eiting

  • Thread starter Thread starter Arfer
  • Start date Start date
A

Arfer

I am aware that W2000 does not support full MS DOS. But is there any
way that I perform any DOS editing using Qbasic and avoid getting this
message C:\WINDOWS\SYSTEM32\AUTOEXEC.NT
The system file is not suitable for running MS-DOS and Microsoft Windows
applications.
Choose Close to terminate the program.
I have both edit.com and qbasic.exe in C:\WINDOWS\SYSTEM32
 
I have never been able to get QBasic to work successfully in Windows 2000. You can try to launch the application using the an application from Microsoft that tries to launch it in Windows 95 mode. I don't have further info on that at the moment but I can tell you I did that done that. Didn't help.

Now I did not get the error you mentioned. I could fire it up and try to run a program but I would always get an exception error. It tries to write to a memory location that is invalid.
 
Eric said:
I've read that this is sometimes caused by a virus deleting the autoexec.nt file
in %SystemRoot%\System32 folder.

Do a search for the autoexec.nt file.

You should have another copy in %SystemRoot%\Repair folder. If so, copy it to
the %SystemRoot%\System32 folder.

See this article for more info:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324767
Thank you both George and Eric.
Sure enough autoexec.nt was not present and with a quick copy I am now
very happily editing away.
Once again thanks so much and very best regards,
Arfer.
 
Many thanks to both George and Eric,
Your suggestion was a winner Eric and I am now happily editing away.
Thanks again,
Arfer
 
Eric said:
I've read that this is sometimes caused by a virus deleting the autoexec.nt file
in %SystemRoot%\System32 folder.

Do a search for the autoexec.nt file.

You should have another copy in %SystemRoot%\Repair folder. If so, copy it to
the %SystemRoot%\System32 folder.

See this article for more info:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324767
I am sorry this post to register my thanks to both George and Eric is a
little slow but I am sure you know how it is!
I would like to let you both know that MS-DOS editing is now happening
(however slowly) and the reason for the difficulty I was experiencing
was the lack of autoexec.nt in the System32 folder.
Thanks again Gentlemen,
Best Regards,
Arfer.
 
Eric McG said:
I've read that this is sometimes caused by a virus deleting the autoexec.nt file
in %SystemRoot%\System32 folder.

Do a search for the autoexec.nt file.

You should have another copy in %SystemRoot%\Repair folder. If so, copy it to
the %SystemRoot%\System32 folder.
[snip]

I had the same problem.
And I fixed that owing to your advice.

Thanks,
 
You're welcome...and thanks for the feedback!

---
Eric

Alex Vinokur said:
I've read that this is sometimes caused by a virus deleting the autoexec.nt file
in %SystemRoot%\System32 folder.

Do a search for the autoexec.nt file.

You should have another copy in %SystemRoot%\Repair folder. If so, copy it to
the %SystemRoot%\System32 folder.
[snip]

I had the same problem.
And I fixed that owing to your advice.

Thanks,

--
Alex Vinokur
email: alex DOT vinokur AT gmail DOT com
http://mathforum.org/library/view/10978.html
http://sourceforge.net/users/alexvn
 
Eric McG said:
You're welcome...and thanks for the feedback!

---
Eric

Alex Vinokur said:
I've read that this is sometimes caused by a virus deleting the autoexec.nt file
in %SystemRoot%\System32 folder.

Do a search for the autoexec.nt file.

You should have another copy in %SystemRoot%\Repair folder. If so, copy it to
the %SystemRoot%\System32 folder.
[snip]

I had the same problem.
And I fixed that owing to your advice.
[snip]

It turned out that the problem was resolved only partially.
After restart/shut down the autoexec.nt file is missing in %SystemRoot%\System32.
So, I need to copy it manually from %SystemRoot%\Repair to %SystemRoot%\System32 after each restart/shut down.

What could cause removing autoexec.nt from %SystemRoot%\System32?
 
If you have an AV app scanning your system during startup, try disabling this
feature temporarily.

If no joy, see if changing the file's attribute to read-only helps.

--
Hope this helps..Reply in newsgroup only.
Eric McGillicudy

Alex Vinokur said:
You're welcome...and thanks for the feedback!

---
Eric

Alex Vinokur said:
I've read that this is sometimes caused by a virus deleting the
autoexec.nt
file
in %SystemRoot%\System32 folder.

Do a search for the autoexec.nt file.

You should have another copy in %SystemRoot%\Repair folder. If so, copy
it
to
the %SystemRoot%\System32 folder.
[snip]

I had the same problem.
And I fixed that owing to your advice.
[snip]

It turned out that the problem was resolved only partially.
After restart/shut down the autoexec.nt file is missing in %SystemRoot%\System32.
So, I need to copy it manually from %SystemRoot%\Repair to
%SystemRoot%\System32 after each restart/shut down.
 
Eric McG said:
If you have an AV app scanning your system during startup, What AV app is?
try disabling this feature temporarily.
How to disable this feature?
Why temporarily?
If no joy, see if changing the file's attribute to read-only helps.

--
Hope this helps..Reply in newsgroup only.
Eric McGillicudy

Alex Vinokur said:
You're welcome...and thanks for the feedback!

---
Eric


I've read that this is sometimes caused by a virus deleting the autoexec.nt
file
in %SystemRoot%\System32 folder.

Do a search for the autoexec.nt file.

You should have another copy in %SystemRoot%\Repair folder. If so, copy it
to
the %SystemRoot%\System32 folder.
[snip]

I had the same problem.
And I fixed that owing to your advice.
[snip]

It turned out that the problem was resolved only partially.
After restart/shut down the autoexec.nt file is missing in %SystemRoot%\System32.
So, I need to copy it manually from %SystemRoot%\Repair to
%SystemRoot%\System32 after each restart/shut down.
What could cause removing autoexec.nt from %SystemRoot%\System32?
[snip]
 
If your AV app (Anti-Virus application) is scanning your hard drive during each
startup, it should be quite noticeable due to its inherent time delay.

Temporarily disable this feature in order to see if it's causing the problem. If
the problem goes away (the autoexec.nt file remains after startup), contact the
AV app's tech support or website FAQ for advice. If it doesn't go away, you can
then enable this feature again.

Exactly how it's disabled/enabled would depend on the features of the app you're
using. Most have options or preference settings which would allow one to
customize the app to suite one's needs.

---
Eric

Alex Vinokur said:
If you have an AV app scanning your system during startup, What AV app is?
try disabling this feature temporarily.
How to disable this feature?
Why temporarily?
If no joy, see if changing the file's attribute to read-only helps.

--
Hope this helps..Reply in newsgroup only.
Eric McGillicudy

Alex Vinokur said:
You're welcome...and thanks for the feedback!

---
Eric


I've read that this is sometimes caused by a virus deleting the autoexec.nt
file
in %SystemRoot%\System32 folder.

Do a search for the autoexec.nt file.

You should have another copy in %SystemRoot%\Repair folder. If so, c
opy
it
to
the %SystemRoot%\System32 folder.
[snip]

I had the same problem.
And I fixed that owing to your advice.
[snip]

It turned out that the problem was resolved only partially.
After restart/shut down the autoexec.nt file is missing in %SystemRoot%\System32.
So, I need to copy it manually from %SystemRoot%\Repair to
%SystemRoot%\System32 after each restart/shut down.
What could cause removing autoexec.nt from %SystemRoot%\System32?
[snip]

--
Alex Vinokur
email: alex DOT vinokur AT gmail DOT com
http://mathforum.org/library/view/10978.html
http://sourceforge.net/users/alexvn
 
Eric McG said:
If you have an AV app scanning your system during startup, try disabling this
feature temporarily.
-----------------------------------------------------------------
If no joy, see if changing the file's attribute to read-only helps.
It seems that it helped.
Thanks.
 
Back
Top