[N8VEM: 19101] Mini-68K CF Update

Discussion:

Richard Cini

2014-12-16 01:13:29 UTC

All â¹

Today I received two brand-new SanDisk 64MB CF cards to try with the
Mini68K. I took one of them, used the same partition tool, and re-sized it
to 32mb (FAT16 type 0x06, primary)/24mb (unformatted type 0x52, primary,
active). For some reason when you do this, thereÂ¹s 8mb of unallocated space
and no seeming way to recover it at least with this tool. Maybe using a *nix
alternative would work better.

I popped it into the PPIDE and selected drive C, ran init and it worked!
PIPped a few files, no problem.

Now, I still canÂ¹t read the FAT partition from CP/M. I put a 5k text file in
the FAT partition but CP/M doesnÂ¹t see it. Looks like I made some progress,
though.

Rich

--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32

--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

Max Scane

2014-12-16 01:24:42 UTC

Permalink

Hi Rich,

That's great news!

Despite supporting Logical Block Addressing, I think a number of disk
partitioners like to align partitions on track/sector boundaries.

I think that is why you have some spare space.

Cheers!

Max

All â
Today I received two brand-new SanDisk 64MB CF cards to try with the
Mini68K. I took one of them, used the same partition tool, and re-sized it
to 32mb (FAT16 type 0x06, primary)/24mb (unformatted type 0x52, primary,
active). For some reason when you do this, thereâs 8mb of unallocated space
and no seeming way to recover it at least with this tool. Maybe using a
*nix alternative would work better.
I popped it into the PPIDE and selected drive C, ran init and it worked!
PIPped a few files, no problem.
Now, I still canât read the FAT partition from CP/M. I put a 5k text file
in the FAT partition but CP/M doesnât see it. Looks like I made some
progress, though.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

Richard Cini

2014-12-16 01:50:01 UTC

Permalink

Thanks Max. Yes, I have heard about the sector alignmentÅ thanks for
reminding me.

Any idea about reading the FAT16 partition? If I can get that working, then
file transfer will be a snap.

Rich

--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32

From: Max Scane <***@gmail.com>
Reply-To: N8VEM-Post <***@googlegroups.com>
Date: Monday, December 15, 2014 at 8:24 PM
To: N8VEM-Post <***@googlegroups.com>
Subject: Re: [N8VEM: 19102] Mini-68K CF Update

Hi Rich,

That's great news!

Despite supporting Logical Block Addressing, I think a number of disk
partitioners like to align partitions on track/sector boundaries.

I think that is why you have some spare space.

Cheers!

Max

Post by Richard Cini
All â¹
Today I received two brand-new SanDisk 64MB CF cards to try with the Mini68K.
I took one of them, used the same partition tool, and re-sized it to 32mb
(FAT16 type 0x06, primary)/24mb (unformatted type 0x52, primary, active). For
some reason when you do this, thereÂ¹s 8mb of unallocated space and no seeming
way to recover it at least with this tool. Maybe using a *nix alternative
would work better.
I popped it into the PPIDE and selected drive C, ran init and it worked!
PIPped a few files, no problem.
Now, I still canÂ¹t read the FAT partition from CP/M. I put a 5k text file in
the FAT partition but CP/M doesnÂ¹t see it. Looks like I made some progress,
though.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to n8vem+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

John Coffman

2014-12-16 03:01:15 UTC

Permalink

<!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">
<tt>Rich,<br>
<br>
I assume you are booting CP/M-68 with the "C" option.<br>
<br>
Does the "D" option work?  [list FAT16 Directory]<br>
<br>
When you get the boot message, the directory of the FAT16
partition, type 0x06, on the CF card (device 44 on the MF/PIC
board) should be listed.  This allows you to boot any m68K .coff
file (A.OUT) or binary (*.BIN) file in the FAT16 partition.<br>
<br>
The cross compiler I have used is the Ashware GCC 2.95 compiler. 
CP/M-68 is compiled with the Ashware suite of cross-tools.<br>
<br>
The FAT16 partition is first; and the CP/M 0x52 partition is
second; I think I have an extended partition on this CF card,
also, third partition table entry.<br>
<br>
--John<br>
<br>
<br>
</tt><br>
On 12/15/2014 05:50 PM, Richard Cini wrote:
<blockquote cite="mid:D0B4F9CE.E9D4%***@verizon.net"
type="cite">
<div>
<div>
<div>Thanks Max. Yes, I have heard about the sector
alignment…thanks for reminding me.</div>
<div><br>
</div>
<div>Any idea about reading the FAT16 partition? If I can get
that working, then file transfer will be a snap.</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> Max
Scane <<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> Monday,
December 15, 2014 at 8:24 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:
19102] Mini-68K CF Update<br>
</div>
<div><br>
</div>
<div dir="ltr">Hi Rich,
<div><br>
</div>
<div>That's great news!</div>
<div><br>
</div>
<div>Despite supporting Logical Block Addressing, I think a
number of disk partitioners like to align partitions on
track/sector boundaries.</div>
<div><br>
</div>
<div>I think that is why you have some spare space.</div>
<div><br>
</div>
<div>Cheers!</div>
<div><br>
</div>
<div>Max</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Dec 16, 2014 at 12:13 PM,
Richard Cini <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:***@verizon.net" target="_blank">***@verizon.net</a>></span>
wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div style="word-wrap: break-word; color: rgb(0, 0, 0);
font-size: 14px; font-family: Calibri,sans-serif;">
<div>
<div>
<div>All —</div>
<div><br>
</div>
<div><span style="white-space: pre-wrap;"> </span>Today
I received two brand-new SanDisk 64MB CF cards to
try with the Mini68K. I took one of them, used the
same partition tool, and re-sized it to 32mb
(FAT16 type 0x06, primary)/24mb (unformatted type
0x52, primary, active). For some reason when you
do this, there’s 8mb of unallocated space and no
seeming way to recover it at least with this tool.
Maybe using a *nix alternative would work better.</div>
<div><br>
</div>
<div><span style="white-space: pre-wrap;"> </span>I
popped it into the PPIDE and selected drive C, ran
init and it worked! PIPped a few files, no
problem.</div>
<div><br>
</div>
<div><span style="white-space: pre-wrap;"> </span>Now,
I still can’t read the FAT partition from CP/M. I
put a 5k text file in the FAT partition but CP/M
doesn’t see it. Looks like I made some progress,
though.</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"
target="_blank">http://www.classiccmp.org/cini</a></div>
<div><a moz-do-not-send="true"
href="http://www.classiccmp.org/altair32"
target="_blank">http://www.classiccmp.org/altair32</a></div>
</div>
</div>
</div>
</div>
<span class="HOEnZb"><font color="#888888">
-- <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"
target="_blank">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com" target="_blank">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem"
target="_blank">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"
target="_blank">https://groups.google.com/d/optout</a>.<br>
</font></span></blockquote>
</div>
</div>
-- <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>
</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>
</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 />

