Next, go to the Servers tab. To increase security, you can select the Log on using Secure Password Authentication check box in the Incoming Mail Server section, but check with your ISP first: Secure passwords might not work in some ISP configurations. (In my experience, Norton AntiVirus Email Protection doesn't work when I select this option.) Depending on whether you select this option, type one of the following entries in the Incoming mail (POP3) text box:
- If you selected the Log on using Secure Password Authentication check box, type
pop3.spa.norton.antivirus
If you cleared the Log on using Secure Password Authentication check box, type
pop3.norton.antivirus
In the Outgoing mail (SMTP) text box, enter your server name (as provided by your ISP). In the Account name text box, enter your username, a slash, then the incoming mail server (as provided by your ISP). For example, I might enter the account name bob/winnetmag.com. In the Password text box, enter your password. Click Apply, click OK, then close Outlook.
Open Norton AntiVirus and click Options on the menu bar. Double-click Email Protection (in the Options list on the left of the Options for Norton AntiVirus dialog box), then click Advanced. Select the Enable Manual configuration check box. Select Email Protection from the Options list. In the Email clients list on the right of the screen, select Microsoft Outlook, then click OK. This step returns you to the main Norton AntiVirus screen. Click Email status and confirm that your manually configured accounts show up in the display and are selected for use. Close Norton AntiVirus and restart the computer.
If these steps don't work for you (they didn't for one of my accounts), the problem, according to Symantec, is that your ISP's POP3 server isn't running at current POP3 specifications. Also, Norton AntiVirus doesn't work with IMAP accounts—a problem that Symantec definitely needs to resolve. Granted, you can siphon all mail through a virus-protected Exchange server, but that process is overkill for an individual user.
When I boot and log on to my Windows 2000 machine, the system gives me the following message: Your maximum registry size is too small. To ensure windows runs properly increase your registry size. What do I need to do to stop receiving this message?
If a system's registry size exceeds the maximum space permitted, the system can rapidly become unstable and cause a problem that can't be fixed short of reinstalling Win2K. The RegistrySizeLimit value, under the HKEY_LOCALMACHINE\SYSTEM\CurrentControlSet\Control subkey, controls the registry's size limit. This value has a default REG_DWORD value of 0x0; consequently, the RegistrySizeLimit value is unseen and permits the registry to increase in size, as needed, up to the maximum size that you've set.
To increase the maximum registry size, right-click the My Computer icon on your desktop and select Properties from the context menu. Go to the Advanced tab and click Performance Options. In the Performance Options dialog box, click Change to open the Virtual Memory dialog box, in which you can reset the maximum size for the registry. The maximum size you set depends on the OS and your particular environment. On my Win2K Professional notebook, on which the registry generally takes up about 20MB, I've set a maximum size of 45MB (i.e., twice the registry size plus 5MB) to avoid any installation problems. (Disk space is relatively inexpensive, so this setting is supportable.)
When I attempt to upgrade a Windows 98 Compaq Presario 5030 to Windows 2000, the system reports that Winnt32 has performed an illegal operation and will be shut down and kills my installation routine. What's happening?
A couple of factors could be causing your problem. First, review your system's documentation and the Microsoft Hardware Compatibility List (HCL) to determine whether Win2K is an acceptable OS for the Presario 5030. (I visited Compaq's Web site but couldn't determine whether Win2K will run on your computer.) Second, Compaq often uses special drivers for its computers. Contact the vendor to find out whether a Win2K driver is available for the Presario 5030.
Does Windows NT 4.0 support removable magneto-optic (MO) devices and removable hard disks? My company is attempting to decide which storage is best for our environment, and someone told us that NT 4.0 restricts the use of removable disks.
NT 4.0 can handle both MO devices and removable hard disks. However, some restrictions exist. The OS treats such removable disks as hard disks, so you must partition the disks and assign them a drive letter. (After you assign a drive letter to a device, you can't change that letter.) NT supports FAT and NTFS on these disks, but the disks can have only a primary partition. You can install the \winnt directory on a removable disk, but the NT boot files (i.e., ntdetect, boot.ini, and NT loader—NTLDR) must be on either a 3.5" disk or a fixed hard disk. Don't place the pagefile on a removable disk: Removable disks slow performance, and NT generally locks such devices to avoid corrupting current files.
End of Article
Prev. page
1
[2]
next page -->
