Fixing the Hard Drive Controller when Transplanting Old Hard Drive into New Windows PC or Laptop - Fix Stop: 0x0000007B Error

We often have customers who love the way their Windows computer was configured with icons in certain places, a particular background, various free or paid programs installed, customized for them, and it was always painful to tell the customer that when their motherboard died, or they wanted to get a new computer, Windows would have to be re-installed, and all of that would have to be re-configured.

If you were to transplant a hard drive previously installed with Windows from one PC into another PC, with a different motherboard and different hard drive controller, upon boot up you would likely get a BSOD with a 0x0000007B error like this:

We sought out to find a way to transplant a used hard drive from one Windows computer into a brand new or used one, with a different motherboard and hard drive controller, without requiring a re-install of Windows, Applications and backup/recovery of all the data on the drive.

The method detailed below has been performed by us now dozens of times and works very well.  Please let us know if you attempt this procedure and have any questions about the process:

1. First obtain the UBCD4WIN boot CD utility from here: http://www.ubcd4win.com/downloads.htm
2. Follow the steps listed here to create the CD: http://www.ubcd4win.com/howto.htm
3. Install your old hard drive in the new computer.
4. Turn on computer and boot off the CD
5. Boot into the live environment
6. Go to Start > Programs> Registry Tools > FIX_hdc> Fix hard disk controller

















7. Assuming your target Windows install is in C:\WINDOWS, push M on your keyboard.
8. Observe any further prompts and take action if necessary.
9. Reboot and remove the CD from the drive, you should now see your Windows OS booting up!

P.S. Assuming you are transplanting your old HDD into a new computer designed to run Windows 8, there are additional settings you need to change in the BIOS to enable this to work.

Insufficient disk space to continue indexing - Fixed by relocating Index to another drive

One day recently, on my personal Windows 7 Home computer, I began noticing that indexing of my Outlook Exchange box was incomplete.  I know that in those situations, I can go to Indexing Options in Control Panel, then Advanced and click to Rebuild the Index, but a strange problem occurred.  The Indexer showed an error I'd never seen before: "Insufficient disk space to continue indexing. Search results might not be complete".

This was even more strange considering I have a 2TB C drive with 1.8TB free!

I tried rebuilding the index, just to encounter the same error.  I edited the registry to force Windows Search to restart/rebuild itself, but had the same issue.

Finally after troubleshooting for what seemed like hours, I found craigp's thread outlining his success on this post entitled "Indexing "insufficient Disk Space Error"" here (about 4/5 down the page): http://forum.wegotserved.com/index.php?/topic/10310-indexing-insufficient-disk-space-error/

He had moved his Index Location to his D drive and that fixed it.

Not having another physical internal drive to point the Index to, I went ahead and partitioned my C Drive and created a 10GB L:\ Drive (I had a lot of drive letters already in use).  I created a folder called Windows Index in the root of that drive (you should make a folder in your new location for the Index to go).

I then went back to Indexing Options in Control Panel, then Advanced and clicked the Select New button to specify a new Index Location path and pointed it to L:\Windows Index.

The Index proceeded to rebuild, and is now working fine!

Mac OSX Connection Failed Accessing Windows 7 Shares - Memory Allocation Error

We had a customer who wanted an inexpensive way to serve shares to about 10 computers in their office, and we put in a high-end desktop with Windows 7 Pro.  The "Server" worked fine for this purpose for all of the XP and 7 computers in the office, but the owner had an iMac which would consistently connect to the SMB shares and act fine, and then disconnect and not show any computers available on the local network.

We tried everything from going from wireless to wired, to checking sharing access, but nothing would fix it - it was always temporary and the next day we'd get a call that he was disconnected again.  His error would conssitently say "Connection failed: The server 'xyz' may not exist or is unavailable at this time" and look like this:

Finally we came across this article entitled "Windows 7 Nonpaged Pool Srv Error 2017" located here: http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

Essentially, the article states that in certain situations when Linux/Unix-based computers are accessing Windows 7 shares (Macs are Unix based), Windows can run into memory allocation issues.

The author of the post noted in the Windows Event Viewer that there was an Error 2017 reflecting the following:

Source: srv
Event ID: 2017
Level: Error
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

