really, no matter what slot the nic is in and was the vid AGP or PCI and what
slot was it in?
On Tuesday 19 March 2002 20:25, you wrote:
Just the one drive on tha first channel, CD ZIP on second channel.
I think I just have a flaky MoBo, even the new one won't run 98SE with the
NIC and the
I'll have to admit to having a temper tantrum about that time and didn't do a
total and complete swap out. Winderz always get's me ire up G.
On Wednesday 20 March 2002 05:29 am, you wrote:
really, no matter what slot the nic is in and was the vid AGP or PCI and
what slot was it in?
On
On Tuesday 19 March 2002 04:43, you wrote:
Yes I agree with Ed , western Digital Hard Disks have problem Sharing
IDE CABLE , this question may destroy your disks.
Got another go figure with a Western Digitalis . On one box, I have to
set the drive as Master, on another, the *same* drive
Thanks a LOT to all your inputs, and especially Brian Parish.
I located the problem with the memtest-x86.bin (on MDK CD1 /images/
directory):
Faulty memory
Again thanks a lot for your quick answers!
Karine
--
Karine ZUERCHER
[EMAIL PROTECTED]
Want to buy your Pack or Services from
In my case, I've changed cables (used both 40 80 pin), changed memory,
video, NIC, HDD and the only thing I haven't tried is disabling the onboard
sound and using a PCI sound card.
On Monday 18 March 2002 10:33 pm, you wrote:
One more thing you might want to check/replace... the ribbon
when you changed the cable did you have one drive on each cable or more than
one drive on each IDE channel?
On Tuesday 19 March 2002 12:48, you wrote:
In my case, I've changed cables (used both 40 80 pin), changed memory,
video, NIC, HDD and the only thing I haven't tried is disabling the
Just the one drive on tha first channel, CD ZIP on second channel.
I think I just have a flaky MoBo, even the new one won't run 98SE with the
NIC and the Matrox vid without locking up.
Take either one out and it's fine in winderz.
Runs much better in mdk8.1
I'm testing 8.2 right now using
Hi everyone,
I got a tremendous problem here.
I shut down my MDK8.1 perfectly, but when I restarted it, it says I have a
corrupted filesystem that needs to be checked. Sometimes the checking doesn't
pass and I have to do fsck in maintenance. This time the rc.d files are
corrupted and I can't
hi karine,
i've seen similar things on our hardware. most of the time the problem
was bios-related stuff (bios in general, dma-settings, prefetch-modes,
...) and almost everytime the problems went away by either disabling dma
(ouch, that hurts, i know) using hdparm or by upgrading buggy bioses.
Karine,
I think you have diagnosed it youself. Sounds like flaky memory. I
would be running a memory checker very intensively before installing
again. There was a thread on these a few days ago, either here or on
newbie. Check the archives with keywords like memory check and you
should find
Karine,
Haven't seen my reply on the list yet, but since sending it I have
checked the archive and the advice from Tom can be found at:
http://www.mail-archive.com/newbie@linux-mandrake.com/msg91074.html
In case the original reply never makes it, what I said was:
I think you have diagnosed it
On Monday 18 March 2002 03:36 am, you wrote:
Hi everyone,
I got a tremendous problem here.
I shut down my MDK8.1 perfectly, but when I restarted it, it says I have a
corrupted filesystem that needs to be checked. Sometimes the checking
doesn't pass and I have to do fsck in maintenance.
Well, I heard a funny story once. A couple of workers from a big
nameless company where woking on (WindBlows) laptops on an American
Airlines flight. Started out fine, but after a few hours things started
to go wrong and eventually both PCs came down in a heap and wouldn't
reboot. It turned
are these both western digital hard drives? have you considered putting each
drive on it's own ide channel?
On Monday 18 March 2002 05:56, you wrote:
hi karine,
i've seen similar things on our hardware. most of the time the problem
was bios-related stuff (bios in general, dma-settings,
One more thing you might want to check/replace... the ribbon cables. I've had some in
the past that with a slight bump would make the data on the drive APEAR corrupt even
though the corruption was in the data transfer not the drive. Then when I'd try to
fsck it... ooops. Since then if it's
15 matches
Mail list logo
