The only problem that I have had with qxl.win was when I had a drive (IE: win1_, win2_) space that was nearly full. If I added, deleted or modified too many files it could get very fragmented and suddenly run out of 'room' even though it showed enough left. To solve that I normally would do a copy command (the C68 copy), tell it to include subdirectories, and copy to a different win drive and then copy it back. That would clean it up 100%. I never noticed much top level fragmentation speed impact.
I found that if I reserved enough empty space on a drive, I totally avoid the fragmentation issue. Don't know if this has been improved with the SMSQE updates but I haven't hit it for a few years now. jim On Apr 25, 2007, at 7:12 PM, P Witte wrote: > Marcel Kilgus writes: > > <> >> While I'm writing anyway, some comments to another topic: of course >> QXL.WIN files can fragment like pretty much all other file systems >> (some more, some less, but basically all have the problem). But >> QXL.WIN files are virtual anyway, so even if the data within the >> drives is not fragmented, the Windows file still can be. > > I can understand that a qxl.win container file could get fragmented > during creation. But do you mean that the container file can get > fragmenbted on the Windoze side by file operations on the QL side too? > > On the QXL the container files were attributed as system files and, > if I > understand correctly, were therefore left alone by the defragger. > Presumably they didnt fragment Windoze side either as according to the > pretty graphs in Defrag, they remain a solid block and in place. > > <> > > Per > _______________________________________________ > QL-Users Mailing List > http://www.q-v-d.demon.co.uk/smsqe.htm _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
