<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Rich,<br>
<br>
Here is the format of the 64Mb SanDisk card:<br>
<br>
LILO version 22.7.3, Copyright (C) 1992-1998 Werner Almesberger<br>
Development beyond version 21 Copyright (C) 1999-2006 John Coffman<br>
Released 11-Aug-2006 and compiled at 20:26:28 on Aug 11 2006.<br>
<br>
vol-ID: 71698E5A<br>
<br>
Type Boot Start End Sector #sectors<br>
1 FAT16_lba 128:0:1 244:15:32
65536 59904<br>
2 WIN extended 32:0:1 127:15:32
16384 49152<br>
3 0x52 0:1:1 31:15:32
32 16352<br>
4 ** empty **<br>
5 0x52 32:1:1 63:15:32
32 16352<br>
6 0x52 64:1:1 95:15:32
32 16352<br>
7 0x52 96:1:1 127:15:32
32 16352<br>
<br>
<br>
Note that the FAT partition is first in the PT, but actually located
high on the card.<br>
The CP/M partition is #3 in the PT, and is located at the start of
the card, making the parameters for 'cpmtools' a little easier to
figure out. 'cpmtools' works in absolute sector addresses.<br>
<br>
I hope this helps.<br>
<br>
--John<br>
<br>
<br>
<br>
<br>
On 12/08/2014 07:47 AM, Richard Cini wrote:
<blockquote
cite="mid:6416E6A4-67AC-49ED-8E1F-***@verizon.net"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div>John --</div>
<div><br>
</div>
<div>Sorry, I should have been more precise. The PIC board with
the PPIDE card works fine and I can access the CF card subject
to the below. The BIOS identifies the card as:</div>
<div><br>
</div>
<div>C: CF CARD</div>
<div><br>
</div>
<div>The only way CP/M can access the card, however, is if the
first partition is of type 0x52 and set to primary. No
combination of multiple Windows (type 0x06) and CP/M partitions
seems to work. Right now I have a 32mb CP/M-only card and was
trying to partition a 128mb card into a 64mb windows partition
and two 32mb CP/M partitions. </div>
<div><br>
</div>
<div>Again I'm using a windows based partitioning tool. I may try
to wipe the card and start over. </div>
<div><br>
Sent from my iPhone</div>
<div><br>
On Dec 8, 2014, at 10:04 AM, John Coffman <<a
moz-do-not-send="true" href="mailto:***@gmail.com">***@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Rich,<br>
<br>
Can you read the card at all? I'm using BIOS version 0.9 of
22-Jan-2012.<br>
64Mb CF card on the PPIDE port of the MF/PIC board. Jumpers
(L to R, board vertical): on,on,off,on (0x40, top to bottom,
card on its side).<br>
In the BIOS setup, the base device of the PPIDE port is (44).
Boot devices, first and second, are C, A.<br>
<br>
The CF card has a DOS partition 1, and a CP/M-68 partition
0x52 as the second. There are 3 other 0x52 partitions in the
DOS extended partition, but extended partitions are not looked
at. The CP/M partition is 16Mb.<br>
<br>
The BIOS comes up with a directory listing of the DOS
partition. Hitting "C" boots CP/M-68 from ROM. Typing the
entire filename (8.3) will execute any of the 68000 programs
in the DOS partition, in either User or Supervisor mode (your
choice).<br>
<br>
Booting CP/M-68 from ROM, I have 149 files on the CF card. No
Xmodem, but there is an XFER86.68K binary. I don't know what
it does. Using 'stat' I have the following:<br>
<br>
B: RW, FREE SPACE: 1,010K<br>
C: RW, FREE SPACE: 5,556K<br>
F: RW, FREE SPACE: 44K<br>
<br>
B is RAMdisk, C is CF primary partition, F is ROMdisk.<br>
<br>
I know the CF card was partitioned under Linux; 'fdisk' can
set partition types. The DOS partition was formatted with
Windoze 2K, and the 0x52 partition was probably Init'ed with
F:INIT.68K, and
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Rich,<br>
<br>
Can you read the card at all? I'm using BIOS version 0.9 of
22-Jan-2012.<br>
64Mb CF card on the PPIDE port of the MF/PIC board. Jumpers
(L to R, board vertical): on,on,off,on (0x40, top to bottom,
card on its side).<br>
In the BIOS setup, the base device of the PPIDE port is (44).
Boot devices, first and second, are C, A.<br>
<br>
The CF card has a DOS partition 1, and a CP/M-68 partition
0x52 as the second. There are 3 other 0x52 partitions in the
DOS extended partition, but extended partitions are not looked
at. The CP/M partition is 16Mb.<br>
<br>
The BIOS comes up with a directory listing of the DOS
partition. Hitting "C" boots CP/M-68 from ROM. Typing the
entire filename (8.3) will execute any of the 68000 programs
in the DOS partition, in either User or Supervisor mode (your
choice).<br>
<br>
Booting CP/M-68 from ROM, I have 149 files on the CF card. No
Xmodem, but there is an XFER86.68K binary. I don't know what
it does. Using 'stat' I have the following:<br>
<br>
B: RW, FREE SPACE: 1,010K<br>
C: RW, FREE SPACE: 5,556K<br>
F: RW, FREE SPACE: 44K<br>
<br>
B is RAMdisk, C is CF primary partition, F is ROMdisk.<br>
<br>
I know the CF card was partitioned under Linux; 'fdisk' can
set partition types. The DOS partition was formatted with
Windoze 2K, and the 0x52 partition was probably Init'ed with
F:INIT.68K, and then cpmtools' parameters were adjusted so
that the directory could be filled with utilities, more likely
from DOS 5.0. [The old Windoze machine can dual boot.]<br>
<br>
With all the programs on the CF card, I'd sure like a user
manual to know what they do.<br>
<br>
--John<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 12/08/2014 03:23 AM, Richard Cini wrote:
<blockquote
cite="mid:A5446489-9891-48D7-9718-***@verizon.net"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div>Thanks John. I tried several combinations of sizes and
cards and I'm not having much success getting a card with
mixed partitions to work. Maybe I have to zero the card
totally and start from scratch or try partitioning it on
my Mac instead. </div>
<div><br>
</div>
<div>I'm not sure why I can't get this working but it's not
the worst thing. As Borut mentioned in another message,
maybe I have to get familiar with cpmtools and use that
for file transfer. </div>
<div><br>
</div>
<div>Thanks all!</div>
<div><br>
Sent from my iPhone</div>
<div><br>
On Dec 8, 2014, at 2:18 AM, John Coffman <<a
moz-do-not-send="true" href="mailto:***@gmail.com">***@gmail.com</a>>
wrote:<br>
<br>
</div>
<div><span></span></div>
<blockquote type="cite">
<div>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
On 12/07/2014 05:31 PM, Richard Cini wrote:
<blockquote
cite="mid:D0AA6932.E370%***@verizon.net"
type="cite">
<div>
<div>
<div>John,</div>
<div><br>
</div>
<div><span class="Apple-tab-span"
style="white-space: pre;"> </span>Ok, I guess
I’m on the right track. Maybe I’ll
start from scratch on that same card and see if
I can get it to work.</div>
<div><br>
</div>
<div><span class="Apple-tab-span"
style="white-space: pre;"> </span>Which
partition corresponds to the CP/M C drive
— the Windows partition or the first CP/M
partition?</div>
</div>
</div>
</blockquote>
<br>
CP/M-68 only looks at primary partitions of type 0x52,
any or all of partitions 1..4. Units are assigned in
the order it finds the 0x52 partition type. Any DOS/Win
partition is completely ignored.<br>
<br>
What may be confusing, is that the BIOS looks for
DOS/Win partitions, will list the directories (8.3
format), and will allow you to boot a program in
Supervisor or User Mode. This was the method used in
debugging new compiles of CP/M when it was under rapid
development. Swapping CF cards is a lot faster than
erasing and reprogramming ROMs.<br>
<br>
--John<br>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
On 12/07/2014 05:31 PM, Richard Cini wrote:
<blockquote
cite="mid:D0AA6932.E370%***@verizon.net"
type="cite">
<div>
<div>
<div>John,</div>
<div><br>
</div>
<div><span class="Apple-tab-span"
style="white-space: pre;"> </span>Ok, I guess
I’m on the right track. Maybe I’ll
start from scratch on that same card and see if
I can get it to work.</div>
<div><br>
</div>
<div><span class="Apple-tab-span"
style="white-space: pre;"> </span>Which
partition corresponds to the CP/M C drive
— the Windows partition or the first CP/M
partition?</div>
</div>
</div>
</blockquote>
<br>
CP/M-68 only looks at primary partitions of type 0x52,
any or all of partitions 1..4. Units are assigned in
the order it finds the 0x52 partition type. Any DOS/Win
partition is completely ignored.<br>
<br>
What may be confusing, is that the BIOS looks for
DOS/Win partitions, will list the directories (8.3
format), and will allow you to boot a program in
Supervisor or User Mode. This was the method used in
debugging new compiles of CP/M when it was under rapid
development. Swapping CF cards is a lot faster than
erasing and reprogramming ROMs.<br>
<br>
--John<br>
<br>
<br>
<br>
<blockquote
cite="mid:D0AA6932.E370%***@verizon.net"
type="cite">
<div>
<div>
<div><br>
</div>
<div>
<div>Rich</div>
<div><br>
</div>
<div>--</div>
<div>Rich Cini</div>
<div>Collector of Classic Computers</div>
<div>Build Master and lead engineer, Altair32
Emulator</div>
<div><a moz-do-not-send="true"
href="http://www.classiccmp.org/cini">http://www.classiccmp.org/cini</a></div>
<div><a moz-do-not-send="true"
href="http://www.classiccmp.org/altair32">http://www.classiccmp.org/altair32</a></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family: Calibri; font-size: 11pt;
text-align: left; color: black; border-width: 1pt
medium medium; border-style: solid none none;
border-color: rgb(181, 196, 223)
-moz-use-text-color -moz-use-text-color; padding:
3pt 0in 0in;"><span style="font-weight: bold;">From:
</span> John Coffman <<a moz-do-not-send="true"
href="mailto:***@gmail.com">***@gmail.com</a>><br>
<span style="font-weight: bold;">Reply-To: </span>
N8VEM-Post <<a moz-do-not-send="true"
href="mailto:***@googlegroups.com">***@googlegroups.com</a>><br>
<span style="font-weight: bold;">Date: </span>
Sunday, December 7, 2014 at 7:55 PM<br>
<span style="font-weight: bold;">To: </span>
N8VEM-Post <<a moz-do-not-send="true"
href="mailto:***@googlegroups.com">***@googlegroups.com</a>><br>
<span style="font-weight: bold;">Subject: </span>
Re: [N8VEM: 19045] New to the mini-68k question<br>
</div>
<div><br>
</div>
<div>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
<div bgcolor="#ffffff" text="#000000"> Rich,<br>
<br>
What you are doing, as long as the partitions
are primary, is exactly what I did to get
CP/M-68 to talk to partitions up to 512Mb. The
large size doesn't do you too much good, because
the allocation size gets so big as to waste a
lot of space.<br>
<br>
Windows and all consumers of CF & SD cards
require that the first partition be FAT16/32,
depending upon the size of the card. They never
look at partitions other than the first. It is
assumed that the card is a single partition. It
does not matter where that first partition is
located; that is why the RomWBW partitioning
scheme works, where there are no indications
that there are partitions, but they are at
absolute locations.<br>
<br>
At the time I did the Mini-68K BIOS, I knew
little about Wayne's partitioning scheme; hence,
it never made it into the CP/M-68 port.<br>
<br>
With Big/Little Endian to support, somebody has
to do byte/word swapping. In order for a 68000
to read a DOS filesystem, byte swapping is
required to read filesystem int16's &
int32's.<br>
<br>
--John<br>
<blockquote
cite="mid:D0AA496E.E337%***@verizon.net"
type="cite">
<div><br>
</div>
</blockquote>
</div>
</div>
</span> -- <br>
You received this message because you are subscribed
to the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving
emails from it, send an email to <a
moz-do-not-send="true"
href="mailto:n8vem+***@googlegroups.com">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem">http://groups.google.com/group/n8vem</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br>
</blockquote>
-- <br>
You received this message because you are subscribed to
the Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails
from it, send an email to <a moz-do-not-send="true"
href="mailto:n8vem+***@googlegroups.com">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem">http://groups.google.com/group/n8vem</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br>
</div>
</blockquote>
-- <br>
You received this message because you are subscribed to the
Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails
from it, send an email to <a moz-do-not-send="true"
href="mailto:n8vem+***@googlegroups.com">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem">http://groups.google.com/group/n8vem</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br>
</blockquote>
-- <br>
You received this message because you are subscribed to the
Google Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from
it, send an email to <a moz-do-not-send="true"
href="mailto:n8vem+***@googlegroups.com">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true" href="mailto:***@googlegroups.com">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem">http://groups.google.com/group/n8vem</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br>
</div>
</blockquote>
-- <br>
You received this message because you are subscribed to the Google
Groups "N8VEM" group.<br>
To unsubscribe from this group and stop receiving emails from it,
send an email to <a moz-do-not-send="true"
href="mailto:n8vem+***@googlegroups.com">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a moz-do-not-send="true"
href="mailto:***@googlegroups.com">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem">http://groups.google.com/group/n8vem</a>.<br>
For more options, visit <a moz-do-not-send="true"
href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br>
</blockquote>
</body>
</html>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "N8VEM" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:n8vem+***@googlegroups.com">n8vem+***@googlegroups.com</a>.<br />
To post to this group, send email to <a href="mailto:***@googlegroups.com">***@googlegroups.com</a>.<br />
Visit this group at <a href="http://groups.google.com/group/n8vem">http://groups.google.com/group/n8vem</a>.<br />
For more options, visit <a href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br />