Gnus development mailing list
 help / color / mirror / Atom feed
From: Pavel.Janik@inet.cz (Pavel Janík ml.)
Subject: flow-filled and ISO-8859-2
Date: Sun, 7 May 2000 09:50:32 +0200	[thread overview]
Message-ID: <m3ln1m4x9a.fsf@totally-fudged-out-message-id> (raw)

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

Hi,

I have the problem with flow-filled messages. The message contains correct
header:

Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit

(see attachment), but is displayed with \202 before each ISO-8859-2
letters. Kai told me he see the same...
-- 
Pavel Janík ml.
Pavel.Janik@inet.cz

[-- Attachment #2: flow-filled message --]
[-- Type: application/octet-stream, Size: 4242 bytes --]

>From nobody Sun May  7 09:43:52 2000
X-From-Line: linux-return-77102-Pavel.Janik=inet.cz@linux.cz  Sat May  6 01:03:19 2000
Return-Path: <linux-return-77102-Pavel.Janik=inet.cz@linux.cz>
Received: from localgw.inet.cz (brno-l.router.inet.cz [62.229.34.226])
	by BigPenguin.inet.cz (8.9.3/8.9.3) with ESMTP id BAA01177
	for <Pavel.Janik@inet.cz>; Sat, 6 May 2000 01:03:19 +0200
Received: from odysseus.linux.cz (odysseus.fi.muni.cz [147.251.48.205])
	by localgw.inet.cz (8.9.0/8.9.0) with SMTP id BAA11205
	for <Pavel.Janik@inet.cz>; Sat, 6 May 2000 01:11:03 +0200
Received: (qmail 26244 invoked by uid 30); 5 May 2000 23:02:35 -0000
Mailing-List: contact linux-help@linux.cz; run by ezmlm
Precedence: bulk
Reply-To: linux@linux.cz
Delivered-To: mailing list linux@linux.cz
Received: (qmail 26221 invoked from network); 5 May 2000 23:02:29 -0000
To: linux@linux.cz
Date: Sat, 06 May 2000 00:32:41 +0200
From: Uzivatel vd <wacd@volny.cz>
X-Gnus-Mail-Source: directory:/home/pavel/.Spool/
Message-ID: <39134C09.90003@volny.cz>
Organization: Video On Line
Sender: cz-comp-linux@ern.kit.vslib.cz
References: <Pine.LNX.4.21.0005052254440.6560-100000@ahoj.fsik.cvut.cz>
Subject: Re: Jeste jednou CD-RW a mazani
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit
X-Gnus-Article-Number: 1630   Sat May  6 14:44:32 2000

Disk je asi na 4 násobný zápis a vy¾aduje vìt¹í mazací sílu.
Zkuste speed=4 (i v pøípadì 2 rychlostní mechaniky).

DAdam Pribyl wrote:

> Protoze vsichni odpovedeli, na to jak a jesli jde vypalit DAO na ATAPI CD
> mechanice, ale ne na to co s tim ze nejde smazat CD-RW, ptam se jeste
> jednou: taktez mi nejde smazat CD-RW disk. Jak na to? Pripojuji
> vserikajici vypis:
> 
> -------------------------------------------------------------------------
> Cdrecord 1.8.1 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
> TOC Type: 1 = CD-ROM
> scsidev: '0,0,0'
> scsibus: 0 target: 0 lun: 0
> Using libscg version 'schily-0.1'
> atapi: 1
> Device type    : Removable CD-ROM
> Version        : 0
> Response Format: 1
> Vendor_info    : 'ATAPI   '
> Identifikation : 'CD-R/RW 4X4X32  '
> Revision       : '3.ER'
> Device seems to be: Generic mmc CD-RW.
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> Driver flags   : SWABAUDIO
> Drive buf size : 374784 = 366 KB
> CDB:  1B 00 00 00 01 00
> Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 44 00 00 00
> Sense Key: 0x4 Hardware Error, Segment 0
> Sense Code: 0x44 Qual 0x00 (internal target failure) Fru 0x0
> Sense flags: Blk 0 (not valid) 
> cmd finished after 0.001s timeout 40s
> CDB:  1B 00 00 00 01 00
> Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 44 00 00 00
> Sense Key: 0x4 Hardware Error, Segment 0
> Sense Code: 0x44 Qual 0x00 (internal target failure) Fru 0x0
> Sense flags: Blk 0 (not valid) 
> cmd finished after 0.001s timeout 40s
> /usr/bin/cdrecord: Input/output error. start/stop unit: scsi
> sendcmd: retryable error
> status: 0x2 (CHECK CONDITION)
> /usr/bin/cdrecord: Input/output error. start/stop unit: scsi
> sendcmd: retryable error
> status: 0x2 (CHECK CONDITION)
> Current Secsize: 2048
>   ATIP start of lead out: 335975 (74:41/50)
> Blocks total: 335975 Blocks current: 248318 Blocks remaining: 248468
> Starting to write CD/DVD at speed 4 in dummy mode for single session.
> CDB:  A1 00 00 00 00 00 00 00 00 00 00 00
> Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 64 00 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x64 Qual 0x00 (illegal mode for this track) Fru 0x0
> Sense flags: Blk 0 (not valid) 
> cmd finished after 0.002s timeout 9600s
> /usr/bin/cdrecord: Input/output error. blank unit: scsi sendcmd: retryable
> error
> status: 0x2 (CHECK CONDITION)
> /usr/bin/cdrecord: Cannot blank disk, aborting.
> --------------------------------------------------------------------------
> 
> A doplnuji:
> Mechanika ACER, emulace SCSI pres ATAPI.
> 
> Diky za pripadne rady
> 
> Adam Pribyl
> 



---------------------------------------------------------------------------
Meta-FAQ (odhlá¹ení, archív, FAQ a dal¹í): http://www.linux.cz/mailing-list


             reply	other threads:[~2000-05-07  7:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-07  7:50 Pavel Janík ml. [this message]
2000-05-07 10:46 ` Kai Großjohann
2000-05-07 14:58 ` Shenghuo ZHU
2000-05-07 19:07   ` Pavel Janík ml.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3ln1m4x9a.fsf@totally-fudged-out-message-id \
    --to=pavel.janik@inet.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).