From owner-freebsd-questions Mon Apr 27 07:23:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20594 for freebsd-questions-outgoing; Mon, 27 Apr 1998 07:23:08 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from ntsvr.medicaltech.com (ntsvr.medicaltech.com [207.70.17.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20584 for ; Mon, 27 Apr 1998 07:23:04 -0700 (PDT) (envelope-from scott@medicaltech.com) Received: by ntsvr.medicaltech.com with Internet Mail Service (5.0.1457.3) id <173QFRZ5>; Mon, 27 Apr 1998 08:24:27 -0600 Message-ID: <8BBBEA98FCB7D011ADB100001B16D9A418ACD0@ntsvr.medicaltech.com> From: Scott Wilson To: "'freebsd-questions@freebsd.org'" Subject: Problem with Iomega ZIP drive and FreeBSD Date: Mon, 27 Apr 1998 08:24:24 -0600 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently purchased FreeBSD 2.2.6 from CDRom.com. The installation program locks up running sysinstall. I have traced it down to a problem with sysinstall and my ZIP drive. The drive is an Iomega ZIP drive attached as the second device on my secondary IDE controller. If I unplug the ZIP drive, sysinstall will run fine but if the ZIP drive is attached, sysinstall appears to lock up during the "probing devices" step. Since I dual boot this machine into Windows NT (and I need the ZIP drive for my NT development work), permanently disconnecting the ZIP drive is not an option. I have tried making a custom kernal with the zip device removed, but this did not help either. Is there a way to make this drive work with FreeBSD? Or at least some way to keep sysinstall from locking up? Thanks, Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message