Support Note
		WinNT4 Verify LAPcan I / LapCAN II installation 1. Install the CAN driver routines if not already done (click here). 2. Insert the LAPcan I/II into the PCMICA slot of your computer. 3. Reboot the compter. 4. Open the "Control Panel" (click "Start" -> "Setting" -> "Control Panel"). 5. Double-click the "CAN Hardware icon" and you will, if everything is working properly, open the following "CAN Driver Configuration" Window. (If you can't find the "CAN Hardware icon" in the "Control panel" the CAN driver routines is not installed properly, try to reinstall them again.) Trouble shooting If your "CAN Driver Configuration" looks like below you are not communicating with the LAPcan I/II card. a) Make sure that your LAPcan I/II is inserted properly in the PCMICA slot of your computer and reboot your PC, this is the most common error. If this doesn't work, try point b of this document. b) It can be a IRQ- or Address conflict. If it is a IRQ-conflict can be verified with a operation from point b1 to b5 of this document. b1) Open "Windows NT diagnostic". (click "Start" -> "Run") and type "winmsd" at the command prompt. b2) In "Windows NT diagnostic" you will see a list of used IRQs under the "Resources" map and click the "IRQ" button. Make sure that the IRQ used by "vcanx" is not also used by annother hardware. Look for a IRQ-level (number) that is not in use (a number that is not present in the "IRQ"-table) and rember this number. b3) To be able to determine if it is a "I/O Port address conflict" is done my clicking the "I/O port" button.  Make sure that the I/O base address for "vcanx" is not used by any other hardware. However, if that is the case, look for a address divadeble with (08h) that is not being used and remeber this value. b4) Open the "CAN Driver Configuration" again (see point 5). Mark the "LAPcan 1" and click the "Configure" button. The dialog window below will pop-up and that's where you reconfigure your LAPcan to the new IRQ and I/O base address. b5) Reboot your PC and try to access the CAN Hardware again. Sometimes there are still conflicts (I/O or IRQ) even if they are not visible so if problem persists it's recommended that you try a number of combinations (change both I/O and IRQ a couple of times - nothing but hard work...)
		Back to Technical Notes index