klute%trillian.irb@unido.uucp (Rainer Klute) (03/17/89)
Dumas' uud failed to decode quikview.uue which was just posted to comp.binaries.atari.st. With the -d flag on uud gave the following output: Begin uudecoding: quikview.arc No sequence check (1). Non uuencoded char <^>, line 40 in file: quikview.uue Bad line =MDH,E^1H2V,1O8 2EH!(&$&A9 \ PL^B0B [P7.09N8/&#!P D3H)P>:($ Then I tried to decode the stuff with the regular Unix uudecode and succeeded; a subsequent test of the generated arc also ran ok. So I deduced that the bug must be in uud. Does someone have the e-mail address of Jean-Pierre Dumas and can report the error to him? Alternativly, does somebody have insight into uud and the uue encoding scheme and write a patch himself? Rainer Klute ---- klute@irb.informatik.uni-dortmund.de Universitaet Dortmund, IRB |)|/ klute@unido.uucp, klute@unido.bitnet Postfach 500500 |\|\ ...uunet!mcvax!unido!klute D-4600 Dortmund 50 ---- Tel.: +49 231 7554663
decouty@irisa.UUCP (Bertrand Decouty) (03/20/89)
In article <1207@laura.UUCP> klute%trillian.irb@unido.UUCP (Rainer Klute) writes: |Dumas' uud failed to decode quikview.uue which was just posted |to comp.binaries.atari.st. With the -d flag on uud gave the |following output: | |Begin uudecoding: quikview.arc |No sequence check (1). |Non uuencoded char <^>, line 40 in file: quikview.uue |Bad line =MDH,E^1H2V,1O8 2EH!(&$&A9 \ PL^B0B [P7.09N8/&#!P D3H)P>:($ | |Then I tried to decode the stuff with the regular Unix uudecode |and succeeded; a subsequent test of the generated arc also ran |ok. So I deduced that the bug must be in uud. | [...] Of course: ^ char does not belong to table data. Change the ~ char in table and all will be fine! This is the correct table: table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ <-- must be ^, not ~ begin 644 quikview.arc M&@A154E#2U!25"Y!0T, TQ, &H29[CB&,<= ,8#0 '"!WD "F 8:\ 8 Hope this help. Bertrand DECOUTY
klute%trillian.irb@unido.uucp (Rainer Klute) (03/20/89)
In article <1207@laura.UUCP> klute%trillian.irb@unido.UUCP (Rainer Klute) writes: > [Problem description about uud'ing quikview.uue] I just got a hint by Jelske Kloppenburg (kloppen@gmdzi.uucp) who noted that the 'table' in quikview.uue is not correct. The last characters in the table are '...XYZ[\]~_' but should be '...XYZ[\]^_'. With this correction uud can decode successfully. However, still the question remains where the false table originated... Rainer Klute ---- klute@irb.informatik.uni-dortmund.de Universitaet Dortmund, IRB |)|/ klute@unido.uucp, klute@unido.bitnet Postfach 500500 |\|\ ...uunet!mcvax!unido!klute D-4600 Dortmund 50 ---- Tel.: +49 231 7554663
jobe@wn2.sci.kun.nl (Jo Beerens) (03/20/89)
From article <1207@laura.UUCP>, by klute%trillian.irb@unido.uucp (Rainer Klute): > Dumas' uud failed to decode quikview.uue which was just posted > to comp.binaries.atari.st. With the -d flag on uud gave the > following output: > > Begin uudecoding: quikview.arc > No sequence check (1). > Non uuencoded char <^>, line 40 in file: quikview.uue > Bad line =MDH,E^1H2V,1O8 2EH!(&$&A9 \ PL^B0B [P7.09N8/&#!P D3H)P>:($ > > Then I tried to decode the stuff with the regular Unix uudecode > and succeeded; a subsequent test of the generated arc also ran > ok. So I deduced that the bug must be in uud. I don't think it's a bug in uud but a wrong character in the character table. If the table you received looks like this table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]~_ begin 644 quikview.arc then change the tilde ( ~ character before the underscore ) into a caret that is a ^. This should solve the problem. Jo Beerens Department of aSTronomy University of Nijmegen
root@yale.UUCP (Celray Stalk) (03/21/89)
In article <1207@laura.UUCP> klute%trillian.irb@unido.UUCP (Rainer Klute) writes: >Dumas' uud failed to decode quikview.uue which was just posted >to comp.binaries.atari.st. With the -d flag on uud gave the >following output: > >Begin uudecoding: quikview.arc >No sequence check (1). >Non uuencoded char <^>, line 40 in file: quikview.uue >Bad line =MDH,E^1H2V,1O8 2EH!(&$&A9 \ PL^B0B [P7.09N8/&#!P D3H)P>:($ > >Then I tried to decode the stuff with the regular Unix uudecode >and succeeded; a subsequent test of the generated arc also ran >ok. So I deduced that the bug must be in uud. The problem seems to be in the quikview.uue file itself. In the copy that reached me, a tilde (~) appared in the table that begins the uuencoded file (4th character after Z), whereas the uuencoded file itself contained carets (^): table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]~_ begin 644 quikview.arc Changing that one occurrence of tilde to a caret allowed it to decode and dearc properly, using Dumas' "uud". I believe the Unix "uudecode" does not know about the table or look at it, which would explain why it wouldn't be bothered by the error. ================================================== | Michael Fischer | | Arpanet: <fischer-michael@cs.yale.edu> | | Bitnet: <fischer-michael@yalecs.bitnet> | | UUCP: <fischer-michael@yale.UUCP> | ==================================================
ralph@laas.laas.fr (Ralph P. Sobek) (03/29/89)
In article <1207@laura.UUCP>, klute%trillian.irb@unido.uucp (Rainer Klute) writes: | Dumas' uud failed to decode quikview.uue which was just posted | to comp.binaries.atari.st. With the -d flag on uud gave the | following output: | | Begin uudecoding: quikview.arc | No sequence check (1). | Non uuencoded char <^>, line 40 in file: quikview.uue | Bad line =MDH,E^1H2V,1O8 2EH!(&$&A9 \ PL^B0B [P7.09N8/&#!P D3H)P>:($ | The problem is that the uud header table became corrupted, but not quikview.uaa! Sounds fishy that one was corrupted without the other!! Anyhow, any uudecode that ignored the table was able to decode the file. Here's the table: table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]~_ begin 644 quikview.arc As any uu-experienced person can see (:-) (thank you Jean-Pierre), the '^' was transformed into '~' which was nowhere to be found further on in the file. That's all. It would be difficult to create a uud to handle this problem automatically. (AI techniques? :-) Cheers, -- Ralph P. Sobek Disclaimer: The above ruminations are my own. ralph@laas.laas.fr Addresses are ordered by importance. ralph@laas.uucp, or ...!uunet!mcvax!laas!ralph If all else fails, try: SOBEK@FRMOP11.BITNET sobek@eclair.Berkeley.EDU