#168 saving partial dvi file: corrupted

a saved partial dvi file is corrupted

xdvi reports

xdvi.bin: Fatal error: Could not open
/home/scholz/Folien-alle_pp.dvi: Page description
doesn't begin with BOP

dvips reports

This is dvips(k) 5.92b Copyright 2002 Radical Eye
Software (www.radicaleye.com)
' TeX output 2003.04.04:1233' -> Folien-alle_pp.ps
dvips: ! Bad DVI file: no font selected

[Stefan Ulrich]

Logged In: YES
user_id=177175

I think this was a bug related to the temp file problems in
#765287.
Does it still occur with the current CVS head? (I've put a
downloadable version of it here):

http://xdvi.sourceforge.net/xdvik-22.76.2-RC2.tar.gz

Does `save partial' mean `save marked', or `save from ... to
...'?
Is the original DVI file secret, or could you send it to me?

[Nobody/Anonymous]

Logged In: NO

save marked

it's also present in the new xdvi 22.76.2-RC2

BTW: xdvi 22.40v reads it!

I put two files on my web page:
thispla.net/Folien-alle.dvi (original, large)
thispla.net/Folien-alle_pp2.dvi
(pages 2,4,5,0,8,9,10 - yes, there is a 0 between
5 an 8)

[Stefan Ulrich]

Logged In: YES
user_id=177175

> xdvi.bin: Fatal error: Could not open
> /home/scholz/Folien-alle_pp.dvi: Page description
> doesn't begin with BOP
[...]
> BTW: xdvi 22.40v reads it!

Hmm, that's a bug then ;-) dvitype says the same as current
xdvi:

Bad DVI file: byte 9736 is not bop!

The error seems to be some weird interaction in the file
pointers while copying; I had this problem with a previous
version and thought that I had fixed it ... could you try
applying the following diff:

http://xdvi.sourceforge.net/testpatch_22.76.2-RC2

and select the pages again - does it print out any lines like:

position in input file: 73767, output: 8230, char: 0

? Is the file still corrupted?

[Stefan Ulrich]

Logged In: YES
user_id=177175

Fixed in 22.77 (problem seemed to be mixing lseek() and
fseek()).