Content-Transfer-Encoding: |
7bit |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Tue, 23 Feb 1999 09:25:50 -0500 |
Content-Type: |
text/plain; charset=us-ascii |
MIME-Version: |
1.0 |
Reply-To: |
|
Parts/Attachments: |
|
|
I have an IBM EduQuest 40 computer that has a Kingston TurboChip 133
plugged into the overdrive socket, about 1.2 GB hard drive, 20 MB of
RAM, and an off brand but SoundBlaster compatible soundcard. I have the
CD-ROM drive connected as a slave to the hard drive and it worked fine
until I decided to plug it into a Promise Techonologies EIDE card as
the master drive there. I left the hard drive hooked into the IDE
socket on the motherboard. Windows 95 recognized the CD-ROM drive and I
left it at that without using it for a number of weeks. Last week I
bought a CD-ROM disk for my 3 year old daughter to introduce her to
computers. When I installed the disk into the CD-ROM the drive light
lighted up indicating to me for a second that it was accessing the setup
files. Next thing I knew the monitor blanked out and the computer
re-booted. I tried again -- same thing. I tried another CD-ROM disk
that I knew worked in the past for me. Same story. I removed the EIDE
card and reinstalled everything as it was before with the CD-ROM hooked
as the slave to the hard disk. Guess what! Same story.
This seems to only happen in Windows 95 as the CD-ROM works when I boot
up using the previous version of MS-DOS although that's since I put it
back to the slave to the hard drive. It did have problems under MS-DOS
when the EIDE card was installed.
My guess is either a bad CD-ROM drive, conflicting IRQ's, or a problem
with the connection with the HD. As a matter of fact I did not check to
see if the HD is set for master/slave jumper settings. That might be
the problem.
Anyway I thought I'd throw this out for anyone's advice.
Thanks.
Dick
PCBUILD's List Owner's:
Bob Wright<[log in to unmask]>
Drew Dunn<[log in to unmask]>
|
|
|