From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <573dcee27e153a7e9ad877e22ef5e904@coraid.com> References: <546c45999f1379d06a0b58e47b8cb0c5@mikro> <257c42.73550a3a.iYYk.mx@tumtum.plumbweb.net> <573dcee27e153a7e9ad877e22ef5e904@coraid.com> Date: Thu, 19 Dec 2013 22:36:28 +0000 Message-ID: From: Conor Williams To: erik quanstrom Content-Type: multipart/alternative; boundary=089e01182e18e061e604edeaca6c Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Ideas from Plan-9 Topicbox-Message-UUID: a2aad6dc-ead8-11e9-9d60-3106f5b1d025 --089e01182e18e061e604edeaca6c Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable cool man, nice follow up... it's the bell-labs one is code 87... your one was fine but it crashed... and that was the pic I sent... don't worry too much about it... gonna get some of my old hardware after christmas, that I know is supported... I will let you know what happens then my friend... On Wed, Dec 18, 2013 at 8:51 PM, erik quanstrom w= rote: > On Wed Dec 18 04:48:29 EST 2013, conor.williams@gmail.com wrote: > > > > i'm getting an error code 87 writing usbdisk to my key: > > > > according to the web: The second fix prevents USB Image Tool from > > restoring invalid images in device mode. A valid device mode image > > has to be multiple of 512. If that=92s not the case, the write > > operation will fail with error code 87 close to the end of the > > process. To prevent this, USB Image Tool now checks, if the image > > file size is a multiple of 512. > > http://www.alexpage.de/tag/usb-image-tool/ > > i'm not sure what tool you're using, but the image is a multiple of > 512 bytes long. > > ; /tmp/usbinstamd64 bunzip2 > ; ls -ltr /tmp > --rw-rw-r-- M 788 quanstro quanstro 524288000 Dec 18 15:48 > /tmp/usbinstamd64 > ; echo 524288000 % 512 | hoc > 0 > > perhaps something got corrupted. > > the crash dump is good information but in this case the pc does not appea= r > to be valid, so i don't see what's wrong yet. > > - erik > --089e01182e18e061e604edeaca6c Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
cool man, nice follow up... it's the bell-labs one is = code 87... your one was fine but it crashed... and that was the pic I sent.= ..=A0

don't worry too much about it... gonna get som= e of my old hardware after christmas, that I know is supported... I will le= t you know what happens then my friend...


On Wed,= Dec 18, 2013 at 8:51 PM, erik quanstrom <quanstro@labs.coraid.com<= /a>> wrote:
On Wed Dec 18 04:48:29 EST= 2013, conor.williams@gmail.com= wrote:


> i'm getting an error code 87 writing usbdisk to my key:
>
> according to the web: The second fix prevents USB Image Tool from
> restoring invalid images in device mode. =A0A valid device mode image<= br> > has to be multiple of 512. =A0If that=92s not the case, the write
> operation will fail with error code 87 close to the end of the
> process. =A0To prevent this, USB Image Tool now checks, if the image > file size is a multiple of 512.
> http://www.alexpage.de/tag/usb-image-tool/

i'm not sure what tool you're using, but the image is a multi= ple of
512 bytes long.

=A0 =A0 =A0 =A0 ; </n/atom/ftp/usbinstamd64.bz2 >/tmp/usbinstamd64 bu= nzip2
=A0 =A0 =A0 =A0 ; ls -ltr /tmp
=A0 =A0 =A0 =A0 --rw-rw-r-- M 788 quanstro quanstro 524288000 Dec 18 15:48 = /tmp/usbinstamd64
=A0 =A0 =A0 =A0 ; echo 524288000 % 512 | hoc
=A0 =A0 =A0 =A0 0

perhaps something got corrupted.

the crash dump is good information but in this case the pc does not appear<= br> to be valid, so i don't see what's wrong yet.

- erik

--089e01182e18e061e604edeaca6c--