Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

PURGE COMPLETE.

devel / comp.os.cpm / Re: CP/M-68K and FAT File System

SubjectAuthor
* CP/M-68K and FAT File SystemTom Szolyga
+- Re: CP/M-68K and FAT File SystemDavid Schultz
`* Re: CP/M-68K and FAT File SystemBill Shen
 `- Re: CP/M-68K and FAT File SystemRandy McLaughlin

1
CP/M-68K and FAT File System

<4fedb097-ae47-46c8-9349-84d2809a1f8bn@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=3867&group=comp.os.cpm#3867

  copy link   Newsgroups: comp.os.cpm
X-Received: by 2002:a0c:ee91:0:b0:4b4:a0b0:2dd8 with SMTP id u17-20020a0cee91000000b004b4a0b02dd8mr72000381qvr.19.1671218668807;
Fri, 16 Dec 2022 11:24:28 -0800 (PST)
X-Received: by 2002:a0d:fdc7:0:b0:3bd:370d:aa42 with SMTP id
n190-20020a0dfdc7000000b003bd370daa42mr3084606ywf.497.1671218668624; Fri, 16
Dec 2022 11:24:28 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.os.cpm
Date: Fri, 16 Dec 2022 11:24:28 -0800 (PST)
Injection-Info: google-groups.googlegroups.com; posting-host=73.231.203.114; posting-account=ZLwvxQoAAABEySN3wi4kx4ECN1-MW5_g
NNTP-Posting-Host: 73.231.203.114
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <4fedb097-ae47-46c8-9349-84d2809a1f8bn@googlegroups.com>
Subject: CP/M-68K and FAT File System
From: tszol...@pacbell.net (Tom Szolyga)
Injection-Date: Fri, 16 Dec 2022 19:24:28 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2261
 by: Tom Szolyga - Fri, 16 Dec 2022 19:24 UTC

I am trying to run CP/M-68K on a ROSCO 68K SBC. The issue is the ROSCO ROM boot code only understands a FAT formatted disc and will only boot from a FAT disc. This ROSCO boot code loads a file called ROSCOBOOT.BIN into memory at 4000 hex and executes it. This app can load any .BIN file and execute it. CP/M-68K has it's own disc format that is not compatible with FAT. The question is how to boot CP/M-68K?
I have written an app that is loaded and executed by the ROSCO Boot app. It has the binary files for CCP, BDOS and BIOS inside the app. It relocates these files to high memory and executes them. CP/M-68K starts and runs until it tries to do a disc operation. It fails because the disc is FAT. This is close, but no cigar.
What is the disc was formatted with two partitions? The first partition would be FAT and rather small. The second partition would be the rest of the disc but not formatted. CP/M-68K would boot as above. All of the CP/M disc drives would be in the unformatted area. These virtual discs would be defined with a track offset that is the size of the FAT partition. in this way, the two file systems could co-exist and ignore each other.
Thoughts???

Re: CP/M-68K and FAT File System

<rqydnT5G9NoFQQH-nZ2dnZfqnPGdnZ2d@earthlink.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=3870&group=comp.os.cpm#3870

  copy link   Newsgroups: comp.os.cpm
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!69.80.99.27.MISMATCH!Xl.tags.giganews.com!local-2.nntp.ord.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 16 Dec 2022 21:01:12 +0000
Date: Fri, 16 Dec 2022 15:01:11 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1
Subject: Re: CP/M-68K and FAT File System
Newsgroups: comp.os.cpm
References: <4fedb097-ae47-46c8-9349-84d2809a1f8bn@googlegroups.com>
Content-Language: en-US
From: david.sc...@earthlink.net (David Schultz)
In-Reply-To: <4fedb097-ae47-46c8-9349-84d2809a1f8bn@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <rqydnT5G9NoFQQH-nZ2dnZfqnPGdnZ2d@earthlink.com>
Lines: 12
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 108.194.109.148
X-Trace: sv3-anCs0tdhKN9eAWA6DbABKqNnqCtS7ITyDFkGBQEuPKtHQe942Jpjs3EkYzfh24ZR5he3l39LM1faYC0!o49EXrcR4/AZjyVwa1V2by+KOhDoZCXbZTWdlU4PDKCcCTeTLwv26+opXY9j/ip0FOdKp1HRyoBv!YjkLq5FoslVByG5AkBrEgIp+QnT9Vxfi4ar/c6MNUvU=
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Received-Bytes: 2042
 by: David Schultz - Fri, 16 Dec 2022 21:01 UTC

On 12/16/22 1:24 PM, Tom Szolyga wrote:

