Where did medslides.com go?

We were recently presented the topic of pre-op clearance. The presentation provided several classic teaching points on the topic and I was interested in reviewing items in the reference section in my own time. Unfortunately one of the referenced websites, http://medslides.com, is no longer available on the internet. The Internet Archive last crawled the page in June of 2004. While the collection of slides is both limited and dated, I was still interested in obtaining the files to see how much has changed. It turns out another site has mirrored the collection here. Hopefully this site won’t go down as well.

Pulmonary Tuberculosis

We’ve seen a rise in patients presenting with Tuberculosis recently. I’ve decided to put together a presentation on Tuberculsosis for an informal teaching session. While its not complete, I’ve started it and plan to have it done soon (fingers crossed). As before, an extensive references section will be made available for those wanting to do some research on their own.

Pancreatic Cancer: Advances in Treatment

I presented on the topic of advances in treatment of pancreatic cancer a few weeks ago in a talk that went well over an hour and a half. The aim was to give a very broad overview that touched on all the major points but I purposely left out the molecular pathogenesis (K-ras, EGF family, CDKN2A, P53, DPC4, BRCA, STK11, MLH1, MSH2, Sonic Hedgehog (SHH) signaling pathway, etc) because of time. Those are all very important molecules involved in critical pathways because of the potential for screening, early detection, and possibly (someday) treatment. The PowerPoint presentation below won’t be very useful as a learning resource on its own without my speaking notes. I’ll consider putting those up if I get a chance to clean them up. In the mean time, if academically inclined, the references section (last 3 slides) has a list of excellent papers and resources I consulted to put this together.

How to Get Facebook’s New Layout

Facebook isn’t offering everyone their new layout just yet so this may be worth it to people who are curious. After logging in, click this link:

http://www.new.facebook.com/home.php?fb95_opt_in=1

If you’re lucky you’ll see the new layout. You can always go back to the old layout by clicking the bar on the top right.

Screenshot:

Vista Error: “Logitech LVPrcSrv Module. has stopped working” Fix

Whenever I use remote desktop to connect to a computer running Windows Vista SP1 with a Logitech QuickCam Chat I get an error that reads:

Logitech LVPrcSrv Module. has stopped working

Updating drivers and searching for a fix proved fruitless until Microsoft’s built in solution software came to the rescue. A little pop-up suggested this fix:

Follow these steps to solve the problem with QuickCam (LVPrcSrv.exe)

This problem was caused by QuickCam (LVPrcSrv.exe), which was created by Logitec Corporation.

Solution

One way to help ensure that QuickCam (LVPrcSrv.exe) will run is to set its compatibility mode to Windows XP Service Pack 2 (SP2). To do this:

  1. Close QuickCam (LVPrcSrv.exe).
  2. Click the Start button , click All Programs, and then right-click QuickCam (LVPrcSrv.exe).
  3. Click Properties, and then click the Compatibility tab.
  4. Under Compatibility mode, select the Run this program in compatibility mode for check box, select Windows XP (Service Pack 2), and then click OK. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
    Restart QuickCam (LVPrcSrv.exe).

I’ve applied the fix and it works. No more crashes for now.

Live Messenger Error 2771 After Installing Windows XP Service Pack 3 (SP3)

Subsequent to successfully installing Windows XP Service Pack 3 (SP3), starting Windows Live Messenger (WLM) may pop up an install error. The error reads: “The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2771.”

Error 2771 means there is a missing component. The simplest fix is to let WLM’s installer repair the issue automatically. If, however, the error dialog keeps popping up every time WLM is started then the suggested fix is to uninstall WLM from Add/Remove Programs in the Control Panel and reinstall the package from Microsoft’s website. This should correct the issue.

On a side note, some users out there don’t want Microsoft cluttering the Windows desktop with ads via WLM so they install A-Patch. The moral and ethical dilemma is up to the reader to sort out but Microsoft is providing instant messaging on an ad-supported model. If too many users do this then it could affect everyone’s free access. Choose wisely!

“Bluetooth Device Not Found” After Windows XP Service Pack 3 (SP3) Install

My Dell-branded Bluetooth module disappeared after installing Windows XP Service Pack 3 (SP3). The fix for this solution is pretty simple as long as your device was working prior to installing SP3. The steps are as follows:

  1. Click Start, click Run, type %windir%\inf in the Open box, and then click OK.
  2. Find a set of eight files beginning with “BTH.INF”.
  3. Move following files to a temporary folder:
    • bth.inf, bth.pnf
    • bthpan.inf, bthpan.pnf
    • bthprint.inf, bthprint.pnf
    • bthspp.inf, bthspp.pnf
  4. Click Start, click Run, type devmgmt.msc in the Open box, and then click OK.
  5. Expand the list under Bluetooth Radio by clicking the “plus” sign.
  6. Right-click “Microsoft Bluetooth Enumerator” and click uninstall. Click OK on the next dialog box.
  7. Right-click “Generic Bluetooth Radio” (it may read “Dell TrueMobile Bluetooth Module” or something similar) and click “Update Driver…”
  8. If a dialog box comes up asking “Can Windows connect to Windows Update to search for software?” click “No, not this time”, and then click NEXT.
  9. On the next screen pick “Install from a list or specific location (Advanced)” and click NEXT.
  10. Click “Search for the best driver in these locations.” and put a check-mark on “Include this location in the search:”. Then click BROWSE.
  11. Find the location where the Dell WIDCOMM drivers were installed. On my system this is “C:\Program Files\WIDCOMM\Bluetooth Software\bin”. Click NEXT.
  12. Windows will now install the drivers.
  13. Restart your system if necessary.

