[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Diagnostic Software for PC
if the controller is internal (on board)
then check that you did not swap the cables to the drives (A:
is at the end of the wire) and that you did not put the cables in
one pin off. Then try to remember how the cables were routed
before the accident. Onboard controllers have problems with
cable lengths and routing (lower drive capability).
else
buy a new controller. ISA controllers almost never have this
problem and cost NIS 100.
You did not say what kind of board. If PCI then the PCI chipset must be
enabled for the controller to work (i.e. it's not enough to enable the
fdd, the PCI interrupts and all must give it the access it wants. Set
PCI interrupts to AUTO if available and IDE interrupts to ISA if
available).
On Fri, 20 Jun 1997, Eli Marmor wrote:
> Hi Hevre'!
>
> It is not connected directly to Linux, but maybe one of you will
> have an answer.
>
> I added a CD-ROM to an old 486 (with a:1.44 and b:1.2), and it worked
> fine. Then I tried to access the floppies, but the computer failed to
> access them (although the LEDs turned on). I tried to put the CD-ROM
> out, but the floppies still refused to work. It is not a problem of
> the software/OS, since even during a boot, the computer doesn't boot
> from a floppy, and skips directly to the hard-disk (althoughit tries
> to boot from the diskette, unsuccessfully).
>
> The CMOS is configured correctly, not only for regular access to a:
> and b:, but also for booting from a: (and then from c:). DMA/IRQ is
> OK.
>
> The power supplier is 200W (which supposes to be enough for the heavy
> configuration) but old, so I thought maybe the addition of the CD-ROM
> (in addition to 2 floppies, hard-disk, 16MB, etc.) was too much for
> the poor power supplier, and a damage was caused to the floppy drives
> (the CD-ROM still works perfectly, "without the bad eye" ;-)
>
> I'll try a floppy drive from another machine, but I don't think it
> will help (I think the problem is internal). Meanwhile, does anybody
> know anything about a diagnostic software which I can use in order to
> find out the exact problem?
>
> Thanks in advance,
> --
> Eli Marmor
> ***************************************************************
> * ___ _ __ ___ __ _ |__ _ _ marmor@elmar.co.il *
> * | | | \ | | \ | / |\/ El-Mar Software Ltd. *
> * | | | _) | | _) / | \ Tel.: 972-50-237338 *
> * ___________________________ Fax: 972-9-7484279 *
> * \_________________________ \ http://www.elmar.co.il *
> * _________ __ ____ \ \____ __ _ *
> * \_______ \ \_\| _ \ __ \____ \ \ \ | | *
> * \ \ | | \ \ \_\ \ \ \ \ | | *
> * \ \ | | _\ \ ) ) \ \ \_\_ *
> * \ \ |_| \___) (_/ \_\ \_\ *
> * \ \_______________________________ *
> * \________________________________\ *
> * *
> *************************************************
>
Peter Lorand Peres
------------------
plp@actcom.co.il 100310.2360@compuserve.com
http://ourworld.compuserve.com/homepages/plp
References: