http://www.emailcashpro.com

ERROR: McAfee Common Framework returned error fffff95b @ 2 (issue: FrameworkManifest.xml corrupt)

Source link


Corporate KnowledgeBase
ERROR: McAfee Common Framework returned error fffff95b @ 2 (issue: FrameworkManifest.xml corrupt)
Corporate KnowledgeBase ID:  KB54520
Published: August 08, 2008

Environment

McAfee Common Management Agent 3.60
McAfee Common Management Agent 3.5x
McAfee VirusScan Enterprise 8.5i
McAfee VirusScan Enterprise 8.0i

Problem 1

The following errors occur after initiating an AutoUpdate:
McAfee Common Framework returned error fffff95b @ 2. (FrameworkManifest.xml corrupt)

Failed to initialize common updater subsystem

Make sure the McAfee Framework Services is running

Problem 2


Subsequent errors when trying to start the McAfee Framework Service:
Could not start the McAfee Framework Service on Local Computer

The system cannot find the file specified

Problem 3


Any of the following update methods will result in the AutoUpdate error:


  • Right-clicking the McShield icon in the system tray and selecting Update Now




  • Right-clicking the AutoUpdate in the VirusScan Console and clicking Start




  • Creating a new scheduled task




  • Editing the properties of the existing AutoUpdate task


Cause

FrameworkManifest.xml has become corrupted.

Solution 1

McAfee Agent 4.0

Changes in the design of the McAfee Agent 4.0 will prevent the corruption of the FrameworkManifest.xml file.
To download the McAfee Agent from the www.mcafee.com website, see KB54808 .

Solution 2


Common Management Agent

Solution 1 - Obtain FrameworkManifest.xml from another computer:


  1. Locate another VirusScan Enterprise (VSE) computer where the updates are working without error.




  2. Copy the FrameworkManifest.xml from the following path:

    For VSE 8.5i  (running on Windows Vista)
    x:\Program Data\McAfee\Common Framework

    For VSE 8.5i (running on Windows XP and earlier)
    x:\Documents and Settings\All Users\Application Data\McAfee\Common Framework

    For VSE 8.0i (running on Windows XP and earlier)
    x:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework





  3. Paste the file to portable media or network share that can be accessed by both computers.




  4. Click Start, Run, type services.msc, and click OK.




  5. Right-click McAfee Framework Service and select Stop.




  6. Copy FrameworkManifest.xml to the Common Framework directory.




  7. Right-click McAfee Framework Service and select Start.




  8. Update the product.



Solution  2 - Delete FrameworkManifest.xml and reinstall the Common Management Agent (CMA)
It is necessary to delete FrameworkManifest.xml because it may not be removed or replaced when an uninstall/re-install is undertaken.
Step 1 - Allow VSE files and settings to be modified (VirusScan Enterprise 8.5i and higher only)


  1. Click Start, Programs, McAfee, VirusScan Console.




  2. Right-click Access Protection, then select Properties.




  3. Select Common Standard Protection.




  4. Select Prevent modification of McAfee files and settings and disable this option.




  5. Click OK.



Step 2 - Delete FrameworkManifest.xml and reinstall CMA:


  1. Delete FrameworkManifest.xml from the following path:

    For VSE 8.5i (running on Windows Vista)
    x:\Program Data\McAfee\Common Framework

    For VSE 8.5i (running on Windows XP and earlier)
    x:\Documents and Settings\All Users\Application Data\McAfee\Common Framework

    For VSE 8.0i (running on Windows XP and earlier)
    x:\Documents and Settings\All Users\Application Data\Network Associates\Common Framework





  2. Restart your computer.




  3. Re-install the Common Management Agent (CMA) / ePO agent.


    NOTE: CMA is available for download from the McAfee Downloads site. See KB54808.


Memory Limits for Windows Releases



Memory Limits for Windows Releases

This topic describes memory limits for supported Windows releases:

Limits on memory and address space vary by platform, operating system, and by whether the IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and 4-gigabyte tuning (4GT) are in use. IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the /LARGEADDRESSAWARE linker option.
Limits on physical memory for 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit Windows systems to use more than 4 GB of physical memory.

Memory and Address Space Limits

The following table specifies the limits on memory and address space for supported releases of Windows.
Memory typeLimit in 32-bit WindowsLimit in 64-bit Windows
User-mode virtual address space for each 32-bit process
2 GB
Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)
4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set
User-mode virtual address space for each 64-bit process
Not applicable
With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default):

x64:  8 TB
Intel IPF:  7 TB
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared
Kernel-mode virtual address space
2 GB
From 1 GB to a maximum of 2 GB with 4GT
8 TB
Paged pool
Limited by available kernel-mode virtual address space or the PagedPoolLimit registry key value.
Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value.
Windows Home Server and Windows Server 2003:  530 MB
Windows XP:  490 MB
Windows 2000:  350 MB
128 GB
Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM.
Windows 2000:  Not applicable
Nonpaged pool
Limited by available kernel-mode virtual address space, the NonPagedPoolLimit registry key value, or physical memory.
Windows Vista:  Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value.
Windows Home Server, Windows Server 2003, and Windows XP/2000:  256 MB, or 128 MB with 4GT.
75% of RAM up to a maximum of 128 GB
Windows Vista:  40% of RAM up to a maximum of 128 GB.
Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM.
Windows 2000:  Not applicable
System cache virtual address space (physical size limited only by physical memory)
Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.

Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value.
Windows Home Server, Windows Server 2003, and Windows XP/2000:  860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.
Always 1 TB regardless of physical RAM
Windows Server 2003 and Windows XP:  Up to 1 TB depending on configuration and RAM.
Windows 2000:  Not applicable

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows 7 Ultimate 4 GB
192 GB
Windows 7 Enterprise 4 GB
192 GB
Windows 7 Professional 4 GB
192 GB
Windows 7 Home Premium 4 GB
16 GB
Windows 7 Home Basic 4 GB
8 GB
Windows 7 Starter 2 GB
2 GB

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.
VersionLimit in 64-bit Windows
Windows Server 2008 R2 Datacenter 2 TB
Windows Server 2008 R2 Enterprise 2 TB
Windows Server 2008 R2 for Itanium-Based Systems 2 TB
Windows Server 2008 R2 Foundation 8 GB
Windows Server 2008 R2 Standard 32 GB
Windows HPC Server 2008 R2 128 GB
Windows Web Server 2008 R2 32 GB

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows Server 2008 Datacenter 64 GB
2 TB
Windows Server 2008 Enterprise 64 GB
2 TB
Windows Server 2008 HPC Edition Not applicable
128 GB
Windows Server 2008 Standard 4 GB
32 GB
Windows Server 2008 for Itanium-Based Systems Not applicable
2 TB
Windows Small Business Server 2008 4 GB
32 GB
Windows Web Server 2008 4 GB
32 GB

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows Vista Ultimate 4 GB
128 GB
Windows Vista Enterprise 4 GB
128 GB
Windows Vista Business 4 GB
128 GB
Windows Vista Home Premium 4 GB
16 GB
Windows Vista Home Basic 4 GB
8 GB
Windows Vista Starter 1 GB
Not applicable

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition
128 GB
64 GB with 4GT
2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition
64 GB
2 TB
Windows Storage Server 2003, Enterprise Edition
8 GB
Not applicable
Windows Storage Server 2003
4 GB
Not applicable
Windows Server 2003 R2 Datacenter Edition
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition
128 GB
16 GB with 4GT
1 TB
Windows Server 2003 R2 Enterprise Edition
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition
64 GB
16 GB with 4GT
1 TB
Windows Server 2003 R2 Standard Edition
Windows Server 2003, Standard Edition SP1
Windows Server 2003, Standard Edition SP2
4 GB
32 GB
Windows Server 2003, Datacenter Edition
128 GB
16 GB with 4GT
512 GB
Windows Server 2003, Enterprise Edition
32 GB
16 GB with 4GT
64 GB
Windows Server 2003, Standard Edition
4 GB
16 GB
Windows Server 2003, Web Edition
2 GB
Not applicable
Windows Small Business Server 2003
4 GB
Not applicable
Windows Compute Cluster Server 2003
Not applicable
32 GB

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.
VersionLimit in 32-bit WindowsLimit in 64-bit Windows
Windows XP 4 GB
128 GB
Windows XP Starter Edition 512 MB
Not applicable

