Acer Aspire One BIOS Recovery

The Acer Aspire One has its own built-in BIOS recovery routine, allowing it possible to flash the BIOS even when the system doesn’t boot anymore. It’s feature meant only for emergencies it may void your warranty, so use at your own risk.

Execute every step carefully!

Step 1 :

Format an USB stick with FAT file system.

Step 2 :

Download the latest Aspire one BIOS, then put both Bios and the FLASHIT.EXE software file in the root directory of the USB stick.

Step 3 :

Important, rename the BIOS file to ZG5IA32.FD and do not remove the USB stick.

Step 4 :

Turn off the A1 and make sure both battery and AC adapter are connected.

Press the Fn+Esc key, keep it pressed and push the power button to turn the Aspire 1 on.

Release the Fn+Esc key you will see after a few seconds, the power button blinking.

Push the power button once at this time the acer One will now initiate the BIOS flash, do not interrupt it under any circumstances.

Wait until the power button stop blinking, the AA1 will reboot shortly after. Wait patiently.

Now the BIOS has been flashed so all settings reset to default.

If for any reason you made a mistake during the procedure let it unable to reboot by itself wait 5 minutes before turning it off( just to be safe that it isn’t still flashing the BIOS).

Bonus :

I would really recommend u to disconnect !!all!! USB devices, especially storage class, from your netbook before doing a reboot.

You can find more solutions  at http://www.laptop-support.net

Solve the Freeze Problem of Outlook 2007 With OST To PST Converter

It is easy to access Outlook mail objects, such as e-mails, tasks, journals, attachments, appointments, and messages without Internet connection. The overall credit goes to the OST files. These files allow you to use mail objects without Internet connection. Using the OST file is the same as using MS-Office file. Whenever you connect with the Exchange server, all the data of the OST file gets automatically converted to PST. But sometimes, it happens you are unable to use mail objects because you fail to synchronize OST files with exchange server. So, there is a need to convert OST to PST file. For conversion, use a third party OST to PST converter tool.

Discussed below is an error that appears when you use Outlook 2007, Outlook application halts after some time and doesn’t allow you to access Outlook application:

“Event Type: Information

Event Source: Outlook

Event Category: None

Event ID: 30 Date: 5/10/2008

Time: 8:33:44 AM

User: N/A

Computer: SBS-Computer

Description: The store C:Documents and Settingsuser.domainLocal SettingsApplication DataMicrosoftOutlookoutlook.ost is being reconciled with the indexer for the following reason: Non-matching max change numbers.”

Causes:

The cause for the occurrence of the above error message is corruption or destruction of your OST file.

Solution:

Such errors can be resolved easily. First repair the corrupt OST file. For checking the OST file, execute OST Integrity Check tool. For executing this tool, follow the below steps:

– Close Outlook.

– Open Scanost.exe. This program is located at drive:Program FilesCommon FilesSystemMSMAPILocaleID folder.

– From the Name list of profile, select a profile that contains OST for checking.

– A dialog box will appear that asks you to Connect or Work offline, select Connect.

– Check the Repair Errors check box. If you uncheck the Repair Errors checkbox, then the tool does not make any change even if changes are required.

– After performing all the above stated steps, choose Begin Scan.

If you are not satisfied with the results of OST Integrity check tool, then use a third party OST to PST converter tool. OST to PST converter tools are read-only tools built with advance technology to safely convert OST to PST file. Built with simple graphical user interface, these tools are easy to understand.

Stellar Phoenix Convert OST PST tool easily converts OST to PST without changing the original structure of the OST file. The tool restores OST to PST onto any drive that can be found by the host operating system easily. The tool employs advance scan and normal scan – whichever is required – to recover OST content. It supports MS-Outlook 2010, 2007, 2003, 2000, and 2002. You can download a demo version of the software to preview its functionality.

Resolving "Cannot Start the Reminder Service" Error in MS Outlook

Microsoft Outlook reminders are scheduling components that can keep you alert at important events. The application shows a peculiar behavior when any of these items get corrupt, one of such has been described later. But if the corruption occurs together with PST file corruption, you need solution that might perform PST Recovery to recover pst file from MS Outlook.

For example, consider a case when you start Microsoft Outlook and receive an error message as below:

“Cannot start the reminder service. Unable to show reminders.”

The error suggests that the issues are related to Outlook reminders, which alone can be taken care of easily. But at times, you encounter this message in conjunction with another error like:

“An unknown error has occurred. 0X80040600”

With this error message, Outlook loses the ability to send and receive e-mail messages.

Cause

Outlook fails to show the reminders if one or more of these items in the folder are damaged or corrupted. You can simply resolve this issue by deleting the reminders. But if Outlook cannot perform e-mail operations as the second error also occurs, your PST might be damaged.

Solution

To solve specific reminders-related problem, you need to clean the reminders as follows:

1. Click ‘Start’ and then ‘Search’ or ‘Find’

2. Click ‘Files and Folders’, type ‘Outlook.exe’ in the named box and press ENTER

3. Note the full path of ‘Outlook.exe’ and close the box

4. Click ‘Start’ and then ‘Run’

5. Type the full path of ‘Outlook.exe’ (as noted above), press SPACEBAR, type ‘/’ (the forward slash) and then command-line switch ‘Cleanreminders’ to delete the reminders

If Outlook starts working as normal, you don’t need to take further steps, but in case e-mail delivery and sending is stopped because of PST issues, you should apply a suitable PST Recovery Tool.

Backup your PST and run Outlook Inbox Repair Tool (Scanpst.exe) to repair the corrupted PST. Scanpst.exe is a hidden file, so keep in mind to include hidden and system files before starting to search the file. If PST corruption still persists, you need a third-party PST File Recovery alternative.

Outlook PST Recovery Software is a professional utility that repairs corrupted PST and restores the data in a new, Outlook-usable PST. The PST Recovery Tool uses an advanced set of procedures to scan the file. The software has a 3-pane display that is easy to navigate and operate. It supports MS Outlook 2007, 2003, 2002, and 2000.

How To Quickly Make A Bootable USB Stick With FreeBSD

Install FreeBSD, or use an existing FreeBSD installation, and follow these steps:

1) First, you need to prepare and format your USB stick:

fdisk -BI /dev/da0
bsdlabel -B -w da0s1
newfs -U -O1 /dev/da0s1a
boot0cfg -v -B da0
(“-U -O1” [“O” like in Olympus, not zero] is for UFS1 which provides much faster copying than UFS2; if you decide for UFS2, type “-U -O2” – but expect that the copying will be slower)

2) Then mount it: mount /dev/da0s1a /usb
3) Copy all directories (FreeBSD) to the stick
4) After copying, modify the /usb/boot/loader.conf (explained below)
5) In the /boot directory on your USB stick you must have MFS (Memory File System – mfsroot.gz), which you will make (instructions are below)
6) Modify your /etc/fstab in MFS and put the following line (only) there:
/dev/md0 / ufs rw 0 0
7) After you boot your computer with the stick, you will be in the MFS environment from which you will mount your USB stick with mount_nullfs (described below)

Modification of /boot/loader.conf on your USB stick

You must have the following lines in your /boot/loader.conf (some lines are optional):

mfsroot_load=”YES”
mfsroot_type=”mfs_root”
mfsroot_name=”/boot/mfsroot”
nullfs_load=”YES”
splash_bmp_load=”YES”
vesa_load=”YES”
geom_uzip_load=”YES”
geom_label_load=”YES”
bitmap_load=”YES”
bitmap_name=”/boot/splash.bmp”
snd_driver_load=”YES”
kern.maxfiles=”25000″
kern.maxusers=”64″
vfs.root.mountfrom=”/dev/md0″

# Additional filesystem drivers

udf_load=”YES”
linux_load=”YES”
fuse_load=”YES”
ntfs_load=”YES”
ext2fs_load=”YES”
reiserfs_load=”YES”

Making your own MFS

FreeBSD, after the kernel boots, can use the root file system in memory (mfsroot_load=”YES” command in /boot/loader.conf will do the trick). To build such a memory file system, type the command:
dd if = /dev/zero of = mfsroot bs = 1024k count = 42

The mfsroot file of about 40 MB in size will be created. You need to format it, mount it and copy the most important files into it from your FreeBSD system (/bin, /sbin, /etc, /root….):

mdconfig -a -f mfsroot md0
newfs /dev/md0
mount /dev/md0 /mnt

Once copied, you must unmount it and gzip it: gzip mfsroot

Optionally, you can chroot it to see if everything works, then copy the mfsroot.gz to /usb/boot onto your USB flash drive (or disk). If you think it may be a problem to pick the most important files for your MFS (from your FreeBSD installation), search for mfsbsd in Google and either use its toolset or the MFS image alone (contained in the downloadable ISO of mfsbsd).

After booting from the USB stick (you will jump into MFS), you must mount the physical USB stick:

/sbin/mount -o ro /dev/da0s1a /usb
/sbin/mount_nullfs /usb/boot /boot
/sbin/mount_nullfs /usb/usr /usr

The above commands will help you use the big /usr directory on your USB stick instead of the /usr dir in MFS. mount_nullfs /usb/boot /boot is optional, as in your MFS/boot directory only the following files are needed for the little MFS to boot (/boot/kernel directory in MFS): geom_label.ko, geom_uzip.ko, zlib.ko a their debug symbols (zlib.ko.symbols, etc.). By mounting the /usb/boot dir via mount_nullfs into the /boot directory in your MFS you will be able to load kernel modules.

The Pros and Cons of Network Attached Storage (NAS)

As the increase in technology becomes more advanced, so do the methods of data recovery. Data recovery has become a need for personal and business reasons, but for businesses a poor disaster recover or data loss plan can lead to the loss of extremely important data that cannot be recovered. While this seems like an issue that can be solved, the loss of data for some businesses can cost thousands or even millions of revenue dollars. For private users, it may not be the loss of millions of dollars, but it can mean the loss of an integral set of information that costs even the personal users many dollars.

With the increasing advancement of data storage, the use of data recovery has also tried to parallel its sister component. Rack and virtual drives have become the new way to save large amounts of data on an array of large network drives. Network Attached Storage, or NAS, has become an official method to store large amounts of data. This type of technology is mostly used in medium to large enterprises and it gives the corporation an added layer of data recovery and fail over solutions.

Pros of Network Attached Storage:

The advantage of NAS is the consolidation of storage platforms for administrators. It is much easier to collaborate all servers onto one machine with an array of drives faster than any standalone server on the market. The other advantage is the administrative headache of managing any failures or other types of typical issues that can affect each, individual machine. Basically, the use of NAS consolidates a bunch of servers and their issues into one, easy to manage machine that is quick and easy to restore any lost data across a network. This leaves an incredibly easier way to manage large corporate data that spans across multiple offices and even mobile locations.

The Cons of Network Attached Storage:

One of the main consolidation issues is the file systems under which NAS operates. End users, who are backing data up on the NAS, connect to it through their installed operating system. However, the actual file system on the NAS it typically Linux. In case of failure it may prove difficult to recover the data without professional data recovery service.

These are only two of the pros and cons of network attached storage that comes with the management of improved and advanced network technology. A business that uses NAS in their network design should ensure that the business is in need of a topology design that is as advanced as NAS. Even when NAS is not a solution that can be used in the business, the use of data recovery is important for any business to ensure its survival through disaster recovery.

Advantages and Disadvantages of Local and Remote Data Backup

Whether you run a small or big enterprise, data backup is an essential routine that you should do to protect all your data. It is for the security of your business. The process of backing up your data can be done remotely through a file server, or locally using tapes, discs, DVDs, external hard drive, or the local drive.

There are advantages and disadvantages of local and remote data backups. Here are a few:

Advantages

Local Backup

One very effective way of backing up your data would be to store them in portable storage devices. These include CD’s, USB’s, DVD’s, external hard drive, and the local hard drive among others, where you could easily retrieve the data that you want to access. Local data backup is an advantage because it could be done fast and easy especially now that there are software that could backup your computer and all your files on schedule. Once your computer crashes, all your files could be retrieved from your storage devices and so too does your operating system where you could restore it at a specific backup point. This is mostly used by most individuals and some small business enterprise.

Remote Backup

