[RogueSpear]

embe, on Sep 25 2006, 07:14 AM, said:

I get error message "System not completely installed, please run setup again"

This error message is generated when you attempt to use a .NET 2.0 installer that is specifically made for svcpack after svcpack. You need to use it from within svcpack only. If you'd like a .NET 2.0 installer that will run from RunOnceEx, then you need an installer that simply makes the msiexec call and nothing else.

[mazin]

RogueSpear, on Sep 26 2006, 01:34 AM, said:

you attempt to use a .NET 2.0 installer that is specifically made for svcpack after svcpack.

First, thank you very much for your time and effort.
Your all-in-one NET package saved me alot of time.

Is your package made to work only from SVCPACK?
Can't I install it from somewhere else?

Thanks.

[RogueSpear]

Any of my installers that have .NET 2.0 in them are svcpack only. I don't believe any of the RunOnceEx installers are still lurking about.

[mazin]

Well, thanks.

But I think it can be run manually on a PC that needs it, am I correct?

[RogueSpear]

mazin, on Sep 25 2006, 09:13 PM, said:

Well, thanks.

But I think it can be run manually on a PC that needs it, am I correct?

I would try it on a VM first if I was you.. because like I said, svcpack is where it should be installed from.

RogueSpear, on Sep 25 2006, 07:34 PM, said:

embe, on Sep 25 2006, 07:14 AM, said:

I get error message "System not completely installed, please run setup again"

This error message is generated when you attempt to use a .NET 2.0 installer that is specifically made for svcpack after svcpack. You need to use it from within svcpack only. If you'd like a .NET 2.0 installer that will run from RunOnceEx, then you need an installer that simply makes the msiexec call and nothing else.

[embe]

RogueSpear, on Sep 26 2006, 02:32 AM, said:

mazin, on Sep 25 2006, 09:13 PM, said:

Well, thanks.

But I think it can be run manually on a PC that needs it, am I correct?

I would try it on a VM first if I was you.. because like I said, svcpack is where it should be installed from.

RogueSpear, on Sep 25 2006, 07:34 PM, said:

embe, on Sep 25 2006, 07:14 AM, said:

I get error message "System not completely installed, please run setup again"

This error message is generated when you attempt to use a .NET 2.0 installer that is specifically made for svcpack after svcpack. You need to use it from within svcpack only. If you'd like a .NET 2.0 installer that will run from RunOnceEx, then you need an installer that simply makes the msiexec call and nothing else.

I did it on real PC and the same error occured - "System not completely installed, please run setup again"

RogueSpear, on Sep 26 2006, 12:34 AM, said:

embe, on Sep 25 2006, 07:14 AM, said:

I get error message "System not completely installed, please run setup again"

This error message is generated when you attempt to use a .NET 2.0 installer that is specifically made for svcpack after svcpack. You need to use it from within svcpack only. If you'd like a .NET 2.0 installer that will run from RunOnceEx, then you need an installer that simply makes the msiexec call and nothing else.

Now i see and understand. Means this if I download .NET 2.0 from M$ site it will work? Coz I downloaded it from your page I think (but I`m not 100% sure)
The problem is if I modify svcpack now, after I added several hotfixes before, it looks like it removes some of them, for example i remember Windows update software...

This post has been edited by embe: 26 September 2006 - 05:46 AM

[ccc]

I like to do regular backups and so like to keep install size to a minimum.
Tried .NET Framework 2.0 and ended up with 163 MB more data on that drive.
Anyone else notice that much bloat?
Anyone else notice the huge increase in install time?
Not to mention the registry.
Tried to uninstall and about 100 MB were left behind.
After manual cleanup, had to reboot twice to get into normal mode.

Just some WARNING -- HAVE FUN!!

[RogueSpear]

Yes .NET 2.0 is rather large for a "runtime" and it does take a considerable amount of time to install, but the whole idea here is to have an "unattended" install isn't it? Anyway if you think 2.0 is bad, just wait for .NET 3.0.