Max Scane

2014-12-16 07:11:09 UTC

Permalink

Hi John,

I'm just jumpering up my 68K board and I am wondering about the orientation
of J1 and J2. Pin 1 is the bottom right but how do they number from
there? Do they go anticlockwise 1 up 2 left 3 down 4 etc or something else?

Cheers!

Max

Post by John Coffman
Rich,
I assume you are booting CP/M-68 with the "C" option.
Does the "D" option work? [list FAT16 Directory]
When you get the boot message, the directory of the FAT16 partition, type
0x06, on the CF card (device 44 on the MF/PIC board) should be listed.
This allows you to boot any m68K .coff file (A.OUT) or binary (*.BIN) file
in the FAT16 partition.
The cross compiler I have used is the Ashware GCC 2.95 compiler. CP/M-68
is compiled with the Ashware suite of cross-tools.
The FAT16 partition is first; and the CP/M 0x52 partition is second; I
think I have an extended partition on this CF card, also, third partition
table entry.
--John
Thanks Max. Yes, I have heard about the sector alignmentâŠthanks for
reminding me.
Any idea about reading the FAT16 partition? If I can get that working,
then file transfer will be a snap.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
Date: Monday, December 15, 2014 at 8:24 PM
Subject: Re: [N8VEM: 19102] Mini-68K CF Update
Hi Rich,
That's great news!
Despite supporting Logical Block Addressing, I think a number of disk
partitioners like to align partitions on track/sector boundaries.
I think that is why you have some spare space.
Cheers!
Max

All â
Today I received two brand-new SanDisk 64MB CF cards to try with the
Mini68K. I took one of them, used the same partition tool, and re-sized it
to 32mb (FAT16 type 0x06, primary)/24mb (unformatted type 0x52, primary,
active). For some reason when you do this, thereâs 8mb of unallocated space
and no seeming way to recover it at least with this tool. Maybe using a
*nix alternative would work better.
I popped it into the PPIDE and selected drive C, ran init and it
worked! PIPped a few files, no problem.
Now, I still canât read the FAT partition from CP/M. I put a 5k text
file in the FAT partition but CP/M doesnât see it. Looks like I made some
progress, though.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

John Coffman

2014-12-16 07:25:42 UTC

Permalink

<!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">
<tt>Max,<br>
<br>
On dual row connectors like J2, the numbering is easy:  pin 1 is
the square pad.  pin 2 is clockwise (from the top).  Then all the
odd numbered pins are on one (long) side, and all the even number
pins are on the opposite side:  viz.,<br>
<br>
<br>
        2  4  6<br>
        1  3  5   etc.<br>
<br>
J1 is a stumper, because it is 2x2.  However, the same rule
applies.  Look at J2 above, and chop off pins 5 & 6.  So J1 is
numbered, as you asked, CLOCKWISE.<br>
<br>
        2  4<br>
        1  3<br>
