21 Apr
2000
21 Apr
'00
3:40 p.m.
On Fri, 21 Apr 2000, Tony Duell wrote:
Good thought, Tony. The command is STAT USR: and it will return two
lines of information. The first reflects the current user area, while
the second reflects user areas that contain files.
- don
I stuck the
disks I'm trying to recover data from in the B: drive and did a
DIR but they all come back with "NO FILE". Now of course this means
that the disks contain no files but I'm thinking there has to be something
wrong here.
This message is also telling you a couple of good (?) things. Firstly
that the drive/controller is managing to read valid sectors off the disk
(so the drive is working, the heads are clean enough to read something,
etc). Otherwise you'd be getting the well-known BDOS errors.
And secondly the directory makes some sense as a CP/M directory. At least
the system thinks it does, and it thinks its empty. So it's likely (not
certain ) that the disks are CP/M86 ones.
One quick question. Have you tried using the USER command to look at
other users files on the disk? The user facilty of CP/M is pretty
useless, actually and mainly serves to cause problems like this. At
boot-up you're likely to be user 0, but you can change this to a number
between 0 and 15 IIRC.
I think one option to the STAT command (STAT USERS, STAT [USERS] ???)
will tell you at least which user numbers have files on the disk -tony