Physical Memory Limits: Windows 2000

The following table specifies the limits on physical memory for Windows 2000.
VersionLimit in 32-bit Windows
Windows 2000 Professional 4 GB
Windows 2000 Server 4 GB
Windows 2000 Advanced Server 8 GB
Windows 2000 Datacenter Server 32 GB

HP Virtual Bus Device installation requires a newer version. Version 4.6.16.0 is required.

Error: HP Virtual Bus Device installation requires a newer version. Version 4.6.16.0 is required.

Solution:


SUPPORT COMMUNICATION - CUSTOMER NOTICE
Document ID: c01684544
Version: 4
Notice: (Revision) HP NC-Series Broadcom 1GbE Multifunction Driver for Windows Server - First Update to Version 4.6.16.0 To Avoid Message "HP Virtual Bus Device Installation Requires a Newer Version. Version 4.6.16.0 is Required."
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.
Release Date: 2009-07-29
Last Updated: 2009-07-29

DESCRIPTION
Document Version
Release Date
Details
4
07/29/2009
Updated Details section to change "Windows 2003 x64 Editions" to "Windows Server 2008 x64 Editions" for cp009684.exe.
3
03/31/2009
Added note stating reboot is required after driver upgrade.
2
03/06/2009
Driver name updated.
1
03/04/2009
Original Document Release.
On a ProLiant server running Windows Server 2003 or Windows Server 2008, if a version of the HP NC-Series Broadcom 1GbE Multifunction Driver for Windows Server earlier than version 4.6.16.0 is installed and an attempt to upgrade the driver to a version later than version 4.6.16.0 is made, the following message is displayed and is written to the cpqsetup.log:
HP Virtual Bus Device installation requires a newer version. Version 4.6.16.0 is required.
This will not occur if running a version of the driver later than version 4.6.16.0. This only occurs when running a driver earlier than version 4.6.16.0 and attempting to update the driver beyond version 4.6.16.0.
DETAILS
The HP NC-Series Broadcom 1GbE Multifunction Driver update does not complete, and the above message is displayed to ensure compatibility.
When running a driver version earlier than version 4.6.16.0, two driver updates are required for the driver to be updated to a version later than version 4.6.16.0. Install version 4.6.16.0 and then upgrade the driver beyond version 4.6.16.0 as follows:
  1. Install the HP NC-Series Broadcom 1GbE Multifunction Driver for Windows Server Version 4.6.16.0, located at the following URLs:
    For Windows Server 2003, use cp009681.exe, located at the following URL:

    For Windows Server 2003 x64 Editions, use cp009682.exe, located at the following URL:

    For Windows Server 2008, use cp009683.exe, located at the following URL:
    For Windows Server 2008 x64 Editions, use cp009684.exe, located at the following URL:

  2. After updating to Version 4.6.16.0, the driver can be updated to a version later than version 4.6.16.0. Perform the following steps to obtain the latest version of the HP NC-Series Broadcom 1GbE Multifunction Driver for Windows Server:
    Note: After upgrading the driver to Version 4.6.16.0 (or later), reboot the server.
  1. Click on the following URL:
  2. Under Select a product category, select Servers .
  3. Select ProLiant/tc Series Servers .
  4. Select the desired ProLiant model.
  5. Select the appropriate operating system.
  6. Select the Driver-Network category.
  7. Select the HP NC-Series Broadcom 1GbE Multifunction Driver and click the "Download" button.

How to Enable PAE in x86 32-bit Windows Server 2003 and 2000 to Use Large 4GB or More RAM Memory

Source Link

"After installing Windows 2000 (Datacenter Server or Advanced Server) or Windows 2003, system properties shows that only around 3.37 GB of physical memory (RAM) is available for application and system use, although 4 GB or more RAM modules have been installed, and BIOS can correctly identifies the full installed size of physical memory, which means that the motherboard and x86 or x64 CPU processor can support more than 4 GB of physical memory.

32-bit Windows operating system depends on PAE (Physical Address Extension) feature to use more than 4 GB of physical memory. On most Windows 2000 and Windows Server 2003 system, especially those run in NUMA mode on a NUMA-capable computer. PAE is disabled by default. PAE is enabled by default only if DEP (Data Protection Execution) is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB.
Thus, if PAE is not enabled in Windows 2000 and Windows Server 2003 (for example, if DEP is turned off by administrator), the system may not able to detect, identify and see more than 4GB memory, and will have to allocate slightly more than 3GB of memory for system and application only as some memory address space has to be reserved and mapped for system devices and peripherals.
To enable PAE in Windows Server 2003 and Windows 2000 (and Windows XP), append the /PAE switch to the end of the line of operating system in the Boot.ini file. To disable PAE, use the /NOPAE switch. The Boot.ini normally located in the root folder (i.e. C:\) with Read-Only and Hidden attributes, which are required to be removed before the file can be edited.
For example,
Original Boot.ini:
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT=”Microsoft Windows 2000 Advanced Server”
/fastdetect
Change the Boot.ini to become:
[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT=”Microsoft Windows 2000 Advanced Server”
/fastdetect /PAE
For Bootcfg command, use:
bootcfg /raw "/pae" /A /ID 1
Restart the computer after modification to make the change effective.
Note that even with PAE enabled, there is still memory limit imposed by the operating system itself. The table below list the maximum memory support with PAE enabled for Windows 2000, Windows Server 2003 and Windows XP. Most 32-bit client based Windows operating system, such as Windows XP and Windows Vista (see way to use large memory of more than 4GB in 32-bit Windows Vista), has OS level limit that restricts the maximum amount of memory able to be used to 4GB.
Operating system Maximum memory support with PAE
Windows 2000 Advanced Server 8 GB of physical RAM
Windows 2000 Datacenter Server 32 GB of physical RAM
Windows XP (all versions) 4 GB of physical RAM*
Windows Server 2003 (and SP1), Standard Edition 4 GB of physical RAM*
Windows Server 2003, Enterprise Edition 32 GB of physical RAM
Windows Server 2003, Datacenter Edition 64 GB of physical RAM
Windows Server 2003 SP1, Enterprise Edition 64 GB of physical RAM
Windows Server 2003 SP1, Datacenter Edition 128 GB of physical RAM

Show Server MS DHCP Stats

Command:
netsh dhcp server \\servername/ipaddress show mibinfo

When you type 'netsh dhcp /?' in Windows XP, you receive 'The following command was not found: dhcp /?'?

If you experience the subject behavior, type:

NETSH SHOW HELPER

If DHCP is not displayed, add the DHCP context:

NETSH ADD HELPER DHCPMON.DLL

Source Link

HP Network Config Corrupt XML file messages



Error : "Corrupt XML file messages when you click on the VLAN tab of the network configuration utility plus missing VLAN parameter errors in the Windows event log. This might only occur if you have teamed two or more network interface cards. (HP calls each card a Miniport.):
- An error occurred due to invalid data in the XML file used by this application. The XML file has been corrupted and should be reinstalled from the installation media."

Solution: The solution is to rename the directory that the network configuration utility was originally installed in (normally C:\Program Files\HP\NCU), and then reinstall the network configuration utility. That forces it to install the new version of the XML file. Your existing network configuration will be lost."

Updated Solution:
1) Create 'VlanID' and 'VlanDefaultID' REG_DWORD 0x0 values 
in 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0008'

I then restarted the server and dissolved and re-created the team. This has solved the problems of the erroneous error messages concerning a corrupt XML file. 

"Access is denied" error message when you run a batch job on a Windows Server 2003-based computer

This issue occurs if all the following conditions are true:

* You run the batch job on a Windows Server 2003-based member server.
* The batch job runs as a non-interactive process.
* The batch job is configured to run under the context of an account that is not a member of the Administrators group.

