I think due to its age it will support 27256 eprom's the design is from begin 80'th. On the museum site you can find the schematics drawn by Tony. He reverse engineered the Integral and some modules, the drawing of the RAM-module explanes the pinout of the memory controller. That should make it possible to figure out the connections to the eproms. The software always contains some manual pages. And I think you have to look for the 'installing peripherals manual' for the integral HP-UX (V1.0 or V5.0) -Rik

Thanks Tony, that should be enough info for me to see if I can get the card to work. So the card will take both 27C256 and 27C512. I have enough 27C256 on hand to stuff the board with those. What is the HP marked IC 1820-2311? Is that the address comparator? I will have to create the EPROM tools disk and then take a look at what info and tools are there. -Glen

On Sat, Dec 6, 2008 at 12:08 PM, Tony Duell <ard at p850ug1.demon.co.uk> wrote: Tony, with your notes on the 82971A EPROM/ROM Module switch settings I was able to do a demonstration test of the one I have. I used (15x) 27C256 EPROMs and built the ROM image to start at 1MB (0x100000) so I set the switch settings like this: S1: ON,off,ON,ON,off,ON,off,ON S2: off,ON,ON,off,off,off,off,ON S3:ON,off,off,off,ON,off,off,ON I used merge_rom with the switches "-b100000 -c8000 -s70000" and built a 448KB ROM image with some of the HP-UX commands {cat, chmod, cp, csh, ls, mkdir, more, mv, pwd, rm, rmdir, sh, vi} and had about 11KB to spare. The set of files to merge into the ROM images were specified in a romrc file I created, along with the .init file from the Rtools disc which must do something magic. Then I used split_rom to create the 15x 27C256 EPROM images {lo0 - lo6, hi0 - hi6}, then use msdoscp to copy those image files to MS-DOS formatted floppy, then used my EPROM programmer PC to burn the 15x EPROMs. The first time I tried the EPROM module in the IPC I got a ROM checksum error message so I used verify_rom to compare the ROM in memory against the ROM image and found what EPROM corresponded to the mismatches. That turned out to be user error while programming that EPROM so I programmed another and tried again and then verify_rom successfully compared ROM in memory against the ROM image. So the end result of this demonstration is that I can boot the IPC without an HP-IB hard drive attached and have a dozen HP-UX commands on hand without swapping floppies. Maybe it would be more useful to put BASIC or some other utilities in the EPROM module for the occasions when the IPC might be used without the HP-IB hard drive attached. I'll repeat this experiment with 27C512 EPROMs when I get a handful of those in a few days. It would still be nice to find a copy of "HP82970A EPROM/ROM Software Development Tools Users Guide" for reference. -Glen EPROM/ROM Software Development Tools ************************************ Release 5.0 (c) Copyright 1986, Hewlett-Packard Co. This disc contains the tools needed to place applications in ROM for the Integral Personal Computer. Brief descriptions of the files found on this disc are: /Rtools Rtools.env - alternative environment that places /Rtools in PATH dump_rom - examines contents of physical ROMs in IPC ld_mod - program used by merge_rom to make ROM executable code merge_rom - creates logical ROM images prog_rom - transfers files to serial PROM programmer split_rom - creates IC images from logical ROM image verify_rom - compares a logical ROM image with physical ROMs view_rom - views the contents of a physical ROM image Installation note : If you are copying these programs to a hard disc, then you need to copy all of the above programs to the hard disc (including ld_mod). Copy the programs to a directory where you normally install executable programs. /Rtools/example1 7x10 - font used in example1 EPROM Autost - Autost file placed in example1 EPROM prog_am512 - command file to burn 512K bit ICs from AMD (AM27512DC) prog_i256 - command file to burn 256K bit EPROMs in DATAIO29B prog_i512 - command file to burn 512K bit EPROMS in DATAIO 29B pre_Iform - command file for Intel format transfer to DATAIO 29B pre_Mform - command file for Motorola format xfer to DATAIO 29B romrc - configuration file for merge_rom set_font - set_font program to be placed in EPROM status - status program to be placed in EPROM time_of_day - time_of_day program to be placed in EPROM /Rtools/example2 .init - program needed to be included in logical ROM image Autost - Autost script for example2 EPROMs romrc - ROM configuration file for merge_rom set_win.c - C source code for set_win to be made ROM executable For detailed information about these programs refer to your HP82970A EPROM/ROM Software Development Tools Users Guide. See the Appendix to this document for a tutorial in using these tools. Usage merge_rom: merge_rom -[bdfosv] <file_names> merge_rom merges files into a logical ROM disc image command line options: -b[hex_number] defines base address of the physical ROM -c[hex_number] defines the number of bytes per IC -f[file_name] names the configuration file for this ROM image -o[filename] defines name of the logical ROM image file -s[hex_number] defines the size of the ROM in bytes -v sets verbose mode -V displays the Version number of this program Defaults are: -b defaults to 0x80000 -c defaults to 0x10000 -f defaults to romrc -o defaults to ROM -s defaults to 0x80000

On Tue, Dec 9, 2008 at 11:15 AM, Tony Duell <ard at p850ug1.demon.co.uk> wrote: Yes, I'm not sure what I was thinking when I typed that. I filled (14x) of the max (16x) EPROM sockets with 27c256 EPROMs for a total of 448KB (458,752 bytes). Maybe some day a copy of that will turn up somewhere. I'm curious what the magic .init file does that appears to be necessary to include in the ROM image, and also what the file annotations mean in the romrc file. Maybe 'a' mean executable application that needs to be fixed up by ld_mod to execute in place, 'D' means non-executable data file, 's' means executable script file with no fix-ups necessary. Not sure what 'on' would mean. Here's the romrc file from the ROM tools disk example2: /Rtools/example2/.init /Rtools/example1/time_of_day a /Rtools/example1/set_font a /Rtools/example1/7x10 D /Rtools/example1/status a /Rtools/example2/Autost s /Rtools/example2/set_win on