Remote backup nowadays is becoming widely used because of some advantages. First, having a data backup at a secure place outside of your infrastructure or your business place can give you peace of mind. Whatever happens at the workplace you’re sure that all your important files are secured. Most of the big companies employ this method of data backup. Second, with the emergence of global outsourcing, remote data backup has become more popular because the data from multinational companies are safe and secured at their own site (that is in their country), while these are being utilized by their offshore sites. They have an assurance that all their data are secured.

Disadvantages

Local Backup

While local data backup is the easiest and fastest way of data backup, there are also disadvantages to it. You are never sure of any calamity that could happen, like fire for instance, or flood. Not only could your computer be ruined by these calamities, but all your storage devices as well that contains your data backup. In addition, it is not uncommon that we forget things sometimes. You never know, you may forget where you store your USB’s. Your files may be lost forever.

Remote Backup

One disadvantage of storing your files remotely is the transfer speed. Remote data backup may take a while depending on the speed of your transmission devices. A high speed LAN could transmit fast, but others could be problematic, because of upload issues and firewalls.

A good suggestion is you employ both local and remote backup so you’re sure, that against all the odds, you have your data secured.

‘Attempting to Validate BBT Refcounts’ Outlook PST Error

Microsoft Outlook PST is the single file consisting of all email messages, notes, journals, tasks, appointments and other Outlook objects. This file is prone to corruption due to reasons like virus attack, saving PST on network, application faults, unexpected shutdown and other similar reasons. Thus for complete file restoration, you need to use your recent file backup. But in case you observe that backup is giving errors or is not updated to restore required data, commercial Outlook PST Repair tools can prove as valid tools to be used.

You might receive the similar error message while using Microsoft Office Outlook Inbox Repair Tool:

“Attempting to validate BBT refcounts”

“Couldn’t find BBT entry in the RBT (211C8)”

You receive such errors in the log report.

Cause

Possible causes for the above error to occur are:

  • PST file is large in size
  • Outlook is unable to find the BBT entry of the file
  • PST is damaged or corrupted

Note: Outlook 2002 and earlier versions have default file size limit of 2 GB. If PST grows beyond this file size limit, Outlook shows strange behavior and PST gets odds to corrupt. In Outlook 2003 and 2007, this file size limit has extended to default value of 20 GB.

Solution

To fix these issues, you should try performing these steps:

  • Try to reduce file size. You can empty the ‘Deleted Items’ folder and delete unimportant email messages from all folders including Inbox, Sent Items etc.
  • Try reinstalling Microsoft Office Outlook to resolve BBT errors
  • If PST corruption is the issue, you need to repair it. Since Inbox Repair Tool cannot repair such files, you should Repair PST using commercial applications.

Outlook PST Repair software are safe and advanced applications to repair damaged PST. These software deploy high-end scanning algorithms to examine a damaged PST file and repair it, without changing file original view and content. You can use these tools to Repair Outlook PST in any case of personal storage file corruption. They come equipped with self-descriptive interface, read-only design and automated recovery options.

The History Of Data Deduplication

Data deduplication has been around, at least in its most primitive form, since the 1970’s. It initially started because companies wanted to store large amount of customer contact information without using a large amount of storage space. One of the first ideas was to go through and remove duplicate data. For example, a company might have an address for shipping, and an address for billing to a given customer. In these cases, those identical addresses would be combined into one file. This was done by data entry clerks who would review the data line by line and get rid of duplicates.

Of course, the amount of personnel needed to do this was extensive and it took a very long time. Sometimes, the data deduplication process would take months to complete. However, considering that most of this occurred on hard copy, it wasn’t a major problem. The big problems cam along when computer use became widespread in office environments.

With computers in wide use and the explosion of the internet, the amount of data available exploded as well. Backup systems were created to ensure that companies would not lose all their data. As time went by, floppy discs and other external hardware was used to store this data. Unfortunately, this data would soon fill up these discs and the amount of space to store this data was extensive.

With cloud storage and other alternative storage options, companies began moving their storage to a virtual environment. They also moved to disk-based storage over tape based, simply because it was low-cost and required less space. However, these storage options were expensive and difficult to manage as data grew. The same data would get saved over and over again. This redundant data was not needed and took up valuable storage space.

