A way of killing a file.
terric
I believe i found a severe bug.
I am running beta 771 of V0.91.
I can repeat this in TMP-assembler, and has tested it only in TMP.
If you save a source and turn off computer, then you will have a
broken file.
If you save source to a name and save again to a diffrent name and
then turn off computer, the file with diffrent name, will die on you.
/terric
Kajtár Zsolt
Hash: SHA1
Is there any difference if you turn off write caching in setup for this drive?
- --
-soci-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk8IGrAACgkQyBOVYiJltRZmWgCg5D9kTCU7yXNinsdnem2oVj4H
y2oAoKLS/rn8jxj9hqO0zyDQ/qz6Abr8
=Kntf
-----END PGP SIGNATURE-----
terric
The problem seems to dissappear. Not sure if there any gain for me to
have it enabled, so it is disabled for all devices.
Thanks.
/terric
On 7 Jan, 04:13, Kajtár Zsolt <kajtarzs...@googlemail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
Kajtár Zsolt
Hash: SHA1
>>
>> On 7 Jan, 04:13, Kajt�r Zsolt <kajtarzs...@googlemail.com> wrote:
>>
>> Is there any difference if you turn off write caching in setup for this
>> drive?
>
>
> Yes. The problem seems to dissappear. Not sure if there any gain for me
> to have it enabled, so it is disabled for all devices.
Ok, then I think it's time to implement explicit cache flushes very soon, as
it seems some devices don't flush their caches alone soon enough if no
further commands are sent. ;(
- --
-soci-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk8XRz4ACgkQyBOVYiJltRaFjwCgjtUnbBEC1OWr5XWZDNMNKzGD
IhoAnilk6klMCvB1IwJj8Td9NAPfZ4UF
=y2x7
-----END PGP SIGNATURE-----