<br>
--John<br>
<br>
</tt><br>
<br>
On 12/15/2014 11:11 PM, Max Scane wrote:
<blockquote
cite="mid:CADv-vyYNrq8Z4-***@mail.gmail.com"
type="cite">
<div dir="ltr">Hi John,
<div><br>
</div>
<div>I'm just jumpering up my 68K board and I am wondering about
the orientation of J1 and J2.Â  Pin 1 is the bottom right but
how do they number from there?Â  Do they go anticlockwise 1 up
2 left 3 down 4 etc or something else?</div>
<div><br>
</div>
<div>Cheers!</div>
<div><br>
</div>
<div>Max</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Dec 16, 2014 at 2:01 PM, John
Coffman <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:***@gmail.com" target="_blank">***@gmail.com</a>></span>
wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> <tt>Rich,<br>
<br>
I assume you are booting CP/M-68 with the "C" option.<br>
<br>
Does the "D" option work?Â  [list FAT16 Directory]<br>
<br>
When you get the boot message, the directory of the
FAT16 partition, type 0x06, on the CF card (device 44 on
the MF/PIC board) should be listed.Â  This allows you to
boot any m68K .coff file (A.OUT) or binary (*.BIN) file
in the FAT16 partition.<br>
<br>
The cross compiler I have used is the Ashware GCC 2.95
compiler.Â  CP/M-68 is compiled with the Ashware suite
of cross-tools.<br>
<br>
The FAT16 partition is first; and the CP/M 0x52
partition is second; I think I have an extended
partition on this CF card, also, third partition table
entry.<span class="HOEnZb"><font color="#888888"><br>
<br>
--John<br>
<br>
<br>
</font></span></tt>
<div>
<div class="h5"><br>
On 12/15/2014 05:50 PM, Richard Cini wrote:
<blockquote type="cite">
<div>
<div>
<div>Thanks Max. Yes, I have heard about the
sector alignmentâ€¦thanks for reminding me.</div>
<div><br>
</div>
<div>Any idea about reading the FAT16 partition?
If I can get that working, then file transfer
will be a snap.</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"
target="_blank">http://www.classiccmp.org/cini</a></div>
<div><a moz-do-not-send="true"
href="http://www.classiccmp.org/altair32"
target="_blank">http://www.classiccmp.org/altair32</a></div>
</div>
</div>
</div>
<div><br>
</div>
<span>
<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> Max Scane <<a
moz-do-not-send="true"
href="mailto:***@gmail.com"
target="_blank">***@gmail.com</a>><br>
<span style="font-weight: bold;">Reply-To: </span>
N8VEM-Post <<a moz-do-not-send="true"
href="mailto:***@googlegroups.com"
target="_blank">***@googlegroups.com</a>><br>
<span style="font-weight: bold;">Date: </span>
Monday, December 15, 2014 at 8:24 PM<br>
<span style="font-weight: bold;">To: </span>
N8VEM-Post <<a moz-do-not-send="true"
href="mailto:***@googlegroups.com"
target="_blank">***@googlegroups.com</a>><br>
<span style="font-weight: bold;">Subject: </span>
Re: [N8VEM: 19102] Mini-68K CF Update<br>
</div>
<div><br>
</div>
<div dir="ltr">Hi Rich,
<div><br>
</div>
<div>That's great news!</div>
<div><br>
</div>
<div>Despite supporting Logical Block
Addressing, I think a number of disk
partitioners like to align partitions on
track/sector boundaries.</div>
<div><br>
</div>
<div>I think that is why you have some spare
space.</div>
<div><br>
</div>
<div>Cheers!</div>
<div><br>
</div>
<div>Max</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Dec 16, 2014 at
12:13 PM, Richard Cini <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:***@verizon.net"
target="_blank">***@verizon.net</a>></span>
wrote:
<blockquote class="gmail_quote" style="margin:
0pt 0pt 0pt 0.8ex; border-left: 1px solid
rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word; color:
rgb(0, 0, 0); font-size: 14px;
font-family: Calibri,sans-serif;">
<div>
<div>
<div>All â€”</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>Today I
received two brand-new SanDisk 64MB
CF cards to try with the Mini68K. I
took one of them, used the same
partition tool, and re-sized it to
32mb (FAT16 type 0x06, primary)/24mb
(unformatted type 0x52, primary,
active). For some reason when you do
this, thereâ€™s 8mb of unallocated
space and no seeming way to recover
it at least with this tool. Maybe
using a *nix alternative would work
better.</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>I popped it
into the PPIDE and selected drive C,
ran init and it worked! PIPped a few
files, no problem.</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>Now, I still
canâ€™t read the FAT partition from
CP/M. I put a 5k text file in the
FAT partition but CP/M doesnâ€™t see
it. Looks like I made some progress,
though.</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"
target="_blank">http://www.classiccmp.org/cini</a></div>
<div><a moz-do-not-send="true"
href="http://www.classiccmp.org/altair32"
target="_blank">http://www.classiccmp.org/altair32</a></div>
</div>
</div>
</div>
</div>
<span><font color="#888888"> -- <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"
target="_blank">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com"
target="_blank">***@googlegroups.com</a>.<br>
Visit this group at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem"
target="_blank">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"
target="_blank">https://groups.google.com/d/optout</a>.<br>
</font></span></blockquote>
</div>
</div>
-- <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"
target="_blank">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com"
target="_blank">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem"
target="_blank">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"
target="_blank">https://groups.google.com/d/optout</a>.<br>
</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"
target="_blank">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com"
target="_blank">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem"
target="_blank">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"
target="_blank">https://groups.google.com/d/optout</a>.<br>
</blockquote>
</div>
</div>
</div>
<div class="HOEnZb">
<div class="h5">
-- <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"
target="_blank">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com" target="_blank">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem"
target="_blank">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"
target="_blank">https://groups.google.com/d/optout</a>.<br>
</div>
</div>
</blockquote>
</div>
</div>
-- <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 />

Max Scane

2014-12-16 07:33:45 UTC

Permalink

Thanks John, holding the board in portrait rather than landscape makes a
lot more sense!

Cheers!

Max

Max,
On dual row connectors like J2, the numbering is easy: pin 1 is the
square pad. pin 2 is clockwise (from the top). Then all the odd numbered
pins are on one (long) side, and all the even number pins are on the
opposite side: viz.,
2 4 6
1 3 5 etc.
J1 is a stumper, because it is 2x2. However, the same rule applies. Look
at J2 above, and chop off pins 5 & 6. So J1 is numbered, as you asked,
CLOCKWISE.
2 4
1 3
--John
Hi John,
I'm just jumpering up my 68K board and I am wondering about the
orientation of J1 and J2.Ã Pin 1 is the bottom right but how do they
number from there?Ã Do they go anticlockwise 1 up 2 left 3 down 4 etc or
something else?
Cheers!
Max

Post by John Coffman
Rich,
I assume you are booting CP/M-68 with the "C" option.
Does the "D" option work?Ã [list FAT16 Directory]
When you get the boot message, the directory of the FAT16 partition, type
0x06, on the CF card (device 44 on the MF/PIC board) should be listed.Ã
This allows you to boot any m68K .coff file (A.OUT) or binary (*.BIN) file
in the FAT16 partition.
The cross compiler I have used is the Ashware GCC 2.95 compiler.Ã
CP/M-68 is compiled with the Ashware suite of cross-tools.
The FAT16 partition is first; and the CP/M 0x52 partition is second; I
think I have an extended partition on this CF card, also, third partition
table entry.
--John
Thanks Max. Yes, I have heard about the sector alignmentÃ¢â¬ÂŠthanks for
reminding me.
Any idea about reading the FAT16 partition? If I can get that working,
then file transfer will be a snap.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
Date: Monday, December 15, 2014 at 8:24 PM
Subject: Re: [N8VEM: 19102] Mini-68K CF Update
Hi Rich,
That's great news!
Despite supporting Logical Block Addressing, I think a number of disk
partitioners like to align partitions on track/sector boundaries.
I think that is why you have some spare space.
Cheers!
Max

All Ã¢â¬â
Today I received two brand-new SanDisk 64MB CF cards to try with the
Mini68K. I took one of them, used the same partition tool, and re-sized it
to 32mb (FAT16 type 0x06, primary)/24mb (unformatted type 0x52, primary,
active). For some reason when you do this, thereÃ¢â¬â¢s 8mb of unallocated
space and no seeming way to recover it at least with this tool. Maybe using
a *nix alternative would work better.
I popped it into the PPIDE and selected drive C, ran init and it
worked! PIPped a few files, no problem.
Now, I still canÃ¢â¬â¢t read the FAT partition from CP/M. I put a 5k text
file in the FAT partition but CP/M doesnÃ¢â¬â¢t see it. Looks like I made some
progress, though.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

Richard Cini

2014-12-16 09:59:21 UTC

Permalink

There are options? I just let the board boot to the F drive. Should I do something different?

Sent from my iPhone

Thanks Max. Yes, I have heard about the sector alignmentâŠthanks for reminding me.
Any idea about reading the FAT16 partition? If I can get that working, then file transfer will be a snap.
Rich,
I assume you are booting CP/M-68 with the "C" option.
Does the "D" option work? [list FAT16 Directory]
When you get the boot message, the directory of the FAT16 partition, type 0x06, on the CF card (device 44 on the MF/PIC board) should be listed. This allows you to boot any m68K .coff file (A.OUT) or binary (*.BIN) file in the FAT16 partition.
The cross compiler I have used is the Ashware GCC 2.95 compiler. CP/M-68 is compiled with the Ashware suite of cross-tools.
The FAT16 partition is first; and the CP/M 0x52 partition is second; I think I have an extended partition on this CF card, also, third partition table entry.
--John

Thanks Max. Yes, I have heard about the sector alignmentâŠthanks for reminding me.
Any idea about reading the FAT16 partition? If I can get that working, then file transfer will be a snap.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
Date: Monday, December 15, 2014 at 8:24 PM
Subject: Re: [N8VEM: 19102] Mini-68K CF Update
Hi Rich,
That's great news!
Despite supporting Logical Block Addressing, I think a number of disk partitioners like to align partitions on track/sector boundaries.
I think that is why you have some spare space.
Cheers!
Max

All â
Today I received two brand-new SanDisk 64MB CF cards to try with the Mini68K. I took one of them, used the same partition tool, and re-sized it to 32mb (FAT16 type 0x06, primary)/24mb (unformatted type 0x52, primary, active). For some reason when you do this, thereâs 8mb of unallocated space and no seeming way to recover it at least with this tool. Maybe using a *nix alternative would work better.
I popped it into the PPIDE and selected drive C, ran init and it worked! PIPped a few files, no problem.
Now, I still canât read the FAT partition from CP/M. I put a 5k text file in the FAT partition but CP/M doesnât see it. Looks like I made some progress, though.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

John Coffman

2014-12-16 15:45:04 UTC

Permalink

<!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">
<tt></tt>Rich,<br>
<br>
can you produce a dump of the partition table on your CF card. 
Here's what I am working with:<br>
<br>
<br>
<br>
<b>FROM LINUX fdisk:<br>
<br>
</b><tt>Disk /dev/sdd: 64 MB, 64225280 bytes<br>
16 heads, 32 sectors/track, 245 cylinders, total 125440 sectors<br>
Units = sectors of 1 * 512 = 512 bytes<br>
Sector size (logical/physical): 512 bytes / 512 bytes<br>
I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
Disk identifier: 0x71698e5a<br>
<br>
   Device Boot      Start         End      Blocks   Id  System<br>
/dev/sdd1           65536      125439       29952    e  W95 FAT16
(LBA)<br>
/dev/sdd2           16384       65535       24576    f  W95 Ext'd
(LBA)<br>
/dev/sdd3              32       16383        8176   52  CP/M<br>
/dev/sdd5           16416       32767        8176   52  CP/M<br>
/dev/sdd6           32800       49151        8176   52  CP/M<br>
/dev/sdd7           49184       65535        8176   52  CP/M<br>
<br>
</tt><br>
<br>
<b>FROM LINUX lilo:<br>
<br>
</b><tt>Partition table entries are not in disk order<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>
</tt><br>
--John<br>
<br>
<br>
<br>
<br>
On 12/16/2014 01:59 AM, Richard Cini wrote:
<blockquote
cite="mid:79F1D2BC-3EF6-466C-A702-***@verizon.net"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div>There are options? I just let the board boot to the F drive.
Should I do something different?<br>
<br>
Sent from my iPhone</div>
<div><br>
On Dec 15, 2014, at 10:01 PM, 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">
<tt>Rich,<br>
<br>
I assume you are booting CP/M-68 with the "C" option.<br>
<br>
Does the "D" option work?  [list FAT16 Directory]<br>
<br>
When you get the boot message, the directory of the FAT16
partition, type 0x06, on the CF card (device 44 on the
MF/PIC board) should be listed.  This allows you to boot any
m68K .coff file (A.OUT) or binary (*.BIN) file in the FAT16
partition.<br>
<br>
The cross compiler I have used is the Ashware GCC 2.95
compiler.  CP/M-68 is compiled with the Ashware suite of
cross-tools.<br>
<br>
The FAT16 partition is first; and the CP/M 0x52 partition is
second; I think I have an extended partition on this CF
card, also, third partition table entry.<br>
<br>
--John<br>
<br>
<br>
</tt><br>
On 12/15/2014 05:50 PM, Richard Cini wrote:
<blockquote cite="mid:D0B4F9CE.E9D4%***@verizon.net"
type="cite">
<div>
<div>
<div>Thanks Max. Yes, I have heard about the sector
alignmentâ€¦thanks for reminding me.</div>
<div><br>
</div>
<div>Any idea about reading the FAT16 partition? If I
can get that working, then file transfer will be a
snap.</div>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<tt>Rich,<br>
<br>
I assume you are booting CP/M-68 with the "C" option.<br>
<br>
Does the "D" option work?  [list FAT16 Directory]<br>
<br>
When you get the boot message, the directory of the
FAT16 partition, type 0x06, on the CF card (device 44
on the MF/PIC board) should be listed.  This allows
you to boot any m68K .coff file (A.OUT) or binary
(*.BIN) file in the FAT16 partition.<br>
<br>
The cross compiler I have used is the Ashware GCC 2.95
compiler.  CP/M-68 is compiled with the Ashware suite
of cross-tools.<br>
<br>
The FAT16 partition is first; and the CP/M 0x52
partition is second; I think I have an extended
partition on this CF card, also, third partition table
entry.<br>
<br>
--John<br>
<br>
<br>
</tt><br>
On 12/15/2014 05:50 PM, Richard Cini wrote:
<blockquote
cite="mid:D0B4F9CE.E9D4%***@verizon.net"
type="cite">
<div>
<div>
<div>Thanks Max. Yes, I have heard about the
sector alignmentâ€¦thanks for reminding me.</div>
<div><br>
</div>
<div>Any idea about reading the FAT16 partition?
If I can get that working, then file transfer
will be a snap.</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> Max Scane <<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>
Monday, December 15, 2014 at 8:24 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: 19102] Mini-68K CF Update<br>
</div>
<div><br>
</div>
<div dir="ltr">Hi Rich,
<div><br>
</div>
<div>That's great news!</div>
<div><br>
</div>
<div>Despite supporting Logical Block Addressing,
I think a number of disk partitioners like to
align partitions on track/sector boundaries.</div>
<div><br>
</div>
<div>I think that is why you have some spare
space.</div>
<div><br>
</div>
<div>Cheers!</div>
<div><br>
</div>
<div>Max</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Dec 16, 2014 at
12:13 PM, Richard Cini <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:***@verizon.net"
target="_blank">***@verizon.net</a>></span>
wrote:
<blockquote class="gmail_quote" style="margin:
0pt 0pt 0pt 0.8ex; border-left: 1px solid
rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word; color:
rgb(0, 0, 0); font-size: 14px; font-family:
Calibri,sans-serif;">
<div>
<div>
<div>All â€”</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>Today I received
two brand-new SanDisk 64MB CF cards to
try with the Mini68K. I took one of
them, used the same partition tool,
and re-sized it to 32mb (FAT16 type
0x06, primary)/24mb (unformatted type
0x52, primary, active). For some
reason when you do this, thereâ€™s 8mb
of unallocated space and no seeming
way to recover it at least with this
tool. Maybe using a *nix alternative
would work better.</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>I popped it into
the PPIDE and selected drive C, ran
init and it worked! PIPped a few
files, no problem.</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>Now, I still
canâ€™t read the FAT partition from
CP/M. I put a 5k text file in the FAT
partition but CP/M doesnâ€™t see it.
Looks like I made some progress,
though.</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"
target="_blank">http://www.classiccmp.org/cini</a></div>
<div><a moz-do-not-send="true"
href="http://www.classiccmp.org/altair32"
target="_blank">http://www.classiccmp.org/altair32</a></div>
</div>
</div>
</div>
</div>
<span class="HOEnZb"><font color="#888888"> --
<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"
target="_blank">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com"
target="_blank">***@googlegroups.com</a>.<br>
Visit this group at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem"
target="_blank">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"
target="_blank">https://groups.google.com/d/optout</a>.<br>
</font></span></blockquote>
</div>
</div>
-- <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>
</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>
</div>
</blockquote>
</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 />

Richard Cini

2014-12-20 01:25:03 UTC

Permalink

Here you go (from OS Xâs fdisk):

