• Please review our updated Terms and Rules here

ICOM FDOS-III for the Poly88

I have the sources for FDOS-M EPROMS as its in the manual I have.
I'll look and see what in the history. Hex files I can work with.
 
I have the sources for FDOS-M EPROMS as its in the manual I have.
I'll look and see what in the history. Hex files I can work with.
The files on the 8" disk (Intel HEX) should be on page 1, the files on the 5.25" disk (Binary hex) on page 2.

One of the unanswered questions is this particular binary hex format, basically the content of the ASCII hex file but with binary values instead of ASCII values for all fields. It might have been something added by a 3rd party, but it's no certainty without more sources. Do your manual mention this format in any way?

And about the manual. It seems like there is a decent chance the manual you have may match the particular version of FDOS that is provided earlier in this thread. The similar manual on Bitsavers is for the 8" drive and controller, so from my understanding it took deramp quite a bit of figuring out (including sourcing a sample of the physical floppy disk controller card) to get it going on his setup. Do you by any chance have the ability to scan it?
 
Last edited:
I have the sources for FDOS-M EPROMS as its in the manual I have.
I'll look and see what in the history. Hex files I can work with.
I’ve never found an FDOS manual that covers FDOS-M and the MicroFloppy specifics of FDOS. If your manual talks about the MicroFloppy and the EPROM listing in the manual is for the MicroFloppy (5.25” drive), then we must get that manual scanned and archived! I’ll be glad to do that if you don’t want to.

Here’s a link to FDOS for the MicroFloppy created from the files user “per” found for us last year:


Mike D
 
Mike,
Thanks for all your work on resurrecting FDOS III and making the videos. I had no idea FDOS was a "lost" OS.

I still have an original 8" FDOS III floppy disk and manual configured for the IMSAI. But, I no longer have the drives and controllers.

Marvin
 
Mike,
Thanks for all your work on resurrecting FDOS III and making the videos. I had no idea FDOS was a "lost" OS.

I still have an original 8" FDOS III floppy disk and manual configured for the IMSAI. But, I no longer have the drives and controllers.

Marvin
Hallelujah! I created FDOS-III for the 8” drive from the 5.25” files discussed in this thread, and it works, but it is not truly the original 8” version. For example, it requires a modified version of the 5.25” FDOS EPROM instead of the original 8” FDOS EPROM, and it requires RAM at B800h since it cant use the scratchpad RAM on the interface board.

If you’re willing, I’d love to archive your disk and then recreate the original 8” version of FDOS.

Mike D
 
I will find it this weekend and make a disk image. Do you have a preferred format?

Marvin
 
A ”raw” image is fine - a linear dump of the sectors from track 0 sector 1 though track 76 sector 26. Should be 256,256 bytes long. Thanks!

Mike D
 
Here is FDOSIII ver1.1 for the IMSAI. It looks like a clean read. I wish I had an FD360 to play around with it. Maybe one of our electrical engineer folks will create a modern iCOM controller. Let us know if you can get this up and running.

In the zip you will find a raw disk image, a binary image, a photo of the system disk, and an ASCII dump of the contents. At the end of the ASCII dump is some interesting text:
NOW IS THE TIME FOR ALL GOOD COMPUTER PHREAQUES TO COME TO THE
AID OF THEIR CPU!
Followed by several lines of:
!!!!!!!!KILROY WAS HERE AND HE STOLE ALL THE SOURCE CODE!!!!!!!!!!!!

Marvin
 

Attachments

I pushed aside a couple of other projects, so that I could look at this disk sooner rather than later :) I now have the disk running on my Altair 8800 with an FD3712 drive cabinet (FD-360 with drives side by side instead of above each other). This is great! I’ll put together more information, a demo video, and the ability to run the disk under simh soon. Huge thanks to Marvin!
 
I have the sources for FDOS-M EPROMS as its in the manual I have.
I'll look and see what in the history. Hex files I can work with.
I’m going to rattle your cage periodically about getting your FDOS-M manual archived. It is the only FDOS manual that addresses the 5.25” version of FDOS that I’ve run across. Thanks!

Mike D
 
Mike,
Thanks for all your work on resurrecting FDOS III and making the videos. I had no idea FDOS was a "lost" OS.

I still have an original 8" FDOS III floppy disk and manual configured for the IMSAI. But, I no longer have the drives and controllers.

Marvin
Marvin,

What manuals do you have with that disk? Anything that covers the Relocating Macro Assembler and Linker?

Mike D
 
I did write a small program to retreive files from the disk image.

Code:
NAME    ATTR TRAK SCTR  SIZE

