Richard Cini
2014-12-20 01:34:16 UTC
Ok, I think I fixed it. When I booted with the new ROM you posted, changing
nothing, I got an exit code 0x02 and the thing halted. So, I re-ran the BIOS
setup and realized the first boot device still said âAâ. So, I changed it to
âCâ and it worked. Now I can see the DOS partition (with the single test
file) and I get a different prompt and a short list of commands.
Whoo hoo. Thanks John!
Now, can I copy from the DOS partition to the CP/M partition?
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: Richard A Cini <***@verizon.net>
Reply-To: N8VEM-Post <***@googlegroups.com>
Date: Friday, December 19, 2014 at 8:25 PM
To: N8VEM-Post <***@googlegroups.com>
Subject: Re: [N8VEM: 19115] Mini-68K CF Update
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
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.
--
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.
nothing, I got an exit code 0x02 and the thing halted. So, I re-ran the BIOS
setup and realized the first boot device still said âAâ. So, I changed it to
âCâ and it worked. Now I can see the DOS partition (with the single test
file) and I get a different prompt and a short list of commands.
Whoo hoo. Thanks John!
Now, can I copy from the DOS partition to the CP/M partition?
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: Richard A Cini <***@verizon.net>
Reply-To: N8VEM-Post <***@googlegroups.com>
Date: Friday, December 19, 2014 at 8:25 PM
To: N8VEM-Post <***@googlegroups.com>
Subject: Re: [N8VEM: 19115] Mini-68K CF Update
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
There are options? I just let the board boot to the F drive. Should I do
something different?
Sent from my iPhone
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.
--something different?
Sent from my iPhone
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
--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,
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
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.
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
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.
--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.
--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.
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.
--
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.
--
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.
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.