Message: 4 Date: Sun, 16 Feb 2014 14:29:16 -0500 From: allison <ajp166@verizon.net> To: cctech@classiccmp.org Subject: Re: CPM3.SYS weirdness? Message-ID: <5301118C.2090508@verizon.net> Content-Type: text/plain; charset=ISO-8859-1 On 02/15/2014 12:41 PM, Chuck Guzis wrote:
> On 02/15/2014 07:21 AM, Alexis Kotlowy wrote:
>> Hello list,
>>
>> I'm attempting to bring up CP/M Plus on one of my Z80 computers by
>> running CPMLDR.COM from CP/M 2.2. It crashes immediately after
>> CPMLDR.COM jumps to CPM3.SYS (I'm sure this isn't surprising). I'm
>> looking at the memory dumps and comparing them to the original file. It
>> appears for every 128 byte block, the order is backwards. I.e. if I look
>> at five 128 byte blocks on my PC they appear in the Z80's memory to be
>> as 5, 4, 3, 2 and 1. Not the 'correct' way.
>
> Back in the day of MP/M and CP/M plus, I found it useful to get a
> basic BIOS running on CP/M 2 first.  Have you done this, using your
> own de-blocking code?
>
> --Chuck
>
The BIOS is the critical element and best done with V2.2 first then the
V3stuff added...


Allison


>
>








Message: 10
Date: Mon, 17 Feb 2014 08:49:36 +1030
From: Alexis Kotlowy <thrashbarg@kaput.homeunix.org>
To: General Discussion: On-Topic and Off-Topic Posts
	<cctalk@classiccmp.org>
Subject: Re: CPM3.SYS weirdness?
Message-ID: <53013978.5080103@kaput.homeunix.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 16/02/2014 4:11 AM, Chuck Guzis wrote:
> Back in the day of MP/M and CP/M plus, I found it useful to get a basic
> BIOS running on CP/M 2 first.  Have you done this, using your own
> de-blocking code?
>
> --Chuck
>
>

I have CP/M 2.2 running already, using the example de-blocking code 
provided by DR. I'm trying to boot CP/M Plus from CP/M 2.2 so I'm using 
the existing file system from 2.2 to read CPM3.SYS, and the existing 
functions from the 2.2 BIOS in CP/M Plus.

I wrote a simple physical sector explorer to see what was being written 
to the hard disk, which is an old 80MB ATA drive. Everything is written 
in order, so I'm not sure what's going on.

If there is a problem it's with my LDRBIOS.ASM file. I'll keep at it.

Alexis.