Re: WinME startup question

Hi Clarence,

Just so I can sleep tonight can you just let me know what the current issue
is? (I wont tell anyone else, it will be our secret!)

Is the system starting and getting into windows correctly?

Is it failing to get to windows correctly?

Does it get to Windows but has an error message during part of the boot
process?

Have you checked the contents of CONFIG.SYS and AUTOEXEC.BAT?

Go on you know you want to tell someone really dont you?

What are (if any) the verbatim errors you are getting and what do they stop
you from doing?

Thanks

TT


"Clarence (Lancy) Howard" <nutz7777@xxxxxxxxxxxx> wrote in message
news:OSCVf.30479$u31.7193@xxxxxxxxxxxxxxxxxxxxxxx
Hi TT

Scandisk.ini is the file you are looking for.

So it's exactly the same as 98SE then, until after Scandisk has done it's
stuff. Scandisk only looks like a Windows program, but it's not. It's a
DOS
prog. You have answered the first two of my questions and saved me a lot
of
time.

What is your actual issue though?

Realistically, I'm trying to pretend that the sick machine is okay and
find
out where and when everything should start. There's loads of stuff that
has
been installed and uninstalled (or badly removed) from this machine. I
just
wanted to know if SYSINIT on ME was starting it's configuration prior to
the
Scandisk event. From what you've said the answer to that is no.

I don't want to be mysterious or evasive. I'm just working my way through
the startup procedure (I've very little knowledge of ME). I run 98SE on a
Compaq box that originally came with ME on board. I just find that 98SE
allows me to do what I want and it runs pretty damn quick on the Compaq
box
(there's no constant thrashing of the hard disk). I use a parallel printer
so the only extra driver I need is for my flash drive.

My suspicion is that another anti-virus program has somehow managed to
comprimise the startup process and in so doing has also also compromised
the
way in which Nportect.VxD is initiated. This then resulted in Norton not
being able to uninstall itself correctly, ie, it was not able to dismantle
the hooks it had placed in the startup process, or indeed, find and remove
it's own code.

From what I've seen and heard, both here and in WinME groups there seems
to
be an acknowledged awareness that there is a problem with Norton being run
in ME. To tell you the truth, I'm beginning to think otherwise. (I
promised
Symantec an apology if I found they were not the problem and it's
beginning
to look that way - oh dear)

Thankyou very much for your help. It is greatly appreciated.

Clarence (Lancy) Howard
nutz7777@xxxxxxxxxxxx (remove one of the 7s)






.

Quantcast