In Windows Server 2003, the Users group does not have Read and Execute permissions to the command processor (Cmd.exe). By default, the Cmd.exe program has the following permissions settings:

* The Interactive implicit group and the Service implicit group have Read and Execute permissions.

Note On a member server, the TelnetClients group also has Read and Execute permissions. On a domain controller, the Batch implicit group also has Read and Execute permissions.
* The Administrators group and the System implicit group have Full Control permissions

Method 1
Grant the Cmd.exe program Read and Execute permissions for the user account that the batch job runs under. To do this, follow these steps:

1. Click Start, and then click Windows Explorer.
2. Locate and then right-click the Cmd.exe file. The Cmd.exe file is located in the %windir%\System32 folder.
3. Click Properties.
4. Click the Security tab.
5. Click Add.
6. In the Enter the object names to select box, type the user name that the batch job runs under, and then click OK two times.

Note When you add the user, the user is automatically granted Read and Execute permissions.
7. Click Yes when you are prompted to continue.


Method 2
Grant Read and Execute permissions for the Cmd.exe file to the Batch group. This permits all batch processes to run the command processor. To do this, follow these steps:

1. Click Start, and then click Windows Explorer.
2. Locate and then right-click the Cmd.exe file. The Cmd.exe file is located in the %windir%\System32 folder.
3. Click Properties.
4. Click the Security tab.
5. Click Add.
6. In the Enter the object names to select box, type Batch, and then click OK two times.
7. Click Yes when you are prompted to continue.

Open Excel Files as Separate Windows

Open the first workbook any way you want.

Start a second instance of excel.
either put a shortcut to excel.exe on your desktop and use that
or
windows start button|run
type:
excel
and hit enter

Then file|open the second workbook.

Bring OFFLINE Cluster to ONLINE

Connect to one of the nodes using RDP.
Start Cluster Administrator.
Use a period '.' for the cluster name.
Bring the group back ONLINE.

Check PC MAC and NETBIOS remotely using nbtstat

Type this 'nbtstat -A {ipaddress}' into the command prompt.
e.g. nbtstat -A 192.168.1.1

Or if you know the hostname, you can type
'nbtstat -a {hostname}'
e.g. nbtstat -a WorkStat123

For more info on 'nbtstat', refer to this link below
http://technet.microsoft.com/en-us/library/cc940106.aspx

Enjoy....

Nokia 5800: Tips and Hints

1) How To Reset The T9 Dictionary
To reset your T9 dictionary without resetting your phone, go to C:/Predic using a 3rd party file manager (the built in manager won’t work, I’d suggest Y-Browser)… delete the .dat file that is in that folder.

Nokia 5800: Codes

1) Display WLAN - *#62209526#
2) Reset to default factory settings - *#7370#
- Default password - 12345

Backing up local Microsoft Outlook files

Reference number: CH000457
Backing up local Microsoft Outlook files.
Issue:

Backing up local Microsoft Outlook files.
Additional information:

This document helps explain how to backup local Microsoft outlook and outlook express files. It is important to note that some companies may store your e-mail or outlook files on a network server, therefore the below information will not apply.
Cause:

Users who have large amounts of e-mail or information in outlook that they wish to backup may find it necessary to backup the mail in case that information is erased.

Solutions:

Microsoft Outlook Express users
Microsoft Outlook users

Microsoft Outlook Express users

Microsoft Outlook Express stores the files in the below types of files.

*.wab files are Microsoft Outlook Express address book files.
*.mbx files are Microsoft Outlook Express mail folders.

The Microsoft Outlook Express 5x Block Sender List and Other Mail Rules are stored in the computer's registry.

Backing up the Outlook Express address book.

1. Locate the file by using the Windows find tool. Click Start / Find / Files or Folders.
2. In the Named box type *.wab - ensure the Look in box is looking on the drive that Microsoft Outlook is located (usually the C: drive).
3. Click Find Now
4. This should locate the Microsoft Outlook Express address book, if present. Generally, this file will be the Outlook Express user's name.
5. Once this file is located, copy the file to an alternate drive or backup media such as a Zip disk.

Backing up the Outlook Express mail

