Custom Query (69 matches)
Results (16 - 18 of 69)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#59 | fixed | SVN rev 298: files without a time/date stamp (all zeros) | ||
Description |
I have files on a FAT32 drive (USB stick) that seemingly have no file time/date stamp. In the WPS they show up with a date of 00.00.1980 and a time of 00.00.00 (in other words: all time and date fields set to zero), in a commandline directory listing it looks like this: [L:\]dir Volume in drive L has no label. The Volume Serial Number is 862F:23B7. Directory of L:\ 935.244 223 a--- alcor.zip 17.03.05 21.09 144.085 358 a--- df_ret.exe 11.08.05 11.52 544.188 224 a--- kernel.$$$ 17.03.05 21.09 59.366 224 a--- kernel.sdf 11.08.05 11.52 545.512 225 a--- kerneld.$$$ 17.03.05 21.09 59.617 225 a--- kerneld.sdf 28.12.16 10.28 9.476 223 a--- mouse.sym 28.12.16 10.28 32.560 357 a--- mouse.sys 8.03.02 17.59 189.354 223 a--- shell.$$$ 8.03.02 17.59 21.279 223 a--- shell.sdf 7.01.17 9.36 28.409.056 222 a--- usb.pcap 7.01.17 9.36 76.931 222 a--- VBox.log 889.307 221 a--- usb.zip 29.07.17 9.33 20 128 ---- CHKDSK.OLD 29.07.17 9.33 20 128 ---- CHKDSK.LOG 15 file(s) 31.916.015 bytes used 15.774.121 K bytes free look at files "alcor.zip" and "usb.zip": they are lacking a file date/time ... |
|||
#58 | fixed | SVN rev 298: recovered EA files are creating files with drive letter prepended (invalid filename) | ||
Description |
using version SVN rev 298: a chkdsk on a FAT32 formatted USB stick found orphaned EA references and recreated EA files. However, these files where created with names with the drive letter prepended such as: G:\USBCOM.SYS.EA G:\USBEHCD.SYS.EA (where g: is the current drive letter of the USB stick). Consequently, these files cannot be opened, deleted or used otherwise. This is also true from a commandline. |
|||
#57 | fixed | Fatal error in reading USB key | ||
Description |
Actually I use ARCAOS 5.0 that come installed without any problem and so I have upgraded installed version of fat32 with the new:fat32-0.10-r293-os2.wpi, for testing. using:
I thought that this error is due to the new widget RemMedia?.dll and uninstall it, but the problem remain, this USB device is not recognized and the system hung. Using the official version fat32_0913.wpi I can read and write on this USB key. |