We checked our Windows 7 "Server" and sure enough had tons of this exact error.

The solution below, suggested in that article, worked for our client and they are no longer calling us about this issue:

On the Windows 7 computer, set the following registry key to "1":

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

and set the following registry key to "3":

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

Reboot the Windows 7 sharing computer and the problem should be solved.

Hopefully this works for you!

The Paste Menu is Grey when I Right Click in OWA

I had a customer who was complaining that on his new Windows 7 PC he could no longer right-click in OWA and paste.  He could use CTRL + V, but he didn't want to - he wanted to use his mouse.

I searched high and low online for an answer to this problem and found all kinds of suggestions:

• Don't use IE 9, go to IE 8
• Don't use IE 8, go to IE 7
• Go into Developer Tools and change browser mode to IE 7
• Edit the registry
• Set the OWA site as trusted

None of that worked.

I finally stumbled on a FAQ on a military website that mentioned that you would lose the ability to right-click and paste if you installed the S/MIME control for OWA.

I realized, that was something I had done early on for this user when setting up his PC.  So I then naturally thought "what if I uninstall the S/MIME control - will that fix it?"

I looked it up, and uninstalling the S/MIME control is rather easy.  You open up:

1. Start->
2. Control Panel->
3. Add or Remove Programs (XP) /Programs and Features (Vista/7)
4. Look for the “Microsoft Outlook Web Access S/MIME” entry.
5. Uninstall that puppy!

After uninstalling I went back into OWA (no reboot necessary) and the right-click paste functionality was back!

So folks, that's how you do it.  You're welcome!

Upgrading to Larger Drives in RAID1 Array with Intel RAID controller and Not Losing Data

I had a job yesterday in which I needed to upgrade the two 160GB Hard Drives in a customer's Dell Server, and replace them with 500GB drives.  The server uses an Intel 82801GR/GH SATA RAID Controller and has the Intel Matrix Storage Console software installed.

I removed one of the 160GB drives and let the RAID rebuild itself to the 500GB drive in Windows.  I then rebooted, removed the second 160GB drive, installed the second 500GB drive, and allowed that drive to be rebuilt in Windows.

I quickly discovered that both 500GB drives only showed up in the Server as 160GB, because the RAID volumes were that size.  What to do??

I installed Easeus Partition Master Server Edition thinking that would let me re-size the drive(s), but no - it showed the RAID as having a max of 160GB.

I finally discovered a post online that detailed what to do, and these are the steps that worked:

1. Remove one of the two original, smaller drives and replace it with one of the larger drives.
2. Rebuild original RAID1 array to new, larger drive.
3. Shut Down PC and remove the other, smaller drive (you should only have the one larger hard drive in the computer at this point)
4. Turn computer on and press CTRL+I to enter RAID Configuration
5. Break the RAID on the one larger drive
6. Reboot into Windows and open  Easeus Partition Master Server Edition (or your favorite partition resizing software)
7. Resize drive to use its full capacity
8. Shut down computer and install second larger drive
9. Reboot into Windows and open the Intel Matrix Storage Console software
10. Click Actions --> Create RAID Volume from Existing Hard Drive
11. Select your Windows Volume as the source drive, and your newly installed, second larger drive as the mirror drive
12. The Intel Matrix Storage Console software will begin mirroring your larger drive volume to the second larger drive.

When all is said and done, your new RAID1 Array should be complete, and you should see an array status such as this:

Hope this can help someone.  Cheers!

Deleting the hal.dll file in Windows XP can delete the ACPI Advanced Power Management (APM) functions of your computer

I recently had a customer with a virus infection that resulted in a missing hal.dll file error message when Windows XP Home started.  I booted Windows from the installation CD and went into the recovery console.  I copied the Hal.dll file from the CD to the Windows System 32 directory, as detailed here: http://pcsupport.about.com/od/fixtheproblem/ht/restorehaldll.htm

After I replaced the file, it still wouldn't boot, and I discovered that the boot.ini file had been corrupted/deleted.  As a result I re-entered the recovery console from the Windows XP CD and rebuilt the boot.ini file, as detailed here: http://support.microsoft.com/kb/330184

The computer booted up just fine and we continued to remove the virus files and fix other errors on the computer.