1. Locate the file by using the Windows find tool. Click Start / Find / Files or Folders.
2. In the Named box type *.mbx - ensure the Look in box is looking on the drive that Microsoft Outlook is located (usually the C: drive).
3. Click Find Now
4. This should locate the Microsoft Outlook Express address book, if present. If more than one .mbx file is located, it is likely that you have more than one mail folder and it is recommended that you copy all the files you wish to backup.
5. Once this file is located, copy the file to an alternate drive or backup media such as a Zip disk.

Backing up the Outlook Express 5x Block Sender List

Note: The below steps take the user through the system registry. If you are unfamiliar with the system registry and the potential risks you take by editing the registry, please see our registry page first.

1. Open the Registry by clicking Start / Run and typing regedit and clicking ok.
2. Locate the below registry key.

HKEY/CURRENT/USER\Identities\{Identity Number}\Software\
Microsoft\Outlook Express\5.0\Block Senders

3. Once in the above registry key, click Registry in the Regedit menu and click "Export Registry File..."
4. Save the Block Senders.reg file to desktop or your backup location.

Backing up the Microsoft Outlook 5x Other Mail Rules

Note: The below steps take the user through the system registry. If you are unfamiliar with the system registry and the potential risks you take by editing the registry, please see our registry page first.

1. Open the Registry by clicking Start / Run and typing regedit and clicking ok.
2. Locate the below registry key.

HKEY/CURRENT/USER\Identities\{Identity Number}\Software\
Microsoft\Outlook Express\5.0\Rules\Mail

3. Once in the above registry key, click Registry in the Regedit menu and click "Export Registry File..."
4. Save the Block Senders.reg file to desktop or your backup location.
5.

Microsoft Outlook users

Microsoft Outlook stores the files in the below types of files.

*.pab files are Microsoft Outlook address book files.
*.pst files are Microsoft Outlook mail files book files.
*.rwz files are the Microsoft Outlook rules wizard files.

Backing up the Microsoft Outlook address book

1. Locate the file by using the Windows find tool. Click Start / Find / Files or Folders.
2. In the Named box type *.pab - ensure the Look in box is looking on the drive that Microsoft Outlook is located (usually the C: drive).
3. Click Find Now
4. This should locate the Microsoft Outlook address book, if present.
5. Once this file is located, copy the file to an alternate drive or backup media such as a Zip disk.

Backing up the Microsoft Outlook mail

1. Locate the file by using the Windows find tool. Click Start / Find / Files or Folders.
2. In the Named box type *.pst - ensure the Look in box is looking on the drive that Microsoft Outlook is located (usually the C: drive).
3. Click Find Now
4. This should locate the Microsoft Outlook mail file, if present. Generally, this file is mailbox.pst.
5. Once this file is located, copy the file to an alternate drive or backup media such as a Zip disk.

Backing up the Microsoft Outlook rules wizard files

1. Locate the file by using the Windows find tool. Click Start / Find / Files or Folders.
2. In the Named box type *.rwz - ensure the Look in box is looking on the drive that Microsoft Outlook is located (usually the C: drive).
3. Click Find Now
4. This should locate the Microsoft Outlook rules file, if present. Generally, this file is rules.rwz.
5. Once this file is located, copy the file to an alternate drive or backup media such as a Zip disk.

Backing up the Microsoft Outlook signatures

Each of the Microsoft Outlook signatures you have are backed up as signature.txt, signature.rtf, and signature.htm, where 'signature' is the name of each of the signatures you have.

1. Locate the signature file by using the Windows find tool. For the name of the file type signature*.* where 'signature' is the name of one of your signatures. Usually these files are stored in C:\Documents and Settings\User\Application Data\Microsoft\Signatures or similar directory.
2. Once you have located them, select each of the signatures you wish to backup and copy to your backup destination.

Nokia 5800: Tips and Tricks

Here are 10 Tips and tricks that you can use on your Nokia 5800 XpressMusic.

.
1. To bring out the Shortcuts on your Screen/Desktop-> Settings/Personal/Home Screen/Home Screen Theme and select Shortcut bar, you can then select which shortcut to display if goto “Shortcuts”. This will also bring out the “Track” playing being displayed when you open the Music Player.

2. Tap the Clock to bring out the Clock menu and make your alarm, alarm repeat is now built-in.

3. Tap the “General” or Date (the set Profile besides the clock) and the Profile selection menu pops out, almost similar to pressing the “Power” button in all S60, but here the Remove memory is not shown, but “Calendar” shortcut is included and the other profiles as well.

4. If you are on the Numeric Keypad, pressing the [#] key alternately will toggle the General and Silent Profiles, same as before, which means long press on zero [0] will bring out bookmarks for the Web.

5. Tapping on the displayed To do or Calendar entry will bring you immediately to that particular item.

6. Tapping the Active Icon on the Top Left (near the battery indicator) will give you shortcuts for any of the active icons.

7. Long press on the Green Call Button will still activate the Voice Command Prompt

8. Long press on the center button is similar to the Long press on the “Menu” key (the yin-yang key on most S60) which will bring out the menu for all the active applications.

9. Go to Applications/File Manager and setup “Backup” for automated backup schedule of your phone data.

10. How to update your Nokia 5800 firmware using your phone.
Presss *#0000# to display phone factory information and firmware
Now press options and select check for updates
The newest update is sent to your phone from nokia
Download and install updates.
This is done using GPRS or WIFI Connectivity.

Dlink DSL-G604T Bittorent problem

This is a very good article showing how to change the configuration for Dlink DSL-G604T so as to solve the bittorrent problem.

"D-LINK (& Several other major routers, netgear, linksys, etc.) has a maximum connection threshold. There are several firmware upgrades for improved p2p performance and also some 3rd party firmware. Please google for it. However, if you don't trust these 3rd party firmware, there is a workaround.

This problem is extremely easy to identify. You utorrent downloads continue running, all connections continues. For example, a Internet explorer downloads continues with no problem. But "non-continuous" connections stops. You can't ping your router. Your MSN Disconnects. You can't use internet explorer to surf the web. Then this is most probably your problem.

PLEASE NOTE THE FOLLOWING IS TO BE USED ON D-LINK DSL-G604T ADSL ROUTERS ONLY. ALTHOUGH OTHER ROUTERS MAY CONTAIN SIMILAR OS, DIRECTORY STRUCTURE & TELNET COMMANDS. USE IT AT YOUR OWN RISK.

This post documents how to automate this process, and how to simplify the re-issuing of commands should it be necessary to reboot or restart the router.

The process is called Telnet Scripting. To use it you need:
- a Telnet Scripting tool
- a file containing Telnet commands (that is, a script file)

Although you can use a normal telnet. You will have to type the commands all over again everytime the router restarts. This includes changing firewall settings, virtual server settings, etc. With a telnet scripting tool, you can do it with 2 clicks.

The Telnet Scripting tool that I use is TST10.EXE, written by Albert Yale. It can be downloaded from at http://users.telenet.be/tontonzen/gg/TST10.zip

Here's a trivial example of its use, a script to login to the DSL-G604T and display the help text:

192.168.1.1 23
WAIT "login:"
SEND "root\m"
WAIT "Password:"
SEND "admin\m"
WAIT "#"
SEND "help\m"
WAIT "#"

The script assumes the default IP address of the router (192.168.1.1) and the default login password (admin).

If the script were stored in the file help.txt then the command to issue it (assuming it is in the same directory as TST10.EXE) would be:

tst10 /r:help.txt

Info on the script syntax and the parameters of TST10.EXE can be found by running the program.

If you like, you can also write a .bat file on your own to run the script so all you have to do is double click to execute the commands. That is what I did.

A real life example of where this is useful is given below. This provides a script to set the NAT session parameters for success (?) with P2P applications, by increasing the number of concurrent NAT sessions and setting appropriate timeout values to ensure 'stale' session data is discarded. Acknowledgement and thanks to a post by samPT in this forum for the values.

192.168.1.1 23
WAIT "login:"
SEND "root\m"
WAIT "Password:"
REM This password is the administrator password you have set.
SEND "admin\m"
WAIT "#"
SEND "cd /proc/sys/net/ipv4/netfilter\m"
WAIT "#"
SEND "echo 4096 > ip_conntrack_max\m"
WAIT "#"
SEND "echo 50 > ip_conntrack_generic_timeout\m"
WAIT "#"
SEND "echo 5 > ip_conntrack_tcp_timeout_close\m"
WAIT "#"
SEND "echo 120 > ip_conntrack_tcp_timeout_close_wait\m"
WAIT "#"
SEND "echo 1200 > ip_conntrack_tcp_timeout_established\m"
WAIT "#"
SEND "echo 120 > ip_conntrack_tcp_timeout_fin_wait\m"
WAIT "#"
SEND "echo 60 > ip_conntrack_tcp_timeout_time_wait\m"
WAIT "#"
SEND "echo 10 > ip_conntrack_udp_timeout\m"
WAIT "#"
SEND "cd /\m"
WAIT "#"
SEND "exit\m"

Save this in a file (say) nat_sessions.txt, edit the default IP address and password to match your installation. Run a command prompt, change to the directory with the script + program, and execute it with:
tst10 /r:nat_sessions.txt /m

Just to confirm that these commands have taken effect and that the values have been written to the specific files, change directory and type them out. Here's an example:
cd /proc/sys/net/ipv4/netfilter/
cat ip_conntrack_max

You can extend this Telnet Scripting technique to do as many things as your Linux knowledge and the embedded toolset in the DSL-G604T allows. Which means that you perhaps won't need to wait for new firmware releases and fixes. Clearly this won't cover everything, but I'm sure you get the idea...

"

nokia 5800 tube ear piece volume problem

A very good article that solves the irritating nokia 5800 ear piece volume problem. And it really works. Believe me, i have tried it. :)



