-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Torfinn Ingolfsen wrote:
> IMHO, you should never use "working on win..." as a statement to say
> that some hardware is
> a) working
> b) compliant with a standard
I was only stating, that after 8 years of use, I would have noticed if
the disk/control
Just so you know... after having done a large number of SCSI target
mode implementations and having seen what initiators do, it's
Microsoft that is the closest to actually adhering to and using the
SCSI standards correctly.
On 7/20/07, Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote:
On Fri, 20 Jul
On Fri, 20 Jul 2007 23:43:35 +0200
"Uffe R. B. Andersen" <[EMAIL PROTECTED]> wrote:
> That's nice to know, though I didn't expect it to be critical, as the
> disk has worked well for all 8 years, running with Windows 2000 and
> XP.
IMHO, you should never use "working on win..." as a statement to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeremy Chadwick wrote:
> On Wed, Jul 18, 2007 at 11:26:33PM +0200, Uffe R. B. Andersen wrote:
>> When I boot my FreeBSD 6.2-RELEASE-p6, I get the following error:
>>
>> (pass0:ahc0:0:0:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0 0 0 0
>> 0
On Wed, Jul 18, 2007 at 11:26:33PM +0200, Uffe R. B. Andersen wrote:
> When I boot my FreeBSD 6.2-RELEASE-p6, I get the following error:
>
> (pass0:ahc0:0:0:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0 0 0 0
> 0 e c 0
> (pass0:ahc0:0:0:0): CAM Status: SCSI Status Error
> (pass0:ahc0:0:0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
When I boot my FreeBSD 6.2-RELEASE-p6, I get the following error:
(pass0:ahc0:0:0:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0 0
0 0 0 e c 0
(pass0:ahc0:0:0:0): CAM Status: SCSI Status Error
(pass0:ahc0:0:0:0): SCSI Status: Check Conditi
