
If you have a problem: Firstly, please make sure that you are using the current P-series drivers and that these are installed on your PC. It is also worth checking that the operating system that you are using is supported by our drivers (See our list of supported operating systems, please note that in NT4 you will require SP6). Then check out the known problems described on these pages. If you cannot find a solution here, please submit our p-series help form.
General Information
Can I use my CardBus (32-bit) PCMCIA card in my front bay adapter?
How do I connect the cables on my P423/P424/P223/P224 adapter? Can I use my front slot model in a 5 1/2 inch drive bay? Multiprocessor Machines - operating problems have been encountered when using multiprocessor motherboards. PCI-to-PCI bridges can cause problems in P-series operation. Motherboard/Bios Problems may cause the PC to crash, particularly common with old BIOS versions. Enabling SRAM/Linear FLASH Card File System Support in Windows Verifying installation of the driver software in Windows 2000 and XP I have Windows 2000/XP and I'm upgrading the PSeries driver to Version 5.06+ or have already installed the hardware, what am I to do?
PC Reboots when a Lucent Orinoco WLAN Card is Inserted - this problem is unrelated to the P-series adaptor itself and will occur with any PCI or ISA adapter and also on a laptop.
"Code 31" error in Windows
WinExec fails on installation with Return Code 87
P-Series Diagnostics Utility
Installation failure in Windows NT4, 2000 and XP
Creative Labs Modem Blaster V90 Card
Using PCMCIA Cards in Older Desktop PCs
Windows 95, 98 and Millennium Edition.
PCI IRQ Routing in Windows 9x - adapter will fail with a error code.
Operating problems with Intel(R) Desktop Motherboard Board D815EEA and Intel(R) "Active Monitor" in Windows 98 - may cause Windows to crash with a page fault when a PC card is inserted. Also "Active Monitor" may report an voltage out of range error.
Windows 95 OSR2 (B/C) fails to allocate resources to the PC-Card
Delay before the PCMCIA Card is Recognised - when a PCMCIA card is inserted the PC takes over 60 seconds to recognise it.
Code 29 error in Windows 95 OSR2 on a Fujitsu/ICL ErgoPro D5/90P slim-line desktop Pentium 90 based PC - the Windows 95 Device Manager shows a yellow exclamation mark and "Code 29" error "Hardware Disabled".
"PCMCIA Card Services" entry in Device Manager shows "Code 1" error in Windows Me
PSeries driver version 5.07 causes some PC's running Windows 95,98 or Me to lock up during boot
Windows locks when a CardBus Network Card is installed on a Machine with an existing PCI Network Adapter installed
Windows NT4, 2000 and XP.
SystemSoft CardWizard : Additional software recommended for operation in NT4.
Installation problem in Windows NT4/2000/XP
Problems with the MSI 694D Motherboard in Windows NT and Cirrus Logic based P-series models.
Status Code 0x5 occurs during installation
Slow operation of PC Cards in Windows NT4
CL6729 Based Adapter Fails "Code 12" in Windows 2000
Problems using a Modem or Serial Card in Windows 2000 or XP
Conflicting PCI IRQs in Windows 2000 and XP
"Interrupt Request 09 not Available" Conflict shown in Windows 2000
SRAM Card Fails "Code 12" in Windows 2000
ACPI BIOS Problem when booting Windows 2000 with IBM Netvista PC
Lucent WaveLAN/ORiNOCO Card Fails to Communicate in Windows NT4.0
Error message from PCI BIOS on Compaq Proliant Server
PCMCIA Card Fails "Code 10" in Windows XP
Psion Dacom Gold Card Modem Fails to Communicate in Windows XP
Installation Error in Windows XP with WinFast AGP Adapter Installed
Setupapi.log Error Message in Windows 2000&XP
Eiconcard "P-Series" Driver Name Conflict
PCMCIA Card Recognised as "MTD-0002" Device
|