trouble installing NIS2004

I have purchased and downloaded NIS 2004 but I cannot
install it. I get the Error message "Set up has detected a
previous install or Uninstall has been completed but
requires a restart." I have tried to clean boot it in to
no avail. Then I tried to install the Microsoft Windows
Installer and THAT stops me with an "Invalid directory"
after I type in just the first command.

Can you help?

Norton 2004 does NOT work on WinME and Norton should acknowledge that on
their website......sigh.

Maybe one of the gurus can help you out, but yours is a common problem.

Heather

"Jane" wrote in message
...
I have purchased and downloaded NIS 2004 but I cannot
install it. I get the Error message "Set up has detected a
previous install or Uninstall has been completed but
requires a restart." I have tried to clean boot it in to
no avail. Then I tried to install the Microsoft Windows
Installer and THAT stops me with an "Invalid directory"
after I type in just the first command.

Can you help?

I heartily concur with Heather's comment . Consult Symantec's
website for further info since it's NOT an MS issue.
Windows Millennium is NOT compatible with NIS2004 ... nor is
Windows XP. NIS2004 is horrible !

MowGreen [MVP}
===============
*-343-* FDNY
Never Forgotten
===============

Heather wrote:

Norton 2004 does NOT work on WinME and Norton should acknowledge that on
their website......sigh.

Maybe one of the gurus can help you out, but yours is a common problem.

Heather

"Jane" wrote in message
...

I have purchased and downloaded NIS 2004 but I cannot
install it. I get the Error message "Set up has detected a
previous install or Uninstall has been completed but
requires a restart." I have tried to clean boot it in to
no avail. Then I tried to install the Microsoft Windows
Installer and THAT stops me with an "Invalid directory"
after I type in just the first command.

Can you help?

nitpick mode
It's NIS - or for that matter ANY Norton 2004 program - that is not
compatible with ME or any other OS (at least as far as I can see - and
hear).
It's a Symantec problem, rather than a Windows problem. - they have still
not learnt how to deal with real-life systems, rather than AV-lab systems!!!
/nitpick mode
other than that, I agree whole-heartedly!!


--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"MowGreen [MVP]" wrote in message
...
I heartily concur with Heather's comment . Consult Symantec's website for
further info since it's NOT an MS issue.
Windows Millennium is NOT compatible with NIS2004 ... nor is
Windows XP. NIS2004 is horrible !

MowGreen [MVP}
===============
*-343-* FDNY
Never Forgotten
===============

Heather wrote:

Norton 2004 does NOT work on WinME and Norton should acknowledge that on
their website......sigh.

Maybe one of the gurus can help you out, but yours is a common problem.

Heather

"Jane" wrote in message
...

I have purchased and downloaded NIS 2004 but I cannot
install it. I get the Error message "Set up has detected a
previous install or Uninstall has been completed but
requires a restart." I have tried to clean boot it in to
no avail. Then I tried to install the Microsoft Windows
Installer and THAT stops me with an "Invalid directory"
after I type in just the first command.

Can you help?