Source link

"
1)
Take the plectrum (a three-cornered-stylus, which came in the box).

2) Take the device, turn it off and remove the battery.

3) We start to remove the upper panel (see diagram). Getting started is strictly bottom, so as to stay top of the plume and accelerometer sensor lights.


4) Removed the lid. You should get as in the picture.


5) Now we see the speaker. It should be pulled out and turned.


6) There will be two contacts which should be unbent (see figure).


7) Unbend them and then collected back.

Cool Everyone can now forget about the problem with the speaker.
"

Official Fix for the Zune 30 Fail

Here's the official extracts from Microsoft

" Early this morning we were alerted by our customers that there was a widespread issue affecting our 2006 model Zune 30GB devices (a large number of which are still actively being used). The technical team jumped on the problem immediately and isolated the issue: a bug in the internal clock driver related to the way the device handles a leap year. That being the case, the issue should be resolved over the next 24 hours as the time change moves to January 1, 2009. We expect the internal clock on the Zune 30GB devices will automatically reset tomorrow (noon, GMT). By tomorrow you should allow the battery to fully run out of power before the unit can restart successfully then simply ensure that your device is recharged, then turn it back on. If you're a Zune Pass subscriber, you may need to sync your device with your PC to refresh the rights to the subscription content you have downloaded to your device.

Customers can continue to stay informed via the support page on zune.net (zune.net/support).

We know this has been a big inconvenience to our customers and we are sorry for that, and want to thank them for their patience.

Q: Why is this issue isolated to the Zune 30 device?
It is a bug in a driver for a part that is only used in the Zune 30 device.

Q: What fixes or patches are you putting in place to resolve this situation?
This situation should remedy itself over the next 24 hours as the time flips to January 1st.

Q: What's the timeline on a fix?
The issue Zune 30GB customers are experiencing today will self resolve as time changes to January 1.

Q: Why did this occur at precisely 12:01 a.m. on December 31, 2008?
There is a bug in the internal clock driver causing the 30GB device to improperly handle the last day of a leap year.

Q: What is Zune doing to fix this issue?
The issue should resolve itself.

Q: Are you sure that this won't happen to all 80, 120 or other flash devices?
This issue is related to a part that is only used in Zune 30 devices.

Q: How many 30GB Zune devices are affected? How many Zune 30GB devices were sold?
All 30GB devices are potentially affected.

"