<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-19107289</id><updated>2024-09-05T03:25:46.893-07:00</updated><title type='text'>Zims Tech Tips</title><subtitle type='html'>This blog is a collection of tech-tips that I have used in over the years. They range from computer hardware to cell phones - it&#39;s all about tech-hacking-fun. &#xa;&#xa;ZimZum</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>12</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-19107289.post-5928262686626137304</id><published>2010-07-04T17:39:00.000-07:00</published><updated>2010-07-04T17:54:39.058-07:00</updated><title type='text'>DD-WRT Wireless Router Won&#39;t Respond</title><content type='html'>I have a Linksys WRT54G V8 wireless router that I installed &quot;&lt;b&gt;DD-WRT v24-sp2 (10/10/09) micro&quot;. &lt;/b&gt;This router is pretty limited in the memory department (only 8MB) which means even running the micro release can cause issues: slow network performance, unable to connect to the web interface, losing wireless connectivity and complete loss of network activity from the device. The only quick solution is to reboot the unit by pulling the power for 10 secs. So here are my tips on how to keep the WRT54G V8 running like a champ:&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Set the max connections to 512 (You can find this under Administration&gt;Management menu)&lt;/li&gt;&lt;li&gt;Set the TCP/UDP timeout settings to 120 (found in the same menu)&lt;/li&gt;&lt;li&gt;Schedule the router to reboot nightly (Administration&gt;Keep Alive menu)&lt;/li&gt;&lt;li&gt; - Ensure that you setup the Time Settings found at the bottom of the Setup&gt;Basic Setup page&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Disable DNSMasq for DNS (Setup&gt;Basic Setup menu)&lt;/li&gt;&lt;li&gt;Disable all services except for DNSMasq (Services&gt;Services menu)&lt;/li&gt;&lt;li&gt;Disable UPnP (NAT/QoS&gt;UPnP menu)&lt;/li&gt;&lt;li&gt;Disable QoS (NAT/QoS&gt;QoS menu)&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;With these settings, you should have a rock solid wireless router that keeps running 24/7.&lt;br /&gt;&lt;br /&gt;Issues to be aware of: This setup will limit the number of connections that your network can handle. That means apps like P2P and online gaming may run into some issues. I would not suggest using this router to support more than 10 systems at once.</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/5928262686626137304/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/5928262686626137304' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/5928262686626137304'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/5928262686626137304'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2010/07/dd-wrt-wireless-router-wont-respond.html' title='DD-WRT Wireless Router Won&#39;t Respond'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-3048353827391349596</id><published>2009-03-01T13:18:00.000-08:00</published><updated>2010-07-04T17:56:52.832-07:00</updated><title type='text'>Wireless speed low with full signal strength</title><content type='html'>I have a Buffalo WHR-HP-G54, running DD-WRT firmware (DD-WRT v24-sp1 (07/26/08) std - build 9994) and noticed that my Dell Latitude e6400 had a low wireless speed, even with a strong signal strength. I would connect to my wireless network at 54mbps, and it would fall down to 36mbps, 10mbps and finally 1mbps. After some checking around, I was able to determine the settings that needed changing to fix the issue.&lt;br /&gt;&lt;br /&gt;In the Wireless&gt;Advanced Settings tab&lt;br /&gt;&lt;br /&gt;TX Antenna: Left&lt;br /&gt;RX Antenna: Left&lt;br /&gt;Sensitivity Range (ACK Timing) : 0&lt;br /&gt;&lt;br /&gt;After that, reboot the router and everything should be working fine. I now stay connected at 54mbps with my laptop.&lt;br /&gt;&lt;br /&gt;The Dell has an Intel WiFi Link 5100 AGN card installed.</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/3048353827391349596/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/3048353827391349596' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/3048353827391349596'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/3048353827391349596'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2009/03/wireless-speed-low-with-full-signal.html' title='Wireless speed low with full signal strength'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-3759883108309705082</id><published>2009-03-01T13:16:00.000-08:00</published><updated>2009-03-01T13:18:27.081-08:00</updated><title type='text'>File synchronization</title><content type='html'>If you are looking for a fast and efficient to sync files between multiple machines, check out &lt;a href=&quot;http://www.getdropbox.com&quot;&gt;Dropbox&lt;/a&gt; . This service allows multiple users/machines to sync folders seemlessly (i.e. all done automatically in the background). It even uses the users file system, so you don&#39;t need to have change the way you load/save files.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span class=&quot;blsp-spelling-corrected&quot; id=&quot;SPELLING_ERROR_0&quot;&gt;&lt;/span&gt;</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/3759883108309705082/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/3759883108309705082' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/3759883108309705082'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/3759883108309705082'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2009/03/file-synchronization.html' title='File synchronization'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-4661086647558001373</id><published>2007-08-24T12:17:00.001-07:00</published><updated>2007-08-24T12:26:16.149-07:00</updated><title type='text'>Dual Core CPU issues</title><content type='html'>I upgraded my system to an Intel &lt;a href=&quot;http://www.intel.com/products/processor_number/chart/core2duo.htm&quot;&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;CoreDuo E6400&lt;/span&gt;&lt;/a&gt; which is essentially two CPUs in one. Installed the CPU onto a new motherboard (Asus P5LD2) with 2GB of RAM and did a fresh install of Windows XP SP2. After the install, I did the full set of updates from Windows Update, which in theory would take care of all issues related to my system. I found later that what is needed is a&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://support.microsoft.com/default.aspx?scid=kb;en-us;896256&quot;&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;896256&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Read more from the Microsoft article.</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/4661086647558001373/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/4661086647558001373' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/4661086647558001373'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/4661086647558001373'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2007/08/dual-core-cpu-issues.html' title='Dual Core CPU issues'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-116209193780186231</id><published>2006-10-28T20:08:00.000-07:00</published><updated>2007-03-17T09:18:58.446-07:00</updated><title type='text'>Wireless connection times out</title><content type='html'>I have two laptops at home, both with wireless cards that I use to connect to my router. It&#39;s a Siemens SpeedStream 6520 DSL Router w/ 4 ethernet ports and a 802.1G wireless access point built in. Once setup, the laptops would either loose the connection to the router, or the connection would time out (i.e. no traffic would go across the link and web pages would time out) every 3-4 minutes. After the 10th time, I had to find a solution. I was not surpised to find out that many other people had the same type of issue with this router (among other issues), but had a difficult time finding a solution.&lt;br /&gt;&lt;br /&gt;After many attempts, I believe I have found a solution that holds up.&lt;br /&gt;&lt;br /&gt;[Solution]&lt;br /&gt;&lt;br /&gt;First off, you need to update the Router&#39;s firmware (for instrustions on this, refer to the manual). There is an auto-update feature within the web management interface. Secondly, update the drivers for your laptop&#39;s wireless adapters. This made a big difference with the overall stability of the connection. And finally, set the router to use &#39;Channel 2&#39; instead of 10 or 11. This seems to operate on a frequency that is less prone to interference (at least it seems to be making a difference with this router).&lt;br /&gt;&lt;br /&gt;[UPDATE]&lt;br /&gt;&lt;br /&gt;Another issue with having your wireless connection drop out at random intervals is when your wirless router is configured to not broadcast it&#39;s SSID. I had set mine this way to avoid having others try to connect to my router, but then discovered that this setting was causing my laptop to drop it&#39;s connection to the router. By enabling the broadcast SSID, this resolved the issue and I have not had a dropped connection since.&lt;br /&gt;&lt;br /&gt;[References]&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://www.squack.net/SpeedStream6500.pdf&quot;&gt;Siemens 6520 Router Manual &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://whirlpool.net.au/forum-replies-archive.cfm/317072.html&quot;&gt;Broadband Help Forum&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/116209193780186231/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/116209193780186231' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/116209193780186231'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/116209193780186231'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2006/10/wireless-connection-times-out.html' title='Wireless connection times out'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-116206683829535674</id><published>2006-10-28T13:08:00.000-07:00</published><updated>2006-10-28T13:20:38.306-07:00</updated><title type='text'>Western Digital Second Generation Serial ATA hard drive not showing up at boot</title><content type='html'>I recentlty purchased a Western Digital 320GB SATA-2 harddrive, installed the drive to my second on-board ATA connector and to my suprise, the drive was not detected on boot. I currently have an Asus A7V880 Motherboard, which uses a  VIA serial ATA controller. After some quick searching, I found the following on WD&#39;s support site:&lt;br /&gt;&lt;br /&gt;Our Second Generation Serial ATA hard drives use autospeed negotiation. This enables our Second Generation Serial ATA hard drives to automatically detect the motherboard data transfer rate, making it backward compatible with First Generation Serial ATA data transfer rates. However, because this technology is so new, some older First Generation Serial ATA controllers are unable to support autospeed negotiation and cannot recognize the drive. This “drive not detected” condition occurs when a chipset is incapable of correctly negotiating the data transfer speed with a Second Generation Serial ATA hard drive.&lt;br /&gt;&lt;br /&gt;[Resolution]&lt;br /&gt;&lt;br /&gt;You need to set a jumped on the back of the drive. From the WD support site:&lt;br /&gt;&lt;br /&gt;To lock the drive at 150 MB/s data transfer rate, install a &lt;span style=&quot;font-weight: bold;&quot;&gt;jumper&lt;/span&gt; shunt on pins &lt;b&gt;OPT1&lt;/b&gt;, shown in the picture below.&lt;br /&gt;&lt;br /&gt;&lt;a onblur=&quot;try {parent.deselectBloggerImageGracefully();} catch(e) {}&quot; href=&quot;http://photos1.blogger.com/blogger/2205/197/1600/sataopt1on.gif&quot;&gt;&lt;img style=&quot;margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;&quot; src=&quot;http://photos1.blogger.com/blogger/2205/197/320/sataopt1on.png&quot; alt=&quot;&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;br /&gt;[References]&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1337&amp;p_created=1112379341&amp;amp;p_sid=U6HYhF2i&amp;p_lva=&amp;amp;%20p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NDEmcF9wcm9kcz0yMDM%20mcF9jYXRzPTAmcF9wdj0xLjIwMyZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2VhcmNoX2ZubCZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PWp1bXBlciBzZXR0aW5ncw**&amp;p_li=&amp;amp;p_topview=1&quot;&gt;WD Support site&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/116206683829535674/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/116206683829535674' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/116206683829535674'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/116206683829535674'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2006/10/western-digital-second-generation.html' title='Western Digital Second Generation Serial ATA hard drive not showing up at boot'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-115292682967804317</id><published>2006-07-14T18:25:00.000-07:00</published><updated>2006-07-15T09:58:42.156-07:00</updated><title type='text'>iPod keeps rebooting</title><content type='html'>I have a 10GB 2nd generation iPod, and after a good 3 years of constant use, one day it started to reboot in loop, never making it past the Apple logo. After a few hours of searching, I was able to locate the proper diagnostic keys to fix the issue:&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;;font-family:Arial,Helvetica;font-size:85%;&quot;  &gt;1st, 2nd, and 3rd Generations&lt;br /&gt;Reboot iPod: Hold down the menu and play buttons.&lt;br /&gt;Disk Mode: Hold down the rewind and fast forward buttons after a reboot.&lt;br /&gt;Diagnostic Mode: Hold Rewind, Fast Forward, and Select buttons after a reboot.&lt;br /&gt;&lt;br /&gt;Mini, 4th, and Photo Generations&lt;br /&gt;Reboot iPod: Hold down the menu and select buttons.&lt;br /&gt;Disk Mode: Hold down the select and play buttons after a reboot.&lt;br /&gt;Diagnostic Mode: Hold Rewind and Select buttons after a reboot.&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;After I got it into Diagnostic mode, I put it into &#39;USB Disk&#39; mode in hopes that I could run the Apple iPod Updater software and restore it. After a few attempts, the Updater would run, and then give the error message &quot;Can&#39;t unmount iPod&quot;. This was due to the fact that the 2nd generation of iPod&#39;s were not powered by USB. The solution? I had to connect the iPod via FireWire to my system, set it into Disk Mode and then run the Updater. After this, the Updater worked correctly and I was able to fix the rebooting loop.&lt;br /&gt;&lt;br /&gt;[References]&lt;br /&gt;&lt;br /&gt;iPod Lounge : &lt;a href=&quot;http://www.ilounge.com/index.php/faqs/&quot;&gt;http://www.ilounge.com/index.php/faqs/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;;font-family:Arial,Helvetica;font-size:85%;&quot;  &gt;&lt;br /&gt;&lt;/span&gt;</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/115292682967804317/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/115292682967804317' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/115292682967804317'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/115292682967804317'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2006/07/ipod-keeps-rebooting.html' title='iPod keeps rebooting'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-114029583845971253</id><published>2006-02-18T12:35:00.000-08:00</published><updated>2006-03-04T17:47:10.343-08:00</updated><title type='text'>Spooler Sub system App issue</title><content type='html'>This was a weird one - on an WinXP system with an HP Laserjet USB printer, an error message started to pop-up constantly, with the following message:&lt;br /&gt;&lt;br /&gt;Spooler Sub System App has encountered a problem and needs to close&lt;br /&gt;Error signature&lt;br /&gt;SZ AppName:Spoolsv.exe&lt;br /&gt;SZ AppVer:5.1.2600.2696&lt;br /&gt;SZ Mod Name: SD1MF32.DLL&lt;br /&gt;SZ Mod Ver: 5.60.2209.0&lt;br /&gt;offset:00004537&lt;br /&gt;&lt;br /&gt;Quite annoyning - So, I went searching for a fix. Found one!&lt;br /&gt;&lt;br /&gt;[Solution]&lt;br /&gt;&lt;br /&gt;You need to remove all printers on your system. Un-install the printers on your system, then to clean any left overs.&lt;br /&gt;&lt;br /&gt;Remove all files in the directory:&lt;br /&gt;&lt;br /&gt;C:\WINDOWS\system32\spool\PRINTERS&lt;br /&gt;&lt;br /&gt;Run regedit and remove all entries under this tree:&lt;br /&gt;&lt;br /&gt;HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers&lt;br /&gt;Then, you simply re-install your printer drivers and all issues should be resolved.</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/114029583845971253/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/114029583845971253' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/114029583845971253'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/114029583845971253'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2006/02/spooler-sub-system-app-issue.html' title='Spooler Sub system App issue'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-113854994485710010</id><published>2006-01-29T07:34:00.000-08:00</published><updated>2006-01-29T07:52:24.896-08:00</updated><title type='text'>Bluetooth - On your laptop, handheld and beyond</title><content type='html'>&lt;p class=&quot;MsoNormal&quot;&gt;For those of you who are starting to get into Bluetooth devices, say a new Bluetooth (BT) mouse or handheld PocketPC, you may quickly discover some of the short comings of these devices. Some of the issues you may encounter are inability to connect to the device, poor connectivity, and overall poor performance. I currently use a Dell Precision M60, IOGear Cordless BT Mouse, Sony Ericsson T637 and a Dell Axim v50 PocketPC - all of which rely on BT to communicate wirelessly.  With a default setup, out of the box type of approach, connecting these devices was a touchy situation - if the device is able to be discovered, I would encounter poor performance/connectivity and typically not be able to re-connect the device in the future.&lt;br /&gt;&lt;br /&gt;[Solution]&lt;br /&gt;&lt;br /&gt;This solution isn&#39;t much of a &#39;magical fix&#39; but more of a best practice. I&#39;ll go through each device:&lt;br /&gt;&lt;br /&gt;Dell Precision M60 Laptop: With the Dell laptop, by default, you are using the Windows XP BT drivers (read: BT stack) and there in is the problem. The first thing I would suggest is to update the drivers via Dell&#39;s support site - in my case it was the Dell TrueMobile drivers. After installation there was a huge jump the connection quality and overall connectivity with my BT devices. I also disabled the power saving options for this device, so that Windows was unable to shut down the device, as I had problems with the BT device not coming back after I shut my laptop (putting it into standby mode)&lt;br /&gt;&lt;br /&gt;IOGear BT Mouse: Simple - fresh batteries all the time. This little guy just needs juice - if you are getting poor performance, change (or recharge) the batteries&lt;br /&gt;&lt;br /&gt;Sony Ericsson T637: This one was a bit more intensive and required that I update the firmware for the phone (which requires special hardware, called a Terminator). Check back later for a step by step on this.&lt;br /&gt;&lt;br /&gt;Dell Axim v50 PocketPC: Again, by default, the drivers that ship with the Axim are less than satisfactory. You need to first update your devices ROM (I went from A01 to A09 - available from Dell&#39;s support site) which made a huge difference across the board. The next step is to install the necessary 3rd party BT drivers/stack for peripherals (such as a keyboard).&lt;br /&gt;&lt;br /&gt;[Review]&lt;br /&gt;&lt;br /&gt;To say that BT is a robust technology would be a stretch, but at least it&#39;s possible (with the right updated drivers) to get good use out of your BT devices. &lt;br /&gt; &lt;!--[if !supportLineBreakNewLine]--&gt;&lt;br /&gt; &lt;!--[endif]--&gt;&lt;/p&gt;</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/113854994485710010/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/113854994485710010' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/113854994485710010'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/113854994485710010'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2006/01/bluetooth-on-your-laptop-handheld-and.html' title='Bluetooth - On your laptop, handheld and beyond'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-113249615701270161</id><published>2005-11-20T05:59:00.000-08:00</published><updated>2005-11-20T06:16:47.313-08:00</updated><title type='text'>WiFi connection keeps disconnecting</title><content type='html'>I used to have a hell of a time with my WiFi wireless connection. I had a Linksys PCMCIA wireless adapter (802.11b) and a Linksys wireless router (802.11b). I installed the wireless card in my laptop, followed the setup instructions and was able to connect to the wireless router for just short periods of time. My connection would continously be reset or disconnected, forcing me to reconnect about every 5 mintues. This of course, drove me crazy...&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-weight: bold;&quot;&gt;[Solution]&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Check the properties of your wireless adapter - specifically the connection settings that allow you to define a wireless network. [&lt;span style=&quot;font-style: italic;&quot;&gt;Note: I was on WinXP SP1 at the time, but this should be relevant for SP2 as well&lt;/span&gt;] There is a tab called authentication and you need to disable IEEE 802.1x authentication [&lt;span style=&quot;font-style: italic;&quot;&gt;I disabled all three options on this tab&lt;/span&gt;] [&lt;span style=&quot;font-style: italic;&quot;&gt;Note: this is not the same tab that has your WEP settings. I would suggest starting with NO security, test the connection and then move to some security like WPA&lt;/span&gt;] .&lt;br /&gt;&lt;br /&gt;The next thing I found made a HUGE difference was to deny Windows the management of the wireless device [&lt;span style=&quot;font-style: italic;&quot;&gt;It&#39;s a check box called &#39;Use Windows to configure my wireless network settings&#39; - turn this off &lt;/span&gt;]. I found that the Linksys utility did a much better job at this then windows - which stayed true when I got a new Dell Precision laptop and used the Dell utility to control my wireless settings as well.</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/113249615701270161/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/113249615701270161' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/113249615701270161'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/113249615701270161'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2005/11/wifi-connection-keeps-disconnecting.html' title='WiFi connection keeps disconnecting'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-113235265461736028</id><published>2005-11-18T14:18:00.000-08:00</published><updated>2005-11-18T14:24:14.620-08:00</updated><title type='text'>IBM Deskstar Hard Drive &#39;Click&#39; failure</title><content type='html'>If your Deskstar drive is doing a click-click-pause, you can get your data back!&lt;br /&gt;&lt;br /&gt;I have 2 IBM Deskstar 60GB drives, about 1.5 years old. A month ago, I was backing up data from one of them, and it froze. I rebooted, and WinXP took 10mins too boot, and the drive in question never showed up. So I ripped the case off, and to my gut renching surpise, the drive was giving me the [&lt;span style=&quot;font-weight: bold;&quot;&gt;click of death&lt;/span&gt;] . So I spent the next few weeks trying to find a solution, as I am not going to RMA a drive with all my data on it. I *NEED* that data. So after trying just about every method I could find, I finally found a combination that worked.&lt;br /&gt;&lt;br /&gt;[&lt;span style=&quot;font-weight: bold;&quot;&gt;Solution&lt;/span&gt;]&lt;br /&gt;&lt;br /&gt;Things to note:&lt;br /&gt;&lt;br /&gt;- Freezing the drive had no effect, but try to keep the drive cool throughout the restore process. I had a fan blowing over the drive in question constantly&lt;br /&gt;&lt;br /&gt;- Putting the drive in different positions (i.e. on it&#39;s side, end, etc) had no effect. Lay it flat.&lt;br /&gt;&lt;br /&gt;- From what I can tell, the data is not lost. The drive seems to make sectors as &#39;bad&#39; in certain sections of the drive, and thus &#39;can&#39;t read them&#39;.&lt;br /&gt;&lt;br /&gt;What you will need:&lt;br /&gt;&lt;br /&gt;- 2 Drives of equal or greater size that are working&lt;br /&gt;- A copy of &quot;Media Tools Professional&quot; [FULL] http://www.atl-datarecovery.com/mtl.htm (I had version 3.3)&lt;br /&gt;- A copy of &quot;Ontrack EasyRecovery Professional 6&quot; [FULL] http://www.ontrack.com/easyrecoveryprofessional/&lt;br /&gt;- A floppy diskette&lt;br /&gt;&lt;br /&gt;[For these instructions, the BAD drive will be called Drive-B, and the good drive will be Drive-A. Drive-C is where the data will be restored (This CAN be an FTP site)]&lt;br /&gt;&lt;br /&gt;1 - Hook up Drive-B and Drive-A onto your mainboards IDE controller (NOT any onboard HPT, RAID, etc)&lt;br /&gt;&lt;br /&gt;2 - Boot off the floppy containing Media Tools Pro&lt;br /&gt;&lt;br /&gt;3 - Select the Drive-B and choose Clone, Drive-to-Drive&lt;br /&gt;&lt;br /&gt;4 - Select the Drive-A as the destination, and press Ctrl-S to bring up the options screen&lt;br /&gt;&lt;br /&gt;5 - Change the rety attepts to &#39;1&#39;, and click off the &#39;disable error control codes on last attempt&#39;&lt;br /&gt;&lt;br /&gt;6 - Choose to &#39;Invert&#39; the clone (the last check box on the options screen)&lt;br /&gt;&lt;br /&gt;7 - Start this process and wait for days (my 60GB drive took 49 hours) You will hear ALOT of clicking and it will the remaining time will bounce around from 200,000 hours down to 2 seconds. This is normal, but be prepared for a LONG wait.&lt;br /&gt;&lt;br /&gt;--After clone is done--&lt;br /&gt;&lt;br /&gt;8 - Reboot into WindowsXP, with Drive-A connected (disconnect Drive-B)&lt;br /&gt;&lt;br /&gt;9 - Open up Ontrack EasyRecovery Pro 6 and do an advanced recovery&lt;br /&gt;&lt;br /&gt;10 - Choose Drive-A and select the Advanced Options&lt;br /&gt;&lt;br /&gt;11 - Choose Advanced scan, and &#39;Disable MFT&#39;&lt;br /&gt;&lt;br /&gt;12 - Start the scan (this took 1.2 hours). Then it will present you with a file list of what it files it found.&lt;br /&gt;&lt;br /&gt;13 - Select the files/directories you want to restore and then select Drive-C as your destination&lt;br /&gt;&lt;br /&gt;14 - As it starts to restore, it will prompt you to &#39;Overwrite&#39; files. DO NOT OVERWRITE ANYTHING. Most of the files are cross-linked, and you will end up with garbage. You need to either &#39;RENAME&#39; each one, OR, wait for it prompt you to rename, then in an explorer window, delete the files that it restored, and then click overwrite. Here is an example:&lt;br /&gt;&lt;br /&gt;    - You have selected the dir &#39;mp3&#39;&lt;br /&gt;    - It starts restoring by putting all your *.mp3 files in there (ex: e:\mp3\*.mp3)&lt;br /&gt;    - After it restores all the files in that dir, it will restore the same files, with different data.&lt;br /&gt;    - At this point, it will ask you if you want to overwrite or rename&lt;br /&gt;    - Open Explorer, and delete all the files in e:\mp3    - Then click &#39;Rename&#39; in the dialogue box&lt;br /&gt;    - It will then write out the GOOD data&lt;br /&gt;&lt;br /&gt;AND THANKS TO THE GRACE OF GOD, YOUR DATA IS BACK! I got %99 of my data restored, using this workflow.&lt;br /&gt;&lt;br /&gt;The ONLY thing I didn&#39;t mention was that I updated the drives BIOS before I did this. I have NO clue if that made any difference.</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/113235265461736028/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/113235265461736028' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/113235265461736028'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/113235265461736028'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2005/11/ibm-deskstar-hard-drive-click-failure.html' title='IBM Deskstar Hard Drive &#39;Click&#39; failure'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-19107289.post-113235214207312404</id><published>2005-11-18T14:07:00.000-08:00</published><updated>2005-11-20T06:21:14.123-08:00</updated><title type='text'>System freezes / locks up - AMD +3200 Asus A7V880</title><content type='html'>Had some serious issues with my Asus AV7880 motherboard after I upgraded the CPU to an AMD Athlon XP +3200 CPU / 2x512 DDR PC3200 400MHz RAM - the system kept freezing or locking up whenever I did anything cpu/disk intensive (ex: Winamp, Folding@home, copying files, accessing USB devies, etc).&lt;br /&gt;&lt;br /&gt;[Solution]&lt;br /&gt;&lt;br /&gt;- Update the motherboard&#39;s BIOS to the latest rev. I updated to &#39;1009&#39; http://support.asus.com/download/download.aspx?Type=All&amp;model=A7V880&lt;br /&gt;&lt;br /&gt;- Reset the BIOS to the factory defaults&lt;br /&gt;&lt;br /&gt;- In your BIOS settings, set your DRAM clock speed to 333MHz&lt;br /&gt;&lt;br /&gt;- In your BIOS settings, set your VCore voltage to v.1.75&lt;br /&gt;&lt;br /&gt;- I also set my CAS# latency settings to 2.0&lt;br /&gt;&lt;br /&gt;[Review]&lt;br /&gt;&lt;br /&gt;To date, the system has been rock solid. It&#39;s running a little hot @ 53C to 55C - but nothing close to the danger range of 80C.&lt;br /&gt;&lt;br /&gt;[Referneces]&lt;br /&gt;&lt;br /&gt;http://forums.amd.com/lofiversion/index.php/t56904.html&lt;br /&gt;&lt;br /&gt;http://www.rojakpot.com/default.aspx?location=9&lt;br /&gt;&lt;br /&gt;-----------&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://easyhitcounters.com/stats.php?site=zimzum&quot; target=&quot;_top&quot;&gt;&lt;img border=&quot;0&quot; alt=&quot;&quot; src=&quot;http://beta.easyhitcounters.com/counter/index.php?u=zimzum&amp;amp;s=scoreboard&quot; align=&quot;middle&quot; hspace=&quot;4&quot; vspace=&quot;2&quot; /&gt;&lt;/a&gt;&lt;script src=&quot;http://beta.easyhitcounters.com/counter/script.php?u=&quot;zimzum&quot;&gt;&lt;/script&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://easyhitcounters.com/&quot; target=&quot;_top&quot;&gt;&lt;span style=&quot;color:#666666;&quot;&gt;Site Counters&lt;/span&gt;&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://zimtech.blogspot.com/feeds/113235214207312404/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/19107289/113235214207312404' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/113235214207312404'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/19107289/posts/default/113235214207312404'/><link rel='alternate' type='text/html' href='http://zimtech.blogspot.com/2005/11/system-freezes-locks-up-amd-3200-asus.html' title='System freezes / locks up - AMD +3200 Asus A7V880'/><author><name>Unknown</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>