- Code: Select all
14/04/2010 22:33 86,016 OTVERT2.MAP
14/04/2010 22:27 16,384 _XCLIENT.DB3
14/04/2010 22:27 1,536 _XSETUP.DB3
14/04/2010 22:27 16,384 XCLIENT.DB3
14/04/2010 22:27 2,562,048 _JOPA.DB3
14/04/2010 22:27 1,536 XSETUP.DB3
14/04/2010 22:27 52,224 _PMAN.DB3
14/04/2010 22:27 2,562,048 JOPA.DB3
14/04/2010 22:27 52,736 _SIGNUP.DB3
14/04/2010 22:27 52,224 PMAN.DB3
14/04/2010 22:27 52,224 _CMD.DB3
14/04/2010 22:27 52,736 SIGNUP.DB3
14/04/2010 22:27 52,224 CMD.DB3
14/04/2010 22:30 1,025,024 _CRID.DB3
14/04/2010 22:30 1,025,024 CRID.DB3
20/04/2010 19:45 98,308 CRID.DBF
01/01/1980 00:01 4,346 XCLIENT.DBF
28/12/2008 12:45 32,768 ROOT_DIR.CP0
01/01/1980 00:01 172,032 OTVERT.MAP
20/04/2010 19:44 532 XSETUP.DBF
01/01/1980 00:01 2,102,580 JOPA
01/01/1980 00:01 4,976 PMAN.DBF
01/01/1980 00:01 38,906 SIGNUP.DBF
20/04/2010 19:45 65,536 XSI1.DB
20/04/2010 19:45 442,145 MDSKVT
01/01/1980 00:01 2,116 CMD.DBF
As for deleting the DB3 files, I attempted this a few hours ago (using the command prompt of course), Windows claimed the file didn't exist (despite being in the dir output). I never checked to see if the volume was write protected but I'd assume that would give me a different error?
I never had the XTVFS drivers installed since I don't use 32-bit Windows (are there any plans to release an x64 version?, although I guess the driver signing stuff may pose an issue)
The drive is back in the box and I'm waiting for it to spin down. It's been in for about 5 minutes and hasn't spun down yet. Seems to be a lot of sporadic disk activity.