1. The REH-IDE board puts +5V out on pin 28 of the IDE interface. This is an old standard. Current CF-IDE adapters bridge pin-28 to ground which will cause a direct short. I smoked one of my +5V traces before I figured this out. I recommend cutting the trace on the REH-IDE board going to pin 28. If Lamar corrects the trace in new boards, then this will not apply to the new boards.
2. Nothing indicates pin-1 on T1 or T2. I mounted mine "face up" which I believe is corect.
3. Be careful to observe pin-1 markings on resistor networks. They are not all the same orientation.
4. D1-4 are spaced too tight to fit individual T1 LEDs. Substitute Dialight 555-4001F (hard to find, but works perfectly).
5. SW-1 and SW-2 are not documented. Looks like you need to short 1-2 on each of them for normal operation. Alternatively, you can just omit IC15 and not implement the functionality which is not needed.
6. The mounting holes for CN3 are too small. I clipped some of the mounting connector to make it work.
7. Stick with Lattice GALs, preferably 15ns. Initial attempts with Atmel GALs resulted in sporadic I/O errors.
8. Use the exact chip family for each chip as specified in the BOM. Again, may be some timing issues with substitutions.

Question: Which is pin 1 on SW-1 and SW-2? What function do these serve?

Update: I'm guessing the top pair on each of these need to be jumpered, since the CPU280 will not run unless that's the case.

Also, which PLD fuse map should I be using? Looks like different port addresses are available: 70h, 80h, A0h, F0h and I'm not sure what Wayne's binary build is looking for.

Update: Looks like the BIOS assumes 80h, so I used that JED file to program the GAL.

1. Edited system.mac and loader.mac to set IDE to 'true' and rebuilt everything per documentation on a Windows 7 system.
2. Converted IMG to HFE and setup the new image as A:
3. Booted new ZPM3 master.
4. It announces that H:-K are IDE volumes, but it cannot access any of these (hangs)
5. Reboot. Run IDETEST. It is able to read parameters back from the 128M solid-state drive I'm using.
6. Set those parameters using option 1.
7. All the various tests, including write/read appear to run without complaint.

I programmed a new pair of EPROMs using odd/even from the IDE build. Doesn't seem to have affected anything one way or the other.

I did discover that the 'diskinfo' program sees h,i,j,k as 9 or 10 MB volumes, which agrees with the boot message about a "42 MB" hard disk being attached. All of the volumes are reported as full since the directories are not initialized. I have not been able to find a utility to clear them to E5, but by using 'erase' I opened up enough space in h0: to copy files to it and verify that it's working as block storage. That's certainly a good step in the right direction.

1. How do I reconfigure ZPM3 to accept 'h:' as a valid drive? The drive map is ABCDE---IJK in the Z-System parameters.

2. What is the correct approach to setting up hard disk partitioning?It's assuming a 42MB hard disk and enforcing built-in partitioning.

3. How do I initialize directories?

4. Is it possible to assign hard disk partitions to A,B, etc. and boot from them?

Unfortunately I cannot figure out how to do block fill over a range with du. There's a 'ch' (change) command, but it won't accept ranges beyond 0-7fh. I need 0-0ffffh. Am I misunderstanding the units?

A>du

DISK UTILITY v89
Universal Version under CP/M 3.1

Type ? for help
Type X to exit

:lk

:t0
G=0000:00, T=0, S=1, PS=0

:s1
G=0000:00, T=0, S=1, PS=0

:ch00-7f,e5
004455202020202020434F4D0000003C...
:<

:w

:+;>;w;/
G=0000:01, T=0, S=2, PS=0
G=0000:02, T=0, S=3, PS=0
G=0000:03, T=0, S=4, PS=0
G=0000:04, T=0, S=5, PS=1
G=0000:05, T=0, S=6, PS=1
G=0000:06, T=0, S=7, PS=1
G=0000:07, T=0, S=8, PS=1
G=0000:08, T=0, S=9, PS=2
G=0000:09, T=0, S=10, PS=2
G=0000:0A, T=0, S=11, PS=2
G=0000:0B, T=0, S=12, PS=2
G=0000:0C, T=0, S=13, PS=3
G=0000:0D, T=0, S=14, PS=3
G=0000:0E, T=0, S=15, PS=3
G=0000:0F, T=0, S=16, PS=3
G=0000:10, T=0, S=17, PS=4
G=0000:11, T=0, S=18, PS=4
G=0000:12, T=0, S=19, PS=4
G=0000:13, T=0, S=20, PS=4
G=0000:14, T=0, S=21, PS=5
G=0000:15, T=0, S=22, PS=5
G=0000:16, T=0, S=23, PS=5
G=0000:17, T=0, S=24, PS=5
G=0000:18, T=0, S=25, PS=6
G=0000:19, T=0, S=26, PS=6
G=0000:1A, T=0, S=27, PS=6
G=0000:1B, T=0, S=28, PS=6
G=0000:1C, T=0, S=29, PS=7
G=0000:1D, T=0, S=30, PS=7
G=0000:1E, T=0, S=31, PS=7
G=0000:1F, T=0, S=32, PS=7
G=0001:00, T=0, S=33, PS=8
G=0001:01, T=0, S=34, PS=8
G=0001:02, T=0, S=35, PS=8
G=0001:03, T=0, S=36, PS=8
G=0001:04, T=0, S=37, PS=9
G=0001:05, T=0, S=38, PS=9
G=0001:06, T=0, S=39, PS=9
G=0001:07, T=0, S=40, PS=9
G=0001:08, T=0, S=41, PS=10
G=0001:09, T=0, S=42, PS=10
G=0001:0A, T=0, S=43, PS=10
G=0001:0B, T=0, S=44, PS=10
G=0001:0C, T=0, S=45, PS=11
G=0001:0D, T=0, S=46, PS=11
G=0001:0E, T=0, S=47, PS=11
G=0001:0F, T=0, S=48, PS=11
G=0001:10^C
:x

The drive map issue affects all Z utilities that I've tried. For example, 'zxd' does not believe that disk h: exists, nor do 'zfiler', etc. The non-Z3 utilities (e.g. pip, set, etc. all work fine.

Is there any way to define the hard disks as, e.g. A,B,C,D and boot directly? Would be most convenient to have the system drive be a hard disk volume.

Yes, I was a bit confused trying to follow Tillman's directions. He refers to a SYSTEM.LIB file that I'm not able to locate in the sources from Github. Did that get moved to kernel.280?

Ah, ok. So the BIOS will assign drive letters as a function of the physical table positions in kernel.280?

I'd like to ask the group which way the 5V issue should be resolved: pull-up to 5V through a resistor, or left open?.

Would it be possible to add a jumper to optionally apply +5V to Pin 20?.