> What is the disc was formatted with two partitions? The first partition would be FAT and rather small. The second partition would be the rest of the disc but not formatted. CP/M-68K would boot as above. All of the CP/M disc drives would be in the unformatted area. These virtual discs would be defined with a track offset that is the size of the FAT partition. in this way, the two file systems could co-exist and ignore each other.
> Thoughts???
Works for me. Except that I would use the loader version of CP/M-68K in
the FAT file system. Then changes to CPM.SYS could skip messing with
that again.

--
http://davesrocketworks.com
David Schultz

Re: CP/M-68K and FAT File System

<53287b2a-b5fc-4ae2-8b57-c802f3068da1n@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=3873&group=comp.os.cpm#3873

  copy link   Newsgroups: comp.os.cpm
X-Received: by 2002:a37:bac5:0:b0:6fa:f354:939f with SMTP id k188-20020a37bac5000000b006faf354939fmr84633434qkf.57.1671282602263;
Sat, 17 Dec 2022 05:10:02 -0800 (PST)
X-Received: by 2002:a25:7756:0:b0:700:334c:2697 with SMTP id
s83-20020a257756000000b00700334c2697mr20506952ybc.40.1671282602107; Sat, 17
Dec 2022 05:10:02 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.os.cpm
Date: Sat, 17 Dec 2022 05:10:01 -0800 (PST)
In-Reply-To: <4fedb097-ae47-46c8-9349-84d2809a1f8bn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:8c0:d80:2f30:91ce:4559:b455:df0d;
posting-account=4LqnLwoAAABkEeOjPXhyBor34oPMgh8H
NNTP-Posting-Host: 2601:8c0:d80:2f30:91ce:4559:b455:df0d
References: <4fedb097-ae47-46c8-9349-84d2809a1f8bn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <53287b2a-b5fc-4ae2-8b57-c802f3068da1n@googlegroups.com>
Subject: Re: CP/M-68K and FAT File System
From: coinstro...@gmail.com (Bill Shen)
Injection-Date: Sat, 17 Dec 2022 13:10:02 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 1997
 by: Bill Shen - Sat, 17 Dec 2022 13:10 UTC

On Friday, December 16, 2022 at 12:24:29 PM UTC-7, tszo....net wrote:
> What is the disc was formatted with two partitions? The first partition would be FAT and rather small. The second partition would be the rest of the disc but not formatted. CP/M-68K would boot as above. All of the CP/M disc drives would be in the unformatted area. These virtual discs would be defined with a track offset that is the size of the FAT partition. in this way, the two file systems could co-exist and ignore each other.

Yes, use the offset to skip over non-CPM disk area is the easiest way. My own implmentation has system programs/utilities in the non-CPM disk area. They are directly accessible as long as the LBA addresses and program length are known.
Bill

Re: CP/M-68K and FAT File System

<b52b392f-0658-49cb-ba32-6e7aeb00126dn@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=3874&group=comp.os.cpm#3874

  copy link   Newsgroups: comp.os.cpm
X-Received: by 2002:a05:620a:1905:b0:6fa:6636:a7b0 with SMTP id bj5-20020a05620a190500b006fa6636a7b0mr67001192qkb.55.1671295264884;
Sat, 17 Dec 2022 08:41:04 -0800 (PST)
X-Received: by 2002:a25:f205:0:b0:6dd:9027:5825 with SMTP id
i5-20020a25f205000000b006dd90275825mr79880016ybe.155.1671295264607; Sat, 17
Dec 2022 08:41:04 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.os.cpm
Date: Sat, 17 Dec 2022 08:41:04 -0800 (PST)
In-Reply-To: <53287b2a-b5fc-4ae2-8b57-c802f3068da1n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.64.86.134; posting-account=PFWPPwoAAACyqfximQYdiAnvYtofle1M
NNTP-Posting-Host: 75.64.86.134
References: <4fedb097-ae47-46c8-9349-84d2809a1f8bn@googlegroups.com> <53287b2a-b5fc-4ae2-8b57-c802f3068da1n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b52b392f-0658-49cb-ba32-6e7aeb00126dn@googlegroups.com>
Subject: Re: CP/M-68K and FAT File System
From: randy...@hotmail.com (Randy McLaughlin)
Injection-Date: Sat, 17 Dec 2022 16:41:04 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1416
 by: Randy McLaughlin - Sat, 17 Dec 2022 16:41 UTC

Quick and dirty do the above using an offset.

Right answer put the cpm loader in small fat directory and have the BIOS read the MBR and have CPM partitions for the CPM drives.

It is much easier to use a fixed offset.

Randy

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor