Lviv PK-01 has been tested with HxC OK!
Lviv PK-01
MFM, 300rpm, 250000 bps
IBM ISO 2 sides, 80 tracks, 16 sectors per track, 256 bytes per sector
it also works OK on FM mode.
I'm attaching profile here.
Lviv PK-01 (USSR)
Lviv PK-01 (USSR)
- Attachments
-
- Lviv floppy_profile.zip
- (182 Bytes) Downloaded 584 times
Re: Lviv PK-01 (USSR)
Would be nice if you can post some pictures of these machines. They are very rare here ! 

Re: Lviv PK-01 (USSR)
Pictures in and out
http://www.retro-pc.net/musei/comp/pk_lviv/index_ru.htm
commercial from USSR TV
https://www.youtube.com/watch?v=bHhU_1hXWTE
http://www.retro-pc.net/musei/comp/pk_lviv/index_ru.htm
commercial from USSR TV
https://www.youtube.com/watch?v=bHhU_1hXWTE
Re: Lviv PK-01 (USSR)
Lviv PK-01 Chameleon DOS and CP/M36
* note PK-01 is unable to WRITE MFM disks due to CPU constraints
it READS MFM OK
MFM, 300rpm, 250000 bps
IBM ISO 2 sides, 83 tracks, 16 sectors per track, 256 bytes per sector
679 936 formatted capacity
and
FM, 300rpm, 250000 bps
IBM ISO 2 sides, 83 tracks, 9 sectors per track, 256 bytes per sector
382 464 formatted capacity
sector order 1,2,3 ...
Track header:
0x4e x 80 - GAP1
0x00 x 12 - sync
0xC2 x 3 - desync
0xFC - marker
0x4e x 65 - GAP
Sector header::
0x00 x 12 - sync
0xa1 x 3 - desync
0xfe - IDAM marker
tt - track number (starting #0)
sd - side
sc - sector number (starting #1)
0x01 - 256 bytes per sector
cc x 2 - CRC
0x4e x 22 - GAP2
Sector Data:
0x00 x 12 - sync
0xa1 x 3 - desync
0xfb - DATA AM marker
dd x 256 - data
cc x 2 - CRC
0x4e x 70 - GAP3
0x4e x 141 - GAP4
6510 bytes total
unformated MFM track at 300RPM = 6250 bytes
extra 40 bytes may be at GAP1 or GAP4
Disk catalog location: Track 0
Sector 0: 17 bytes disk attributes + 14 x 17 bytes file records + 1 byte = 0x00 padding to 256 bytes
Sector 1 and each subsequent: 15 x 17 bytes file records + 1 byte = 0x00 padding to 256 bytes
Disk attr in catalog - 17 bytes
- 11 bytes disk name
- 1 byte first free sector
- 1 byte first free track
- 1 byte write protection
- 3 bytes unknown
File entry in catalog - 17 bytes
- 8 bytes file name (if first byte = 0x01 then file is marked as deleted)
- 3 bytes file extention
- 1 byte file status: 0x00 Normal, 0x01 Protected, 0x02 Protected and Hidden;
- 1 byte file location sector
- 1 byte file location track
- 2 bytes RAM loading address = start address
- 1 byte file length in sectors of 256 bytes
* note PK-01 is unable to WRITE MFM disks due to CPU constraints
it READS MFM OK
MFM, 300rpm, 250000 bps
IBM ISO 2 sides, 83 tracks, 16 sectors per track, 256 bytes per sector
679 936 formatted capacity
and
FM, 300rpm, 250000 bps
IBM ISO 2 sides, 83 tracks, 9 sectors per track, 256 bytes per sector
382 464 formatted capacity
sector order 1,2,3 ...
Track header:
0x4e x 80 - GAP1
0x00 x 12 - sync
0xC2 x 3 - desync
0xFC - marker
0x4e x 65 - GAP
Sector header::
0x00 x 12 - sync
0xa1 x 3 - desync
0xfe - IDAM marker
tt - track number (starting #0)
sd - side
sc - sector number (starting #1)
0x01 - 256 bytes per sector
cc x 2 - CRC
0x4e x 22 - GAP2
Sector Data:
0x00 x 12 - sync
0xa1 x 3 - desync
0xfb - DATA AM marker
dd x 256 - data
cc x 2 - CRC
0x4e x 70 - GAP3
0x4e x 141 - GAP4
6510 bytes total
unformated MFM track at 300RPM = 6250 bytes
extra 40 bytes may be at GAP1 or GAP4
Disk catalog location: Track 0
Sector 0: 17 bytes disk attributes + 14 x 17 bytes file records + 1 byte = 0x00 padding to 256 bytes
Sector 1 and each subsequent: 15 x 17 bytes file records + 1 byte = 0x00 padding to 256 bytes
Disk attr in catalog - 17 bytes
- 11 bytes disk name
- 1 byte first free sector
- 1 byte first free track
- 1 byte write protection
- 3 bytes unknown
File entry in catalog - 17 bytes
- 8 bytes file name (if first byte = 0x01 then file is marked as deleted)
- 3 bytes file extention
- 1 byte file status: 0x00 Normal, 0x01 Protected, 0x02 Protected and Hidden;
- 1 byte file location sector
- 1 byte file location track
- 2 bytes RAM loading address = start address
- 1 byte file length in sectors of 256 bytes