Back on Puppy, still problems

[Bronco Billy]

GOT IT!!!!

It was the PATA driver on the motherboard.

I thought it was part of the Intel chipset but there was a separate file for it.

Roger

1. When You disconnected, depowered the drives, set the Bios to CD Boot Only Did You COLD Boot??? If ~ ---> Ram was not zeroed....
2. How in the Hell can You Blame a PATA Driver on a Cancer that You initially Caused on this Machine????

It Seems the Basic Philosophy Here is to ALWAYS try and Fix a problem that was caused by a User as Oppossed to Reinstalling and then Directing one's Energy and resources to PREVENT the Problem from Occurring in the Future..... Have a Great Day....

[Roger Hunter]

rjbrewer;

Odd question. I replaced the PATA driver of course. Got a new one from Intel website. I had already done that for the 845G chipset but the PATA driver was a separate file.

Bronco Billy;

Do you really think I'm inside a hot PC pulling cables?

Of necessity it was a cold boot.

And how did I cause the problem?

Roger

[rjbrewer]

rjbrewer;

Odd question. I replaced the PATA driver of course. Got a new one from Intel website. I had already done that for the 845G chipset but the PATA driver was a separate file.

Bronco Billy;

Do you really think I'm inside a hot PC pulling cables?

Of necessity it was a cold boot.

And how did I cause the problem?

Roger

Thanks Roger,

I have no previous experience with pata or sata.
Never even had a computer with a working Windows install
until Santa brought me this 700m.
Only used xp to ugrade bios; 1st time for that too.

I'm trying Macpup foxy right now, a bit overwhelming, but a
lot of fun.

Puppy does seem to attract a few ranting, raving, lunatics
occasionally.

[Bronco Billy]

rjbrewer;

Odd question. I replaced the PATA driver of course. Got a new one from Intel website. I had already done that for the 845G chipset but the PATA driver was a separate file.

Bronco Billy;

Do you really think I'm inside a hot PC pulling cables?
Of necessity it was a cold boot.

And how did I cause the problem?

Roger

You Didn't Cause the Problem....I Guess I Was Lecturing to the Rest of the Forum... Not You... I Believe You on Your Testing.... But I am Still Baffled Why that B*sterd Wouldn't Boot with all the Drives Pulled... In any Event Have a Great Day.....

[Roger Hunter]

Bronco Billy;

I was puzzled too. That's why I checked for an IDE driver. If the CD was good, the drives were good, the cable was good, what's left?

I thought it might be motherboard hardware problem.

Thankfully, it was not.

Roger

[Bronco Billy]

Bronco Billy;

I was puzzled too. That's why I checked for an IDE driver. If the CD was good, the drives were good, the cable was good, what's left?

I thought it might be motherboard hardware problem.

Thankfully, it was not.

Roger

Maybe that Driver Burnt a Jump to Itself in Main Memory in Your Bios?? What Do You Think....Hey it Only works Correctly now when the Driver is Installed..... If it Did that's Dirty Pool(Unethical, maybe Illegal)....Just a thought.... Have a Great Day....

[Roger Hunter]

Bronco Billy;

You might be right because that error cropped up again.

I'm beginning to suspect the CD-RW drive itself. It's the older of the two drives.

I've moved grub to a small partition of its own so I don't have to worry about losing the menu to a reinstall.

Roger

[Bronco Billy]

Bronco Billy;

You might be right because that error cropped up again.

I'm beginning to suspect the CD-RW drive itself. It's the older of the two drives.

I've moved grub to a small partition of its own so I don't have to worry about losing the menu to a reinstall.

Roger

In My Opinion it's Definitely a Memory Boundry Problem....Some Program or Programs are Jumping PARTITION Boundrys and Screwing up the Works.... Hell You're a Low level Programmer... You Know Whats Happening..... The Golden Rule Solves All.... Have a Great Day...

Those Who Have the Gold Rule......