Companies might have customized their backup plans to eliminate duplication, but there was no fast way to do this. That is when IT professionals began working on algorithms to automate the data deduplication process. They generally did this on a cases by case basis, with their goal to optimize their own backup files. Their algorithms would be customized to meet their own individual needs.

There was no one company that came up with the idea of data deduplication. Instead, the need to find a way to reduce duplicate files was a common need in the industry. There were many computer scientists who advanced data deduplication technology significantly, but there is no one scientist who was solely responsible for it. While many have claimed credit for the term ‘data deduplication’ itself, no one person can claim credit for the idea itself.

Instead, the creation of data deduplication algorithms was more of a compilation. People in the IT industry saw a need to reduce data duplicates and they filled that need to reduce those duplicated file by creating algorithms. As data increases, people will continue to find ways to compress data in a way that makes it easy to store.

Password Recovery on the Cisco ASA Security Appliance

In this article, I’ll explain how to perform a password “reset” on your Cisco ASA security appliance. The more commonly used term for this procedure is “password recovery” which is left over from the days when you could actually view passwords in configuration files in plain text. Today, such passwords are encrypted and not actually recoverable. Instead, you will gain access to the appliance via the console port and reset the password(s) to known values.

This procedure requires physical access to the device. You will power-cycle your appliance by unplugging it at the power strip and plugging it back in. You will then interrupt the boot process and change the configuration register value to prevent the appliance from reading its stored configuration at boot. Since the device ignores its saved configuration on boot, you are able to access its configuration modes without passwords. Once you’re in configuration mode, you will load the saved configuration from flash memory, change the passwords to a known value, change the configuration register value to tell the device to load its saved configuration on boot, and reload the device.

Caution: As with all configuration procedures, these procedures should be tested in a laboratory environment prior to usage in a production environment to ensure suitability for your situation.

The following steps were designed using a Cisco ASA 5505 Security Appliance. They are not appropriate for a Cisco PIX Firewall appliance.

1. Power-cycle your security appliance by removing and re-inserting the power plug at the power strip.

2. When prompted, press Esc to interrupt the boot process and enter ROM Monitor mode. You should immediately see a rommon prompt (rommon #0>).

3. At the rommon prompt, enter the confreg command to view the current configuration register setting: rommon #0>confreg

4. The current configuration register should be the default of 0x01 (it will actually display as 0x00000001). The security appliance will ask if you want to make changes to the configuration register. Answer no when prompted.

5. You must change the configuration register to 0x41, which tells the appliance to ignore its saved (startup) configuration upon boot: rommon #1>confreg 0x41

6. Reset the appliance with the boot command: rommon #2>boot

7. Notice that the security appliance ignores its startup configuration during the boot process. When it finishes booting, you should see a generic User Mode prompt: ciscoasa>

8. Enter the enable command to enter Privileged Mode. When the appliance prompts you for a password, simply press (at this point, the password is blank): ciscoasa>enable Password: ciscoasa#

9. Copy the startup configuration file into the running configuration with the following command: ciscoasa#copy startup-config running-config Destination filename [running-config]?

10. The previously saved configuration is now the active configuration, but since the security appliance is already in Privileged Mode, privileged access is not disabled. Next, in configuration mode, enter the following command to change the Privileged Mode password to a known value (in this case, we’ll use the password system): asa#conf t asa(config)#enable password system

11. While still in Configuration Mode, reset the configuration register to the default of 0x01 to force the security appliance to read its startup configuration on boot: asa(config)#config-register 0x01

12. Use the following commands to view the configuration register setting: asa(config)#exit asa#show version

13. At bottom of the output of the show version command, you should see the following statement: Configuration register is 0x41 (will be 0x1 at next reload)

14. Save the current configuration with the copy run start command to make the above changes persistent: asa#copy run start Source filename [running-config]

15. Reload the security appliance: asa# reload System config has been modified. Save? [Y]es/[N]o:yes

Cryptochecksum: e87f1433 54896e6b 4e21d072 d71a9cbf

2149 bytes copied in 1.480 secs (2149 bytes/sec) Proceed with reload? [confirm]

When your security appliance reloads, you should be able to use your newly reset password to enter privileged mode.

Copyright (c) 2007 Don R. Crawley