need help on NT 4.0 error

[visualuser]

One of our NT machines is getting a weird message when windows is booting up. I'm not sure how to fix it.

"Cannot find the file 'C:\Program' ( or one of its components). Make sue the path and filename are correct and the required libraries are available."

Can anyone shed some light on this. I'm not sure what has been uninstalled or deleted since I'm at the pc all the time.

Thanks for any suggestions.

 

[mrsnrub]

This error is usually the result of a program trying to load on startup after required files have been removed. There are two places you can look for a solution to this problem:

See if there are any refereneces under Start/Programs/Startup to programs that have been removed. If so, delete them.

Check the registry under HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Run
and see if there are any entries under here that should not be there. If so, delete them.

Hope this helps

 

[djhawthorn]

Also check

HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Run

and any of the RunOnce keys too.
MCSE NT4/W2K

 

[nhidalgo]

You can also check the "win.ini" file to see if there is a "run" statment in there pointing to an incorrect place.

Nick

 

[chrisv71]

Hi, I hate to re-introduce an old topic but I'm seeing a similar problem after our application install. I've verified that the path under:

HKEY_LOCAL_MACHINE/.../RunOnce

is valid but for some reason it generates an error on restart. The particular path points to a setup folder and uses the RESTART switch, i.e:

P:\Programming\current application\setup.exe "-RESTART"

(This is just an example and not the actual entry, the restart switch is coded correctly in the registry but the example above is for illustration purposes only and may not be exactly accurate)

When I restart and get the error message it states that the path is invalid and it shows the path to be:

P:\Programming\current

Which looks like it is parsing the entry at the first space encountered (possibly to identify the various switches??) Are there any known problems with using RunOnce and path names containing spaces? The only other thing to note is that the P:\ drive path is a public drive mapped to my machine, not a local drive. Is it possible the link to this mapped drive is not accessible at the time Windows is trying to execute this process? I'm not sure what order these steps are taken when the OS starts. Any help would be appreciated! Thanks.

Chris

 

[wolluf]

Haven't you just tried it with quotes to avoid any possible space problems. You should then find out if the drive has been mapped or not (if its mapped in a logon script I'd expect it to be present, but if its a manual persistent mapping I'm not sure).

 

[TheLad]

I am with Wolluf on this one. I have seen this many times whereby it is a lack of quotes issue. The system is basically treating the spaces in the directory path as seperates instead of one entire path.

Solutions: a) put the path in quotes, or b) put in the DOS 8.3 direcotry names. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[waba]

A computer that I am working on is creating the same error that visualuser stated at the top of this thread. I have checked the Run folder and the RunOnce folder in the registry, and I have checked the win.ini file. The error originally popped up twice. I removed an unecessary line in the win.ini file, and now the error only pops up once. Where else can I go to locate this problem? Thanks.

 

[wolluf]

Try installing

http://www.lpacomputers.telinco.co.uk/SM.zip

- then see if it has any entries which look suspicious (eg, including spaces in the path with no quotes). It picks up from all locations NT starts apps from I think

 

[TheLad]

Check your startup folders as well - both your own user and All Users ...

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------