Вид для печати
Wow! Никаких плясок с бубном не надо, лишь добавить в конфиг точно такую же строку, что и для PROЦитата:
Сообщение от Djoni
QDI походу отличается от PRO только тем, что в нулевой дорожке пятый сектор имеет номер 5, а не 9.Код:QDI = 01010301050050002800040F008E017F00C00020000000
Да формат диска почти такой жа только каталог диска у Profi начинается с 0 track 0 sector а у Кворума я так понял с 4 trackа.
Да, с 4го.Цитата:
Сообщение от Djoni
Какого оно только черта тогда работает, непонятно :)
На всякий случай поменял на формат на 01010301050050002800040F008E017F00C00020000400
И получил практически копию конфига Ориона за исключением поля "user space size in 2048b blocks"
---------- Post added at 23:45 ---------- Previous post was at 21:59 ----------
Если что, перегнал все свои CP/M дискеты для Кворума в QDI, обновил соответствующий пост
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.Цитата:
Сообщение от Gelip
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.
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:Цитата:
Сообщение от ZXMAK
SYSGEN.COM offset 1400:
This is cpm_sys.kdi image:Код:$ 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
Код: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:
Menu 2 & 4 runs file SYS1.OVLКод: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 3 & 5 runs file SYS2.OVL
Вложение 41882 Вложение 41884
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.Цитата:
Another example: if we want to store disk image for the computer "Exercise", using extension "exe" is a bad idea.
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 :-)
wrong guess ;)Цитата:
Сообщение от Gelip
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?Цитата:
Сообщение от esl
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
OK, if KDI is standard should be open in CP/M Explorer but this is not possible.Цитата:
All CP/M-80 machines are compatible with each other because binary compatibility is the main reason for CP/M popularity.
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 ??
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.Цитата:
Сообщение от Gelip
Oh, I thought that it could be opened and the only problem is file extension.Цитата:
So if Byte01.kdi is not possible to open should not be called .KDI