Upgrading template today

Today, RChase Computer Consulting is under going an upgrade. Things make look funny throughout the day......hopefully, if all goes well, the new template will be in place by tomorrow morning. Stay tuned for future posts relating to Windows XP, Windows Vista and computer troubleshooting.....

Print jobs Backwards After SP3 Installed

Today, I came across a client that had some print jobs that were printing out backwards. Never having seen this before, I had to make sure she was telling the truth so I printed a test page from her HP Officejet printer at her desk. Sure enough, the test page printed out backwards. I had no idea why this happened. The only thing that was different in the past few days was that we (meaning the IT dept) did a mass install through WSUS of Windows XP SP3. Apparently, SP3 was the culprit although I am not sure why but here is what happened:

On the print preferences tab of the print queue, there was an option called "mirror image". Somehow, it much have been turned on which causes print jobs to come out backwards. I turned the feature off and printed another test page with no issues. This did not seem to affect network printers, just her local desktop printer.

To give proper credit, I found the solution here: Microsoft Technet

Apparently, this may only be happening if its an HP Officejet printer. Has this happened to you? Do you know why SP3 may have caused this change? Let me know.

HP Officejet Installation issues again

A few months ago, I wrote about having some installation issues with an HP Officejet 7680. Well, I might as well go on record to say that these installation issues occur with most HP Officejet models. I attempted to install an Officejet 6310 today and the same HP installation issues occurred.

At about 25 minutes into the 6310 install, the installer got stuck at 96% and stayed there for another 20 minutes or so before I gave up. This should not be the case. So I decided to unplug the USB cable, and suddenly, the installation finished!. But I was very suspicious so I opened the HP Solution Center and of course, I get the following message:

No HP devices detected. HP solutions Center will close now.

(So basically, the 6310 installation is now corrupt.)

Here is what did to fix the installation issues for the Officejet 6310, you can try it for the Officejet 7680 too, but good luck!

1) Remove all HP software from add remove programs.(in both cases, the client had older printers & scanners installed previously).

2) End any remaining HP****.exe tasks running in task manager.

3) Delete all HP and Hewlett Packard folders located in these areas:
c:\program files\hp
c:\program files\hewlett packard
c:\program files\common files\hp (or hewlett packard or both)

4) Delete all HP & Hewlett Packard registry entries found (do at your own risk).

5) Download latest full software package from HP.com for the correct model Officejet device.

6) Reboot PC and then install HP Officejet 6310 again using the file you just downloaded and not
the install CD.

I can not guarantee this will work for you, but nothing else I found online worked.

Did you have success? Let me know.

error 53 not enough storage

Computer troubleshooting usually involves time and patience when you get such errors as in the title of this article. Yesterday, on a PC with Windows XP SP3, a client received the following error while working in a Sharepoint website:

Error 53, not enough storage to complete the command.

While troubleshooting this error across multiple IT forums, I found the following suggestions that did NOT work:

1) Problem is due to not enough RAM (not true, PC has 2GB of RAM which rarely goes past 1GB during daily use)

2) Move the paging file to another hard drive. (Did not try this because it sounds stupid for the above error message)

3) Try upgrading Internet Explorer to IE7 or IE8. (I did this, but it did not solve the issue.

4) The last thing recommended was to remove .NET Framework 3.5 SP1 which also did not help.

I said all of the above to help the next person having the same error 53 message....I am 99% certain that the ONLY issue is that the person's Windows profile became corrupt. Usually, when this happens, you can not un-corrupt the profile.

To fix it, create a new profile and move the data back from the old to the new profile.

That's it, simple as that. I came across this solution because I decided to logon to the PC myself and I tried exactly what the client was doing at the time and I did not get the error 53 message. I then renamed his windows profile and had him logon like he was a new user and just like that, the error was gone.

Moral of the story....when weird stuff happens like this, just try making a new Windows profile first or logon to the PC as another user to see if the same errors still happen with that profile. If they do, then something else is wrong, but if not, its safe to say the Windows profile became corrupt.
Has something like this happened to you recently?

Windows 7: Build 7048 is here

Windows 7, build 7048, which incorporates many noticeable changes since the previous versions especially when compared to the public beta build 7000 has already been leaked online. I honestly think Microsoft "lets" this happen on purpose so they can get beta testers trying it out faster.

Build 7048 was said by some sources to be the Release Candidate build, which is currently scheduled for sometime in April. So we could possibly be seeing the Release Candidate for Windows 7 if you can get your hands on one but you will have to get it from one of the popular torrents.

Perhaps the most notable change of all is the ability to uninstall and exclude Windows staples such as Windows Media Player, Windows Media Center, Windows DVD Maker, Windows Search, Handwriting Recognition, Windows Gadget Platform, Fax and Scan, XPS Viewer, and yes, Internet Explorer 8. Without Internet Explorer 8 installed, users will have to install some other browser for any hopes of accessing the World Wide Web.

Even so, build 7048 looks to be as close to a Release Candidate as Microsoft can get. Any more changes and they'll have to change the name again. What are your thoughts about this release?

WhoCrashed tool diagnoses BSOD

During a recent Blue Screen of Death, (a.k.a BSOD), I was doing some research in Google when I came across a repair tool called WhoCrashed. When a system crashes, it leaves behind something called a “crash dump” usually in the form of a BSOD, (which means Blue Screen of Death). This crash dump contains information about what happened and in order to read it on a system you need to download and install Microsoft's debugging tools, its dependencies called “symbols” and run some commands. WhoCrashed is designed to read the crash dump files with a single click. Just open it, press “Analyze” and it will tell you what driver/hardware caused the BSOD.While it wont tell you exactly what happened, it lists a hardware error message or a driver file that failed which you can Google and find the cause of the BSOD.








Download from Official Site -716kb

More information: Resplendence.com

Unable to burn ISO image to DVD

In the past, I've used Roxio (now Sonic) Easy CD Creator to burn CDs/DVDs for audio and data. But yesterday, I needed to burn an ISO image of the new Windows 7 beta to a DVD. Every time I tried with Easy CD Creator, it would tell me to insert a blank DVD even though it was blank! I tried 3 different brands of DVDs which were all new and never used. Apparently, some CD/DVD burning applications are not too user friendly depending on what you are trying to do.

So, I found a trial version of an independent ISO burner called ImTOO ISO Burner. I was able to burn the ISO on the 1st try with no issue. It recognized the same DVD that I was trying with the Roxio application.

I'm sure there are other independent ISO burners out there but ImTOO ISO burner did the trick. You can download it here:
ImTOO ISO burner
 
Computer Blogs - Blog Catalog Blog Directory My Zimbio Privacy Policy