The customer called back to say that when he told the computer to shut down, he was now getting a message that "It is Now Safe to Turn Off Your Computer" and looked like this:



I returned to his house and discovered that as a result of replacing the hal.dll file, the computers Advanced Power Management features were missing, and instead of showing an ACPI PC in Device Manager, it showed a Standard PC:



When I went into Power Options in Control Panel, several ACPI-related options such as Sleep, Hibernate, and the Power Button options were missing.  All the guides I read said that if that happened, you had to completely reinstall Windows XP.

Before I went ahead with that, I discovered some instructions on another blog that detailed how to edit the Registry and then perform a hardware upgrade of the "Standard PC" to an ACPI-compatible PC.  I performed the steps and it fixed the ACPI-related problems.  Here are the steps (which should only be performed if you are SURE your PC is ACPI-compatible):

1. Regedit. Browse to:
   HKLM\System\CurrentControlSet\Enum\Root\PCI_HAL000
2. Right click the 0000 key and choose “Permissions…”.
3. Check the “Full Control” checkbox for “Everyone”. This allows you to edit this next value…
4. Open the “HardwareID” value and change it from “e_isa_up” to “acpipic_up” (followed by one line break, the cursor should be on the line directly under “acpipic_up”).
5. Open Device Manager, open the “Computer” key, right-click “Standard PC”, and select “Update Driver”.
6. You’ll pick from a list, don’t search, answer accordingly.
7. Select the ACPI entry, which will now be shown in the Compatible Hardware list (joy!), thanks to the reg-tweak.
8. Once again, if you actually CONTINUE with this, and your system is NOT originally an ACPI system, it very well may make it unbootable.
9. Select “Next” and let the new HAL install.
10. Reboot, and you’re done! Enjoy your ability to select the multi-processor HAL once again if you were curiously poking around. Since hal.inf locks you into only “compatible” HALs, you can now update again and select Multi-Processor PC if your system supports it, then you’ll have multi-cores again.

These original instructions are located here: http://falconfour.wordpress.com/2011/03/19/how-to-switch-windows-xp-hal-_back_-from-standard-pc-to-acpi-the-clean-way/, and I thank the poster for helping me avoid a complete Windows XP reinstall.

Vonage vs. MagicJack - A Comparative Analysis

I am a IT professional and have my own IT company in Palm Beach Gardens, FL.  I often need to research topics that are not easily found with simple searches on the internet and require me to piece information together to come up with a solution.  My goal with this blog is to share some of the information I've compiled every few days, in hopes that some may find it interesting and others may find it useful.

My first post today will be about some of the basic pros and cons a customer asked me to compile about Vonage and MagicJack.  Neither service is very transparent about their plans, services and pricing, so I hope this information can help someone who is comparing the two services:

	Vonage	MagicJack
Initial Setup Fee:	FREE with 12 mo. Agreement & Month to Month Plans	None, besides equipment purchase. One year of free local and long distance calling to the United States, Canada, Puerto Rico and the US Virgin Islands are included with your initial purchase.
Equipment Costs:	FREE with 12 mo. Agreement & Month to Month Plans	magicJack™ USB Phone Jack = $40 (requires PC connection) magicJack PLUS™ VoIP Phone Adapter = $70 (can be plugged in to PC or used stand-alone)
Able to Port Existing Number:	Yes, FREE	Yes, $19.99 one-time fee and $9.95 annual charge after the first year
Initial Term Required:	12 mo. Agreement or Month to Month Plans (30 day money-back guaranty)	No Term Required
Basic Residential Calling Plan:	$9.99/mo. + tax	One year of free local and long distance calling to the United States, Canada, Puerto Rico and the US Virgin Islands are included with your initial purchase.
Fax Service Supported:	Yes, included at no charge with residential plan	Yes, included at no charge with equipment purchase
International Calling:	$9.99/mo. for 6 months, then $24.99/mo. w/ 12 mo. Agreement.  If month-to-month it’s $9.99/mo. for 3 months, then $24.99/mo. ($0.25 to $0.28/min for international cell calling)	You must prepay for international minutes (Italy, Germany & UK = $0.02/min)
Early Termination Fee:	$120 Termination Fee w/ 12 mo. Agreement (reduces by $10/mo. each month during term)	No Termination Fee