cview answers a very kind soul has mailed me this reply for the bugs in cview since he isn t in the position to post this himself he asked me to post it for him but to leave his name out so here it comes cview has quite a number of bugs the one you mention is perhaps the most annoying but not the most dangerous as far as i can determine it has to do with the temp files that cview creates cview gives the user no control over where it places its temp files it just places them in its current directory the problem you mention occurs as far as i can tell when it runs out of disk space for its temp files it seems as if cview doesn t check properly for this situation as cview decodes a jpeg it seems to write out a temp file with all the pixel data with bit colour information then for bit displays it does the dithering again writing another file with the bit colour information while it is writing this second file it also writes the data to your colour card then when it does the last chunk of bit data it recopies all the data from the bit file to your screen again it does this last recopy operation for its fit to screen feature even when this feature is not enabled the result of this process is the following if it runs out of disk space when writing the first bit file all you ever see is as much data as it has room for and the last bit of data is simply repeated over and over again because cview never realizes the disk has filled up and disk writes reads aren t performed if it has enough room for the bit data but runs out of room for the bit data you see almost all of the picture as it does the dithering and writes to the screen card however then when it finishes the dithering and recopies the data from the bit file to screen for whatever reason it does this one again just gets a repetition of the last chunk of data for which there was room on the disk this is just a guess but probably fairly accurate at least the general idea is on track i think although i have probably made errors in details about file i o etc the way around this is of course to clear up sufficient disk space the temp files for large jpeg s x and bigger can be very large meg meg on some of the largest i have needed in excess of meg free disk space cview has a much more serious bug if you are trying to display a file from a floppy and you change floppies while cview has some temp file open on the floppy then cview in certain circumstances will write the directory and fat table i can t remember for the removed floppy onto the newly inserted floppy thus corruptimg the new floppy in a very serious possibly unrevcoverable way so be careful it is incredibly poor programming for a program to do this on the other hand when choosing files in the open files menu cview insists on doing a few disk reads every time one moves the hi lighter square incredibly annoying when it could do them all at once when it gets the directory info and really how much effort does it take to sort a directory listing with much thanks to the originator of this article rene walter renew stack urc tue nl will i drown in tears of sorrow is there hope for tomorrow will this world ever get better can t we all just live together i don t wanna live in strife i just wanna live my life i deserve to have a future the good girls future
