We are using cf 30's for fire engines to assist in computer aided dispatching. When a unit sites in a station for a prolong period of time the GPS location can float as much as 10 miles from the actual location, which causes the unit not to get picked for a response. We have switched out laptops, antennas, and done software updates to no avail. This problem seems to only effect 3 units out of the 20 units using cf 30's.. we have another 40 units on the cf 29's with external modems with no problems

When idling for long periods of time the spark plugs can get fouled, Soon as you step on the gas the engine will usually spit and sputter then go or just stall. Avoid prolonged idling, if you must do it periodically give it some gas (pump the pedal a few times) to clear the plugs and keep them from fouling.

Most police stations are using the new motorola trunking units, they are on encrypted custom band channels and you will not be able to hear them. All police helicopters are equipped with them. All i can hear where i live is Fire dispatch, I cant even hear the fire fighters responses .

Water in a starter motor is not a real problem but if you are burning motors due to prolong cranking then have the engine looked at as it should start within 6 revolutions of the engine. When using a starter remember that you are drawing up to 400 amps from the battery so the start period should be restricted to 30 secs. with minute rest between attempts. No starter will last if you just keep cranking away forever.

If your Toughbook has an integrated GPS, this may be conflicting with the touchpad or touchscreen driver. You can fix this by running the GPS Registry Patch - SKIPENUM.REG, which is found in the C:\UTIL\GPS\ folder. This file can also be found by following the link below.

If you are using a GPS module that is not integrated, you should contact the manufacturer of the GPS module for a similar patch.

If you are not using a GPS module, or if the above steps do not fix your problem, re-install the touchpad and/or touchscreen drivers.

• Hi, I can help.

• You can listen to live audio feeds on your computer for your area here http://www.radioreference.com/apps/audio/?ctid=2311

• Here are all existing frequencies for your Cranston,RI

• Frequency
• 154.01000 Cranston FD Fire F1 Fire-Tac
• 159.46500 Cranston FD2 Fire F2 Fire-Talk
• 151.28000 Cranston FG4 Fireground Fire-Tac
• 482.41250 Cranston PD Police Law Dispatch
• 482.46250 Cranston PD2 Police Law Tac
• 482.56250 Cranston PD3 Police Law Talk
• 483.63750 Cranston PD4 Police Car-to-Car Law Talk
• 159.40500 Cranston FG5 Fireground F5 Fire-Tac
• 460.60000 Cran FD Disp FD - Station Dispatch Fire Dispatch

• If you have any comments please feel free to leave them here.
• Hope this helps and thank you for using FixYa.

Regards, Tony

Chances are you have the infamous Nvidia chipset of death issue. Basically there is a design flaw in the computer that causes failure after a prolonged period of use (usually after warranty) and HP is not fixing or standing behind their product.

There was a lawsuit against HP and Nvidia - and a settlement was reached. But only certain HP DV9xxx models are included in the settlement. Do a google search for Nvidia HP lawsuit.

Basically there is too much heat in the unit for the chips and connections that where used. The Nvidia chip generates most of the heat. The end result is that after a period of time - your motherboard will fry itself. Starting with the graphics (first the laptop display) then followed by the wireless card, followed by the entire motherboard.

There are "fixes" that you can try - but most are not really fixing the problem - just getting around it for a short period - more of a band aid.

Hi all, I had much the same problem, engine bouncing around when idling as if it were firing on a few cylinders and even cutting out completly sometimes. I found out it was the breather hose at the rear right hand side of the engine that runs to the front. there is an elbow piece at the back, this could have developed a leak or in my case it was further back behind the engine, hope this has been of use guys. one thing I would like to point out, beware of the cooling system plastice hose conectors, the outer may look fine but some of mine just brake off and crumble in your fingers, it's as if the inner plastic is destroyed by the hot collant over a period of time, i'm in the process of replacing most of mine.


Dave.

The "E30" error code is displayed when reading/writing data on a CF card has failed. Especially, the error code "E30" may appears when you tried to remove a CF card while the camera was processing data. Solution To clear the "E30" error, try performing the following procedure. 1. Try using another CF card. If you have another CF card, try loading it in the camera. If the error code is not displayed when the other CF card is loaded, there may be something wrong with the first one rather than with the camera. 2. Use your computer's ScanDisk utility to check the CF card for errors. Use ScanDisk to check the CF card for card error or card failure. Refer to the instruction manual for your operating system or Windows Help for further instructions. (If you are using a Macintosh, use the "Disk First Aid" program to check for card error or card failure. Refer to the instruction manual for your Macintosh OS for further information.) Be sure to back up the data on the CF card on the computer before you check the CF card. If a card error or card failure occurs when you use your computer's ScanDisk, there is something wrong with the CF card. Follow ScanDisk's on-screen instructions to solve the problem. 3. Format the CF card with your camera Try to format the CF card with your camera. Please refer to the "Camera User Guide" for your camera for instructions on formatting CF cards. Also, please note that formatting a CF card will erase all data on the card. Once the CF card is formatted, follow the procedure described in step 2 above and use your computer's ScanDisk on your computer to check the CF card for errors. If a card error or card failure occurs when you are using computer's ScanDisk, there is something wrong with the CF card.