A Seagate Backup Exec Heads Up; Disabling the Briefcase

Seagate Backup Exec Heads Up
According to Microsoft Support Online article Q242118 (http://support.microsoft.com/support/kb/articles/Q242/1/18.asp), Seagate Backup Exec 7.19 deletes the Registry value MaxRequestThreads=16, and this missing data disables the Windows NT Messenger service. If your system has this problem, it might either hang or lose its remote connections after you install the Backup Exec 7.19 update. The article indicates that you can restore normal Messenger service operation by manually replacing the missing Registry data, but the edit instructions don’t include the correct value entry to modify. On my system, MaxRequestThreads=16 appears at the end of the data associated with the value entry Windows:REG_EXPAND_SIZE in

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Subsystems. I recommend that you verify this edit with Seagate before you make the modification.

Disabling the Briefcase Icon
You can use two methods to remove the Briefcase icon from a Windows NT desktop: exclude it during the original installation or disable it after building the system. Microsoft Support Online article Q163481 (http://support.microsoft.com/ support/kb/articles/ Q163/4/81.asp) describes how to disable the Briefcase permanently during an initial NT install. You need to edit the line that contains syncap.exe in the layout.inf and txtsetup.sif files before starting the installation, but the article cautions that this technique works only if you perform the install from a network drive or via an unattended installation.

If you install NT without disabling the Briefcase, you can modify the Registry to disable the fuction that automatically creates the icon each time a new user logs on. Find your way to the Winlogon Registry entry

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

and add the value entry RunSyncApp:REG_DWORD:0. Then, rename the %systemroot%\system32\syncapp.exe file to syncapp.old. If the RunSyncApp Registry entry disables the executable, I’m not sure why you need to rename the file, but that’s Microsoft’s recommended method. Remember, you can interactively modify the Registry with the Registry editor, you can include the edit in a logon script, and you can incorporate the modification in your custom system policy.

Removing a Deleted Print Job
Have you ever had a print job that hangs, so you delete it from the print queue, but the job stays in the queue with a status of "Deleting" and never goes away? And because the job is stuck in the print queue, you can’t correct the problem by deleting the printer associated with the queue. I’ve seen this symptom on and off for years. According to Microsoft Support Online article Q242126 (http://support.microsoft.com/support/ kb/articles/q242/1/26.asp), you can flush the job by stopping and starting the print spooler from the command line using two commands: Net Stop Spooler and Net Start Spooler.

Removing IIS 4.0 and the NT Option Pack
Microsoft Support Online article Q242083 (http://support.microsoft.com/support/kb/articles/Q242/0/83.asp) documents an 18-step procedure for completely removing Microsoft Internet Information Server (IIS) 4.0 and the Windows NT 4.0 Option Pack. I started to write this one up and paused after reading the vague instructions in step 2, which tell you to stop SQL Server, IIS 4.0, all Exchange Server services, and "all other nonessential services, including but not limited to third-party products …" I’m not sure how you figure out which other services you need to stop. The instructions should list these additional services--the native NT services at a minimum. Step 13 tells you to clear all the event logs, but gives you no explanation of why you need clean logs. Then step 14 stopped me cold because it instructs you to install the NT Option Pack and make a note of any errors that occur. How does installing the NT Option Pack help you remove it? Am I missing something? Maybe we’ll get an updated version of this procedure—or at least a better explanation—next week.

A Dump File Catch-22
I’m including this one primarily for its entertainment value. A Windows NT pagefile can be a maximum of 4GB. When you install NT on a system with 4GB of main memory or more, you can’t create a pagefile large enough to hold the memory dump. Microsoft suggests two workarounds for NT 4.0: you can limit the amount of physical memory the system uses with the /MAXMEM switch in the boot.ini file, or you can physically remove some of the RAM—chuckle, chuckle. You can read the details in Microsoft Support Online article Q241046 (http://support.microsoft.com/support/ kb/articles/Q241/0/46.asp).

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish