General discussion

Locked

IRQ conflict

By SciFiMan ·
How do I remove/disable Secondary IDE Channel or assign it a different IRQ?

I have a problem with an IRQ conflict on a IBM 4835-152 kiosk, which is basically a 15 inch laptop head mounted on a pedestal. Boots W2K Pro fine and all is well except for IRQ 15 is statically assigned in the bios (can't be changed) for the touchscreen, and when Windows boots it assigns 15 to the secondary IDE channel (which may be its natural IRQ), so the touchscreen won't work. It only has one disk, with serial ports for the barcode scanner, internal, and external receipt printers so no other IDE devices and no floppy. I can disable and/or uninstall the secondary IDE channel in device manager, but next boot Windows adds it back in during startup.

We also have the same unit in a tabletop model that does not have this problem, and in its device manager settings the Secondary IDE Channel isn't seen. Comparing bios settings, they are the same. IRQ 15 is static for the touch screen, and the only IDE setting in bios is set to Primary just like the problem unit. I tried changing the IDE setting in bios to Disabled, Secondary, and Both but still same conflict. Anyone have ideas?

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to IRQ conflict

hummm wonder what the BIOS sees that as? SCSI Host adapter?

How old a mainboard is it? could be theres a jumper on the board for disabling the secondary IDE channel though most new mainboard intergrated peripherals are disabled in the BIOS.

Heck I dunno maybe the BIOS sees the touch screen as a SCSI Host adapter which would explain why it wants to assign IRQ 15 to it.

Collapse -

by CG IT In reply to

Chas ought to know. might ask him.

Collapse -

by CG IT In reply to

moves with the drive...thats an interesting one....stump me....I would have said a BIOS issue in identifing the device or that you have PnP aware O/S enabled in one system and not in the other...but if it moves with the drive.....Clueless here.

Collapse -

by SciFiMan In reply to

Poster rated this answer.

Collapse -

by sgt_shultz In reply to IRQ conflict

you are saying, you tried to disable the secondary ide channel both in bios *and* in windows device manager at the same time and it didn't work?
you sure have interrupt conflict, not io base conflict...
what is model of touchscreen?
how behind is the bios version on this laptop? have you contacted laptop mfg about this problem?
what other devices are in laptop? did you try disabling touchpad in bios...disable modem, touchpad, ir interface, everything. for test.
you are saying you are unable to change interrrupt for ts in Device Manager? sheesh.
if you can't eliminate the conflict, only other thing i can think of to save the day is if you can get dos driver for ts to load from config or autoexec before windows comes up you can stake claim to interrupt that way. it is really screwy that touch screen wants 15 if you ask me. i would contact manufacturer to see about that...

Collapse -

by SciFiMan In reply to

Poster rated this answer.

Collapse -

by SciFiMan In reply to IRQ conflict

--------
UPDATE: Because we have the two units, I swapped the drives around and the problem moves with the drive so it must be a misconfig in W2K. How do I tell W2K Pro (a fresh install with only MS updates so far, plus drivers for printers and touchscreen) to not scan for hardware changes so it doesn't reinstall the secondary IDE channel?

That kiosk is probably a year old at least but I think the bios said from 2001. I will compare the two and update the bios first and test again.

To clarify, it isn't really a laptop, more like a LCD with the basic Ethernet, serial, USB ports (minus headphone jack, CD, floppy, etc.) in a locked shell that kiosk customers can't do anything with but touch the screen to order stuff.
Thanks, and keep the suggestions coming!!
--------

Collapse -

by RCOM In reply to IRQ conflict

It's not the IRQ it's because they both go to COM5.

There's a patch at IBM to disable the secondary IDE controller that will fix your problem.

http://tinyurl.com/2hpwd

http://tinyurl.com/2e4kh

Collapse -

by SciFiMan In reply to

Thanks! That patch did it.

Collapse -

by SciFiMan In reply to IRQ conflict

This question was closed by the author

Back to Hardware Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums