Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.os.development > #18677 > unrolled thread

z/PDOS-generic

Started by"Paul Edwards" <mutazilah@gmail.com>
First post2024-07-18 23:07 +0800
Last post2025-03-10 14:46 +0000
Articles 8 on this page of 88 — 13 participants

Back to article view | Back to alt.os.development


Contents

  z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-07-18 23:07 +0800
    Re: z/PDOS-generic Grant Taylor <gtaylor@tnetconsulting.net> - 2024-07-18 22:40 -0500
      Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-07-19 18:43 +0800
        Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2024-07-19 16:18 +0000
          Re: z/PDOS-generic BGB-Alt <bohannonindustriesllc@gmail.com> - 2024-07-19 17:12 -0500
            Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2024-07-19 23:21 +0000
              Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2024-07-19 23:31 +0000
              Re: z/PDOS-generic BGB <cr88192@gmail.com> - 2024-07-20 01:30 -0500
              Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2024-07-22 07:51 -0700
                Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2024-07-22 15:22 +0000
                  Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2024-07-22 09:07 -0700
                    Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2024-07-22 17:37 +0000
                      Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2024-07-22 18:07 +0000
                        Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2024-07-22 19:38 +0000
                      Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2024-07-22 11:18 -0700
                Re: z/PDOS-generic BGB <cr88192@gmail.com> - 2024-07-22 14:16 -0500
                  Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2024-07-22 20:14 +0000
                    Re: z/PDOS-generic BGB <cr88192@gmail.com> - 2024-07-22 18:03 -0500
                      Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2024-07-22 23:58 +0000
                        Re: z/PDOS-generic BGB <cr88192@gmail.com> - 2024-07-22 23:06 -0500
                          Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-08-21 04:31 +0800
                            Re: z/PDOS-generic BGB <cr88192@gmail.com> - 2024-08-28 02:28 -0500
                              Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-08-28 16:54 +0800
                                Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-08-28 16:58 +0800
                                Re: z/PDOS-generic BGB <cr88192@gmail.com> - 2024-08-28 18:03 -0500
                                  Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-08-29 11:14 +0800
                                    Re: z/PDOS-generic George Neuner <gneuner2@comcast.net> - 2024-08-30 06:49 -0400
                                      Re: z/PDOS-generic George Neuner <gneuner2@comcast.net> - 2024-08-30 10:27 -0400
                                      Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-08-31 10:21 +0800
                                        Re: z/PDOS-generic George Neuner <gneuner2@comcast.net> - 2024-08-31 15:30 -0400
                                      Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2024-09-03 14:27 +0000
                                  Re: z/PDOS-generic wolfgang kern <nowhere@never.at> - 2024-08-30 13:29 +0200
            Re: z/PDOS-generic Waldek Hebisch <antispam@fricas.org> - 2024-09-03 23:38 +0000
              Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-09-06 07:46 +0800
                Re: z/PDOS-generic J. Curtis <unknown@protocol.invalid> - 2024-09-06 20:08 +0100
                  Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-09-07 08:12 +0800
                    Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-01-22 17:34 +1100
          Re: z/PDOS-generic J. Curtis <unknown@protocol.invalid> - 2024-07-20 00:02 +0100
          Re: z/PDOS-generic Salvador Mirzo <smirzo@example.com> - 2025-03-08 14:42 -0300
            Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-09 02:09 +0000
              Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2025-03-09 15:40 +0000
                Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-10 12:38 +0000
                  Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2025-03-10 14:49 +0000
                    Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-10 15:00 +0000
              Re: z/PDOS-generic Salvador Mirzo <smirzo@example.com> - 2025-03-10 09:21 -0300
                Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-10 13:50 +0000
                  Re: z/PDOS-generic Salvador Mirzo <smirzo@example.com> - 2025-03-10 14:10 -0300
                    Studying the system (was Re: z/PDOS-generic) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-10 18:29 +0000
                    Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-11 05:38 +1100
                      Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2025-03-10 19:07 +0000
                        Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-10 19:09 +0000
                        Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2025-03-10 13:00 -0700
                          Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-10 20:20 +0000
                            Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-11 07:59 +1100
                            Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2025-03-10 15:11 -0700
                              Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-10 23:11 +0000
                                Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-11 10:51 +1100
                                Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2025-03-11 08:37 -0700
                                  Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-11 17:28 +0000
                                    Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-12 05:40 +1100
                                    Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2025-03-11 12:41 -0700
                                      What is an operating system? (was Re: z/PDOS-generic) cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-11 21:00 +0000
                                        Re: What is an operating system? (was Re: z/PDOS-generic) "Paul Edwards" <mutazilah@gmail.com> - 2025-03-12 17:30 +1100
                                Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2025-03-11 09:04 -0700
                        Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-11 08:29 +1100
              Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-11 05:06 +1100
                Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2025-03-10 19:01 +0000
                  Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-11 08:04 +1100
                  Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-11 08:47 +1100
              Re: z/PDOS-generic antispam@fricas.org (Waldek Hebisch) - 2025-03-11 18:15 +0000
                Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-11 18:29 +0000
                  Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-12 05:52 +1100
                  Re: z/PDOS-generic antispam@fricas.org (Waldek Hebisch) - 2025-03-11 23:05 +0000
                    Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-11 23:48 +0000
                      Re: z/PDOS-generic antispam@fricas.org (Waldek Hebisch) - 2025-03-12 02:23 +0000
                        Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-12 02:34 +0000
                          Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2025-03-12 18:41 +1100
        Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2024-07-19 09:35 -0700
          Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-08-21 04:20 +0800
            Re: z/PDOS-generic John Ames <commodorejohn@gmail.com> - 2024-08-21 09:51 -0700
              Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-08-22 13:24 +0800
        Re: z/PDOS-generic Grant Taylor <gtaylor@tnetconsulting.net> - 2024-07-19 19:46 -0500
          Re: z/PDOS-generic "Paul Edwards" <mutazilah@gmail.com> - 2024-08-21 04:18 +0800
      Re: z/PDOS-generic Salvador Mirzo <smirzo@example.com> - 2025-03-08 14:41 -0300
        Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-09 01:58 +0000
          Re: z/PDOS-generic Salvador Mirzo <smirzo@example.com> - 2025-03-10 09:31 -0300
            Re: z/PDOS-generic cross@spitfire.i.gajendra.net (Dan Cross) - 2025-03-10 14:28 +0000
            Re: z/PDOS-generic scott@slp53.sl.home (Scott Lurndal) - 2025-03-10 14:46 +0000

