82 lines
2.3 KiB
Plaintext
82 lines
2.3 KiB
Plaintext
![]() |
|
||
|
[R] C:\CBBS>
|
||
|
[R] C:\CBBS>type next
|
||
|
44845
|
||
|
xxxxx
|
||
|
364
|
||
|
400
|
||
|
20553
|
||
|
222015
|
||
|
[*,PIRATE,]/8
|
||
|
[BB*,*,]/8
|
||
|
[CC*,*,]/8
|
||
|
[DD*,*,]/8
|
||
|
[EE*,*,]/8
|
||
|
[FF*,*,]/8
|
||
|
[GEORGES,BROW*,]/9
|
||
|
[GG*,*,]^C
|
||
|
|
||
|
[R] C:\CBBS>exit
|
||
|
|
||
|
[R] C:\CBBS>
|
||
|
[R] C:\CBBS>
|
||
|
CBBS(R) 4.0.3b
|
||
|
06/08/91 22:48:32
|
||
|
|
||
|
Y/N: want CBBS "1st time user" info?n
|
||
|
What is your FIRST name?CBBS(R) 4.0.3b
|
||
|
06/09/91 22:00:43
|
||
|
|
||
|
Y/N: want CBBS "1st time user" info?^U
|
||
|
?^U
|
||
|
?^U
|
||
|
?n;ward;christensen;odraw;;fullc;piss
|
||
|
|
||
|
Logging name to disk...
|
||
|
You are caller 222022; next msg =44845; 363 active msgs.
|
||
|
Prev. call 06/08/91 @ 22:42, next msg was 44845
|
||
|
Recording logon for next time...
|
||
|
Use FULL? to check assignments
|
||
|
?^U
|
||
|
?xxxxx
|
||
|
"Mine" command checking for msgs TO you, ^
|
||
|
>Function:?dir c:log;dir c:killed;dir summary;type-20 log,ward c;or;*;short
|
||
|
LOG. 9
|
||
|
KILLED. 10
|
||
|
SUMMARY. 23
|
||
|
06/08/91,22:42:27,222014,2,WARD CHRISTENSEN,,
|
||
|
06/08/91,22:49:15,222015,X,WARD CHRISTENSEN,,1
|
||
|
]Looks like you found a bug! Somehow, a file was created that has an EOF
|
||
|
character in the last byte of the sector - not sure, perhaps it went to the
|
||
|
next sector, ... Heck, I have no idea. But I think the fact that there's
|
||
|
a 1a in byte 128 indicates a possible problem. Hmmm..
|
||
|
WARD CHRISTENSEN,
|
||
|
]S,MESSAGE.BAK,
|
||
|
]R,MESSAGE.X42,11
|
||
|
]Oh, OK, this was the known 'extent bug' in the CP/M emulator. Somehow
|
||
|
the file gets over 16K, and WHAM, the emulator grabs big blocks of memory
|
||
|
and writes 'em to the end of the file. I dl'd it, cleaned it up, and sent
|
||
|
it back - the next time we roll around to xxx42 and xxx43 we should be OK.
|
||
|
WARD CHRISTENSEN,
|
||
|
]R,MESSAGE.X42,15
|
||
|
]__AHA! Since the extent bug was at fault, that meant your msg was THERE
|
||
|
just in the wrong place (e.g. after some EOF chars, @ the end of the file
|
||
|
after more garbage). SO I resurrected both messages with an editor,
|
||
|
and then deleted the 2nd (as a dup of the first).
|
||
|
__Sorry for the problems.
|
||
|
WARD CHRISTENSEN,
|
||
|
06/09/91,02:45:14,222016,9,DENNIS LEONG,,3
|
||
|
06/09/91,03:56:20,222017,2,HARVEY BURR,skokie/il,9
|
||
|
06/09/91,08:00:27,222018,1,PETER FLIEGEL,,0
|
||
|
06/09/91,18:06:07,222019,1,TOM KIMES,STREATOR/IL,4
|
||
|
06/09/91,18:41:43,222020,1,DAVID JOHNSON,,1
|
||
|
06/09/91,21:32:04,222021,2,ED FOSTER,,0
|
||
|
06/09/91,22:00:47,222022,2,WARD CHRISTENSEN,,
|
||
|
|
||
|
---- End of summary ----
|
||
|
No dup. chars.
|
||
|
>Function:?/
|
||
|
06/09/91 22:01:20
|
||
|
Connect time 1 minutes
|
||
|
|