||Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
|(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix|
|News||Recommended Links||Portable Dock
|Latitude C610||Programmable Keyboards||Choosing Your Computer Mouse|
|Synaptic driver problem||3Com Documents||3com drivers||C/Dock II Audio problems||Humor||Etc|
C600 is a solid laptop that is reasonably priced at Dell auctions and on eBay. It suffers from absence of UCB 2.0 ports. The latter problem can be partially resolved by buying docking station and installing USB 2.0 card in it.
For some unknown reason a very good docking stations C Dock/II that are compatible with Dell C600, C610 as well as C800 and C810 are dirt cheap on eBay. If you take into account that it contains a built-in SCSI controller and additional Ethernet adapter you can assume that dock station itself is free :-). C-Dock additional bay is hot-pluggable and unplaggable (if you do not close the docking latch) and that's a very convenient feature as you can have configurations with two CD-roms writers, additional harddrive or DVD reader/writer. Module for the additional harddrive was around $40 on eBay in 2005.
Internally the docking station has enough space to add an additional internal SCSI drive or IDS drive, but the best solution is probably to buy Sun SCSI drive and connect it to the external SCSI interface. It sits perfectly on the top of the docking station. Try to search "Sun External Ultra SCSI hard drive case", "Sun DDS3 external drive/enclosure" or any substring on this. They are often ~$10 with shipping ($1 + $8 shipping).
Here are some typical problems:
Touchpad interferes with
typing on internal keyboard. If you use internal keyboard touchpad
interferes with you tying. The best way to deal with this problem is to
disable touchpad in BIOS by selecting PS/2 mouse setting. In this case if
PS/2 mouse is present touchpad will be disabled. Cheap Microsoft wireless
mini-mouse works excellent and is much better pointing device then touchpad
in most circumstances.
Outdated Synaptic driver may
interfere with network drives for docking station. Dell driver support is not
impressive and one thing that I would instantly recommend is to update
Synaptic drivers to the recent version from the Synaptic site (not
from Dell site). You also can get 3Com drivers directly from 3Com site
if (and only if) you experience blue screen with network driver in docked
position (see below).
Synaptic driver causes a lot of problems (and probably consume a lot of resources). Also if it is enabled then often it moves the cursor when you are trying to type something on the internal keyboard. That's why for presenting sanity is in important to set PS/2 mouse in BIOS.
Periodic crashes ("blue screen of
death") in docked position (with docking station) Ethernet adapter are more difficult to resolve and I do not
know the solution that eliminates them completely. This is more typical
with earlier models of C600, then later models (1GHz models). I also observed
crashes with laptop miniport adapter as well, but they are very rare event.
All my games with driver versions proved to be fruitless. More or less stable combinations are:
Combination 1 (conservative):
Miniport network adapter: 05/02/2000 version 220.127.116.11
Docking station network adapter (3C920): 10/03/2001 18.104.22.168.
Combination 2 (the latest versions):
Miniport network adapter: 09/27/2001 version 22.214.171.124
Docking station network adapter
(3C920) 8/13/2002 126.96.36.199 (I got it from 3Com site)
Sometimes deletion of hardware profile helps but
after several Microsoft updates, drive updates and/or software reinstallations
(I never managed to determine what changes caused it) blue screen may return (may be
crashes are the sigh of corrupted docked hardware profile, I do not know).
Crashes can return just after
undocking and docking of laptop.
Typical C/Dock II Audio problem
(no audio from the dock connector) is resolved by installing the specific
version (older driver) that does not have this problem.
"Death in sleep" problem.
Sometimes laptop when in docking station can never recover from hibernation.
disabling hibernation does not help -- after a while laptop freezes anyway
-- mouse simply stop working. Might be caused from overheating in dock:
using external fan helps to prolong the agony but never indefinitely.
Sometimes docking hardware profile
became corrupted and that introduces really strange behaviors that paradoxically
is in some way independent from drivers installed. Booting laptop without
docking station and deleting the profile resolves the problem.
This year, my mouse is on the fritz. It’s the worst kind of problem where the mouse ‘drifts’ on its own while idle. I don't know if it's divine intervention - No, don't click there on that evil spot - or whether my magnetic personality is getting in the way <g>.
Latitude Docking Station - Latitude - General Hardware - Dell Community Forum
If you run the Quick Setup for the C/Dock, you must do so before docking the system for the first time.
If you docked the system first, you can install only the network drivers from that CD instead of running the entire Quick Setup.
If you need to reload the original factory software:
There is a method (known as ZIGZAG) to restore your system's software to its original, factory-downloaded condition. (NOTE--Any data not backed up before running the ZIGZAG program will be lost from the C: partition)
The first step is to boot to the Dell Diagnostics diskette and choose 'Exit to MS-DOS' from the menu. At the A:\ prompt, type ZZTOP and press
. Press 1 to choose 'Run Image Integrity Check'.
This normally takes 3 - 5 minutes. The drive and the image are checked for errors. Once it has been determined that the image is good and can be restored the screen will flash:
Integrity Check Passed
In the event that the image has been written over or otherwise corrupted the screen will flash:
Integrity Check Failed. Call Your Dell Tech Support Representative.
Next, (assuming the check passed) you will see this menu:
1. Proceed with Software Restore
2. Exit to DOS
Choose option 1 'Proceed with Software Restore'.
ZIGZAG will once again verify the integrity of the image. After the second integrity check is complete you will see this prompt:
Proceed with partition load - destination will be overwritten?
At the prompt, answer "YES" to proceed with the restore process.
The progress indicator at the top of the screen will go to 100%. The last line of the screen will show the current file being copied. Once the progress has completed, reboot the system without the diagnostics disk and the drive should now be set with the factory downloaded software and configuration.
Latitude Windows 2000 3C905C-TX (3C920) dock station Integrated Ethernet controller related crash (blue screen of death) .3C920 ( compatible)
3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible) ...
have a Dell Latitude notebook and I can't get it to synchronize with my Windows CE device. How do I get it to work? Cross reference: 3Com EL90X driver
If you have a Dell notebook computer, or your computer has a 3Com EL90X driver, you may experience some serious problems with getting CE to synchronize. The problem may actually be a bug in the driver which is exposed by CE Services. The information below explains the problem and the solution.
Uffe K. Mortensen posted the following problem on microsoft.public.windowsce:
Our company's helpdesk just upgraded my office PC to a brand new docked Dell latitude PC running Win95. Everything fine, until I put in the MS Windows CE 2.0 Services CD rom to install ActiveSync for my HPC.
Disaster stroke then:
The device/interrupt settings became corrupted on the PC and the PC could no longer run Windows - except in 'safe mode'! It seems the setup.exe install ActiveSync, but also corrupts the device settings (amongst others?) in windows.
For those who asked: The versions used are all 'out of the box': w95 4.00.950B, BIOS level A02, PCI drivers MS 4.00.1117. After installing CE services, device configurations becomes currupted (hard to analyse in safe mode, but includes strange interrupt settings, modem devices (COM, LPT) that makes no sense, etc). Windows stops brutally with 'Windows protection violation error' written on a black screen. The system cannot even re-boot with the usual ctrl-alt-del, and can only run in safe mode
after power reset.
Uffe finally got this fixed, here is the solution:
Thanks to the good advice I received here the problem is finally cured!
For those that might run into the same problem, here is the solution:
The Dell computer has a problem with a driver 'EL90X' for 3COM devices.
Both Windows CE 2.0 and 2.2 are ok, but happens to trigger the bug in the 3com driver and violently crash Windows 95 for good (device tables becomes corrupted and cannot be recovered).
The fixed 3com driver can be found and downloaded at the Dell site.
The network card you need is currently the first one listed, for the 3Com 3C920 chipset. (SuSE lists this as `3Com 3C59x', with no parameters. Anyway, I only found that information later on the euro dell latitude page. I found out which one to use by randomly trying the various 3Com entries after having read the USA dell latitude page, which says someting about `3Com 10/100', which other brands do have that make as an option, but not 3Com.
Google matched content
Troubleshooting Hardware Issues Windows XP
Troubleshoot Hardware and Software Driver Problems in Windows XP
Microsoft Knowledge Base Article: 322205 - After you install a new hardware device or new software, your computer may start to restart spontaneously, or you may receive error messages on a blue screen.
3Com driver search
3C90x - 3C59x - 3C339 - Changing the IRQ
Changing the Interrupt Request (IRQ) for the 3c90x Family of NICs
NOTE: This document uses the 3C90x NIC family as an example, but can be applied to the 3C59x family and the 3C339 NIC.
3Com's EtherLink XL and Fast EtherLink XL family of NICs (3C905-TX, 3C905-T4, 3C900-COMBO & 3C900-TPO) are the PCI 2.1 compliant adapters installed in the system's small, white expansion slots. The slots usually reside on the PCI bus.
Should the IRQ Be Changed?
NOTE: 3Com recommends assigning its NICs to IRQs 10, 11 or 12 because these are often unused. IRQs 2, 9, and 15 are not recommended because they are often used by other PCI devices.
NOTE: NICs must be installed in slots that support busmastering, and busmastering must be enabled within the BIOS.
NIC IRQs should be changed to avoid conflict with other PCI devices. Although 3Com NICs support IRQ sharing, other PCI devices may not support this function. Sharing IRQs with these devices may cause one or more of the symptoms listed below:
- Hanging, freezing, or locking at bootup, or when accessing another PCI device.
- Slow performance.
- Absence of video.
- No logon available.
- Blue screen
When the system boots, BIOS recognizes NICs, and other attached PCI devices, and assigns resources, such as IRQs, I/O, and memory, to these devices. IRQ assignments depend on:
The presence of devices, such as video, SCSI, sound, modem, etc. The BIOS finds out what resources each PCI device needs and assigns the resources as it sees fit. The BIOS assigns resources to all PCI devices, whether they are part of the motherboard or installed in a PCI slot.
The system's setup. Because BIOS is customized to the particular system's configuration, systems with the
same BIOS version, but different configurations, may handle the allocation of resources differently.
The PCI devices cannot request specific resources or control the manner in which the BIOS assigns resources. Resources cannot be jumpered or soft-set by any type of software, including Windows 95, Windows NT or the 3Com Configuration & Diagnostics program.
To Change the IRQ for the 3c90x Family of NICs:
NOTE: If you have questions about configuring IRQs in your system's BIOS, refer to the system's documentation, or contact your dealer or the system's manufacturer.
NOTE: You cannot manually configure NIC IRQs in Windows 95 or NT. The nature of the PCI device causes the system to display one of the following messages:
In Windows 95 - This resource setting cannot be modified.
In Windows NT - Cannot configure the software component.
In systems with user-configurable PCI settings:
Configure the NICs' IRQs using the BIOS or CMOS utility, a.k.a. the Setup Utility. (Refer to your motherboard vendor, the computer's documentation, or start the CMOS setup program, for information on the options available.)
The program is usually accessible immediately after the system boots. You may need to use a pre-determined key or set of keys, i.e. F10, DEL, SHIFT-ALT-ENTER, etc., to access the utility.
In systems without user-configurable PCI settings:
Move the PCI card to a different slot. Sometimes the move causes the system to assign a different IRQ to the card. Update the BIOS. Sometimes a newer BIOS will allow the user to configure the PCI resources.
To Troubleshoot IRQ Conflicts:
Examine the system BIOS.
Move the NIC to a different slot.
Isolate the conflict by removing other PCI devices, such as Video, SCSI, modem, etc.
Try an ISA video adapter.
To View IRQs in the Operating System:
For Windows 95
Right-Click on MY COMPUTER.
Click on PROPERTIES.
Click on DEVICE MANAGER.
Double-click on COMPUTER.
View the 3Com NIC via an Interrupt setting on this screen.
For Windows NT 4.0
Go to START, then PROGRAMS, then ADMINISTRATIVE TOOLS.
Click on WINDOWS NT DIAGNOSTICS.
Click on RESOURCES.
Click on IRQ.
View the 3Com NIC via an Interrupt setting, such as El90x.
For DOS 6.x
Type MSD in your DOS directory.
Keywords: Change IRQ, Resource Conflict, Change Interrupt, Configuration, Change the IRQ
|Chip Set||3Com 3C916B; 10/100 BASE-TX (PC97-compliant)|
|Data bus width||32-bit PCI host-bus interface|
How do I get my microphone to work when plugged into a Dell™ C-Dock or C-Dock II docking station
How do I get my microphone to work when plugged into a Dell™ C/Dock or C/Dock II docking station?
When connecting a microphone directly to a C/Dock or C/Dock II while the system is docked, the microphone does not work. If the microphone is connected directly to the system while docked, it will function properly.
Windows does not enable the docking microphone by default, but it can be enabled through the Volume Properties menu.
Verify that the latest audio drivers are installed. If they are not, download and install them.
To help you install your operating system, drivers, and related software for your Dell system, view or print step-by-step instructions from the Dell Software Reinstall Guide at: http://support.us.dell.com/us/en/kb/org/.
To enable the docking microphone, perform the following steps:
- Click the Start button, point to Programs, point to Accessories, point to Entertainment, and then click the Volume Control.
The Volume Control window appears.
- Click Options and the click Properties.
- Under the Adjust volume for section, click to select Recording.
- Under the Show the following volume controls: section, verify that the check box for any listing of mic or microphone is checked and click OK.
NOTE: The docking microphone may be listed as Microphone 2 or Docked Mic.
At this point, the microphone should function properly when connected directly to the docking station.
For help with specifics on your Dell system, or additional troubleshooting support, search the Dell Support Web site at http://support.dell.com.
Latitude C640 -- C Dock-II Audio problem - Latitude - Audio - Dell Community Forum
Q: Although the internal audio output from my notebook works fine (docked or undocked), I can't seem to get the audio output from the C/Dock II to work. When I initially purchased my notebook, my network administrators insisted on taking Windows XP off, and installing Windows 2000. XP was later installed when the network started supporting it. I know the C/Dock audio worked fine under Win 2000. I think it stopped working when XP was re-installed. I had originally thought this was a hardware problem, but I recently noticed a Knowledge Base article regarding Latitude C600 and C800 portables (Document TT1061041). It addressed this exact problem (loss of C/Dock II audio functionality with upgrading to WinXP), and recommended upgrading the audio driver from the Upgrade Drivers and Utilities CD. Unfortunately, I don't have an Upgrade Drivers and Utilities CD, only a Drivers and Utilities CD that came with the computer that is only for reinstalling drivers, not upgrading them. When I go to upgrade the driver from this CD, it does not offer me the choice recommended in the Knowledge Base article (ESS Maestro 3i (Audio Only)/M3WUA09A). It only offers me a Crystal driver.
Is there a driver that will help me with this problem? If so, how can I find it? Any other suggestions?
Thank you for the help.
A: just install the A02 version and it works just fine. I just figured it out.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to to buy a cup of coffee for authors of this site|
Last modified: May 30, 2010