Page 5 of 5 — ← Prev page 1 2 3 4 [5]


#18709

From"Paul Edwards" <mutazilah@gmail.com>
Date2024-08-22 13:24 +0800
Message-ID<va6i1r$9tvo$1@dont-email.me>
In reply to#18708
"John Ames" <commodorejohn@gmail.com> wrote in message
news:20240821095101.00005887@gmail.com...

> So, to summarize: all you need in order to accomplish this is

This is a very complicated new system. That is not my goal.
My goal is a simple starter system. z/PDOS-generic is an
example of a simple starter system.

> 1. a DOS-
> based hypervisor which almost certainly doesn't exist, 2. a 64-bit DPMI
> extender which probably doesn't,

Note that I have 32-bit MSDOS which is accomplished by
switching from PM32 to RM16 in order to make BIOS calls.
This works on an AMD64-like processor if someone has
made a BIOS availlable. I actually bought a Lenovo Kaitian
with a Zhaoxin processor in order to get this. The BIOS is
literally in Chinese and I needed help from a friend in order
to know how to switch between UEFI and legacy BIOS.

Also note that I have a thin wrapper on top of UEFI that switches
a UEFI system into a mini Windows 64-bit clone. That is also
MSDOS-like.

And at this level you need to define wihat "MSDOS" actually means.

BFN. Paul.

[toc] | [prev] | [next] | [standalone]


#18686

FromGrant Taylor <gtaylor@tnetconsulting.net>
Date2024-07-19 19:46 -0500
Message-ID<v7f1cb$3b5$1@tncsrv09.home.tnetconsulting.net>
In reply to#18679
On 7/19/24 05:43, Paul Edwards wrote:
> Sure - but why not make it available anyway? What's the barrier 
> to someone doing that? No-one is interested? Too much work?

I believe you answered your own question.

> It didn't need to be Microsoft personally.

Assuming the MS in MS-DOS stands for Microsoft, yes, it does need to be 
Microsoft.

If you just want DOS on a mainframe, IBM did that.

Link - DOS/360 and successors - Wikipedia
  - https://en.wikipedia.org/wiki/DOS/360_and_successors



-- 
Grant. . . .

[toc] | [prev] | [next] | [standalone]


#18702

From"Paul Edwards" <mutazilah@gmail.com>
Date2024-08-21 04:18 +0800
Message-ID<va2tm6$3gq54$1@dont-email.me>
In reply to#18686
"Grant Taylor" <gtaylor@tnetconsulting.net> wrote in message
news:v7f1cb$3b5$1@tncsrv09.home.tnetconsulting.net...
> On 7/19/24 05:43, Paul Edwards wrote:
> > Sure - but why not make it available anyway? What's the barrier
> > to someone doing that? No-one is interested? Too much work?
>
> I believe you answered your own question.
>
> > It didn't need to be Microsoft personally.
>
> Assuming the MS in MS-DOS stands for Microsoft, yes, it does need to be
> Microsoft.
>
> If you just want DOS on a mainframe, IBM did that.
>
> Link - DOS/360 and successors - Wikipedia
>   - https://en.wikipedia.org/wiki/DOS/360_and_successors

And that is really crappy compared to Microsoft's version. The
Microsoft version (or equivalent) could have been used for
debugging system problems, or experimenting on a DR site.

BFN. Paul.

[toc] | [prev] | [next] | [standalone]


#18752

FromSalvador Mirzo <smirzo@example.com>
Date2025-03-08 14:41 -0300
Message-ID<87tt83besr.fsf@example.com>
In reply to#18678
Grant Taylor <gtaylor@tnetconsulting.net> writes:

> On 7/18/24 10:07, Paul Edwards wrote:
>> For 35+ years I have wondered why there was no MSDOS for the mainframe.
>
> The answer is in the name.
>
> MS-DOS
>
> Microsoft DOS
>
> Micro
>
> micro-computers are the smallest end of the system with mainframes and
> supers at the other end of the system.
>
> IBM provided a Disk Operating System for early and / or smaller
> mainframes.

And why is /Disk/ Operating System?  What's so /disky/ about it?

[toc] | [prev] | [next] | [standalone]


#18755

Fromcross@spitfire.i.gajendra.net (Dan Cross)
Date2025-03-09 01:58 +0000
Message-ID<vqisk2$77u$2@reader1.panix.com>
In reply to#18752
In article <87tt83besr.fsf@example.com>,
Salvador Mirzo  <smirzo@example.com> wrote:
>Grant Taylor <gtaylor@tnetconsulting.net> writes:
>
>> On 7/18/24 10:07, Paul Edwards wrote:
>>> For 35+ years I have wondered why there was no MSDOS for the mainframe.
>>
>> The answer is in the name.
>>
>> MS-DOS
>>
>> Microsoft DOS
>>
>> Micro
>>
>> micro-computers are the smallest end of the system with mainframes and
>> supers at the other end of the system.
>>
>> IBM provided a Disk Operating System for early and / or smaller
>> mainframes.
>
>And why is /Disk/ Operating System?  What's so /disky/ about it?

Simple: it drove a system with a disk.  Most early mainframes
didn't have disks, so once they came along, system software had
to evolve to meet the needs of new hardware.

IBM's DOS/360 was pretty anemic compared to it's flagship OS360.
But it was built as something of a stopgap because OS was behind
schedule.

	- Dan C.

[toc] | [prev] | [next] | [standalone]


#18759

FromSalvador Mirzo <smirzo@example.com>
Date2025-03-10 09:31 -0300
Message-ID<878qpd130b.fsf@example.com>
In reply to#18755
cross@spitfire.i.gajendra.net (Dan Cross) writes:

> In article <87tt83besr.fsf@example.com>,
> Salvador Mirzo  <smirzo@example.com> wrote:
>>Grant Taylor <gtaylor@tnetconsulting.net> writes:
>>
>>> On 7/18/24 10:07, Paul Edwards wrote:
>>>> For 35+ years I have wondered why there was no MSDOS for the mainframe.
>>>
>>> The answer is in the name.
>>>
>>> MS-DOS
>>>
>>> Microsoft DOS
>>>
>>> Micro
>>>
>>> micro-computers are the smallest end of the system with mainframes and
>>> supers at the other end of the system.
>>>
>>> IBM provided a Disk Operating System for early and / or smaller
>>> mainframes.
>>
>>And why is /Disk/ Operating System?  What's so /disky/ about it?
>
> Simple: it drove a system with a disk.  Most early mainframes
> didn't have disks, so once they came along, system software had
> to evolve to meet the needs of new hardware.
>
> IBM's DOS/360 was pretty anemic compared to it's flagship OS360.
> But it was built as something of a stopgap because OS was behind
> schedule.

