Просмотр образов CP/M дисков

[Eltaron]

Если поплясать с бубном можно попробовать настроить плагин OdiWcx by Sergey A. для TotalCommanderа для работы с образами Кворума.

Wow! Никаких плясок с бубном не надо, лишь добавить в конфиг точно такую же строку, что и для PRO

QDI = 01010301050050002800040F008E017F00C00020000000

QDI походу отличается от PRO только тем, что в нулевой дорожке пятый сектор имеет номер 5, а не 9.

[Djoni]

Да формат диска почти такой жа только каталог диска у Profi начинается с 0 track 0 sector а у Кворума я так понял с 4 trackа.

[Eltaron]

Да формат диска почти такой жа только каталог диска у Profi начинается с 0 track 0 sector а у Кворума я так понял с 4 trackа.

Да, с 4го.
Какого оно только черта тогда работает, непонятно
На всякий случай поменял на формат на 01010301050050002800040F008E017F00C00020000400

И получил практически копию конфига Ориона за исключением поля "user space size in 2048b blocks"

---------- Post added at 23:45 ---------- Previous post was at 21:59 ----------

Если что, перегнал все свои CP/M дискеты для Кворума в QDI, обновил соответствующий пост

[ZXMAK]

"Byte01" should be have own file extension image like other clones because .KDI extension clearly indicates that is image for Korvet computer.

Floppy disk from Korvet not working in Byte01.

I don't think so, the file extension should indicate the file format instead of content name. For compatibility purposes, the file extesion should contains 3 letters. And this is not enough to cover all known file formats. So, using different file extensions for the same file format will cause format conflicts and wrong format interpretation.
So, the content name should be specified in the name instead of extension. For example:
bmygame.kdi - byte
kmygame.kdi - korvet


Also, I'm not sure that the kdi extension represent files with unique file format. Can you tell me format structure? I want to make sure that the kdi extension used in the right way...

Another example: if we want to store disk image for the computer "Exercise", using extension "exe" is a bad idea.

[Gelip]

I don't think so, the file extension should indicate the file format instead of content name.

Of course yes, but KDI Byte01 image is for Byte01 not for Korvet computer. After that, I do not understand why the system image was made on a floppy 800KB while data take only 257KB ??? In image is tool SYSGEN.COM to make OS disk and possible make other, smaller disk:
SYSGEN.COM offset 1400:

$ 1024*5*80 S2 DD-DS 776K
$ 1024*5*80 S3 DD-SS 380K
$ 1024*5*40 S3 DD-SS 182K
$ 512*9*80  S2 DD-DS 698K
$ 512*9*40  S2 DD-DS 338K
$ 512*9*80  S3 DD-SS 342K
$ 512*9*40  S3 DD-SS 164K
$ 256*16*80 S2 DD-DS 620K
$ 256*16*80 S3 DD-SS 304K
$ 256*16*40 S3 DD-SS 146K
$ 1024*5*80 korwet DD-DS 780K
$ 1024*5*80 korwet DD-SS 790K

This is cpm_sys.kdi image:

Offset              Description
00000 - 04FFF       Probably CP/M OS
05000 - 05FFF       File (directory) structure
06000 - 1DFFF       Files CP/M OS
1E000 - 21FFF       ZX Spectrum 48 original ROM (SYS2.OVL)
22000 - 25FFF       TR-DOS 5.01 (SYS3.OVL)
40500 - end file    empty E5 E5 E5...

This is MENU of program SYS.COM:

   wyberite revim raboty

1. operacionnaq sistema CP/M
2. operacionnaq sistema TR-DOS s bejsikom
                   p|wm "bajt"
3. operacionnaq sistema TR-DOS s bejsikom
                   p|wm "ZX SPECTRUM"
4. bejsik p|wm "bajt"
5. bejsik p|wm "ZX SPECTRUM"

Menu 2 & 4 runs file SYS1.OVL
Menu 3 & 5 runs file SYS2.OVL

Another example: if we want to store disk image for the computer "Exercise", using extension "exe" is a bad idea.

Of course, for "Byte01" need use extension that do not in Windows. I think that BYT or BTE is pretty good. I don't know of a program that use this extensions.

After that:

Korvet is clone IBM PC and is not compatible with ZX Spectrum.
Byte01 is clone ZX Spectrum and is compatible with ZX Spectrum :-)

[esl]

Korvet is clone IBM PC and is not compatible with ZX Spectrum.

wrong guess

Korvet is a i8080 based computer developed in NIIJAF MGU
mainly wide used for education purporses in schoool

[Gelip]

wrong guess

Korvet is a i8080 based computer developed in NIIJAF MGU
mainly wide used for education purporses in schoool

OK, maybe is not IBM PC clone but is not compatible from ZX Spectrum right?

[Eltaron]

OK, maybe is not IBM PC clone but is not compatible from ZX Spectrum right?

But KDI is not ZX Spectrum format at all, it is CP/M disk image. All CP/M-80 machines are compatible with each other because binary compatibility is the main reason for CP/M popularity.

[Gelip]

All CP/M-80 machines are compatible with each other because binary compatibility is the main reason for CP/M popularity.

OK, if KDI is standard should be open in CP/M Explorer but this is not possible.
So if Byte01.kdi is not possible to open should not be called .KDI

Let us assume that the author CP/M Explorer adds support for version Byte.KDI:

1. While open KDI image CP/M Explorer will have to scan file to recognize that is Korvet or Byte instead open file directly. It will take unnecessary time to recognize it.
2. In Windows is not possible set different file icon for the same file type - .kdi

If computer disk images such as Orion, Korvet, Kvorum etc. are the same why everyone uses a different file extension: .odi, .kdi, .qdi ?
I not understand why computer "Byte01" can not have its own extension name ??

[Eltaron]

If computer disk images such as Orion, Korvet, Kvorum etc. are the same why everyone uses a different file extension: .odi, .kdi, .qdi ?

Have no idea. Not familiar with Korvet, but Orion and Quorum disks seems to have exactly the same format: 1024 bytes per sector, 5 sectors per track, 80 tracks and all track sectors are numbered sequently from 1 to 5. The only reason to have different format is filesystem difference - but seems that Orion and Quorum filesystems are equal. It's better to unite all equal file formats under one single extension.

So if Byte01.kdi is not possible to open should not be called .KDI

Oh, I thought that it could be opened and the only problem is file extension.