NIS2004 is NOT compatible with Win ME and Win XP ...
NISany version is a waste of
$$$$$$$$ or ££££££££££
????????? or €€€€€€€€€
????????? or ¥¥¥¥¥¥¥¥¥
( don't have a deutschmark sign

better ?

MG

Noel Paton wrote:

nitpick mode
It's NIS - or for that matter ANY Norton 2004 program - that is not
compatible with ME or any other OS (at least as far as I can see - and
hear).
It's a Symantec problem, rather than a Windows problem. - they have still
not learnt how to deal with real-life systems, rather than AV-lab systems!!!
/nitpick mode
other than that, I agree whole-heartedly!!

???.......will that do? It is the Euro one......don't believe there are any
deutschmarks left.......or francs.......or pesetas......(G)

Heather
"MowGreen [MVP]" wrote in message
...
NIS2004 is NOT compatible with Win ME and Win XP ...
NISany version is a waste of
$$$$$$$$ or ££££££££££
????????? or ?????????
????????? or ¥¥¥¥¥¥¥¥¥
( don't have a deutschmark sign

better ?

MG

Noel Paton wrote:

nitpick mode
It's NIS - or for that matter ANY Norton 2004 program - that is not
compatible with ME or any other OS (at least as far as I can see - and
hear).
It's a Symantec problem, rather than a Windows problem. - they have
still
not learnt how to deal with real-life systems, rather than AV-lab
systems!!!
/nitpick mode
other than that, I agree whole-heartedly!!

Well, those 3 question marks WERE Euro designations......guess MS doesn't
know them, grin.

Heather

"Heather" wrote in message
...
???.......will that do? It is the Euro one......don't believe there are
any
deutschmarks left.......or francs.......or pesetas......(G)

Heather
"MowGreen [MVP]" wrote in message
...
NIS2004 is NOT compatible with Win ME and Win XP ...
NISany version is a waste of
$$$$$$$$ or ££££££££££
????????? or ?????????
????????? or ¥¥¥¥¥¥¥¥¥
( don't have a deutschmark sign

better ?

MG

Noel Paton wrote:

nitpick mode
It's NIS - or for that matter ANY Norton 2004 program - that is not
compatible with ME or any other OS (at least as far as I can see - and
hear).
It's a Symantec problem, rather than a Windows problem. - they have
still
not learnt how to deal with real-life systems, rather than AV-lab
systems!!!
/nitpick mode
other than that, I agree whole-heartedly!!

I ran across a lot of these posts that say that NIS or any Norton
product doesn't work with ME. This is not true, I've been working
phone support at a computer company for about three years now and I've
FORCED almost all Norton programs to work with WinME systems.

The first thing you've got to understand is how the protected file
system works... I'm not about to go into that here, I don't have the
time and I'm not getting paid. Once I began to understand the system I
only had trouble with one or two computers. The main cause is
wininit.exe and MS doesn't have anything about how that works in the
KB so here goes:

When a program installation needs to alter the files in the windows
protected file system it has to do so outside of DOS. The program
being installed adds the files it needs to alter into the wininit.ini
file so that the wininit.exe file can alter them before loading
windows. A problem with wininit is usually indicated by WinME locking
up at the Windows loading screen. If you hit ESC before it locks up
you are greeted by "Could not upgrade the file %1 to %2. You have to
start from a boot disk and go to DOS (thank MS for the lack of that
option on the advanced startup menu)then make your way to C:\windows
and run wininit.exe. Running this file will process the changes
needed, but I hear you saying, "What if it locks up?" Easy answer,
delete the file change list. The file is named wininit.ini(and yep,
it's in C:\windows). NOTE, however, that if you do this, any program
you were trying to install may not work b/c windows will not put the
files into the program directory. It also doesn't hurt to run MSConfig
and uncheck "load startup group items", clean out your browser cache,
and maybe even empty the BHO's out of C:\windows\downloaded program
files. This helps if there's an ActiveX object running in install when
explorer starts.

If that doesn't work... I usually give up at that point and reload b/c
I don't feel like walking a customer through looking for the session
manager keys in the registry or editing winstart.bat or the
system.ini... you get the idea.

I hope all this helps someone. Oh, and they're right Norton is useless
but do you really want grandma to setup and configure everything on
her own?

Ryan Rester

Ryan
What you're saying is mostly utter rubbish - The problem of %1%2 is
frequently encountered in these newsgroups - and the cause is almost always
the use of Norton LiveUpdate - which corrupts the control files in System
Restore, and creates an effectively infinite number of files within the
Restore archive - running wininit.exe can't work properly, because it
attempts to put more files into the Restore folder - and if it fails, then
it will break System Restore (which, OK, is already broken)
The cure is to clear the System Restore control and archive files -
(C:\_Restore) - not to attempt to force the completion of a faulty
wininit.ini.

Reloading the OS is quite possibly not going to fix this - although it may
do so simply because the archive is removed and rebuilt early in the
process. Certainly reinstalling while any trace of Norton is running is
going to break the system horribly.



--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Ryan Rester" wrote in message
om...
I ran across a lot of these posts that say that NIS or any Norton
product doesn't work with ME. This is not true, I've been working
phone support at a computer company for about three years now and I've
FORCED almost all Norton programs to work with WinME systems.

The first thing you've got to understand is how the protected file
system works... I'm not about to go into that here, I don't have the
time and I'm not getting paid. Once I began to understand the system I
only had trouble with one or two computers. The main cause is
wininit.exe and MS doesn't have anything about how that works in the
KB so here goes:

When a program installation needs to alter the files in the windows
protected file system it has to do so outside of DOS. The program
being installed adds the files it needs to alter into the wininit.ini
file so that the wininit.exe file can alter them before loading
windows. A problem with wininit is usually indicated by WinME locking
up at the Windows loading screen. If you hit ESC before it locks up
you are greeted by "Could not upgrade the file %1 to %2. You have to
start from a boot disk and go to DOS (thank MS for the lack of that
option on the advanced startup menu)then make your way to C:\windows
and run wininit.exe. Running this file will process the changes
needed, but I hear you saying, "What if it locks up?" Easy answer,
delete the file change list. The file is named wininit.ini(and yep,
it's in C:\windows). NOTE, however, that if you do this, any program
you were trying to install may not work b/c windows will not put the
files into the program directory. It also doesn't hurt to run MSConfig
and uncheck "load startup group items", clean out your browser cache,
and maybe even empty the BHO's out of C:\windows\downloaded program
files. This helps if there's an ActiveX object running in install when
explorer starts.

If that doesn't work... I usually give up at that point and reload b/c
I don't feel like walking a customer through looking for the session
manager keys in the registry or editing winstart.bat or the
system.ini... you get the idea.

I hope all this helps someone. Oh, and they're right Norton is useless
but do you really want grandma to setup and configure everything on
her own?

Ryan Rester

Why on earth should a user want to FORCE Norton on to their system when it
then causes so many problems? Whilst you clearly seem to like Norton you
are clearly ignorant of the many ill effects of installing this faulty
software on Win Me. You say you work for a computer company but clearly
have not the slightest clue as to the cause of the %1 %2 error which in
99+% of cases has nothing whatsoever to do with the presence of a
wininit.ini file. I can only assume that whilst working at a computer
company it involves no hands on use or expertise in using computers.
--
Mike Maltby MS-MVP [2001-2004]



Ryan Rester wrote:

I ran across a lot of these posts that say that NIS or any Norton
product doesn't work with ME. This is not true, I've been working
phone support at a computer company for about three years now and I've
FORCED almost all Norton programs to work with WinME systems.

The first thing you've got to understand is how the protected file
system works... I'm not about to go into that here, I don't have the
time and I'm not getting paid. Once I began to understand the system I
only had trouble with one or two computers. The main cause is
wininit.exe and MS doesn't have anything about how that works in the
KB so here goes:

When a program installation needs to alter the files in the windows
protected file system it has to do so outside of DOS. The program
being installed adds the files it needs to alter into the wininit.ini
file so that the wininit.exe file can alter them before loading
windows. A problem with wininit is usually indicated by WinME locking
up at the Windows loading screen. If you hit ESC before it locks up
you are greeted by "Could not upgrade the file %1 to %2. You have to
start from a boot disk and go to DOS (thank MS for the lack of that
option on the advanced startup menu)then make your way to C:\windows
and run wininit.exe. Running this file will process the changes
needed, but I hear you saying, "What if it locks up?" Easy answer,
delete the file change list. The file is named wininit.ini(and yep,
it's in C:\windows). NOTE, however, that if you do this, any program
you were trying to install may not work b/c windows will not put the
files into the program directory. It also doesn't hurt to run MSConfig
and uncheck "load startup group items", clean out your browser cache,
and maybe even empty the BHO's out of C:\windows\downloaded program
files. This helps if there's an ActiveX object running in install when
explorer starts.

If that doesn't work... I usually give up at that point and reload b/c
I don't feel like walking a customer through looking for the session
manager keys in the registry or editing winstart.bat or the
system.ini... you get the idea.

I hope all this helps someone. Oh, and they're right Norton is useless
but do you really want grandma to setup and configure everything on
her own?

Ryan Rester