- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
ISA is a very old technology and cards usually require switches or links to be set to avoid conflicts with other cards. ISA is not plug-n-play like PCI or PCI-e.
The software talks to an ISA card by knowing parameters such as IRQ number, DMA number, address range. These values may be permanently set on some cards, while others allow changing via the DIL switches or jumper links. To get two ISA cards working in one PC, the two cards need to use their own IRQ, DMA & address ranges. Make sure there are no conflicts of settings on the sound card and the tape drive card.
Try changing the settings on one of the cards. The tape drive may be the easiest for this. The tape drive is probably connected via a ISA to SCSI interface card. This should have DIP switches or Links to allow the above settings to be changed.
Assuming that your objective is to have an ISA server to protect each building's separate internet connection while maintaining a separate link for the internal networks between buildings then the answer is yes.
Here are a few things to watch:
1. Each building needs to be on its own subnet
2. You can connect the buildings to each other through ISA in several ways or by using a layer 3 switch or router on each end. Either way, you'll need to provide routes between the two private networks.
3. If you only have on DC and it's handling all DHCP you'll need to make sure that the switches can handle DHCP helpers and configure this appropriately. If you need help on this, let me know.
4. If you want to have the ability to quickly configure one ISA server to handle traffic for the opposite building in the event of an internet failure you'll need to configure a short DHCP lease. That way you can re-configure the gateway and get it out quickly to the clients after a failure, i.e. if you can stand an hour without internet easily, a one hour lease would be appropriate. The price for this is increased DHCP overhead traffic on the network.
If you are looking for a true high availability solution where you'll have no downtime on either side if the internet goes down then you will need ISA Enterprise on each end and the implementation will be quite complex and well beyond the scope of what we can do here.
If any of my assumptions are wrong, let me know and I'll try to fill in the holes.
There is an adapter available if you look on computer sites for product purchases, try to google it as there or companies than make such items, might be harder to find as PCI and ISA are older connectors and even AGP is begin phased out an PCI express is the lading connector. Google ISA to PCI adapter and see what you can get your compangies to pruchases from. Your local computer hardware shop might have it call first and ask before driving out there, If you find nothing try calling Tigerdirect as they might have older stock, you never know, If to no avail you will have to try and locate an older Motherboard with the two conncectors on it and run that if possible, or find this certain ISA card you're talking about in PCI. Good luck! :)
Since version 7.3, Redhat have removed support for ISA devices. If you have a older computer that uses an ISA sound device (such as my Asus L7200 laptop with Yamaha OPL3 chip), the ISA device will not be recognized. What you need to do is to download the ISAPNPTOOLS package. Unzip and untar the file and then follow the readme file's instruction to compile, install and configure it. You will also need to add the sound device module to /etc/modules.conf. After that the sound should work. Refer to the Linux Howtos for more information. Since 2005, Linux ALSA sound architecture support pretty much have eliminated that issue even for ISA sound devices.