Thanks!  Changing the subject a bit to the history of DOS, if that's
okay.  I was not quite aware that there was a mainframe DOS in the IBM
world.  So it seems to me tbat Microsoft found the DOS made by ``Seattle
Computer Products'' the right choice to buy because they wanted to
produce a system for IBM micro-computers---it makes sense in sort of
keeping the same user interface.  But this strategy assumes that the
users of micro-computers would be the more or less the same users as IBM
mainframes.  Am I imagining things correctly here and did the strategy
really make sense?  (It could also be the case that Microsoft just
didn't have any other option.)  (Background: I've watched the film
``Pirates of Sillicon Valley'' a long time ago.  That's how much I know
about the history of MS-DOS.)

[toc] | [prev] | [next] | [standalone]


#18762

Fromcross@spitfire.i.gajendra.net (Dan Cross)
Date2025-03-10 14:28 +0000
Message-ID<vqmsuc$abj$1@reader1.panix.com>
In reply to#18759
In article <878qpd130b.fsf@example.com>,
Salvador Mirzo  <smirzo@example.com> wrote:
>cross@spitfire.i.gajendra.net (Dan Cross) writes:
>> In article <87tt83besr.fsf@example.com>,
>> Salvador Mirzo  <smirzo@example.com> wrote:
>>>Grant Taylor <gtaylor@tnetconsulting.net> writes:
>>>
>>>> On 7/18/24 10:07, Paul Edwards wrote:
>>>>> For 35+ years I have wondered why there was no MSDOS for the mainframe.
>>>>
>>>> The answer is in the name.
>>>>
>>>> MS-DOS
>>>>
>>>> Microsoft DOS
>>>>
>>>> Micro
>>>>
>>>> micro-computers are the smallest end of the system with mainframes and
>>>> supers at the other end of the system.
>>>>
>>>> IBM provided a Disk Operating System for early and / or smaller
>>>> mainframes.
>>>
>>>And why is /Disk/ Operating System?  What's so /disky/ about it?
>>
>> Simple: it drove a system with a disk.  Most early mainframes
>> didn't have disks, so once they came along, system software had
>> to evolve to meet the needs of new hardware.
>>
>> IBM's DOS/360 was pretty anemic compared to it's flagship OS360.
>> But it was built as something of a stopgap because OS was behind
>> schedule.
>
>Thanks!  Changing the subject a bit to the history of DOS, if that's
>okay.

Yes, of course.

>I was not quite aware that there was a mainframe DOS in the IBM
>world.  So it seems to me tbat Microsoft found the DOS made by ``Seattle
>Computer Products'' the right choice to buy because they wanted to
>produce a system for IBM micro-computers---it makes sense in sort of
>keeping the same user interface.  But this strategy assumes that the
>users of micro-computers would be the more or less the same users as IBM
>mainframes.  Am I imagining things correctly here and did the strategy
>really make sense?  (It could also be the case that Microsoft just
>didn't have any other option.)  (Background: I've watched the film
>``Pirates of Sillicon Valley'' a long time ago.  That's how much I know
>about the history of MS-DOS.)

Well, I would urge some caution here; I don't think that DOS/360
had much resemblence, if any, to MS-DOS: it was a batch system
for very low-end mainframes in the IBM 360 line.  The name clash
is just a coincidence.  At the time, lots of manufacturers were
starting to introduce "DOS" systems, since disks were relatively
new and gaining favor for long-ish term secondary storage of
data (tape was still preferred for really long-term storage; in
lots of places, this was true even up until the 1990s and into
the early 2000s).  Before that, tape dominated, with occasional
use of drums for high-speed temporary storage that was nearly
random-access.  When PCs started to show up on the scene, and
started to ship with floppy disks, the name "DOS" was recycled.
Indeed, lots of early PCs had "DOS" operating systems, but these
are generally completely unrelated to one another; it was just a
common term for systems that were disk-oriented.

The MS-DOS interface, inherited from QDOS, which mimmicked that
of CP/M, has much more in common with DEC operating systems than
anything in the IBM mainframe world.  The interface of IBM's
time sharing systems, like VM/CMS (now z/VM) has more in common
with Multics, or CTSS (which was the predecessor of both), than,
say, TOPS-10 or TENEX or DOS/8.  It may be worth clarifying that
these things didn't usually spring forth from a bubble; a lot of
the peole who were building these things in their garages and
who started the early PC companies had some experience with
mainframe and minicomputer systems; they naturally drew some
influence from those when they started putting together the UIs
for their machines.

