Defining Disk Image Dump Standard

From: Richard Erlacher <richard_at_idcomm.com>
Date: Tue May 30 19:00:51 2000

Yes! So why's Sellam Ismail wanting to mix OS and data elements? He's
unhappy with the notion of putting only what you need on a diskette which
holds what you want to archive. What good does CP/M OS material do him if
he's using OS-8?

Dick

----- Original Message -----
From: allisonp <allisonp_at_world.std.com>
To: <classiccmp_at_classiccmp.org>
Sent: Tuesday, May 30, 2000 4:24 PM
Subject: Re: Defining Disk Image Dump Standard


> >> The way you separate the operating system from the executables is by
> never,
> >> Never, NEVER, mixing them on the same medium, particularly if it's
> intended
> >> for dissemination. If the platforms are disparate, you certainly don't
> need
> >
> >Ok, Mr. Wizard. Build a time machine, travel back in time, and urge all
> >the various computer manufacturers to never, NEVER mix their OS with the
> >rest of the program space on the disk. Fortunately, we are not trying to
> >revise the reality of our world, but are merely trying to deal with what
> >it has become, which is a much simpler procedure.
>
>
> Done! the OS was never mixed with data on CPM disks until CPM3 and
> CPM86.
>
> the system booted off OS specific tracks and DATA was never stored there
> and SYSTEM was never stored on DATA tracks. This applies to CP/M
> {1.3, 1.4, 2.0, 2.2} explicitly and many others as well.
>
> It makes little difference though. as then only reason is to make the
boot
> easier as the booter then doesn't have to know the file system to read
> and launch the system which for cpm wasn't defined until boot completed
> (as the system tables were part of the boot image).
>
> Allison
>
Received on Tue May 30 2000 - 19:00:51 BST

This archive was generated by hypermail 2.3.0 : Fri Oct 10 2014 - 23:33:10 BST