Disk: /dev/disk7 geometry: 497/4/63 [125440 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: 06 0 0 33 - 3 254 63 [ 32 - 64228] DOS > 32MB

*2: 52 4 0 1 - 6 254 63 [ 64260 - 48195] CP/M or SysV

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

Using the â-dâ option:

32,64228,0x06,-,0,0,33,3,254,63

64260,48195,0x52,*,4,0,1,6,254,63

0,0,0x00,-,0,0,0,0,0,0

0,0,0x00,-,0,0,0,0,0,0

Rich

--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32

From: John Coffman <***@gmail.com>
Reply-To: N8VEM-Post <***@googlegroups.com>
Date: Tuesday, December 16, 2014 at 10:45 AM
To: N8VEM-Post <***@googlegroups.com>
Subject: Re: [N8VEM: 19112] Mini-68K CF Update

Rich,

can you produce a dump of the partition table on your CF card. Here's what
I am working with:

FROM LINUX fdisk:

Disk /dev/sdd: 64 MB, 64225280 bytes
16 heads, 32 sectors/track, 245 cylinders, total 125440 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x71698e5a

Device Boot Start End Blocks Id System
/dev/sdd1 65536 125439 29952 e W95 FAT16 (LBA)
/dev/sdd2 16384 65535 24576 f W95 Ext'd (LBA)
/dev/sdd3 32 16383 8176 52 CP/M
/dev/sdd5 16416 32767 8176 52 CP/M
/dev/sdd6 32800 49151 8176 52 CP/M
/dev/sdd7 49184 65535 8176 52 CP/M

FROM LINUX lilo:

Partition table entries are not in disk order
LILO version 22.7.3, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 11-Aug-2006 and compiled at 20:26:28 on Aug 11 2006.

vol-ID: 71698E5A

Type Boot Start End Sector #sectors
1 FAT16_lba 128:0:1 244:15:32 65536
59904
2 WIN extended 32:0:1 127:15:32 16384
49152
3 0x52 0:1:1 31:15:32 32
16352
4 ** empty **
5 0x52 32:1:1 63:15:32 32
16352
6 0x52 64:1:1 95:15:32 32
16352
7 0x52 96:1:1 127:15:32 32
16352

--John

Post by Richard Cini
There are options? I just let the board boot to the F drive. Should I do
something different?
Sent from my iPhone

Post by John Coffman
Thanks Max. Yes, I have heard about the sector alignmentÃ¢â¬ÂŠthanks for
reminding me.
Any idea about reading the FAT16 partition? If I can get that working, then
file transfer will be a snap.
Rich,
I assume you are booting CP/M-68 with the "C" option.
Does the "D" option work? [list FAT16 Directory]
When you get the boot message, the directory of the FAT16 partition, type
0x06, on the CF card (device 44 on the MF/PIC board) should be listed. This
allows you to boot any m68K .coff file (A.OUT) or binary (*.BIN) file in the
FAT16 partition.
The cross compiler I have used is the Ashware GCC 2.95 compiler. CP/M-68
is compiled with the Ashware suite of cross-tools.
The FAT16 partition is first; and the CP/M 0x52 partition is second; I
think I have an extended partition on this CF card, also, third partition
table entry.
--John

Post by John Coffman
Thanks Max. Yes, I have heard about the sector alignmentÃ¢â¬ÂŠthanks for
reminding me.
Any idea about reading the FAT16 partition? If I can get that working, then
file transfer will be a snap.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
Date: Monday, December 15, 2014 at 8:24 PM
Subject: Re: [N8VEM: 19102] Mini-68K CF Update
Hi Rich,
That's great news!
Despite supporting Logical Block Addressing, I think a number of disk
partitioners like to align partitions on track/sector boundaries.
I think that is why you have some spare space.
Cheers!
Max

All Ã¢â¬â
Today I received two brand-new SanDisk 64MB CF cards to try with the
Mini68K. I took one of them, used the same partition tool, and re-sized it
to 32mb (FAT16 type 0x06, primary)/24mb (unformatted type 0x52, primary,
active). For some reason when you do this, thereÃ¢â¬â¢s 8mb of unallocated
space and no seeming way to recover it at least with this tool. Maybe
using a *nix alternative would work better.
I popped it into the PPIDE and selected drive C, ran init and it worked!
PIPped a few files, no problem.
Now, I still canÃ¢â¬â¢t read the FAT partition from CP/M. I put a 5k text
file in the FAT partition but CP/M doesnÃ¢â¬â¢t see it. Looks like I made
some progress, though.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
--
You received this message because you are subscribed to the Google Groups
"N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to n8vem+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

John Coffman

2014-12-20 17:45:51 UTC

Permalink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Rich,<br>
<br>
Although CP/M-68 supports partitions > 8Mb (16384 sectors), in
fact up to 512Mb, I don't think 'cpmtools' can handle anything as
big as a 24Mb partition.  Cut that 0x52 partition down to 8Mb or
under, and I think you'll be able to get to it with 'cpmtools.'<br>
<br>
--John<br>
<br>
<br>
</tt><br>
On 12/19/2014 05:25 PM, Richard Cini wrote:
<blockquote cite="mid:D0BA396B.EC4B%***@verizon.net"
type="cite">
<div>
<div>Here you go (from OS X’s fdisk):</div>
<div><br>
</div>
<div>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);"><br>
</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);">Disk: /dev/disk7<span class="Apple-tab-span"
style="white-space: pre;"> </span>geometry: 497/4/63
[125440 sectors]</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);">Signature: 0xAA55</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);">         Starting       Ending</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);"> #: id  cyl  hd sec -  cyl  hd sec [     start -      
size]</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);">------------------------------------------------------------------------</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);"> 1: 06    0   0  33 -    3 254  63 [        32 -     
64228] DOS > 32MB  </p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);">*2: 52    4   0   1 -    6 254  63 [     64260 -     
48195] CP/M or SysV</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);"> 3: 00    0   0   0 -    0   0   0 [         0 -       
  0] unused      </p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);"> 4: 00    0   0   0 -    0   0   0 [         0 -       
  0] unused      </p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0, 0,
0);"><br>
</p>
</div>
<div>
<div><br>
</div>
<div>Using the “-d” option:</div>
<div><br>
</div>
<div>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0,
0, 0);">32,64228,0x06,-,0,0,33,3,254,63</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0,
0, 0);">64260,48195,0x52,*,4,0,1,6,254,63</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0,
0, 0);">0,0,0x00,-,0,0,0,0,0,0</p>
<p style="margin: 0px; font-size: 12px; font-family: 'Andale
Mono'; color: rgb(41, 249, 20); background-color: rgb(0,
0, 0);">0,0,0x00,-,0,0,0,0,0,0</p>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</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><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> Tuesday,
December 16, 2014 at 10:45 AM<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:
19112] Mini-68K CF Update<br>
</div>
<div><br>
</div>
<div>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div bgcolor="#ffffff" text="#000000"> Rich,<br>
<br>
can you produce a dump of the partition table on your CF
card.  Here's what I am working with:<br>
<br>
<br>
<br>
<b>FROM LINUX fdisk:<br>
<br>
</b><tt>Disk /dev/sdd: 64 MB, 64225280 bytes<br>
16 heads, 32 sectors/track, 245 cylinders, total 125440
sectors<br>
Units = sectors of 1 * 512 = 512 bytes<br>
Sector size (logical/physical): 512 bytes / 512 bytes<br>
I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
Disk identifier: 0x71698e5a<br>
<br>
   Device Boot      Start         End      Blocks   Id 
