have you looked here yet?
https://661.org/p112/
Does anyone have instructions on how to make a C/PM 2.2 installation on
a hard disk on the P112 with the GIDE? Might look at CPM 3.0 as well,
but I would really like a C/PM 2.2 hard disk system to work with.
Seems like Terry used to have stuff on his site which I can no longer
find.
On Tuesday, November 22, 2022 at 2:20:49 PM UTC-8, Dennis Boone wrote:
Seems like Terry used to have stuff on his site which I can no longer
find.
Terry has a site at http://stack180.com. You can find his latest P112 work there. It is a BPBIOS implementation for P112, so perhaps not the OS you want, but it works quite well. He has BIOS, floppy, and hard disk (GIDE) images.
On 11/22/22 20:35, Wayne Warthen wrote:
Terry has a site at http://stack180.com. You can find his latest P112 work there. It is a BPBIOS implementation for P112, so perhaps not the OS you want, but it works quite well. He has BIOS, floppy, and hard disk (GIDE) images.
I had been there but hadn't found anything. I'll try again.
On Thursday, December 1, 2022 at 3:26:22 PM UTC-8, Bill Gunshannon wrote:
On 11/22/22 20:35, Wayne Warthen wrote:
Terry has a site at http://stack180.com. You can find his latest P112 work there. It is a BPBIOS implementation for P112, so perhaps not the OS you want, but it works quite well. He has BIOS, floppy, and hard disk (GIDE) images.I had been there but hadn't found anything. I'll try again.
Hmmm... From the left nav, look under "P112 Local Links" and choose "Downloads". You should then get to a page with a table of downloads for the ROM, Floppy, and GIDE Hard Disk images.
I recently made floppy disks for another person based on those images,
and verified that the CPM 2.2 floppy boots up fine. I did not try any
hard disk images. My P112 on runs the GIDE ZSDOS/ZCPR3 HDD disk image normally.
Then I will look at the CF file but I really
have no idea what to do with it yet. I assume there is a program for
Windows to write it to a CF card (like RAWRITE does for floppies).
Small steps, but getting closer to having working machines.
On Friday, December 2, 2022 at 5:19:03 PM UTC-8, Bill Gunshannon wrote:
Then I will look at the CF file but I really
have no idea what to do with it yet. I assume there is a program for
Windows to write it to a CF card (like RAWRITE does for floppies).
Small steps, but getting closer to having working machines.
The CF Card image must be written to a CF Card starting at the first sector. On Windows, I use Win32 Disk Imager (https://sourceforge.net/projects/win32diskimager). Yes, this is essentially the same thing as RAWRITE is for floppies.
Assuming you have a GIDE, you can use one of the little CF-IDE adapters to add a CF Card socket (https://www.ebay.com/itm/111977195791).
On Friday, December 2, 2022 at 5:19:03 PM UTC-8, Bill Gunshannon wrote:
Then I will look at the CF file but I really
have no idea what to do with it yet. I assume there is a program for
Windows to write it to a CF card (like RAWRITE does for floppies).
Small steps, but getting closer to having working machines.
The CF Card image must be written to a CF Card starting at the first sector. On Windows, I use Win32 Disk Imager (https://sourceforge.net/projects/win32diskimager). Yes, this is essentially the same thing as RAWRITE is for floppies.
The CF Card image must be written to a CF Card starting at the first sector. On Windows, I use Win32 Disk Imager (https://sourceforge.net/projects/win32diskimager). Yes, this is essentially the same thing as RAWRITE is for floppies.I have done this. Numerous times. Even tried using differnt
size CF cards. Always with the same result: "Unrecognizable
disk format".
On Thursday, December 8, 2022 at 7:43:54 AM UTC-8, Bill Gunshannon wrote:
The CF Card image must be written to a CF Card starting at the first sector. On Windows, I use Win32 Disk Imager (https://sourceforge.net/projects/win32diskimager). Yes, this is essentially the same thing as RAWRITE is for floppies.I have done this. Numerous times. Even tried using differnt
size CF cards. Always with the same result: "Unrecognizable
disk format".
Surprising. Are you using the same ROM that is distributed on the stack180.com website?
On 12/9/22 18:19, Wayne Warthen wrote:
On Thursday, December 8, 2022 at 7:43:54 AM UTC-8, Bill Gunshannon wrote:
The CF Card image must be written to a CF Card starting at the first sector. On Windows, I use Win32 Disk Imager (https://sourceforge.net/projects/win32diskimager). Yes, this is essentially the same thing as RAWRITE is for floppies.I have done this. Numerous times. Even tried using differnt
size CF cards. Always with the same result: "Unrecognizable
disk format".
Surprising. Are you using the same ROM that is distributed on the stack180.com website?Yes. I have upgraded both my P112s to 5.8. But if I read it correctly
that actually got me nothing from 5.7. It seems to only address "higher
clock rates and faster CPUs".
I am more concerned that the image does not end in .img or .iso. It
seems to just be a file. DiskImager seems to want .img. After writing
it returns success from a verify.
While I have your attention. I have seen mention of SCSI for the P112.
Any idea where I could learn more about that? I have an abundance of
SCSI disks floating around my place.
On Friday, December 9, 2022 at 3:43:23 PM UTC-8, Bill Gunshannon wrote:
On 12/9/22 18:19, Wayne Warthen wrote:
On Thursday, December 8, 2022 at 7:43:54 AM UTC-8, Bill Gunshannon wrote: >>>>> The CF Card image must be written to a CF Card starting at the first sector. On Windows, I use Win32 Disk Imager (https://sourceforge.net/projects/win32diskimager). Yes, this is essentially the same thing as RAWRITE is for floppies.Yes. I have upgraded both my P112s to 5.8. But if I read it correctly
I have done this. Numerous times. Even tried using differnt
size CF cards. Always with the same result: "Unrecognizable
disk format".
Surprising. Are you using the same ROM that is distributed on the stack180.com website?
that actually got me nothing from 5.7. It seems to only address "higher
clock rates and faster CPUs".
OK, no idea. I am running a ROM and disk image that are just slightly modified from the posted one. Give me a day or two and I will try the exact stuff that is posted on my P112 and report back.
I am more concerned that the image does not end in .img or .iso. It
seems to just be a file. DiskImager seems to want .img. After writing
it returns success from a verify.
Yes, the lack of an extension is a little odd, but I have confirmed that the start of the file looks correct. I assume you are extracting it from the .zip before writing it.
While I have your attention. I have seen mention of SCSI for the P112.
Any idea where I could learn more about that? I have an abundance of
SCSI disks floating around my place.
Although I have seen some references to SCSI, I don't know anything about it. I came to the conclusion that the SCSI board was unobtanium at this point.
Thanks,
I assumed that. I saw comments by people who seemed to be using one but never saw anything about how you get (or build) one.
On 12/9/22 20:33, Wayne Warthen wrote:
On Friday, December 9, 2022 at 3:43:23 PM UTC-8, Bill Gunshannon wrote:
Yes. I have upgraded both my P112s to 5.8. But if I read it correctly
that actually got me nothing from 5.7. It seems to only address "higher >> clock rates and faster CPUs".
OK, no idea. I am running a ROM and disk image that are just slightly modified from the posted one. Give me a day or two and I will try the exact stuff that is posted on my P112 and report back.It is curious as I assume other people are running this.
ZEX: ldp2d
ZEX: zsconfig +a-
ZEX: tdd u
ZEX: ldr sys.rcp,sys.fcp,sys.ndr
ZEX: zscfg2 cb +a +c m- >-
COPY .COM..Ok (Dated) Verify..Ok0 Errors
DIRU .COM..Ok (Dated) Verify..Ok
L80 .COM..Ok (Dated) Verify..Ok
M80 .COM..Ok (Dated) Verify..Ok
UCOPY .COM..Ok (Dated) Verify..Ok
ZED .COM..Ok (Dated) Verify..Ok
ZMAC .COM..Ok (Dated) Verify..Ok
ZML .COM..Ok (Dated) Verify..Ok
ZZAP .COM..Ok (Dated) Verify..Ok
On Friday, December 9, 2022 at 6:45:57 PM UTC-8, Bill Gunshannon wrote:the CF Card. This makes me think there must be a hardware difference of some kind. The P112 itself is a pretty standard thing and there are no differences in the various runs of the board that I am aware of. However, I do believe there were a few
On 12/9/22 20:33, Wayne Warthen wrote:
On Friday, December 9, 2022 at 3:43:23 PM UTC-8, Bill Gunshannon wrote: >>>> Yes. I have upgraded both my P112s to 5.8. But if I read it correctlyIt is curious as I assume other people are running this.
that actually got me nothing from 5.7. It seems to only address "higher >>>> clock rates and faster CPUs".
OK, no idea. I am running a ROM and disk image that are just slightly modified from the posted one. Give me a day or two and I will try the exact stuff that is posted on my P112 and report back.
Well, I just downloaded the current ROM and CF Card image directly from stack180.com. I updated my P112 with both of them. I seem to be able to start and boot off of the CF Card image with no issues. Below is a log of my system startup and boot from
As you will see below, I am booting with the command "Z 3" to boot directly from the GIDE. I am curious what happens if you use the "L 3" command. This should read the boot tracks and return to the ROM prompt. Even if the CF Card image is bad, thisshould work. If not, then I would think there is an issue with the GIDE and/or CF Card (as opposed to the image on the CF Card). When I use "L 3", I get a message back like "Boot Track(s) loaded @ 8100H. Execute via G 8060".
For what it is worth, I can also boot to floppy with no issues. If you can write the floppy image to a floppy, you should be able to try that without any reliance on the GIDE hardware.
On Sunday, December 11, 2022 at 4:46:47 PM UTC-8, Bill Gunshannon wrote:
I grabbed a copy of the latest CP/M 2.2 floppy and booted it.Where are you getting the CP/M 2.2 floppy image? I want to try it myself.
The floppy image I use is the one posted on stack180.com which is not
CP/M 2.2, it is BPBIOS.
I grabbed a copy of the latest CP/M 2.2 floppy and booted it.
FDISK sees the CF-IDE Adapter and reports a correct size. It
also says there is a "B/P BIOS boot record". But it sees no
partition table and the CF still won't boot.
I even tried
using a Linux Image Writer tool. But still nothing. One new
curiosity. The image is reported as being 1.5 M too big for
a 64M CF card. Windows writes it anyway but Linux refuses.
I used a 128M CF and was able to write it on both Windows and
Linux but it still won't boot and defies examination with the
tools available to me.
I wonder what would happen if I tried to write it to a real disk?
Does anyone have instructions on how to make a C/PM 2.2 installation on
a hard disk on the P112 with the GIDE? Might look at CPM 3.0 as well,
but I would really like a C/PM 2.2 hard disk system to work with.
> Does anyone have instructions on how to make a C/PM 2.2 installation on
> a hard disk on the P112 with the GIDE? Might look at CPM 3.0 as well,
> but I would really like a C/PM 2.2 hard disk system to work with.
Bill,
Have you run BPCNFG and IDEINIT on this CF card? Some notes here
that might be useful:
https://sites.google.com/site/tingox/p112-gide
On Sunday, December 11, 2022 at 6:22:08 PM UTC-8, Wayne Warthen wrote:
On Sunday, December 11, 2022 at 4:46:47 PM UTC-8, Bill Gunshannon wrote:
I grabbed a copy of the latest CP/M 2.2 floppy and booted it.Where are you getting the CP/M 2.2 floppy image? I want to try it myself.
The floppy image I use is the one posted on stack180.com which is not
CP/M 2.2, it is BPBIOS.
OK, I think I found the CP/M 2.2 disk. It does indeed have an FDISK program on it.
This would imply that this implementation of CP/M 2.2 is enhanced to understand
hard disk partitions. When I run FDISK, like you, it does not see any partition on
my CF Card. So, I don't think that means much except that the CF Card is being
accessed. I would still encourage you to try the stack180.com floppy image.
On Sunday, December 11, 2022 at 4:46:47 PM UTC-8, Bill Gunshannon wrote:
I grabbed a copy of the latest CP/M 2.2 floppy and booted it.
Where are you getting the CP/M 2.2 floppy image? I want to try it myself. The floppy image I use is the one posted on stack180.com which is not
CP/M 2.2, it is BPBIOS.
FDISK sees the CF-IDE Adapter and reports a correct size. It
also says there is a "B/P BIOS boot record". But it sees no
partition table and the CF still won't boot.
Hmmm... a BPBIOS hard disk has no partition table and BPBIOS
has no FDISK program. Did this FDISK come on the CP/M 2.2
floppy?
The CF Card image from stack180.com would
definitely not have a partition table, which is normal.
It is not supposed to have one.
I am a bit unclear whether
you have tried the floppy image from stack180.com or not.
If not, I suggest you try that one.
I even tried
using a Linux Image Writer tool. But still nothing. One new
curiosity. The image is reported as being 1.5 M too big for
a 64M CF card. Windows writes it anyway but Linux refuses.
I used a 128M CF and was able to write it on both Windows and
Linux but it still won't boot and defies examination with the
tools available to me.
CF Cards that are labeled 64MB are typically sized using the definition
of 1M = 1,000,000 bytes instead of 1,024 * 1024 bytes. So, the image
may indeed be too big for the CF Card. Although I would expect it to
fail both on Windows and Linux.
I wonder what would happen if I tried to write it to a real disk?
Should work.
If we are talking about the floppy image on the same page as the CF
image and new ROM image, what do I do with it when I have it? Mine
is DOS+ and I see no hard disk utilities on it anywhere.
And, just out of curiosity, is this DOS+ in any way related to the
versions of DOS+ that used to tun on the TRS-80's? That was one of
my favorite micro computer DOSes back in the day.
On Monday, December 12, 2022 at 6:28:49 AM UTC-8, Bill Gunshannon wrote:
If we are talking about the floppy image on the same page as the CF
image and new ROM image, what do I do with it when I have it? Mine
is DOS+ and I see no hard disk utilities on it anywhere.
The floppy disk image on stack180.com is not DOS+, it is BPBIOS which is
a derivative of the ZCPR series of CP/M compatible OSes. The hard disk utilities are in user area 15.
Just to make sure we are talking about the same floppy disk image, please confirm that when you boot from it, the first line you see is as follows:
P112 - B/P 52.00k Bios V1.3 28 Mar 17
Is this what you see?
If you are indeed using the same floppy image as me, then you should
find a program called HDIAG in user area 15. This will let you exercise
your IDE-based CF Card.
Then you can use BPCNFG. Option 5 will show you the logical
drive mappings. Just see which drive letters are mapped to the
hard disk (CF Card). Those drive letters should allow you to
get a directory listing from the CF Card file systems.
And, just out of curiosity, is this DOS+ in any way related to the
versions of DOS+ that used to tun on the TRS-80's? That was one of
my favorite micro computer DOSes back in the day.
It is not DOS+ and it is not related to DOS+ in any way that I am aware of.
On 12/12/22 13:57, Wayne Warthen wrote:
On Monday, December 12, 2022 at 6:28:49 AM UTC-8, Bill Gunshannon wrote:
The floppy disk image on stack180.com is not DOS+, it is BPBIOS which isSomehow I think we are looking at a different page and a different
a derivative of the ZCPR series of CP/M compatible OSes. The hard disk utilities are in user area 15.
floppy image.
Just to make sure we are talking about the same floppy disk image, please confirm that when you boot from it, the first line you see is as follows:
P112 - B/P 52.00k Bios V1.3 28 Mar 17Nope.
CCP+ Vder, 2.2
Made from: P112 Boot Floppy 01-30-17.zip
Which gives: P112 Boot Floppy 01-30-17.img
Taken from: http://stack180.com/P112%20Downloads.htm
Is this and/or ZCPR the only OSes that still run on the P112?
I hope not as that is not what I was looking for. Maybe I
waited to long for the P112 to stabilize and missed the boat
entirely. :-(
And it still leaves me wondering why the pre-built CF image
doesn't boot. Am I also running the wrong ROM image on my
P112? It came from the same web page at stack180.
Sorry, this was a second question. I wondered if there was any
relationship between the DOS+ that was available for the P112
and the DOSPLUS that ran on the TRS80 Model 1m Model3 and Model4.
Haven't seen either of those commands. Which disk should I be
looking on?
Why would I need to do any prep on the CF card when I am copying
a complete image onto it?
On Monday, December 12, 2022 at 11:25:55 AM UTC-8, Bill Gunshannon wrote:
On 12/12/22 13:57, Wayne Warthen wrote:
On Monday, December 12, 2022 at 6:28:49 AM UTC-8, Bill Gunshannon wrote: >>>Somehow I think we are looking at a different page and a different
The floppy disk image on stack180.com is not DOS+, it is BPBIOS which is >>> a derivative of the ZCPR series of CP/M compatible OSes. The hard disk
utilities are in user area 15.
floppy image.
Nope.
Just to make sure we are talking about the same floppy disk image, please >>> confirm that when you boot from it, the first line you see is as follows: >>>
P112 - B/P 52.00k Bios V1.3 28 Mar 17
CCP+ Vder, 2.2
Made from: P112 Boot Floppy 01-30-17.zip
Which gives: P112 Boot Floppy 01-30-17.img
Taken from: http://stack180.com/P112%20Downloads.htm
OK, well I think we have found the problem. You are somehow booting a different
floppy than I am. I downloaded "P112 Boot Floppy 01-30-17.zip" again and looked
at the extracted .img file with a hex editor. There is no occurrence of the string
"CCP+" in it anywhere. I am really perplexed by this. It sounds like your floppy still has a DOSPLUS image on it.
As a way to see if we actually do have different image files or not, I am listing
the first 16 bytes (in hex) of my image. Can you confirm yours is the same?
76 21 80 B3 C9 C3 00 CA 00 00 00 00 00 00 00 00
It is hard to imagine we are downloading different files from the same site. This may be a long shot, but is there any possibility that the tool you are using to write the image to the floppy is not actually working? Is the floppy
write protected? Could you use a different tool to read and verify the
first few bytes of the floppy?
Is this and/or ZCPR the only OSes that still run on the P112?
I hope not as that is not what I was looking for. Maybe I
waited to long for the P112 to stabilize and missed the boat
entirely. :-(
It is the most recent work with respect to P112 OSes, but
I am not aware of any issues with the other OSes ported to it.
I sent you down this path because it is a known working set
of stuff and would (hopefully) allow you to determine conclusively
whether your GIDE is fully functional.
And it still leaves me wondering why the pre-built CF image
doesn't boot. Am I also running the wrong ROM image on my
P112? It came from the same web page at stack180.
I agree it is a mystery why you are unable to boot the pre-built
CF image.
If your ROM boots and displays version 5.8 then you have the
ROM image from the stack180.com site which is definitely the
right ROM to boot the floppy and CF images from that site.
I guess I can't say if this ROM has in some way broken support
for the other OSes.
Sorry, this was a second question. I wondered if there was any
relationship between the DOS+ that was available for the P112
and the DOSPLUS that ran on the TRS80 Model 1m Model3 and Model4.
Ah, sorry. I don't have a clue about that. Sorry.
On Monday, December 12, 2022 at 11:25:55 AM UTC-8, Bill Gunshannon wrote:
On 12/12/22 13:57, Wayne Warthen wrote:
On Monday, December 12, 2022 at 6:28:49 AM UTC-8, Bill Gunshannon wrote: >>>Somehow I think we are looking at a different page and a different
The floppy disk image on stack180.com is not DOS+, it is BPBIOS which is >>> a derivative of the ZCPR series of CP/M compatible OSes. The hard disk
utilities are in user area 15.
floppy image.
Nope.
Just to make sure we are talking about the same floppy disk image, please >>> confirm that when you boot from it, the first line you see is as follows: >>>
P112 - B/P 52.00k Bios V1.3 28 Mar 17
CCP+ Vder, 2.2
Made from: P112 Boot Floppy 01-30-17.zip
Which gives: P112 Boot Floppy 01-30-17.img
Taken from: http://stack180.com/P112%20Downloads.htm
Well, I don't really know how but I hae it running.
I found an image called zs113005.img on a site
called 661.org and loaded it
onto a floppy. It booted giving a message about
not liking my NVRAM settings. I restarted the P112
and hit escape. Typed in values I thought were
reasonable and rebooted. It worked.
So, I thought I would try the CF again. I took the
128MB CF and put it in. "OS Loaded Booting" and there
it hung. So I took the 64 MB which it said was too
small and tried that. And it booted. ANd, I was able
to make a real boot floppy, just in case this all
falls apart.
I guess that's a start. Still need to see what I need
I need to do to get other OSes running but at least it's
better than I was yesterday.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 489 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 23:32:50 |
| Calls: | 9,665 |
| Files: | 13,716 |
| Messages: | 6,168,233 |