unusual error message installing memtest86

  • Thread starter Thread starter news.microsoft.com
  • Start date Start date
N

news.microsoft.com

I am getting an unusual error message Installing memtest86: It starts
writing the A drive and then tells me c:\windows\system32\cmd.exe (which is
obviously running) followed by c:\progra~1\symantec\s32evnt1.dll. An
installable virtual device driver failed dll initialisation and asks me if I
want to choose close to terminate the application (or ignore).

As I haven't got any Symantec programs loaded or running, I am wondering
what error there is in my registry making it think that I have and/or how I
can get rid of this or is something running in SERVICES which I should get
rid of?

(Obviously I am pressing IGNORE and memtest then runs for three or four
seconds.)
 
news.microsoft.com said:
I am getting an unusual error message Installing memtest86: It starts
writing the A drive and then tells me c:\windows\system32\cmd.exe
(which is
obviously running) followed by c:\progra~1\symantec\s32evnt1.dll. An
installable virtual device driver failed dll initialisation and asks
me if I want to choose close to terminate the application (or ignore).

As I haven't got any Symantec programs loaded or running, I am
wondering what error there is in my registry making it think that I
have and/or how I can get rid of this or is something running in
SERVICES which I should get rid of?

(Obviously I am pressing IGNORE and memtest then runs for three or
four seconds.)
Click to expand...

You don't install Memtest86+. You download either the precompiled binary
for Windows and use it to create a floppy boot disk OR the .iso to
create a bootable cd (with third-party burning software) from
www.memtest.org. Then you boot with the media you created and
Memtest86+ will automatically run. You can remove the bootable media at
that point.

Malke
 
You don't install Memtest86+. You download either the precompiled binary
for Windows and use it to create a floppy boot disk
Click to expand...

Yes, that is what I am doing when I get the symantec error message

OR the .iso to
 
news.microsoft.com said:
Yes, that is what I am doing when I get the symantec error message
Click to expand...

I have no idea what's wrong. In all the many years that I've been using
Memtest86 and Memtest86+, creating both floppies and bootable cd's,
I've never seen that. Of course, I don't have any Symantec products
either. Either download the bootable .iso for the cd or make a bootable
floppy on another machine.

Malke
 
It made the floppy from that process as I mentioned: I was wondering what
caused the error message and how I could get rid of it
 
news.microsoft.com said:
It made the floppy from that process as I mentioned: I was wondering
what caused the error message and how I could get rid of it
Click to expand...

Sorry, but I don't know. I suppose you could ask Symantec but if it
doesn't happen when you run cmd normally, I wouldn't worry about it.

Sorry that I couldn't help you.

Malke
 
Did you ever have a Symantec product installed on this PC, like Norton
Anti-Virus or Internet Security? If yes, then the uninstall process is
usually "flawed" and leaves "left-overs" on your PC. Look on Symantec's web
site for the enhance Symantec removal instructions / tool.
 
Yves Leclerc said:
Did you ever have a Symantec product installed on this PC, like Norton
Anti-Virus or Internet Security?
Click to expand...
Actually no, but I did have it on some earlier computer and used PC
Relocator: It is a great program for relocating your system from one
computer to another; but it does some pretty weird things when relocating
whatever it relocates. (I had run the removal tools on that computer before
relocation!)

It does relocate some things which don't really need relocating, such as the
old computer name and processes like this sym event one!

If yes, then the uninstall process is
usually "flawed" and leaves "left-overs" on your PC. Look on Symantec's
web
site for the enhance Symantec removal instructions / tool.
Click to expand...
Yes, I kinda knew that and have in the past had to run them but they don't
really work either: THey now give the error message "you are running the
removal tool for the wrong product" if you have run the removal tool once
before and there is a catch-all removal product which also doesnt work. I
dont really mind all of this as Malke says, but there is some nagging doubt
that some symantec process (or as they seem to call it, event) IS still
running which leads to the worry with Symantec and McAfee, how much in the
way of resources is it using? A sort of 'how much better would my computer
run if it wasnt event-ing?'
 
Back
Top