System<br>
/dev/sdd1           65536      125439       29952    e 
W95 FAT16 (LBA)<br>
/dev/sdd2           16384       65535       24576    f 
W95 Ext'd (LBA)<br>
/dev/sdd3              32       16383        8176   52 
CP/M<br>
/dev/sdd5           16416       32767        8176   52 
CP/M<br>
/dev/sdd6           32800       49151        8176   52 
CP/M<br>
/dev/sdd7           49184       65535        8176   52 
CP/M<br>
<br>
</tt><br>
<br>
<b>FROM LINUX lilo:<br>
<br>
</b><tt>Partition table entries are not in disk order<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>
</tt><br>
--John<br>
<br>
<br>
<br>
<br>
On 12/16/2014 01:59 AM, Richard Cini wrote:
<blockquote
cite="mid:79F1D2BC-3EF6-466C-A702-***@verizon.net"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div>There are options? I just let the board boot to the F
drive. Should I do something different?<br>
<br>
Sent from my iPhone</div>
<div><br>
On Dec 15, 2014, at 10:01 PM, 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">
<tt>Rich,<br>
<br>
I assume you are booting CP/M-68 with the "C"
option.<br>
<br>
Does the "D" option work?  [list FAT16 Directory]<br>
<br>
When you get the boot message, the directory of the
FAT16 partition, type 0x06, on the CF card (device
44 on the MF/PIC board) should be listed.  This
allows you to boot any m68K .coff file (A.OUT) or
binary (*.BIN) file in the FAT16 partition.<br>
<br>
The cross compiler I have used is the Ashware GCC
2.95 compiler.  CP/M-68 is compiled with the Ashware
suite of cross-tools.<br>
<br>
The FAT16 partition is first; and the CP/M 0x52
partition is second; I think I have an extended
partition on this CF card, also, third partition
table entry.<br>
<br>
--John<br>
<br>
<br>
</tt><br>
On 12/15/2014 05:50 PM, Richard Cini wrote:
<blockquote
cite="mid:D0B4F9CE.E9D4%***@verizon.net"
type="cite">
<div>
<div>
<div>Thanks Max. Yes, I have heard about the
sector alignmentÃ¢â‚¬Â¦thanks for reminding
me.</div>
<div><br>
</div>
<div>Any idea about reading the FAT16 partition?
If I can get that working, then file transfer
will be a snap.</div>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<tt>Rich,<br>
<br>
I assume you are booting CP/M-68 with the "C"
option.<br>
<br>
Does the "D" option work?  [list FAT16
Directory]<br>
<br>
When you get the boot message, the directory
of the FAT16 partition, type 0x06, on the CF
card (device 44 on the MF/PIC board) should be
listed.  This allows you to boot any m68K
.coff file (A.OUT) or binary (*.BIN) file in
the FAT16 partition.<br>
<br>
The cross compiler I have used is the Ashware
GCC 2.95 compiler.  CP/M-68 is compiled with
the Ashware suite of cross-tools.<br>
<br>
The FAT16 partition is first; and the CP/M
0x52 partition is second; I think I have an
extended partition on this CF card, also,
third partition table entry.<br>
<br>
--John<br>
<br>
<br>
</tt><br>
On 12/15/2014 05:50 PM, Richard Cini wrote:
<blockquote
cite="mid:D0B4F9CE.E9D4%***@verizon.net"
type="cite">
<div>
<div>
<div>Thanks Max. Yes, I have heard about
the sector alignmentÃ¢â‚¬Â¦thanks for
reminding me.</div>
<div><br>
</div>
<div>Any idea about reading the FAT16
partition? If I can get that working,
then file transfer will be a snap.</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>
Max Scane <<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>
Monday, December 15, 2014 at 8:24 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: 19102] Mini-68K CF
Update<br>
</div>
<div><br>
</div>
<div dir="ltr">Hi Rich,
<div><br>
</div>
<div>That's great news!</div>
<div><br>
</div>
<div>Despite supporting Logical Block
Addressing, I think a number of disk
partitioners like to align partitions on
track/sector boundaries.</div>
<div><br>
</div>
<div>I think that is why you have some
spare space.</div>
<div><br>
</div>
<div>Cheers!</div>
<div><br>
</div>
<div>Max</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Dec 16,
2014 at 12:13 PM, Richard Cini <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:***@verizon.net"
target="_blank">***@verizon.net</a>></span>
wrote:
<blockquote class="gmail_quote"
style="margin: 0pt 0pt 0pt 0.8ex;
border-left: 1px solid rgb(204, 204,
204); padding-left: 1ex;">
<div style="word-wrap: break-word;
color: rgb(0, 0, 0); font-size:
14px; font-family:
Calibri,sans-serif;">
<div>
<div>
<div>All Ã¢â‚¬”</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>Today I
received two brand-new SanDisk
64MB CF cards to try with the
Mini68K. I took one of them,
used the same partition tool,
and re-sized it to 32mb (FAT16
type 0x06, primary)/24mb
(unformatted type 0x52,
primary, active). For some
reason when you do this,
thereÃ¢â‚¬™s 8mb of
unallocated space and no
seeming way to recover it at
least with this tool. Maybe
using a *nix alternative would
work better.</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>I popped
it into the PPIDE and selected
drive C, ran init and it
worked! PIPped a few files, no
problem.</div>
<div><br>
</div>
<div><span style="white-space:
pre-wrap;"> </span>Now, I
still canÃ¢â‚¬™t read the FAT
partition from CP/M. I put a
5k text file in the FAT
partition but CP/M
doesnÃ¢â‚¬™t see it. Looks
like I made some progress,
though.</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" target="_blank">http://www.classiccmp.org/cini</a></div>
<div><a moz-do-not-send="true"
href="http://www.classiccmp.org/altair32" target="_blank">http://www.classiccmp.org/altair32</a></div>
</div>
</div>
</div>
</div>
<span class="HOEnZb"><font
color="#888888"> -- <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"
target="_blank">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email
to <a moz-do-not-send="true"
href="mailto:***@googlegroups.com"
target="_blank">***@googlegroups.com</a>.<br>
Visit this group at <a
moz-do-not-send="true"
href="http://groups.google.com/group/n8vem"
target="_blank">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"
target="_blank">https://groups.google.com/d/optout</a>.<br>
</font></span></blockquote>
</div>
</div>
-- <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>
</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>
</div>
</blockquote>
</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>
</div>
</div>
-- <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>
</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>
</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 />

John Coffman

2014-12-17 07:31:28 UTC

Permalink

Rich,

The missing utilities in the 512K ROM image have been found. There is
some glitch in 'cpmtools' in creating the ROMdisk image which depends
upon whether the IOspace (uppermost 64K addresses) is accounted for
before or after creating the disk image.

Anyhow, I have uploaded the new CPM68.BIN image; this updates ONLY the
ROMdisk image in the 512K ROM file. In addition, I uploaded a zip file
of the two *.BIN's, just in case someone wants to download the images
with some checksums.

--John

Post by Richard Cini
There are options? I just let the board boot to the F drive. Should I
do something different?
Sent from my iPhone

Thanks Max. Yes, I have heard about the sector alignmentÃ¢EURÂŠthanks
for reminding me.
Any idea about reading the FAT16 partition? If I can get that
working, then file transfer will be a snap.
Rich,
I assume you are booting CP/M-68 with the "C" option.
Does the "D" option work? [list FAT16 Directory]
When you get the boot message, the directory of the FAT16 partition,
type 0x06, on the CF card (device 44 on the MF/PIC board) should be
listed. This allows you to boot any m68K .coff file (A.OUT) or
binary (*.BIN) file in the FAT16 partition.
The cross compiler I have used is the Ashware GCC 2.95 compiler.
CP/M-68 is compiled with the Ashware suite of cross-tools.
The FAT16 partition is first; and the CP/M 0x52 partition is second;
I think I have an extended partition on this CF card, also, third
partition table entry.
--John

