Groups | Search | Server Info | Login | Register
Groups > comp.sys.unisys > #2558
| From | Stephen Boyd <sboydlns@gmail.com> |
|---|---|
| Newsgroups | comp.sys.unisys |
| Subject | Re: OS2200 MFD question |
| Date | 2025-01-12 10:22 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <06147a0a-8adf-470f-8bd2-7a295db170bc@gmail.com> (permalink) |
| References | <vltv8e$ld0n$1@dont-email.me> <15bf6012a0c40cd4d60fe63663fced61@www.novabbs.com> |
On 2025-01-11 3:06 p.m., lewiscole wrote: > Setting aside the issue of whether or not you are legally allowed to > look at the internals of the disk file image (I thought disassembly was > one of the things forbidden in the license), Not sure how this differs from using IOW$ to explore the file system from within OS2200 itself. The same info is being looked at one way or another. This way is just easier since I don't have to mess with MASM. Also, like I said, this is strictly an academic exercise. It's not like I'm trying to reverse engineer Exec. That would be a career not a hobby and I'm way too old for that. > Unfortunately, Univac/Sperry Univac/Sperry/Unisys (USUSU) has had a long > standing habit of making such old manuals disappear and so I suspect > that it will be virtually impossible for you to find such a manual. > Very true. I have an old version of the Data Structures manual and there is a lot of stuff in there that isn't in the new one. There are problems with even the old manual though. First, it assumes a level of knowledge of Exec internals that I simply don't have. Second, it is out of date. The structures described in the manual don't always match the latest version. Third, it is just plain vague in places. Which was always a problem with Univac docs, 1100 or otherwise. I even tried looking at the source for an old version of the MFD processor. But, like the manual, it is out of date and some of the code simply doesn't match the modern reality. -- This email has been checked for viruses by AVG antivirus software. www.avg.com
Back to comp.sys.unisys | Previous | Next — Previous in thread | Next in thread | Find similar
OS2200 MFD question Stephen Boyd <sboydlns@gmail.com> - 2025-01-11 09:29 -0500
Re: OS2200 MFD question l_cole@juno.com (lewiscole) - 2025-01-11 20:06 +0000
Re: OS2200 MFD question Stephen Boyd <sboydlns@gmail.com> - 2025-01-12 10:22 -0500
Re: OS2200 MFD question l_cole@juno.com (lewiscole) - 2025-01-12 18:49 +0000
Re: OS2200 MFD question R Daneel Olivaw <Danny@hyperspace.vogon.gov> - 2025-01-13 08:41 +0100
Re: OS2200 MFD question Stephen Boyd <sboydlns@gmail.com> - 2025-01-13 10:02 -0500
Re: OS2200 MFD question l_cole@juno.com (lewiscole) - 2025-01-15 02:04 +0000
Re: OS2200 MFD question David W Schroth <davidschroth@harrietmanor.com> - 2025-01-31 22:34 -0600
Re: OS2200 MFD question l_cole@juno.com (lewiscole) - 2025-02-02 20:50 +0000
Re: OS2200 MFD question David W Schroth <davidschroth@harrietmanor.com> - 2025-02-02 20:23 -0600
Re: OS2200 MFD question David W Schroth <davidschroth@harrietmanor.com> - 2025-01-31 22:30 -0600
Re: OS2200 MFD question Stephen Boyd <sboydlns@gmail.com> - 2025-02-01 10:21 -0500
csiph-web