× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Okay, I've got my analysis program started climbing around the offsets for
a SAV *SAVF, and I found the directory path, and the filename, poking
around with QuestView. But a couple of interesting things showed up:
1. When I found the LNK structure, it had a nonzero "Offset to next LNK
structure," but there was no other LNK to be found, and
2. When I found the filename, everything but the first character turned
out to indeed be straightforward UNICODEd ASCII, but the first character
of the name, which I had expected to be a capital "A" (ASCII 41 hex,
Unicode 0041 hex), turned ot to be 099D hex, which is some Bengali letter,
and the name length, which I expected to be either 12 characters or 24
bytes, turned out to be 988372765 (3AE95F1D hex).

Then, too, while this sample save file contains but a single *STMF saved
from the root directory, what should I expect to find when I look at one
that's more complex? I don't see anything about "Offset to next DIR."

--
JHHL



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.