In article <46e225a0$0$28832$4c368faf@roadrunner.com>, jull43@tampabay.REMover.rr.com (Matt Giwer) writes: > Is there a reason you want to boot from the IDE? If it is a secondary > drive does it do things where transfer times matter? I mean put it > together and solve the problem later. In my case, the reason for booting from IDE was laziness - I couldn't be bothered figuring out all that initrd stuff needed to get my box (Slackware 10.2, kernel 2.6.13 on an Athlon 3500 with 1GB of RAM) to boot from the SATA drive. I had a spare 4-gig IDE drive lying around, so I dropped it in and made it my boot partition. Once the box boots, my SATA drive runs just fine (actually, I've since dropped in a second one and they both run just fine) - unless I'm accessing the (IDE) DVD reader. Then _everything_ bogs down horribly. As long as I'm not making heavy use of the DVD drive, all is well, so I haven't worried too much about it. But this discussion makes me wonder whether there's something similar happening on my box, just not with the hard drives. -- /~\ cgibbs@kltpzyxm.invalid (Charlie Gibbs) \ / I'm really at ac.dekanfrus if you read it the right way. X Top-posted messages will probably be ignored. See RFC1855. / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!