problem with memtest86

[Paul Heslop]

I tried running this prog some time ago but after one use found it
wouldn't work. I used a windows memory tester instead but I was
curious and tried again to run memtest, this time from a new download,
only when i try to install to floppy I get this popup
#
16 bit MS-DOS susbsystem

C:\windows\system32\cmd
C:\windows\system32\autoexec.nt. the system file is not suitable for
running ms-dos and microsoft windows applications. choose 'close' to
terminate the appication

anyone any ideas? This didn't happen before and I don;t understand why
it's happening now

 

[Paul Heslop]

I tried running this prog some time ago but after one use found it
wouldn't work. I used a windows memory tester instead but I was
curious and tried again to run memtest, this time from a new download,
only when i try to install to floppy I get this popup
#
16 bit MS-DOS susbsystem

C:\windows\system32\cmd
C:\windows\system32\autoexec.nt. the system file is not suitable for
running ms-dos and microsoft windows applications. choose 'close' to
terminate the appication

problem solved, though I don't know why it happened. apparently it's
quite common for the file autoexec.nt to just be missing or corrupt,
in my case missing. I downloaded it to the system32 folder and viola!
it works.

 

[Malke]

problem solved, though I don't know why it happened. apparently it's
quite common for the file autoexec.nt to just be missing or corrupt,
in my case missing. I downloaded it to the system32 folder and viola!
it works.

Are you sure? Memtest86 is meant to be used outside of the operating
system. It is Linux-based. You are supposed to make either a bootable
floppy with the precompiled Windows binary or download the .iso and
burn it (you'll need third-party burning software for that) to make a
bootable cd. Then you boot with the media you chose and Memtest86 will
run immediately. Allow it to run for an extended period of time unless
you see errors immediately.

Malke

 

[Alexander Grigoriev]

Autoexec.nt is usually screwed up by some malware. Check your system.

 

[Paul Heslop]

Are you sure? Memtest86 is meant to be used outside of the operating
system. It is Linux-based. You are supposed to make either a bootable
floppy with the precompiled Windows binary or download the .iso and
burn it (you'll need third-party burning software for that) to make a
bootable cd. Then you boot with the media you chose and Memtest86 will
run immediately. Allow it to run for an extended period of time unless
you see errors immediately.

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

Sorry Malke, I meant when I tried to install it to the floppy was when
I got the problem

 

[Paul Heslop]

Autoexec.nt is usually screwed up by some malware. Check your system.

Thanks Alexander. I know I've had some attacks as I stupidly visited a
couple of lyrics sites recently and ended up with over 100 instances
of dialers/redirecters/trojans etc. I could almost see it happening,
and I wouldn't like to guess how bad it would have got if I hadn't
realised it was going on. I ended up having to run spybot AND adaware
from safe mode to clear them, so it's probable the damage was done
then

 

[Malke]

Thanks Alexander. I know I've had some attacks as I stupidly visited a
couple of lyrics sites recently and ended up with over 100 instances
of dialers/redirecters/trojans etc. I could almost see it happening,
and I wouldn't like to guess how bad it would have got if I hadn't
realised it was going on. I ended up having to run spybot AND adaware
from safe mode to clear them, so it's probable the damage was done
then

Ah. So once you get the malware completely cleaned up - and that means
also scanning with a current version (not earlier than 2003) antivirus
using updated definitions in Safe Mode - here is more information about
the 16-bit issue:

Error message when you install or start an MS-DOS or 16-bit
Windows-based program:

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767&Product=winxp

This can also be caused by malware.

Also, AVAST (antivirus software) can be the cause if you have WinXP SP2
installed:

http://groups.google.com/[email protected]

You can put back the standard version of autoexec.nt/config.nt by
copying a backup copy held in %windir%\repair\ to %windir%\system32\
(%windir% is typically C:\Windows) instead of using the procedure in
the KB article above.

Malke

 

[Alex Nichol]

I tried running this prog some time ago but after one use found it
wouldn't work. I used a windows memory tester instead but I was
curious and tried again to run memtest, this time from a new download,
only when i try to install to floppy I get this popup
#
16 bit MS-DOS susbsystem

C:\windows\system32\cmd
C:\windows\system32\autoexec.nt. the system file is not suitable for
running ms-dos and microsoft windows applications. choose 'close' to
terminate the appication

anyone any ideas? This didn't happen before and I don;t understand why
it's happening now

This sounds like a trojan has damaged that autoexec.nt file - there
seems to be an epidemic of this. So run a good AV and AntiSpyware
check, then make a copy of the reserve file windows\repair\autoexec.nt
into windows\system32

 

[Paul Heslop]

Ah. So once you get the malware completely cleaned up - and that means
also scanning with a current version (not earlier than 2003) antivirus
using updated definitions in Safe Mode - here is more information about
the 16-bit issue:

Error message when you install or start an MS-DOS or 16-bit
Windows-based program:

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767&Product=winxp

This can also be caused by malware.

Also, AVAST (antivirus software) can be the cause if you have WinXP SP2
installed:

http://groups.google.com/[email protected]

You can put back the standard version of autoexec.nt/config.nt by
copying a backup copy held in %windir%\repair\ to %windir%\system32\
(%windir% is typically C:\Windows) instead of using the procedure in
the KB article above.

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

thanks for all the info. I should be getting better at this :O)

 

[Paul Heslop]

This sounds like a trojan has damaged that autoexec.nt file - there
seems to be an epidemic of this. So run a good AV and AntiSpyware
check, then make a copy of the reserve file windows\repair\autoexec.nt
into windows\system32

cheers Alex. I'm always scanning for nasties so i catch them pretty
quick and as I don't have a proper windows disc, just a rollback
thing, I've downloaded the relevant file too