BESX Installation Walkthrough

For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.

The main benefit of using BlueScreenView over other minidump reading applications is that it does not require the Microsoft debugging tools (which are 16 – 225mb in itself) which makes this application small, quick and portable. This tool is definitely worth having in your kit to track down the cause of BSOD’s.

Check out their official website here:

http://www.nirsoft.net/utils/blue_screen_view.html

1. Remove the printer from Print Manager

2. Delete the printer Drivers located in %windir%\system32\spool\drivers\w32×86\2 and/or \0 and/or \1

3. Edit the registry and delete the driver references at:

Hkey_Local_Machine\System\CurrentControlSet\Control\Print\Environments\WIndows NT x86\Drivers\Version-1     for NT 3.51
Hkey_Local_Machine\System\CurrentControlSet\Control\Print\Environments\WIndows NT x86\Drivers\Version-2     for NT 4.0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\

For a Network printer, edit:
HKEY_CURRENT_USER\Printers\Connections\<Server Name>

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers\<Server Name>\Printers\

4. Restart the computer

Microsoft has released hot fix KB943337 that should resolves the problem for most users with webfolders (also known as webdav) and PDFs. You must request this hot fix as it is not part of their automatic update process.

http://support.microsoft.com/kb/943337

Sources:

http://mydocsonline.blogspot.com/2008/10/problems-opening-pdf-files-using-web.html

Adobe forum

Ahhh, nothing like reinstalling an older pc and not knowing what exactly some of the hardware is.  Once in a blue moon these utilities can become handy to fix the dreaded:

Here’s a couple utilities that help detect what the “Unknown Device” in the device manager is

http://www.halfdone.org/ukd/

http://www.zhangduo.com/udi.html

I personally have used the first one, and it doesn’t’ require an install, so it’s great for portable / usb drives.

After searching around online, I found out via some forums that some people were having similar problems.  Here was the fix to remove the KB and to get the computers back up.

1. Boot from your Windows XP CD or DVD and start the recovery console (see this Microsoft article for help with this step)

2. Type this command: CHDIR $NtUninstallKB971486$\spuninst

3. Type this command: BATCH spuninst.txt

4. Type this command: exit

The computer should restart and hopefully your problem will be fixed. Again, go to the Add/Remove Programs control panel and properly uninstall KB971486.

Here is more info on this specific update:   http://support.microsoft.com/kb/971486

The comcast installer didn’t recognize it was 64 bit so after the software installed and I inserted the zte tu25 usb modem, it would get an error saying the drivers were not successfully installed.

The reason why was because the comcast software installer wasn’t detecting my laptop was x64 so it was only installing the x86 drivers.

What I had to do is use 7-zip to open the setup.exe file as an archive, browse into where the driver files were at and install them manually.    Here was the location I used:

Setup.exe\CommonAppData\Comcast\Connection Manager\drivers\wimax\Vista\64Bit\Beceem\Beceem 5.2.4.4\

It actually installs the device as a network adapter named "Beceem Communications Inc. Tarang3"

Hope this helps someone else who may be having trouble installing Comcast 2go / WiMAX on a Windows 7 pc.

Update on Sunday, August 9, 2009 at 11:18PM by Philip Fuesser

Yikes, After installing the RTM version of Windows 7, I’m unable to get this to work!

My above post was done on the RC version of Windows 7.  I assumed that this should have worked with the RTM’d version as well, but apparently not!

I’ll keep you posted on any additional fixes or workarounds I find in order to get this resolved.   I would appreciate any feedback as well. 

Update on Monday, August 10, 2009 at 1:44AM by Philip Fuesser

I tried Windows 7 RTM x86 instead of x64, and I was able to sucessfully install the drivers.    So it may just be an issue with the x64 drivers.

I’m going to try one last thing with x64 install and see if it works.   I’ll post an update with my results.

Update on Monday, August 10, 2009 at 2:54AM by Philip Fuesser

Finally!   I was able to get the drivers to successfully load in Windows 7 RTM x64.   The problem was due to some of the files in the 64bit driver folder being shortcuts and not real files.   Two important files had ".ale" extensions, and if you opened the files in notepad, it was just a redirect to another folder.

What I ended up doing was copying the files out of the folder the redirect was going to (CommonAppData\Comcast\Connection Manager\drivers\wimax\xp\32Bit\Beceem\Beceem 5.2.4.4) and put them in the 64bit driver folder.

Here’s the incorrect files:

Here’s the correct files:

I hope this helps someone successfully get the Clear / Comcast USB WiMAX modem installed!