home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.whtech.com
/
ftp.whtech.com.tar
/
ftp.whtech.com
/
compuserve
/
P-Code
/
P-SYS1.INF
< prev
next >
Wrap
Text File
|
2006-10-19
|
1KB
|
35 lines
RA
#: 60182 S0
29-Oct-85 20:55:40
Sb: #60131-#P-CODE IN DL3
Fm: Bob Peterson 76703,532
To: Paul Charlton 75136,2256 (X)
Paul,
Once the p-System directory is valid, ie, tephost.code shows up, try
transferring that file to another volume. If it transfers correctly, you've
got your good (writable) disk.
The other way to build the correct directory entry is, after running RECOVER,
get into Filer and do an E(xtended directory listing and note both the starting
block and number of blocks. Again Z(ero the volume.
If the starting block of TEPHOST.CODE wasn't block 6, M(ake a file that fills
the gap (type M, then FILLER[?], where ? is the number of block needed to fill
between block 6 and the first block of TEPHOST.CODE.
Now M(ake again using TEPHOST.CODE[??] where ?? is the size of the .CODE
file. You should end up with a 100% valid p-System disk.
For example, assume after RECOVER that TEPHOST.CODE shows up in an E(xtended
directory listing as
TEPHOST.CODE 20 29-Oct-85 10 512 Codefile
"20" is the size of the .CODE file, "10" is the beginning block of the .CODE
file.
Z(ero the volume
M(ake FILLER[4] (fill block 6, 7, 8, & 9)
M(ake TEPHOST.CODE[20]
* Reply:
60201
(UA RE T) (D=delete):