You will need to find the utilities that come with each card. These are usually dos utilities that can be downloaded from the manufacturer's website. That means you will need to boot some version of dos, usually 6.x or higher. You can easily make a dos boot disk if you have access to any machine that has dos on it. Put a floppy in the drive, format it, the run the "sys a:" command to make it bootable. It may be possible to make a bootable dos disk under linux, I don't know for sure. The typical utility to change the i/o settings on an interface card can easily fit on the same disk so put everything on the same disk. Once everything is in place, put the floppy in and reboot the machine. Run the setup progs from the dos prompt taking care to set your irq's to something safe, usually irq3, i/o 300 for a network card and irq 5 or 7 and i/o 280, 260 or 220 for a sound card. Consult all the manufacturer documentation and any relevant faqs if you get stuck. If it's available on the dos machine, copy a program called "msd.exe", microsoft dianostics, and run that to get a look at the interrupts. This procedure is usually the only way to setup a card. Irq assignments look like this: 0 = system 1 = system 2 = redirected irq because of funky computer evolution from 8 irq's to 16. 3 = serial 2 (usually avail and can be forced to become avail by disabling the port thru the bios or jumpers) 4 = serial 1 (can be forced to become avail by disabling the port...) 5 = printer 1 (avail if no printer) 6 = floppy 7 = printer 2 (avail if no second printer) 8 = something usually taken 9 = something usually taken but may be available but your card may not work with it - last choice 10 = ide disk 1 11 = ide disk 2 (avail if no second disk but the system may not let u use it) 12 = math coprocessor 13 = mouse or something 14 = scsi 1 (avail if no scsi but 14 and 15 are rarely valid settings in setup software) 15 = scsi 2 <em>>From this chart it is easy to see that conflicting irq settings can cause all kinds of wierdness. Yes, it's a bit frustrating to have to depend on dos to configure everything but there are very few linux setup utilities made by manufacturers. Once you setup everything, you can safely file the dos boot disk away to collect dust and slowly degenerate to the point where it will not boot from disuse - you should only need it once or if you change your hardware sometime in the future. <p>----- Original Message ----- From: "Chopin Cusachs" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 18, 2001 3:53 PM Subject: [brluglist] Continuing Saga <p><em>> <em>> Decided to see if there was a book I should have read that <em>> would have prepared me to do a better job with my project. <em>> Spent an hour at a big chain bookstore, and found one <em>> useful reference, to getting a list of IRQs assigned in a <em>> running system, the command cat /proc/interrupt as <em>> well as sound info from cat /proc/sound. That was all <em>> I found. <em>> <em>> Wonder if anyone can post a URL or two for hardware <em>> debugging of Linux systems. It took me a bit of time <em>> and help from some patient people to learn how to <em>> fix an IRQ conflict in a notorious other OS. It did run, <em>> if badly, even with mouse and modem trying to use the <em>> same IRQ, and I was able to see the problem. Glanced <em>> through Scott Mueller's upgrading and repairing book, <em>> Linux version, some time ago, but don't recall seeing <em>> much of help. <em>> <em>> I wonder what utilities there are out there to do the same <em>> for a Linux box that has never had another OS on it. <em>> <em>> BTW, today received a S3 Savage4 32 MB AGP video <em>> card for the Linux box. It was inexpensive as a geek <em>> clearance house. DriverGuide says it is supported, as <em>> did vendor. Will swap out the floppy drive when I install <em>> the card. Plan to reinstall RH7.1 going through the <em>> partitioning and formatting phase to make a swap <em>> partition big enough for 128MB memory. Will also be <em>> on the lookout for name and location of the installation <em>> log file..... <em>> <em>> Choppy <em>> <em>> <em>> ================================================ <em>> BRLUG - The Baton Rouge Linux User Group <em>> Visit http://www.brlug.net for more information. <em>> Send email to [EMAIL PROTECTED] to change <em>> your subscription information. <em>> ================================================ ================================================ BRLUG - The Baton Rouge Linux User Group Visit http://www.brlug.net for more information. Send email to [EMAIL PROTECTED] to change your subscription information. ================================================ <!-- body="end" --> <hr noshade> <ul> <li><strong>Next message:</strong> Chopin Cusachs: "Re: [brluglist] Continuing Saga" <li><strong>Previous message:</strong> John Hebert: "Re: [brluglist] Continuing Saga" <li><strong>In reply to:</strong> Chopin Cusachs: "[brluglist] Continuing Saga" <li><strong>Next in thread:</strong> Chopin Cusachs: "Re: [brluglist] Continuing Saga" <li><strong>Reply:</strong> Chopin Cusachs: "Re: [brluglist] Continuing Saga" <li><strong>Messages sorted by:</strong> [ date ] [ thread ] [ subject ] [ author ] [ attachment ] </ul> <hr noshade>
<small> <em> This archive was generated by hypermail 2.1.2 : <em>Thu Sep 06 2001 - 11:10:55 CDT</em> </em> </small> </body> </html>
