From owner-freebsd-scsi Tue Dec 30 23:55:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10342 for freebsd-scsi-outgoing; Tue, 30 Dec 1997 23:55:23 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from m-net.arbornet.org (root@m-net.arbornet.org [209.142.209.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10334 for ; Tue, 30 Dec 1997 23:55:17 -0800 (PST) (envelope-from kb8rjy@m-net.arbornet.org) Received: from localhost (kb8rjy@localhost) by m-net.arbornet.org (8.8.5/8.8.6) with SMTP id AAA14087; Wed, 31 Dec 1997 00:01:50 -0500 (EST) Date: Wed, 31 Dec 1997 00:01:50 -0500 (EST) From: "Shaun Q." To: Leif Neland cc: freebsd-scsi@freebsd.org Subject: Re: zip drive problems In-Reply-To: <77b_9712302325@swimsuit.swimsuit.roskildebc.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To clarify the subject: I was on the phone with Iomega last night and they have admitted that they changed the ROM on the latest zip (the rom version seems to be J.03) I don't know if anything else was changed, but the rom was definately changed. Anyone come up with anything yet? Thanks! Shaun q. On 30 Dec 1997, Leif Neland wrote: > At 30 Dec 97 05:18:16 Mike Smith wrote regarding Re: zip drive problems > > MS> Changing the ROM itself shouldn't cause any problems. It sounds > MS> though as if they have changed a great deal more than just the > MS> ROM. > > Yes, they probably changed the contents of the ROM too. :-) > > Surely a change in the firmware in the zip-drive could require changes in the > driver on fbsd. > > > Leif Neland > leifn@image.dk > > --- > |Fidonet: Leif Neland 2:234/49 > |Internet: leifn@image.dk >