IBM's larger machines (what we usually associate with
"mainframes") had come out of a world that was bifurcated
between scientific and business computing; systems like the 1401
were targeted towards business, which needed high throughput,
but performed relatively simple (usually decimal or integer)
calculations.  Systems like the 7094 were targeted towards
scientific computing, which needed fast floating point for
complex calculations, but relatively low throughput.  To
illustrate, consider charging compound interest on a bank's
portfolio of mortgage loans at the beginning of each month,
versus calculating the trajectory of a rocket.  The rules for
the former may be complex, but the math is pretty simple ("take
this number, add 10 percent to it, and store it somewhere"); the
latter is helaciously complex ("evaluate this integral to
compute the area under this curve as time varies from a to b,
but mass decreases nonlinearly as a function of fuel consumption
and decreasing drag as we move out of the atmosphere...").  A
large bank might run their mortgage interest program over a
million or more loans, while NASA's only doing the trajectory
calculation for a single mission at a time; they may run it more
than once, of course, but probably not a million times.

The IBM 360 line was supposed to unify these two worls onto a
single ISA, hence "360" in the name, as in "a 360 degree view of
the world of computing."  The problem was that the software for
the 360 was famously delivered behind schedule, well after the
hardware, as recounted in Fred Brooks's masterful, "The Mythical
Man Month"; so IBM had 360 systems sitting on loading docks but
no software to go with them.  While OS/360 was still being
developed, they quickly put together stopgap operating systems
so that they could move their machines into customer hands.

DOS/360 was one of those, and it was small enough that it could
run on a 360/30 with something like 8 or 16KiB of RAM and a
disk.  They also shipped a TOS/360 ("tape operating system") for
systems without disks.  But it was a batch system, with no real
user interface that would be meaningful in the context of a PC
or interactive timesharing system.

IBM got into the PC market largely because they saw a business
opportunity, but it's not clear that they really believed in it;
the original IBM PC project, coming out of Florida, was run very
differently than projects in New York and is a reflect of that.

	- Dan C.

[toc] | [prev] | [next] | [standalone]


#18763

Fromscott@slp53.sl.home (Scott Lurndal)
Date2025-03-10 14:46 +0000
Message-ID<uXCzP.209127$zz8b.85444@fx09.iad>
In reply to#18759
Salvador Mirzo <smirzo@example.com> writes:
>cross@spitfire.i.gajendra.net (Dan Cross) writes:
>
>> In article <87tt83besr.fsf@example.com>,
>> Salvador Mirzo  <smirzo@example.com> wrote:
>>>Grant Taylor <gtaylor@tnetconsulting.net> writes:
>>>
>>>> On 7/18/24 10:07, Paul Edwards wrote:
>>>>> For 35+ years I have wondered why there was no MSDOS for the mainframe.
>>>>
>>>> The answer is in the name.
>>>>
>>>> MS-DOS
>>>>
>>>> Microsoft DOS
>>>>
>>>> Micro
>>>>
>>>> micro-computers are the smallest end of the system with mainframes and
>>>> supers at the other end of the system.
>>>>
>>>> IBM provided a Disk Operating System for early and / or smaller
>>>> mainframes.
>>>
>>>And why is /Disk/ Operating System?  What's so /disky/ about it?
>>
>> Simple: it drove a system with a disk.  Most early mainframes
>> didn't have disks, so once they came along, system software had
>> to evolve to meet the needs of new hardware.
>>
>> IBM's DOS/360 was pretty anemic compared to it's flagship OS360.
>> But it was built as something of a stopgap because OS was behind
>> schedule.
>
>Thanks!  Changing the subject a bit to the history of DOS, if that's
>okay.  I was not quite aware that there was a mainframe DOS in the IBM
>world.

There were several "Disk Operating Systems" available from various
computer manufacturers a decade before CP/M was developed and
microsoft introduced the PC DOS
operating system.   IBM, Burroughs, various others all had some form
of DOS.

>  So it seems to me tbat Microsoft found the DOS made by ``Seattle
>Computer Products'' the right choice to buy because they wanted to
>produce a system for IBM micro-computers---it makes sense in sort of
>keeping the same user interface.

https://en.wikipedia.org/wiki/Disk_operating_system
 
https://en.wikipedia.org/wiki/CP/M

[toc] | [prev] | [standalone]


Page 5 of 5 — ← Prev page 1 2 3 4 [5]

Back to top | Article view | alt.os.development


csiph-web