WOW! That was quite good - thank you for the updates. Like many others on this list, I build my own systems, and I learned and worked with this limitation for many years, without having checked again with the new stuff I put together recently ... to me this was almost like a "given" ... and - combined with the fact that I always had the possibility to do it the way I thought being right (never had more than two (E)IDE hard drives, or more than two CD/DVD/ZIPs in any system, thus no problem in "grouping" them), I never gave the issue second thoughts.
But now you made me curious ... I will try some of these on my new systems at home ... Thx again for this great - updated - info ;) Stef On Tuesday 21 January 2003 03:15 am, Dave Laird wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Good morning, Stef... > > I thought enough of what you said to set up a few testing combinations on > an old Pentium I had downstairs. If my hunch is correct, now that I've > tried some combinations, I think this is largely dependent upon the type of > EIDE interface, itself. Some of the older IDE interfaces, particularly > those that came on a card (remember THEM?) suffered from this problem. An > older pair of IDE interfaces on a 1998 motherboard had similar problems. > > I tried a somewhat esoteric combination of IDE cards, 486 motherboards and > a pair of old Pentium motherboards, each with approximately the same level > of failure. > > However, on a newer motherboard, particularly with a newer BIOS, the > problem goes away. Thus far, using a more modern motherboard and BIOS, I > have been able to get the BIOS to recognize the Zip drive in about every > position, without regard to the speed of any devices sharing the buss. > > In fact, as an update of sorts, so long as I manually mount the zip drive > thus: > > mount -t ext2 /dev/hdd /zip > > it works flawlessly, and is very usable. If I don't manually mount the > device, however, because of some KDE strangeness, it mounts the drive, but > defaults it to vfat. I'll have to locate where the mount statement occurs > in KDE's startup scripts and fix it to where it works the same as the > manual statement (above). All in all, it's working fine now, and the drive > chain problems that existed on older systems appears to be a thing of the > past. > > Thanks again... > > Dave > - -- > Dave Laird ([EMAIL PROTECTED]) > The Used Kharma Lot / The Phoenix Project > Web Page: http://www.kharma.net updated 01/02/2003 > Music Calendar & Website: http://www.kharma.net/calendar.html > Usenet news server : news://news.kharma.net > > An automatic & random thought For the Minute: > The world is coming to an end--save your buffers! > A lost ounce of gold may be found, a lost moment of time never.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
