I found that if I remove the first 136 sectors from the image it can be used by SIMH to boot. Likely any spared sector will not be properly corrected. Some info

Hard disk manual

gcc -o tomfmext tomfmext.c
./tomfmext < /tmp/ViewPoint-2.0-11-9-1990-18-38.img 
ext2emu --ext tomfmext.ext --emu tomfmext.emu --format xerox_8010 --heads 8 --cyl 512

todarkstar.c will convert the extracted data file from mfm tools to darkstar format.

./todarkstar > /tmp/dark.img

Both have hardcoded file names of convert.ext and convert.ext.metadata for the data files its converting.

The image converted from darkstar to emulator file didn't boot properly so more work is needed.

This machine uses TTL drivers which interfere with the automatic shutdown and power on function. See TTL driver support page for more information.

I made some Kaypro 10 disk images for a machine I was working on. This as made from mixture of 2.2G and 2.2H disk images. Found later other choices. My notes from creating the image. Emulator image kaypro10gh.zip and Directory listing. Also blank formatted emulator image disk

Set P7 to drive 2. Remove or set P8 to other than drive 2.

MFM emulator XENIX disk image

Circuit to power on beaglebone needed modification since 3.3V rises to about 1.9V when host computer is powered on. This is still being investigated but likely due to the OMTI 5200 using push pull instead of open collector drivers and feeding power through RN1 to the beaglebone. Fixed with rev D board

This machine uses TTL drivers which interfere with the automatic shutdown and power on function. See TTL driver support page for more information.

Recommend using fix in previous link. Users fix was to cut the trace going from U17 pin 1 to R3 and solder two series diodes (type 1n4148 or equivalent) from R3 (first diode Anode) to U17 pin 1 (second diode Cathode), From the junction between the two diodes solder a 47K 1/8 W resistor to ground. The function of this little circuit is to drop the 1.9 Volts, present during the power up problem, to a logic low level at U17 pin 1. Thread reporting and discussing issues"

The computer inverts the data bytes. See shell script at bottom of page which can be used to invert extracted data file.

Trying to create new disk image instead of using these !HForm Format may not work correctly. You can work around with these instructions. See last couple of messages.

Since I was last on here, I've implemented and included in the image
source+binaries for:
- dhcp client
- telnetd
- ifdump  (reverse engineered the network params)
- window manager
- ported uemacs
- whereis & tee
- binary patched 'ls' to work on a pseudo-terminal

Both uses first cylinder for storing disk format information. First two tracks has the format information. Rest of track on cylinder had different format so controller probably didn't format those tracks. If you are trying to use the extracted data file you will likely need to remove the first cylinder. Calculate cylinder size = bytes per sector * sectors per track * heads. For example 512*17*4 = 34816. Use dd to remove cylinder.
dd if=infile of=outfile bs=34816c skip=1

To use ext2emu the cylinder with the format information needs to be at the start of the extracted data file.

If you have an extracted data file and can't regenrate with --xebec_skew this code can remap the sectors. Format is Xebec_104527_512B