Based on my own experience from many years ago, Leeb, that doesn't sound right. Are you certain that you're not confusing a disk interleave with file data ordering?
The source disk SEEMS to read properly in the emulator and the file was directly xferred from there to a disk that I have never had issue reading/writing before... and from there thru 22disk to the PC...
However, the SID dump I did was done from WITHIN the emulator... 'printed' to a PC file as the emulator can (printed.prn) and played with from there...
But, simply put, I dont know enuf about the CPM3.sys file to say ANYTHING for certain... I cannot say where the loader begins/ends altho I THINK I know where (some of) the BDOS begins... and possibly the BIOS..
I did not keep a non-reordered version of the dump, but if you are interested/willing I will send you a copy of the 'reordered' SID dump I have...
I did not (yet) remove the location values from the front of the lines...
Radio Shack did not (naturally) supply anything but the generic 'start-from-scratch-with-examples-that-are-nowhere-close-to-your-machine' sources that come with CPM3 itself, so I can only go by what appears to be correct, text-wise...
The '3' system is simply so different from the MM 2.2 version Im used to working with that I am literally starting from scratch.
If I werent intending to build a new system for the machine Im designing as well as wanting to use it on the 4p it is likely that I would simply stay with 2.2 and modify it...
But... that wouldnt be.... fun! :D
EDIT:
From one of the CPM3 PDFs... regarding GENCPM:
Display Load Table at Cold Boot (Y) ?
Enter Y - On Cold Boot the system displays the
load table containing the
filename, filetype, hex starting address, length of system modules, and the TPA
size.
That answers that! :mrgreen:
EDIT2:
More from the PDF...
Table D-1. CPM3.SYS File Format
Record Contents
0 Header Record (128 bytes)
1 Print Record (128 bytes)
2-n CP/M 3 operating system in reverse order, top down.
Table D-2. Header Record Definition
Byte Contents
0 Top page plus one, at which the resident
portion of CP/M 3 is to be loaded top down.
1 Length in pages (256 bytes) of the resident
portion of CP/M 3.
2 Top page plus one, at which the banked portion
of CP/M 3 is to be loaded top down.
3 Length in pages (256 bytes) of the banked
portion of CP/M 3.
4-5 Address of CP/M 3 Cold Boot entry point.
6-15 Reserved.
16-51 Copyright Message.
52 Reserved.
53-58 Serial Number.
59-127 Reserved.
I read the above to mean that the file is loaded from FFFF down to whatever (presuming FFFF is the 'top' being used).
Or am I attempting to read 'something else'? :roll:
EDIT AGAIN:
That looks to be right according to what I have here...
0100: F4 27 80 34
00 D3 00 00 00 00 00 00 00 00 00 00 .'.4............
0110: 43 6F 70 79 72 69 67 68 74 20 28 43 29 20 31 39 Copyright (C) 19
0120: 38 32 2C 20 44 69 67 69 74 61 6C 20 52 65 73 65 82, Digital Rese
0130: 61 72 63 68 00 00 00 00 00 01 30 00 00 00 00 00 arch......0.....
0140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
That, I believe, is the Header Record (bold is the cold boot entry point [D300]), and
0180: 0D 0A 20 42 4E 4B 42 49 4F 53 33 20 53 50 52 20 .. BNKBIOS3 SPR
0190: 20 44 33 30 30 20 20 32 31 30 30 0D 0A 20 42 4E D300 2100.. BN
01A0: 4B 42 49 4F 53 33 20 53 50 52 20 20 37 41 30 30 KBIOS3 SPR 7A00
01B0: 20 20 30 36 30 30 0D 0A 20 52 45 53 42 44 4F 53 0600.. RESBDOS
01C0: 33 20 53 50 52 20 20 43 44 30 30 20 20 30 36 30 3 SPR CD00 060
01D0: 30 0D 0A 20 42 4E 4B 42 44 4F 53 33 20 53 50 52 0.. BNKBDOS3 SPR
01E0: 20 20 34 43 30 30 20 20 32 45 30 30 0D 0A 20 0A 4C00 2E00.. .
01F0: 0D 20 35 31 4B 20 54 50 41 0A 0D 24 24 24 24 24 . 51K TPA..$$$$$
is supposed to be the PRINT record...
I guess I will have to put this back into 'normal' order to see it fully, but it DOES seem to run from 'high' to 'low' and the 'end of file' is at the beginning...
Wow... :shock: