I just got the packet writing patch working in Linux 2.4.19 and am fairly impressed, but I have been having some interesting troubles. 1 - When using the drive normally, editing files on it directly, the changes don't seem to be sticking. Sometimes when I unmount nothing gets written and changes don't occur. Come to think of it this may have started when I used it in a windows 98 drive with directCD. 2- my system periodically locks up while I have a CDRW mounted. This appears to be kernel level because every application stops, even the mpg123 playing in the background which is usually unaffected by such things. I have tried to catch any massive process with top but haven't seen any. 3- This last time, javac had a fit about some IOException. I tried to unmount the drive and nothing got written. Then when I tried to mount again the mount program just hung...I ended up killing it eventually (that took some doing also). Then it acted like it wrote something and future attempts to mount failed with a device busy or mounted error. A reboot took care of the matter but no changes took place - the old directory I deleted was back and the one I replaced it with was gone. I have made the assumption that there is some massive buffering going on and it is not flushing as it should. Is there some way to force a flush of the cdrw buffer? Is packet writing still really unstable or am I seing especially unique features? If someone told me what to do to get a good error report generated I would be more than willing. Nothing interesting is in messages. Here is some crap from dmesg....this is after reboot though and may not be helpful....looks normal to me but I don't know anything about udf or pkt. pktcdvd: inserted media is CD-RW pktcdvd: Fixed packets, 32 blocks, Mode-2 disc pktcdvd: speed (R/W) 6/4 pktcdvd: 180672kB available on disc UDF-fs DEBUG lowlevel.c:57:udf_get_last_session: XA disk: no, vol_desc_start=0 UDF-fs DEBUG super.c:1414:udf_read_super: Multi-session=0 UDF-fs DEBUG super.c:407:udf_vrs: Starting at sector 16 (2048 byte sectors) UDF-fs DEBUG super.c:750:udf_load_pvoldesc: recording time 1036479266/961095, 2002/11/04 23:54 (1e5c) UDF-fs DEBUG super.c:760:udf_load_pvoldesc: volIdent[] = 'LinuxUDF' UDF-fs DEBUG super.c:767:udf_load_pvoldesc: volSetIdent[] = '3dc77932LinuxUDF' UDF-fs DEBUG super.c:959:udf_load_logicalvol: Partition (0:0) type 2 on volume 1 UDF-fs DEBUG super.c:969:udf_load_logicalvol: FileSet found in LogicalVolDesc at block=32, partition=0 UDF-fs DEBUG super.c:797:udf_load_partdesc: Searching map: (0 == 0) UDF-fs DEBUG super.c:838:udf_load_partdesc: unallocSpaceBitmap (part 0) @ 0 UDF-fs DEBUG super.c:879:udf_load_partdesc: Partition (0:0 type 1522) starts at physical 1408, block length 88640 UDF-fs DEBUG super.c:1212:udf_load_partition: Using anchor in block 256 UDF-fs DEBUG super.c:1441:udf_read_super: Lastblock=0 UDF-fs DEBUG super.c:722:udf_find_fileset: Fileset at block=32, partition=0 UDF-fs DEBUG super.c:783:udf_load_fileset: Rootdir at block=64, partition=0 UDF-fs INFO UDF 0.9.6 (2002/03/14) Mounting volume 'LinuxUDF', timestamp 2002/11/04 22:54 (1e20) NR