TIP: When you install a service pack, the installation can sometimes
fail to properly update all the necessary files. The most common mismatch of new
and old files involves ntoskrnl.exe and exhibits the following error:
System Process--Driver Entry Point Not Found
The \systemroot\system32\drivers\srv. sys device driver could not locate
the entry point rtllsnamelegaldos8dot3 in driver ntoskrnl.exe?
The following system events appear in the Event Viewer:
Event ID: 2508
Source: Server
Type: Error
Description: The server service was unable to load the server driver.
Event ID: 7023
Source: Service Control Manager
Type: Error
Description: The Server service terminated with the following error:
The system cannot find the file specified.
In such a case, the system did not upgrade properly and is trying to run
srv.sys and the Windows NT 3.51 (Build 1057) ntoskrnl.exe. This attempt does not
work. Copy the ntoskrnl.exe file from the NT 3.51 service pack to the
%systemroot%\system32 directory.
If the system is multiprocessor system (MPS)-compliant, copy and rename the
ntkrnlmp.exe (multiprocessor kernel) file from the NT 3.51 service pack to the
%systemroot%\system32 directory to overwrite the ntoskrnl.exe.
Q: I have a bet with a friend. He tells everyone that you don't need
boot.ini to boot to NT. I say no. This bet sounds like easy money to me, but
knowing Microsoft, anything is possible.
Don't bet a lot: Your friend is correct. However, the circumstances in
which such a boot is possible don't occur often.
If ntldr can't find boot.ini, the system defaults to booting from the
%systemroot%\winnt directory (the default NT install directory). However, if you
don't install NT to this default directory, the system won't find the files it
needs for booting.
Q: I'm having trouble getting the Schedule service to work across my
network. I've tried everything, including the suggestions you published in March
and July, with no luck. Any other ideas?
Because the Schedule service doesn't run as a network user, a security
violation can occur. You can fix this problem by creating a batch file that
reads
net use k: \\server\share /user:domain\account password
ntbackup...(usualparameter list)
net use k: /delete
This solution presupposes that drive K is available.
Running the Schedule service across an entire network is dangerous. Network
administrators need to be aware that this solution involves the open posting of
a password in the batch file.
Q: I'm having problems with certain Explorer icons hanging. Does NT 4.0
cache icons? How can you tell?
Problems with icons hanging are related to icon caching. You can use
Explorer to delete the cached file in question, or you can clear the cache
error. After you use NT Explorer/View/Options to enable Show all files,
find the hidden ShellIconCache file in your %systemroot%\winnt directory. This
file is for caching icons. On my system, the size of this file is 390KB. Delete
it, and reboot.
Q: I installed Service Pack 4 for NT 3.51. Now my TCP/IP printing doesn't
work. What's the problem, and how can I fix it?
The service pack has changed your spool and print permissions. Use File
Manager to change these permissions in the %systemroot%\winnt\system32\spool and
\printer directories so the Everyone group has change permissions.
Q: If I set a modem to answer in Remote Access Service (RAS) mode, how can
I use it for a different task? Do I need to buy software?
You can try two approaches. First, you can go to Control Panel/Services,
stop RAS, use the modem for your task, and restart the server when you are
finished. Alternatively, you can write a batch file to automate the process:
net stop remoteaccess
drive:\directory\app_name.exe
net start remoteaccess
When you start this batch file, it will stop RAS and start your application.
When you exit the application (which, in this example, is app_name.exe), the
batch file will restart RAS.
Previous
Register
