You must use the "Have Disk" method of specifying the driver location. The sequence is critical.įurther, do not be fooled by the New Hardware Wizard into thinking it can autodetect the appropriate device and driver set for this adapter. But, if the manufacturer specifies driver installation prior to connecting physicly the device to the system do not take this as casual advice. Check the web site of the adapter manufacturer, as there often have been updates to the driver set. Look carefully at the userguide, as this differs by manufacturer. If possible, you want no IRQ sharing.įor your USB device you install the drivers prior to connecting the adapter to your computer. Remember that COM1 & COM3 share IRQ4, and COM4 share IRQ3 by default. For serial port devices select the correct port and IRQ assignments. For each new device set the values yourself, rather than let XP automaticly select the driver. If the New Hardware Wizard appears, cancel it.Ĭontrol Panel, Add Hardware. Reboot (without the USB adapter, and without any other serial connection). These steps are often best done in Safe Mode. Under the section, Mice and other Pointing Devices, Disable and do not uninstall the ballpoint Mouse device.Ĭheck as well the "Human Interface Devices" section, and [Disable not uninstall any erronous entries.įinally, under Ports, uninstall all serial ports shown whether greyed-out or not. In Device Manager, Hardware, View, Show all hidden devices. The serial port is now read-only (one does not have a need, nor does the driver support, a write to the mouse). In most cases the guess will be that your serial device is an older ballpoint serial mouse. The chances of Windows correctly identifying the device if it is anything other than a Mouse is nearly zero. The New Hardware Wizard runs, and the user says Okay, automaticly detect the device. The most common misidentification occurs because someone connected an unidentified port and/or device prior to installing drivers for it. this mis-identification is persistant unless the entries are removed from the configuration settings for the computer. The principal reason is that during an initialization on startup it mis-identifies a new device. In particular, to handle ACPI issues, the advanced power features of current computer BIOS.ĭoes it screw this up? Yes, it can and does screw this up fairly often. On startup NTDETECT is run, and one of its purposes is to resolve issues between BIOS enumerated devices and the Plug-and-Play service of XP. Yes, Win2k and XP enumerate serial ports differently than previous OS versions. In your situation your laptop does not have a serial port, you have the USB connector, see if any of the following may help.ġ. I have seen issues with USB-to-Serial, and I really do not like it, preferring native serial ports or the use of PCMCIA serial adapters. RE: Serial port problems with Win XP ZappaDog (TechnicalUser) This is very device driver and manufacturer specific and decidedly not a generic solution.Īnd again, if your boss's machine tech told him it was an XP problem be glad he is not in the IT department. But as a generic solution there is usually enough to go outbound, but nothing in the driver to receive the serial communications after conversion. The difficulty with USB-Serial is that it can work perfectly for specific devices where you can find WHQL certified drivers. Anything, anything than trying USB to serial. If your laptop has its serial cable occupied by a mouse or another device, get a PCMCIA card an run a new com port from that. Get a serial cable and bag the USB to serial conversion. There is not one credible individual that I know of that views how Win2k and upwards for MS operating systems that does not know that because of ACPI compliance all com ports are scanned at startup (one of the first things that ntdetect does), that exceptions can be made in special cirucmstances as boot.ini parameters, and that using USB devices, (not even supported at all in the original release of Win95, Win98, Win98SE, NT (not even today), Win2k, or XP) is an unproductive way to try and do something as immediate as workstation to machine tool serial communications and control. Tell your boss to get a new machine tech. Get a parallel connector (on your laptop) to parallel connector (on your machine) cable. I have a hard time believing that there is not some way to make it work, but I can't seem to figure it out. that my boss talked to said that windows XP just will not work for sending to machines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |