On 01/08/2017 10:03 AM, Chuck Guzis wrote:
I'm looking at a sample of what I see as a directory of sorts and am
attempting to decode the file names from it. They're not anything as
elegant as Rad50, but the encoding has escaped my weary brain.
Hmm, do you have any clues to go on? Knowledge of
On 01/08/2017 04:24 PM, Jules Richardson wrote:
> On 01/08/2017 10:03 AM, Chuck Guzis wrote:
>> I'm looking at a sample of what I see as a directory of sorts and
>> am attempting to decode the file names from it. They're not
>> anything as elegant as Rad50, but the encoding has escaped my weary
>>
Inverse 8085?
Bill Degnan
twitter: billdeg
vintagecomputer.net
On Jan 8, 2017 7:38 PM, "Chuck Guzis" wrote:
> On 01/08/2017 04:24 PM, Jules Richardson wrote:
> > On 01/08/2017 10:03 AM, Chuck Guzis wrote:
> >> I'm looking at a sample of what I see as a directory of sorts and
> >> am attempting t
On 01/08/2017 04:42 PM, william degnan wrote:
> Inverse 8085?
I don't think so. If it helps, here's the first few lines of the
"directory":
000: 00 a1 7a c1 c0 00 00
0007: 00 00 00 00 00 00 00 80 1a 02 38 00
0013: a1 7a c1 c0 00 00 00 00 1b ff 00 00
001f: 5c 25 15 1b 4c 40 00 00 ff ff 37 05
I don't know the names, but the use of extents might be something going on.
I highlighted the c4a3 extent. The last two columns maybe cylinder and
sector number.
There may be a free count going on with the next to the last two bytes
0xff85 for instance in the first stick.
Since line 0x000
Jim, that occurred to me right off the bat, but the disk has only 35
cylinders and is single-sided.
No file names in the body text. The text itself isn't proprietary, but
merely an early cut of an already-published public report, so I have no
problem sharing any part of the disk image.
--Chuck
On 01/08/2017 09:09 PM, Chuck Guzis wrote:
> On 01/08/2017 04:42 PM, william degnan wrote:
>> Inverse 8085?
> I don't think so. If it helps, here's the first few lines of the
> "directory":
>
> 000: 00 a1 7a c1 c0 00 00
> 0007: 00 00 00 00 00 00 00 80 1a 02 38 00
> 0013: a1 7a c1 c0 00 00 00 00
On 01/08/2017 06:25 PM, allison wrote:
> I haven't ground on what it may be but there are four likely
> directory/catalog cases.
I've certainly seen my share of various filesystems. In fact, I can
laboriously reconstruct the original files, there being only 70 1200
byte blocks on the disk. I
Chuck Guzis writes:
> I can get the raw text, but how it's linked together and what file
> names might is still a mystery.
The Lanier 103 is apparently a rebadged AES Superplus, and one owner
says:
"The word processor had some strange features, such as each page had to
be stored as a separate f
Need there BE a filename?
An OS, particularly for a word processor, could have an IMPLICIT list of
filenames on a disk of
DOCUMENT1
DOCUMENT2
DOCUMENT3
in which case, the table that you have found could be little more than
record keeping of which "documents" are allocated V free-space, how
m
The web search breadth increases a bit when the term "No Problem" is
substituted for "103" when looking for Lanier documents. Not much, but
there are some tidbits.
Such as:
" Its main drawback was that it was a page-oriented program as opposed
to a document-oriented program. You got only 99 line
On 01/09/2017 09:28 AM, Fred Cisin wrote:
> Need there BE a filename?
>
> An OS, particularly for a word processor, could have an IMPLICIT list
> of filenames on a disk of DOCUMENT1 DOCUMENT2 DOCUMENT3
I found this document:
http://www.dtic.mil/get-tr-doc/pdf?Location=U2&doc=GetTRDoc.pdf&AD=ADA
On 01/09/2017 11:51 AM, Chuck Guzis wrote:
On 01/09/2017 09:28 AM, Fred Cisin wrote:
Need there BE a filename?
An OS, particularly for a word processor, could have an IMPLICIT list
of filenames on a disk of DOCUMENT1 DOCUMENT2 DOCUMENT3
I found this document:
http://www.dtic.mil/get-tr-doc/
On 01/09/2017 03:33 PM, Jules Richardson wrote:
> It seems unlikely that a simple system would resort to something
> like frequency analysis of characters when encoding filenames,
> though, particularly given the size of the data (the overhead would
> probably not make it worthwhile) - so I'm gues
On 01/09/2017 12:51 PM, Chuck Guzis wrote:
> On 01/09/2017 09:28 AM, Fred Cisin wrote:
>> Need there BE a filename?
>>
>> An OS, particularly for a word processor, could have an IMPLICIT list
>> of filenames on a disk of DOCUMENT1 DOCUMENT2 DOCUMENT3
>
> I found this document:
>
> http://www.dtic.m
On 01/09/2017 02:58 PM, allison wrote:
> Low majik there... 8 bytes of 7 bit ascii means one free bytes
> worth of bits, to do that start with an 8byte area as 64 bits and
> stuff the bits. The only question is are the left justified or
> right a few minutes by hand can discover that. Done tha
16 matches
Mail list logo