[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [N8VEM: 2353] Re: Building a common CP/M source file
- To: N8VEM-Post <n8...@googlegroups.com>
- Subject: Re: [N8VEM: 2353] Re: Building a common CP/M source file
- From: "Richard A. Cini" <rc...@optonline.net>
- Date: Mon, 02 Feb 2009 22:36:13 -0500
- Authentication-results: mx.google.com; spf=neutral (google.com: 167.206.4.196 is neither permitted nor denied by best guess record for domain of rc...@optonline.net) smtp.mail=rc...@optonline.net
- In-reply-to: <49866FFF.8060700@nj7p.org>
- Thread-index: AcmFsI/LzowskPGjEd2cYQAWy6f/wQ==
- Thread-topic: [N8VEM: 2353] Re: Building a common CP/M source file
- User-agent: Microsoft-Entourage/11.4.0.080122
On 2/1/09 11:01 PM, "Bill Beech (NJ7P)" <nj...@nj7p.org> wrote:
>
> Richard,
>
> I agree with everything but the F drive. I plan on having a BIOS that
> will allow the B drive to be on any size ROM from 32K to 1024K and
> dynamically adjust to it when it selects the drive the first time. The
> DPB defining the drive is in the actual ROM image. Having a separate F
> drive wastes space in the ROM, duplicating the directory spaces, etc.
>
> Bill
Ok. I can appreciate the implicit cost of supporting another drive letter,
so I see your point. I guess what I'm looking for is a larger ROM drive so I
can stuff it with a "full" CP/M distribution and a bunch of common
utilities. If that means a larger "B", I'm cool with that.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.altair32.com
http://www.classiccmp.org/cini