Thanks Max. Yes, I have heard about the sector alignmentÃ¢EURÂŠthanks
for reminding me.
Any idea about reading the FAT16 partition? If I can get that
working, then file transfer will be a snap.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
Date: Monday, December 15, 2014 at 8:24 PM
Subject: Re: [N8VEM: 19102] Mini-68K CF Update
Hi Rich,
That's great news!
Despite supporting Logical Block Addressing, I think a number of
disk partitioners like to align partitions on track/sector boundaries.
I think that is why you have some spare space.
Cheers!
Max
On Tue, Dec 16, 2014 at 12:13 PM, Richard Cini
All Ã¢EUR"
Today I received two brand-new SanDisk 64MB CF cards to try
with the Mini68K. I took one of them, used the same partition
tool, and re-sized it to 32mb (FAT16 type 0x06, primary)/24mb
(unformatted type 0x52, primary, active). For some reason when
you do this, thereÃ¢EUR^(TM)s 8mb of unallocated space and no
seeming way to recover it at least with this tool. Maybe using
a *nix alternative would work better.
I popped it into the PPIDE and selected drive C, ran init and
it worked! PIPped a few files, no problem.
Now, I still canÃ¢EUR^(TM)t read the FAT partition from CP/M. I
put a 5k text file in the FAT partition but CP/M
doesnÃ¢EUR^(TM)t see it. Looks like I made some progress, though.
Rich
--
Rich Cini
Collector of Classic Computers
Build Master and lead engineer, Altair32 Emulator
http://www.classiccmp.org/cini
http://www.classiccmp.org/altair32
--
You received this message because you are subscribed to the
Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it,
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it,
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google
Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it,
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "N8VEM" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at http://groups.google.com/group/n8vem.
For more options, visit https://groups.google.com/d/optout.

John Coffman

2014-12-16 06:59:40 UTC

Permalink

<!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">
<tt>Rich,<br>
<br>
Looking at the ROMdisk contents, I have noticed that it is coming
up short.  The 128K ROM is necessarily short of utilities, but the
512K ROM should have a good set.  I have never noticed the lack
because I have all the 68K executables I could find on my CF
card.  These were put there with 'cpmtools' into the CP/M
partition.  The whole lot of them are in the file '68k(1).zip' on
the Wiki.  I believe the Alcyon C-compiler is in there, with
assembler, linker, and libraries.<br>
<br>
Why the ROM disk is coming up short is a mystery at this point. 
Or rather, I should say a BUG.  It is buried deep in the code
somewhere and will take some time to find.<br>
<br>
BTW:  the disk boot order in the BIOS setup seems to give the best
results:  C, then A.<br>
<br>
<br>
</tt><br>
On 12/15/2014 05:50 PM, Richard Cini wrote:
<blockquote cite="mid:D0B4F9CE.E9D4%***@verizon.net"
type="cite">
<div>
<div>
<div>Thanks Max. Yes, I have heard about the sector
alignment…thanks for reminding me.</div>
<div><br>
</div>
<div>Any idea about reading the FAT16 partition? If I can get
that working, then file transfer will be a snap.</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> Max
Scane <<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> Monday,
December 15, 2014 at 8:24 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:
19102] Mini-68K CF Update<br>
</div>
<div><br>
</div>
<div dir="ltr">Hi Rich,
<div><br>
</div>
<div>That's great news!</div>
<div><br>
</div>
<div>Despite supporting Logical Block Addressing, I think a
number of disk partitioners like to align partitions on
track/sector boundaries.</div>
<div><br>
</div>
<div>I think that is why you have some spare space.</div>
<div><br>
</div>
<div>Cheers!</div>
<div><br>
</div>
<div>Max</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Dec 16, 2014 at 12:13 PM,
Richard Cini <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:***@verizon.net" target="_blank">***@verizon.net</a>></span>
wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div style="word-wrap: break-word; color: rgb(0, 0, 0);
font-size: 14px; font-family: Calibri,sans-serif;">
<div>
<div>
<div>All —</div>
<div><br>
</div>
<div><span style="white-space: pre-wrap;"> </span>Today
I received two brand-new SanDisk 64MB CF cards to
try with the Mini68K. I took one of them, used the
same partition tool, and re-sized it to 32mb
(FAT16 type 0x06, primary)/24mb (unformatted type
0x52, primary, active). For some reason when you
do this, there’s 8mb of unallocated space and no
seeming way to recover it at least with this tool.
Maybe using a *nix alternative would work better.</div>
<div><br>
</div>
<div><span style="white-space: pre-wrap;"> </span>I
popped it into the PPIDE and selected drive C, ran
init and it worked! PIPped a few files, no
problem.</div>
<div><br>
</div>
<div><span style="white-space: pre-wrap;"> </span>Now,
I still can’t read the FAT partition from CP/M. I
put a 5k text file in the FAT partition but CP/M
doesn’t see it. Looks like I made some progress,
though.</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"
target="_blank">http://www.classiccmp.org/cini</a></div>
<div><a moz-do-not-send="true"
href="http://www.classiccmp.org/altair32"
target="_blank">http://www.classiccmp.org/altair32</a></div>
</div>
</div>
</div>
</div>
<span class="HOEnZb"><font color="#888888">
-- <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"
target="_blank">n8vem+***@googlegroups.com</a>.<br>
To post to this group, send email to <a
moz-do-not-send="true"
href="mailto:***@googlegroups.com" target="_blank">***@googlegroups.com</a>.<br>
Visit this group at <a moz-do-not-send="true"
href="http://groups.google.com/group/n8vem"
target="_blank">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"
target="_blank">https://groups.google.com/d/optout</a>.<br>
</font></span></blockquote>
</div>
</div>
-- <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>
</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>
</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 />