O.T. Can't logon to the Internet:

  • Thread starter Thread starter magineer02
  • Start date Start date
I tried running update again with no luck. Also, the 8200
has a yellow triangle with a question mark on the bottom
right hand side of the screen from time to time. I tried holding
the mouse over it and clicking it to see what it was but neither
worked.

I checked device manager and it was all good.

I searched again for ngen.exe, this is what I have:

C:\WINDOWS\ Prefetch executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\ngen.exe executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems

I open up the command prompt and did the first one:

It came back with this:

Display the ngen state
ngen executeQueuedItems [1:2:3]
Executes queued complilation jobs.
If priority is not specified all queued compilation jobs are done.
If priority is specified all queued compilation jobs with greater or equal
prority than the specified are done. <short form: eqi>
negen queue [pause: continue: status]
Allows the user to pause and continue the NGen Service, and to
query its status.

Scenarios:
/Debug - Generate images that can be that can be used under a debugger
/Profile - Generate images that can be that can be used under a profiler
- Generate the minimal number of native images
required by this scenario


Config:
/ExConFig:<path to exe> - Use the configuration of the specified

/AppBase:<path to appbase directory> - Use the specified directory as
the appbase


Thoughts/Suggestions
Robert
Click to expand...

Your first result, suggests the first item on the command
line was ignored, and the Command Prompt window tried to execute
"executequeueditems" instead.

There should be only one space character in the command line. It's
not like the path has a space in it.

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems

It the path had a space character, you could try
surrounding the command portion in double quotes, like this.

"C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe" executequeueditems

Some of the program shortcuts are done that way.

There are no spaces at the beginning of the command at all.
The C: portion, you enter that right next to the command prompt.

I don't thing the parameter "executequeueditems" has any
forward or backward slash in front of it, nor any hyphen
character. It should just be the word itself.

Paul
 
I agree, there is only one space (between exe and execute,.....) However,
just to play it safe I tried it again with quotes. This is what I typed:

C:\>"WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe" executequeueditems

It came back with this:

Microsoft <R> CLR Native Image Generator - Version 4.0.30319.1
Copyright <c> Microsoft Corporation. All rights reserved.
All compilation targets are up to date.

Robert
 
I agree, there is only one space (between exe and execute,.....) However,
just to play it safe I tried it again with quotes. This is what I typed:

C:\>"WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe" executequeueditems

It came back with this:

Microsoft <R> CLR Native Image Generator - Version 4.0.30319.1
Copyright <c> Microsoft Corporation. All rights reserved.
All compilation targets are up to date.

Robert
Click to expand...

OK, now there should be no delay for the networking to
start on your PC, just after WinXP finishes booting.

The "All compilation targets are up to date" means
that all .NET code assemblies detected on the computer,
have been pre-compiled for faster loading. They're stored
in a cache folder somewhere, all to shave one second off
some program's start time. A lot of drama, for nothing.

Paul
 
Still doesn't update.

I checked all the egen.exe on the command
prompt and it came back command not recognized.

I'll try again tomorrow.

Robert
 
Here's what I did:
I went back and opened the command prompt and did each of my ngen.exe files:


C:\WINDOWS\ Prefetch executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\ngen.exe executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems


it came back with the following:

Prefetch executequeueditems - I ran this twice and the first time
it gave me:

The system cannot find the path specified

The second time it gave me:

'C:\WINDOWS\Microsoft.NET\Framewok\Prefetch' is not recognized
as an internal or external command, operable program or batch file.

4322 - The system cannot find the file specified
50727 - All compilation targets are up to date
30319 - All compilation targets are up to date

I checked the device manager and everything was ok

I then tried running update and it ran for 30 minutes when the yellow
triangle with an exclamation mark appeared again and this time it said
updates were ready to install. So I clicked it and the updates (8) started to
install!
After installation, I restarted the computer and checked the device manager
and it all looked good. The screen came up faster than before and the
computer 'seems' much more responsive. I then checked for updates to see
if the problem had cleared; and yes, it cleared the problem and have installed
(7) more updates including Skype. It all seems working normally now.

My last question, (hopefully) will I have to continue to look for egen.exe files or
anything else? I appreciate all your help and guidance and sticking with me
through all of this and walking me through it.

Again, many thanks,

Robert
 
Here's what I did:
I went back and opened the command prompt and did each of my ngen.exe files:


C:\WINDOWS\ Prefetch executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\ngen.exe executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe executequeueditems

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems


it came back with the following:

Prefetch executequeueditems - I ran this twice and the first time
it gave me:

The system cannot find the path specified

The second time it gave me:

'C:\WINDOWS\Microsoft.NET\Framewok\Prefetch' is not recognized
as an internal or external command, operable program or batch file.

4322 - The system cannot find the file specified
50727 - All compilation targets are up to date
30319 - All compilation targets are up to date

I checked the device manager and everything was ok

I then tried running update and it ran for 30 minutes when the yellow
triangle with an exclamation mark appeared again and this time it said
updates were ready to install. So I clicked it and the updates (8) started to
install!
After installation, I restarted the computer and checked the device manager
and it all looked good. The screen came up faster than before and the
computer 'seems' much more responsive. I then checked for updates to see
if the problem had cleared; and yes, it cleared the problem and have installed
(7) more updates including Skype. It all seems working normally now.

My last question, (hopefully) will I have to continue to look for egen.exe files or
anything else? I appreciate all your help and guidance and sticking with me
through all of this and walking me through it.

Again, many thanks,

Robert
Click to expand...

You use NGEN to correct a specific set of symptoms.

1) You start your day, running Windows Update.
2) In the list of updates, is an update to .NET.
You install the .NET security update.
3) Later, after a reboot, you notice that the network icon on
your computer, isn't normal, and networking does not function
on the computer, until a couple minutes have passed.

If those are the symptoms and results, then you can try to
repair the problem with

ngen.exe executequeueditems

You don't need to do that command otherwise.

If on your system, it needs " " around the command portion,
then use that in the future too.

"C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ngen.exe" executequeueditems

If you don't notice "funny problems with networking, after
a reboot", then your .NET assemblies are up to date.

HTH,
Paul
 
Back
Top