EXEC     01   05   01   00093
SYSGN    01   08   16   00030
RDBFL    01   09   20   00013
LIB      01   10   07   00033
DIAGS    01   11   14   00069
DIAGO    01   14   05   00028
DKHNB    01   15   07   00015
MTDKS    01   15   22   00095
MTDK     01   19   13   00019
CMNDF    01   20   06   00001
LINK     01   20   07   00055
TESTS    01   22   10   00055
BATCH    01   24   13   00008
EDIT     01   24   21   00058
ASMB     01   27   01   00158
TEST1    01   33   03   00001
COPY     01   33   04   00018

There also seems to be a TEST2, X, TESTB, TESTO and a TEST3 that has been deleted and can likely be recovered by just changing the file-table, and also a whole lot of files at the far end of the file-table that has been long since overwritten.

*Edit*
Re-added the files, due to a small bug in the script I made that screwed up where in a file it continues on the next track. Now it should be all correct.
 

Attachments

Last edited:
I did write a small program to retreive files from the disk image.

Code:
NAME    ATTR TRAK SCTR  SIZE

EXEC     01   05   01   00093
SYSGN    01   08   16   00030
RDBFL    01   09   20   00013
LIB      01   10   07   00033
DIAGS    01   11   14   00069
DIAGO    01   14   05   00028
DKHNB    01   15   07   00015
MTDKS    01   15   22   00095
MTDK     01   19   13   00019
CMNDF    01   20   06   00001
LINK     01   20   07   00055
TESTS    01   22   10   00055
BATCH    01   24   13   00008
EDIT     01   24   21   00058
ASMB     01   27   01   00158
TEST1    01   33   03   00001
COPY     01   33   04   00018

There also seems to be a TEST2, X, TESTB, TESTO and a TEST3 that has been deleted and can likely be recovered by just changing the file-table, and also a whole lot of files at the far end of the file-table that has been long since overwritten.
I pulled the files off as well. I noticed that most every executable file has the same problem the ones on the 5.25” version you found has: They don’t specify their own entry address, so if you run a program that doesn’t execute at 40h (default address that overlays/clobbers FDOS), then subsequent execution of the editor, assembler, etc., fails because it jumps to the address of the previously executed program.

I added a single hex record to each executable file that specifies its load address and prevents this problem.

Mike D
 
  • Like
Reactions: per
Marvin,

What manuals do you have with that disk? Anything that covers the Relocating Macro Assembler and Linker?

Mike D
I have:
FDOS-III Operator's Manual - September, 1977
FDOS-III Relocating Assembler Manual - September, 1977 (includes Link info)

Also have:
FDOS II Operator's Manual - Rev. October 15, 1976
and some FD360/CF360 docs.

Marvin
 
I have:
FDOS-III Operator's Manual - September, 1977
FDOS-III Relocating Assembler Manual - September, 1977 (includes Link info)

Also have:
FDOS II Operator's Manual - Rev. October 15, 1976
and some FD360/CF360 docs.

Marvin
Great! The community is missing the Relocating Assembler Manual. Can you scan it? If not, I'll be glad to do it. I figured out enough through trial and error to generate .hex files from it, but not enough to use the relocatable output option and linker.


For FD360 documentation, see if you have anything I don't have here:


Thanks!

Mike D
 
There also seems to be a TEST2, X, TESTB, TESTO and a TEST3 that has been deleted and can likely be recovered by just changing the file-table, and also a whole lot of files at the far end of the file-table that has been long since overwritten.
I figured what these are, they are generated and then deleted by the BATCH file, an example batch-script.
 
Great! The community is missing the Relocating Assembler Manual. Can you scan it? If not, I'll be glad to do it. I figured out enough through trial and error to generate .hex files from it, but not enough to use the relocatable output option and linker.


For FD360 documentation, see if you have anything I don't have here:


Thanks!

Mike D
I will try to get the assembler docs scanned this week. I will then check out the other stuff and see if it is already archived or not.

Marvin
 
I still have an original 8" FDOS III floppy disk and manual configured for the IMSAI. But, I no longer have the drives and controllers.

Marvin
Since it’s hard to come by a working FD-360 or FD-3712 setup, you can run original 8” FDOS disks using the Altair FDC+ and a couple of Shugart 800 drives or a couple of 5.25” HD drives (like the Teac 55-GFR). I’ll be making a video and posting more information soon.

Mike D
 
I attempted to scan the assembler manual today at work. They just installed new copiers/scanners and the scan function did not work. I informed the helpdesk and will try again next week.

Marvin
 
Back
Top