Follow these instructions at your own risk! Make sure you backup your computer before attempting this procedure. I can’t be held responsible if you screw up your computer.

Windows Updaters: Where Is the Unified API?

In the last couple of years nearly every program comes with its own updating software. Don’t believe me? Try Apple Software Update, Adobe Updater, Google Updater, Mcafee AutoUpdate, and the list goes on. All of these pieces of software have their individualized settings and behaviors with no unified interface which leads to confusion and missed updates–some of which are critical for security.

Several attempts have been made to consolidate this process with the ultimate goal of simplicity for the end-user. Examples include CNet’s defunct CatchUp, VersionTracker, Secunia PSI, and FileHippo.com Update Checker. The one underlying theme is none of these systems catch everything on their own and most of them fail to detect some software altogether.

I wonder why Microsoft hasn’t addressed this issue especially since they’ve claimed pursuing a security-centric approach with the Windows platform. Microsoft should provide a framework for a System Update Center for third party applications and encourage its usage through its development tools. A robust API will give software developers the ability to tailor the system for their applications while allowing end-users to be free of the particulars. How great would it be just to push a button and have all the needed updates install in the background without any further intervention? Gone will be the days of multiple updaters runnings in the background chewing up resources.

Windows XP SP3 Leaked onto Bittorrent and Usenet

UPDATE (5.6.2008): Microsoft has updated the TechNet article detailing official download locations. If you are updating more than one computer then you can download the full 300+ meg version here. Otherwise, for single computers go through Windows Update.

As expected Microsoft’s upcoming Windows XP Service Pack 3 (SP3) has been leaked onto Bittorrent and Usenet ahead of the official release to the general public.

The official filename is: WindowsXP-KB936929-SP3-x86-ENU.exe. (MD5 Hash: BB25707C919DD835A9D9706B5725AF58)

SP3 doesn’t offer many new features. Of the new features it does offer, the backported items from Windows Vista leave me a bit concerned about security application compatibility. These should all be discovered and addressed between now and June 10 (the official release date of SP3 on Windows Update) as I’m expecting to see a surge of SP3-related posts in all of the usual technical help forums. This makes the job of us close enough to the bleeding edge to live vicariously though early adopters without getting burned. I’m not saying don’t update, but I’m suggesting that we wait until the official release so the computer whizzes and troubleshooters of the world have a stab at SP3 and any of its unknown problems.

As expected, there are early reports of endless reboot loops in botched SP3 upgrades due to an error in GDI32.DLL. If you do go the route of upgrading via leaked copies then be sure to backup your system using Acronis TrueImage or Norton Ghost. Also make sure you’ve review the legality of using leaked software in your jurisdiction.

Corsair Flash Voyager: Lifetime Warranty

During the last few years we’ve seen price competition in the electronic gadget arena become so fierce that the bottom line often times trumps customer service. That is why I’m so excited and surprised by the package that came in the mail today. Let me explain…

In December 2006 a European friend of mine asked me to bring him back the bigger USB flash drive money could buy in the good ole USA. At the time, the 8gig Corsair Flash Voyager USB drive was the beast that best met his storage requirements. He used it for about 9 long months before the drive fell apart due to excessive wear-and-tear. (The fact that is lasted 9 months in his possession is a feat in and of itself but that’s not the point.) The drive was only showing 4 gigs of usable space and would cause the USB subsystem to become extremely unstable on any Windows machine after it was plugged in.

On yet another hiatus back to California, he gave me the drive hoping there would be some way to get it warrantied. My personal assessment of the device was rather bleak but I took it back with me anyway. After several months of procrastinating and delays I asked for an RMA form on Corsair’s website. At first they asked me to do a low-level format but that failed. The next email was a link to a shipping label and instructions on how to send it in. Corsair did a wonderful job of keeping me up-to-date with the progress of the RMA through automated email alerts. After two weeks, I have a brand new USB drive sealed in a plastic display case.

I’m speechless. They not only honored the warranty but sent a brand new drive! This sort of customer service is worth the little extra cost. As a result of this experience I’ll be sure to heavily favor purchasing other Corsair products for myself and give recommendations to friends/family for their headache-free approach to customers.

Note: I wasn’t paid at all for this entry nor did Corsair know I have a personal blog. Googling the drive shows others who have had similar experiences. Corsair is the real deal.

Next Page →