News games checked.

Post all your Kryoflux related topics in here. From questions about the hardware through to disks you've managed to image up and, probably most importantly, write back without any problems :)

Moderators: DrCoolZic, mr.vince, Moderator Team

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

News games checked.

Postby dlfrsilver » Sat Dec 17, 2016 2:40 pm

I got lately those games to check :

- Dragon's Lair
- Galactic Conqueror
- Highway Patrol 2
- Quartz
- Total Eclipse
- Transputor

Dragon's Lair disk format is actually unsupported (illegal sector numbering + Shift Track with Data over index + Sector within sector + Data Checksum error). The disks are seen as modified (i will need another dump to check if this is also the case on any other original, if it's not, could have been copied with the ST special Discovery Cartridge possibly).

Galactic Conqueror use the Starter/KBI-29 sectors in track 80 side 0.

Highway Patrol 2 is perfect, however it uses a fuzzy sector on track 0 side 0 and 1. This is unsupported yet.

Quartz use 11 sectors per track (nothing special).

Total Eclipse use a Copylock ST (long sector variant).

Transputor is perfect and not copy protected.
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

AtariZoll
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 2798
Joined: Mon Feb 20, 2012 4:42 pm
Contact:

Re: News games checked.

Postby AtariZoll » Sat Dec 17, 2016 4:47 pm

You can check any ReadySoft laserdisc game (Space Ace 1-2 ...) - they all use same system. There is no sector in sector, just truncated last sector, with checksum inside data area. All it is to put as much data possible on track, actually no any special protection beside that.
Negative feedback has usually positive effect.

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Sat Dec 17, 2016 5:17 pm

AtariZoll wrote:You can check any ReadySoft laserdisc game (Space Ace 1-2 ...) - they all use same system. There is no sector in sector, just truncated last sector, with checksum inside data area. All it is to put as much data possible on track, actually no any special protection beside that.


The last sector is not truncated, it roll over at the beginning of the track. And yes this game use what Dr Coolzic calls SWS aka sector within sector.

I have used Aufit aside the CTA, and it indicates that this game uses a complex disk format. It uses many copy protections as follows :

* 6400-6412 bytes per tracks,

* 11x512 bytes sectors on the 3 first tracks,

* followed by 6x1024 bytes tracks,

In those 6x1024 bytes tracks, a big number use a fuzzy sector.

* the index hole is never at the same place, it changes every tracks, with the following :

IIF-ISN (Invalid ID field: XXX is an invalid Sector Number (ISN)
DCE (data CRC error)
SWS (Sector within sector)
SHT-DOI (Shifted Track with Data Over Index)
FZS (Fuzzy sector)
SHT-DBI (Shifted Track with Data Beyond Index)

(SHT-DOI and SHT-DBI explains the index hole changing on every track.)

check the log :

Protection analysis for I:\KRYOFLUX\KODAK80\[Kryoflux-Atari ST] DragonsLair_disk format unsupported\DragonsLair-D1.raw

T00.0 SHT-DOI Shifted Track with Data over Index
T01.0 SHT-DOI Shifted Track with Data over Index

T01.0-S245 IIF-ISN Invalid ID Field: 245 is an Invalid Sector Number (ISN)
T01.0-S246 IIF-ISN Invalid ID Field: 246 is an Invalid Sector Number (ISN)
T01.0-S247 IIF-ISN Invalid ID Field: 247 is an Invalid Sector Number (ISN)
T01.0-S248 IIF-ISN Invalid ID Field: 248 is an Invalid Sector Number (ISN)
T01.0-S249 IIF-ISN Invalid ID Field: 249 is an Invalid Sector Number (ISN)
T01.0-S250 IIF-ISN Invalid ID Field: 250 is an Invalid Sector Number (ISN)
T01.0-S251 IIF-ISN Invalid ID Field: 251 is an Invalid Sector Number (ISN)

T02.0 SHT-DOI Shifted Track with Data over Index

T02.0-S250 IIF-ISN Invalid ID Field: 250 is an Invalid Sector Number (ISN)
T02.0-S251 IIF-ISN Invalid ID Field: 251 is an Invalid Sector Number (ISN)
T02.0-S245 IIF-ISN Invalid ID Field: 245 is an Invalid Sector Number (ISN)
T02.0-S246 IIF-ISN Invalid ID Field: 246 is an Invalid Sector Number (ISN)
T02.0-S247 IIF-ISN Invalid ID Field: 247 is an Invalid Sector Number (ISN)
T02.0-S248 IIF-ISN Invalid ID Field: 248 is an Invalid Sector Number (ISN)
T02.0-S249 IIF-ISN Invalid ID Field: 249 is an Invalid Sector Number (ISN)

T03.0 SHT-DOI Shifted Track with Data over Index

T03.0-S246 IIF-ISN Invalid ID Field: 246 is an Invalid Sector Number (ISN)
T03.0-S247 IIF-ISN Invalid ID Field: 247 is an Invalid Sector Number (ISN)
T03.0-S248 IIF-ISN Invalid ID Field: 248 is an Invalid Sector Number (ISN)
T03.0-S249 IIF-ISN Invalid ID Field: 249 is an Invalid Sector Number (ISN)
T03.0-S250 IIF-ISN Invalid ID Field: 250 is an Invalid Sector Number (ISN)
T03.0-S251 IIF-ISN Invalid ID Field: 251 is an Invalid Sector Number (ISN)
T03.0-S245 IIF-ISN Invalid ID Field: 245 is an Invalid Sector Number (ISN)
T04.0-S245 IIF-ISN Invalid ID Field: 245 is an Invalid Sector Number (ISN)
T04.0-S246 IIF-ISN Invalid ID Field: 246 is an Invalid Sector Number (ISN)
T04.0-S247 IIF-ISN Invalid ID Field: 247 is an Invalid Sector Number (ISN)
T04.0-S248 IIF-ISN Invalid ID Field: 248 is an Invalid Sector Number (ISN)
T04.0-S249 IIF-ISN Invalid ID Field: 249 is an Invalid Sector Number (ISN)
T04.0-S250 IIF-ISN Invalid ID Field: 250 is an Invalid Sector Number (ISN)
T04.0-S251 IIF-ISN Invalid ID Field: 251 is an Invalid Sector Number (ISN)

T05.0 SHT-DOI Shifted Track with Data over Index
T05.0-S15 DCE DATA CRC Error
T05.0-S10 SWS Sector Within Sector
T06.0 SHT-DOI Shifted Track with Data over Index
T06.0-S17 DCE DATA CRC Error
T06.0-S12 SWS Sector Within Sector
T07.0 SHT-DOI Shifted Track with Data over Index
T07.0-S19 DCE DATA CRC Error
T07.0-S14 SWS Sector Within Sector
T08.0 SHT-DOI Shifted Track with Data over Index
T08.0-S21 DCE DATA CRC Error
T08.0-S21 FZS Fuzzy Sector
T08.0-S16 SWS Sector Within Sector
T09.0 SHT-DOI Shifted Track with Data over Index
T09.0-S23 DCE DATA CRC Error
T09.0-S23 FZS Fuzzy Sector
T10.0 SHT-DOI Shifted Track with Data over Index
T10.0-S25 DCE DATA CRC Error
T10.0-S20 SWS Sector Within Sector
T11.0 SHT-DBI Shifted Track with Data Beyond Index
T11.0-S27 DCE DATA CRC Error
T11.0-S22 SWS Sector Within Sector
T12.0 SHT-DOI Shifted Track with Data over Index
T12.0-S29 DCE DATA CRC Error
T12.0-S24 SWS Sector Within Sector
T13.0 SHT-DOI Shifted Track with Data over Index
T13.0-S31 DCE DATA CRC Error
T13.0-S26 SWS Sector Within Sector
T14.0 SHT-DOI Shifted Track with Data over Index
T14.0-S33 DCE DATA CRC Error
T15.0 SHT-DOI Shifted Track with Data over Index
T15.0-S35 DCE DATA CRC Error
T15.0-S35 FZS Fuzzy Sector
T15.0-S30 SWS Sector Within Sector
T16.0 SHT-DOI Shifted Track with Data over Index
T16.0-S37 DCE DATA CRC Error
T16.0-S32 SWS Sector Within Sector
T17.0 SHT-DOI Shifted Track with Data over Index
T17.0-S39 DCE DATA CRC Error
T17.0-S39 FZS Fuzzy Sector
T17.0-S34 SWS Sector Within Sector
T18.0 SHT-DBI Shifted Track with Data Beyond Index
T18.0-S41 DCE DATA CRC Error
T18.0-S36 SWS Sector Within Sector
T19.0 SHT-DOI Shifted Track with Data over Index
T19.0-S43 DCE DATA CRC Error
T20.0 SHT-DOI Shifted Track with Data over Index
T20.0-S45 DCE DATA CRC Error
T20.0-S40 SWS Sector Within Sector
T21.0 SHT-DOI Shifted Track with Data over Index
T21.0-S47 DCE DATA CRC Error
T21.0-S42 SWS Sector Within Sector
T22.0 SHT-DOI Shifted Track with Data over Index
T22.0-S49 DCE DATA CRC Error
T22.0-S49 FZS Fuzzy Sector
T22.0-S44 SWS Sector Within Sector
T23.0 SHT-DOI Shifted Track with Data over Index
T23.0-S51 DCE DATA CRC Error
T23.0-S46 SWS Sector Within Sector
T24.0 SHT-DOI Shifted Track with Data over Index
T24.0-S53 DCE DATA CRC Error
T24.0-S53 FZS Fuzzy Sector
T25.0 SHT-DBI Shifted Track with Data Beyond Index
T25.0-S55 DCE DATA CRC Error
T25.0-S50 SWS Sector Within Sector
T26.0 SHT-DOI Shifted Track with Data over Index
T26.0-S57 DCE DATA CRC Error
T26.0-S52 SWS Sector Within Sector
T27.0 SHT-DOI Shifted Track with Data over Index
T27.0-S59 DCE DATA CRC Error
T27.0-S54 SWS Sector Within Sector
T28.0 SHT-DOI Shifted Track with Data over Index
T28.0-S61 DCE DATA CRC Error
T28.0-S56 SWS Sector Within Sector
T29.0 SHT-DOI Shifted Track with Data over Index
T29.0-S63 DCE DATA CRC Error
T30.0 SHT-DOI Shifted Track with Data over Index
T30.0-S65 DCE DATA CRC Error
T30.0-S60 SWS Sector Within Sector
T31.0 SHT-DOI Shifted Track with Data over Index
T31.0-S67 DCE DATA CRC Error
T31.0-S62 SWS Sector Within Sector
T32.0 SHT-DBI Shifted Track with Data Beyond Index
T32.0-S69 DCE DATA CRC Error
T32.0-S64 SWS Sector Within Sector
T33.0 SHT-DOI Shifted Track with Data over Index
T33.0-S71 DCE DATA CRC Error
T33.0-S66 SWS Sector Within Sector
T34.0 SHT-DOI Shifted Track with Data over Index
T34.0-S73 DCE DATA CRC Error
T35.0 SHT-DOI Shifted Track with Data over Index
T35.0-S75 DCE DATA CRC Error
T35.0-S70 SWS Sector Within Sector
T36.0 SHT-DOI Shifted Track with Data over Index
T36.0-S77 DCE DATA CRC Error
T36.0-S72 SWS Sector Within Sector
T37.0 SHT-DOI Shifted Track with Data over Index
T37.0-S79 DCE DATA CRC Error
T37.0-S74 SWS Sector Within Sector
T38.0 SHT-DOI Shifted Track with Data over Index
T38.0-S81 DCE DATA CRC Error
T38.0-S76 SWS Sector Within Sector
T39.0 SHT-DBI Shifted Track with Data Beyond Index
T39.0-S83 DCE DATA CRC Error
T40.0 SHT-DOI Shifted Track with Data over Index
T40.0-S85 DCE DATA CRC Error
T40.0-S80 SWS Sector Within Sector
T41.0 SHT-DOI Shifted Track with Data over Index
T41.0-S87 DCE DATA CRC Error
T41.0-S82 SWS Sector Within Sector
T42.0 SHT-DOI Shifted Track with Data over Index
T42.0-S89 DCE DATA CRC Error
T42.0-S84 SWS Sector Within Sector
T43.0 SHT-DOI Shifted Track with Data over Index
T43.0-S91 DCE DATA CRC Error
T43.0-S86 SWS Sector Within Sector
T44.0 SHT-DOI Shifted Track with Data over Index
T44.0-S93 DCE DATA CRC Error
T44.0-S88 SWS Sector Within Sector
T45.0 SHT-DOI Shifted Track with Data over Index
T45.0-S95 DCE DATA CRC Error
T45.0-S95 FZS Fuzzy Sector
T45.0-S90 SWS Sector Within Sector
T46.0 SHT-DOI Shifted Track with Data over Index
T46.0-S97 DCE DATA CRC Error
T46.0-S92 SWS Sector Within Sector
T47.0 SHT-DOI Shifted Track with Data over Index
T47.0-S99 DCE DATA CRC Error
T47.0-S94 SWS Sector Within Sector
T48.0 SHT-DOI Shifted Track with Data over Index
T48.0-S101 DCE DATA CRC Error
T48.0-S101 FZS Fuzzy Sector
T48.0-S96 SWS Sector Within Sector
T49.0 SHT-DOI Shifted Track with Data over Index
T49.0-S103 DCE DATA CRC Error
T49.0-S103 FZS Fuzzy Sector
T49.0-S98 SWS Sector Within Sector
T50.0 SHT-DOI Shifted Track with Data over Index
T50.0-S105 DCE DATA CRC Error
T50.0-S100 SWS Sector Within Sector
T51.0 SHT-DOI Shifted Track with Data over Index
T51.0-S107 DCE DATA CRC Error
T52.0 SHT-DOI Shifted Track with Data over Index
T52.0-S109 DCE DATA CRC Error
T52.0-S109 FZS Fuzzy Sector
T52.0-S104 SWS Sector Within Sector
T53.0 SHT-DOI Shifted Track with Data over Index
T53.0-S111 DCE DATA CRC Error
T53.0-S106 SWS Sector Within Sector
T54.0 SHT-DOI Shifted Track with Data over Index
T54.0-S113 DCE DATA CRC Error
T54.0-S108 SWS Sector Within Sector
T55.0 SHT-DOI Shifted Track with Data over Index
T55.0-S115 DCE DATA CRC Error
T55.0-S115 FZS Fuzzy Sector
T55.0-S110 SWS Sector Within Sector
T56.0 SHT-DOI Shifted Track with Data over Index
T56.0-S117 DCE DATA CRC Error
T56.0-S117 FZS Fuzzy Sector
T57.0 SHT-DOI Shifted Track with Data over Index
T57.0-S119 DCE DATA CRC Error
T57.0-S114 SWS Sector Within Sector
T58.0 SHT-DOI Shifted Track with Data over Index
T58.0-S121 DCE DATA CRC Error
T58.0-S116 SWS Sector Within Sector
T59.0 SHT-DOI Shifted Track with Data over Index
T59.0-S123 DCE DATA CRC Error
T59.0-S123 FZS Fuzzy Sector
T59.0-S118 SWS Sector Within Sector
T60.0 SHT-DOI Shifted Track with Data over Index
T60.0-S125 DCE DATA CRC Error
T60.0-S120 SWS Sector Within Sector
T61.0 SHT-DOI Shifted Track with Data over Index
T61.0-S127 DCE DATA CRC Error
T61.0-S127 FZS Fuzzy Sector
T62.0 SHT-DOI Shifted Track with Data over Index
T62.0-S129 DCE DATA CRC Error
T62.0-S124 SWS Sector Within Sector
T63.0 SHT-DOI Shifted Track with Data over Index
T63.0-S131 DCE DATA CRC Error
T63.0-S126 SWS Sector Within Sector
T64.0 SHT-DOI Shifted Track with Data over Index
T64.0-S133 DCE DATA CRC Error
T64.0-S128 SWS Sector Within Sector
T65.0 SHT-DOI Shifted Track with Data over Index
T65.0-S135 DCE DATA CRC Error
T65.0-S130 SWS Sector Within Sector
T66.0 SHT-DOI Shifted Track with Data over Index
T66.0-S137 DCE DATA CRC Error
T67.0 SHT-DOI Shifted Track with Data over Index
T67.0-S139 DCE DATA CRC Error
T67.0-S139 FZS Fuzzy Sector
T67.0-S134 SWS Sector Within Sector
T68.0 SHT-DOI Shifted Track with Data over Index
T68.0-S141 DCE DATA CRC Error
T68.0-S136 SWS Sector Within Sector
T69.0 SHT-DOI Shifted Track with Data over Index
T69.0-S143 DCE DATA CRC Error
T69.0-S138 SWS Sector Within Sector
T70.0 SHT-DOI Shifted Track with Data over Index
T70.0-S145 DCE DATA CRC Error
T70.0-S140 SWS Sector Within Sector
T71.0 SHT-DOI Shifted Track with Data over Index
T71.0-S147 DCE DATA CRC Error
T72.0 SHT-DOI Shifted Track with Data over Index
T72.0-S149 DCE DATA CRC Error
T72.0-S149 FZS Fuzzy Sector
T72.0-S144 SWS Sector Within Sector
T73.0 SHT-DOI Shifted Track with Data over Index
T73.0-S151 DCE DATA CRC Error
T73.0-S146 SWS Sector Within Sector
T74.0 SHT-DOI Shifted Track with Data over Index
T74.0-S153 DCE DATA CRC Error
T74.0-S148 SWS Sector Within Sector
T75.0 SHT-DOI Shifted Track with Data over Index
T75.0-S155 DCE DATA CRC Error
T75.0-S150 SWS Sector Within Sector
T76.0 SHT-DOI Shifted Track with Data over Index
T76.0-S157 DCE DATA CRC Error
T77.0 SHT-DOI Shifted Track with Data over Index
T77.0-S159 DCE DATA CRC Error
T77.0-S154 SWS Sector Within Sector
T78.0 SHT-DOI Shifted Track with Data over Index
T78.0-S161 DCE DATA CRC Error
T78.0-S156 SWS Sector Within Sector
T79.0 SHT-DOI Shifted Track with Data over Index
T79.0-S163 DCE DATA CRC Error
T79.0-S158 SWS Sector Within Sector
T00.1 SHT-DOI Shifted Track with Data over Index
T00.1-S6 DCE DATA CRC Error
T00.1-S1 SWS Sector Within Sector
T01.1 SHT-DBI Shifted Track with Data Beyond Index
T01.1-S8 DCE DATA CRC Error
T01.1-S3 SWS Sector Within Sector
T02.1 SHT-DOI Shifted Track with Data over Index
T02.1-S10 DCE DATA CRC Error
T02.1-S5 SWS Sector Within Sector
T03.1 SHT-DOI Shifted Track with Data over Index
T03.1-S12 DCE DATA CRC Error
T03.1-S7 SWS Sector Within Sector
T04.1 SHT-DBI Shifted Track with Data Beyond Index
T04.1-S14 DCE DATA CRC Error
T05.1 SHT-DOI Shifted Track with Data over Index
T05.1-S16 DCE DATA CRC Error
T05.1-S11 SWS Sector Within Sector
T06.1 SHT-DOI Shifted Track with Data over Index
T06.1-S18 DCE DATA CRC Error
T06.1-S13 SWS Sector Within Sector
T07.1 SHT-DOI Shifted Track with Data over Index
T07.1-S20 DCE DATA CRC Error
T07.1-S20 FZS Fuzzy Sector
T07.1-S15 SWS Sector Within Sector
T08.1 SHT-DOI Shifted Track with Data over Index
T08.1-S22 DCE DATA CRC Error
T08.1-S17 SWS Sector Within Sector
T09.1 SHT-DOI Shifted Track with Data over Index
T09.1-S24 DCE DATA CRC Error
T09.1-S19 SWS Sector Within Sector
T10.1 SHT-DOI Shifted Track with Data over Index
T10.1-S26 DCE DATA CRC Error
T10.1-S21 SWS Sector Within Sector
T11.1 SHT-DOI Shifted Track with Data over Index
T11.1-S28 DCE DATA CRC Error
T11.1-S28 FZS Fuzzy Sector
T11.1-S23 SWS Sector Within Sector
T12.1 SHT-DOI Shifted Track with Data over Index
T12.1-S30 DCE DATA CRC Error
T12.1-S25 SWS Sector Within Sector
T13.1 SHT-DOI Shifted Track with Data over Index
T13.1-S32 DCE DATA CRC Error
T13.1-S27 SWS Sector Within Sector
T14.1 SHT-DOI Shifted Track with Data over Index
T14.1-S34 DCE DATA CRC Error
T14.1-S29 SWS Sector Within Sector
T15.1 SHT-DOI Shifted Track with Data over Index
T15.1-S36 DCE DATA CRC Error
T15.1-S36 FZS Fuzzy Sector
T15.1-S31 SWS Sector Within Sector
T16.1 SHT-DOI Shifted Track with Data over Index
T16.1-S38 DCE DATA CRC Error
T17.1 SHT-DOI Shifted Track with Data over Index
T17.1-S40 DCE DATA CRC Error
T17.1-S35 SWS Sector Within Sector
T18.1 SHT-DOI Shifted Track with Data over Index
T18.1-S42 DCE DATA CRC Error
T18.1-S37 SWS Sector Within Sector
T19.1 SHT-DOI Shifted Track with Data over Index
T19.1-S44 DCE DATA CRC Error
T19.1-S39 SWS Sector Within Sector
T20.1 SHT-DOI Shifted Track with Data over Index
T20.1-S46 DCE DATA CRC Error
T20.1-S46 FZS Fuzzy Sector
T20.1-S41 SWS Sector Within Sector
T21.1 SHT-DOI Shifted Track with Data over Index
T21.1-S48 DCE DATA CRC Error
T22.1 SHT-DOI Shifted Track with Data over Index
T22.1-S50 DCE DATA CRC Error
T22.1-S45 SWS Sector Within Sector
T23.1 SHT-DOI Shifted Track with Data over Index
T23.1-S52 DCE DATA CRC Error
T23.1-S52 FZS Fuzzy Sector
T23.1-S47 SWS Sector Within Sector
T24.1 SHT-DOI Shifted Track with Data over Index
T24.1-S54 DCE DATA CRC Error
T24.1-S49 SWS Sector Within Sector
T25.1 SHT-DOI Shifted Track with Data over Index
T25.1-S56 DCE DATA CRC Error
T25.1-S51 SWS Sector Within Sector
T26.1 SHT-DOI Shifted Track with Data over Index
T26.1-S58 DCE DATA CRC Error
T26.1-S58 FZS Fuzzy Sector
T27.1 SHT-DOI Shifted Track with Data over Index
T27.1-S60 DCE DATA CRC Error
T27.1-S60 FZS Fuzzy Sector
T27.1-S55 SWS Sector Within Sector
T28.1 SHT-DOI Shifted Track with Data over Index
T28.1-S62 DCE DATA CRC Error
T28.1-S57 SWS Sector Within Sector
T29.1 SHT-DOI Shifted Track with Data over Index
T29.1-S64 DCE DATA CRC Error
T29.1-S59 SWS Sector Within Sector
T30.1 SHT-DOI Shifted Track with Data over Index
T30.1-S66 DCE DATA CRC Error
T30.1-S66 FZS Fuzzy Sector
T30.1-S61 SWS Sector Within Sector
T31.1 SHT-DOI Shifted Track with Data over Index
T31.1-S68 DCE DATA CRC Error
T31.1-S68 FZS Fuzzy Sector
T32.1 SHT-DOI Shifted Track with Data over Index
T32.1-S70 DCE DATA CRC Error
T32.1-S65 SWS Sector Within Sector
T33.1 SHT-DOI Shifted Track with Data over Index
T33.1-S72 DCE DATA CRC Error
T33.1-S67 SWS Sector Within Sector
T34.1 SHT-DOI Shifted Track with Data over Index
T34.1-S74 DCE DATA CRC Error
T34.1-S69 SWS Sector Within Sector
T35.1 SHT-DOI Shifted Track with Data over Index
T35.1-S76 DCE DATA CRC Error
T35.1-S76 FZS Fuzzy Sector
T35.1-S71 SWS Sector Within Sector
T36.1 SHT-DOI Shifted Track with Data over Index
T36.1-S78 DCE DATA CRC Error
T37.1 SHT-DOI Shifted Track with Data over Index
T37.1-S80 DCE DATA CRC Error
T37.1-S80 FZS Fuzzy Sector
T37.1-S75 SWS Sector Within Sector
T38.1 SHT-DOI Shifted Track with Data over Index
T38.1-S82 DCE DATA CRC Error
T38.1-S77 SWS Sector Within Sector
T39.1 SHT-DOI Shifted Track with Data over Index
T39.1-S84 DCE DATA CRC Error
T39.1-S79 SWS Sector Within Sector
T40.1 SHT-DOI Shifted Track with Data over Index
T40.1-S86 DCE DATA CRC Error
T40.1-S81 SWS Sector Within Sector
T41.1 SHT-DOI Shifted Track with Data over Index
T41.1-S88 DCE DATA CRC Error
T41.1-S88 FZS Fuzzy Sector
T42.1 SHT-DOI Shifted Track with Data over Index
T42.1-S90 DCE DATA CRC Error
T42.1-S90 FZS Fuzzy Sector
T42.1-S85 SWS Sector Within Sector
T43.1 SHT-DOI Shifted Track with Data over Index
T43.1-S92 DCE DATA CRC Error
T43.1-S87 SWS Sector Within Sector
T44.1 SHT-DOI Shifted Track with Data over Index
T44.1-S94 DCE DATA CRC Error
T44.1-S89 SWS Sector Within Sector
T45.1 SHT-DOI Shifted Track with Data over Index
T45.1-S96 DCE DATA CRC Error
T45.1-S91 SWS Sector Within Sector
T46.1 SHT-DOI Shifted Track with Data over Index
T46.1-S98 DCE DATA CRC Error
T46.1-S98 FZS Fuzzy Sector
T47.1 SHT-DOI Shifted Track with Data over Index
T47.1-S100 DCE DATA CRC Error
T47.1-S95 SWS Sector Within Sector
T48.1 SHT-DOI Shifted Track with Data over Index
T48.1-S102 DCE DATA CRC Error
T48.1-S102 FZS Fuzzy Sector
T48.1-S97 SWS Sector Within Sector
T49.1 SHT-DOI Shifted Track with Data over Index
T49.1-S104 DCE DATA CRC Error
T49.1-S99 SWS Sector Within Sector
T50.1 SHT-DOI Shifted Track with Data over Index
T50.1-S106 DCE DATA CRC Error
T50.1-S101 SWS Sector Within Sector
T51.1 SHT-DOI Shifted Track with Data over Index
T51.1-S108 DCE DATA CRC Error
T51.1-S108 FZS Fuzzy Sector
T51.1-S103 SWS Sector Within Sector
T52.1 SHT-DOI Shifted Track with Data over Index
T52.1-S110 DCE DATA CRC Error
T52.1-S105 SWS Sector Within Sector
T53.1 SHT-DOI Shifted Track with Data over Index
T53.1-S112 DCE DATA CRC Error
T53.1-S107 SWS Sector Within Sector
T54.1 SHT-DOI Shifted Track with Data over Index
T54.1-S114 DCE DATA CRC Error
T54.1-S109 SWS Sector Within Sector
T55.1 SHT-DOI Shifted Track with Data over Index
T55.1-S116 DCE DATA CRC Error
T55.1-S111 SWS Sector Within Sector
T56.1 SHT-DOI Shifted Track with Data over Index
T56.1-S118 DCE DATA CRC Error
T56.1-S113 SWS Sector Within Sector
T57.1 SHT-DOI Shifted Track with Data over Index
T57.1-S120 DCE DATA CRC Error
T57.1-S115 SWS Sector Within Sector
T58.1 SHT-IBI Shifted Track with ID Beyond Index
T58.1-S122 DCE DATA CRC Error
T58.1-S117 SWS Sector Within Sector
T59.1 SHT-DOI Shifted Track with Data over Index
T59.1-S124 DCE DATA CRC Error
T59.1-S124 FZS Fuzzy Sector
T59.1-S119 SWS Sector Within Sector
T60.1 SHT-DOI Shifted Track with Data over Index
T60.1-S126 DCE DATA CRC Error
T60.1-S121 SWS Sector Within Sector
T61.1 SHT-DOI Shifted Track with Data over Index
T61.1-S128 DCE DATA CRC Error
T61.1-S123 SWS Sector Within Sector
T62.1 SHT-DOI Shifted Track with Data over Index
T62.1-S130 DCE DATA CRC Error
T62.1-S125 SWS Sector Within Sector
T63.1 SHT-DOI Shifted Track with Data over Index
T63.1-S132 DCE DATA CRC Error
T64.1 SHT-DOI Shifted Track with Data over Index
T64.1-S134 DCE DATA CRC Error
T64.1-S134 FZS Fuzzy Sector
T64.1-S129 SWS Sector Within Sector
T65.1-S136 DCE DATA CRC Error
T65.1-S131 SWS Sector Within Sector
T66.1 SHT-DOI Shifted Track with Data over Index
T66.1-S138 DCE DATA CRC Error
T66.1-S133 SWS Sector Within Sector
T67.1 SHT-DOI Shifted Track with Data over Index
T67.1-S140 DCE DATA CRC Error
T67.1-S135 SWS Sector Within Sector
T68.1 SHT-DOI Shifted Track with Data over Index
T68.1-S142 DCE DATA CRC Error
T69.1 SHT-DOI Shifted Track with Data over Index
T69.1-S144 DCE DATA CRC Error
T69.1-S139 SWS Sector Within Sector
T70.1 SHT-DOI Shifted Track with Data over Index
T70.1-S146 DCE DATA CRC Error
T70.1-S141 SWS Sector Within Sector
T71.1 SHT-DOI Shifted Track with Data over Index
T71.1-S148 DCE DATA CRC Error
T71.1-S143 SWS Sector Within Sector
T72.1-S150 DCE DATA CRC Error
T72.1-S145 SWS Sector Within Sector
T73.1 SHT-DOI Shifted Track with Data over Index
T73.1-S152 DCE DATA CRC Error
T74.1 SHT-DOI Shifted Track with Data over Index
T74.1-S154 DCE DATA CRC Error
T74.1-S154 FZS Fuzzy Sector
T74.1-S149 SWS Sector Within Sector
T75.1 SHT-DOI Shifted Track with Data over Index
T75.1-S156 DCE DATA CRC Error
T75.1-S151 SWS Sector Within Sector
T76.1 SHT-DOI Shifted Track with Data over Index
T76.1-S158 DCE DATA CRC Error
T76.1-S153 SWS Sector Within Sector
T77.1 SHT-DOI Shifted Track with Data over Index
T77.1-S160 DCE DATA CRC Error
T77.1-S155 SWS Sector Within Sector
T78.1 SHT-DOI Shifted Track with Data over Index
T78.1-S162 DCE DATA CRC Error
T79.1 SHT-DOI Shifted Track with Data over Index
T79.1-S164 DCE DATA CRC Error
T79.1-S159 SWS Sector Within Sector
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

AtariZoll
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 2798
Joined: Mon Feb 20, 2012 4:42 pm
Contact:

Re: News games checked.

Postby AtariZoll » Sat Dec 17, 2016 10:02 pm

What a waste of forum space. But I expected that U will again do same as always.
So, shortly: I traced loader code in all those laserdisk games, and I know exactly how it goes - afterall I made hard disk adaptations, which are complete. So, track data is 6048 bytes in all tracks with 6x 1K sectors. 6144 bytes just can not fit reliable. All what that Kryoflux SW shows is just a mess, confusion. They did not listen when I told them some things, and here is the result. Should stick to Amiga together with you, when act like here - totally ignoring people with much more Atari experience. I think that it was last from me to you and about Kryoflux here. Really no sense to talk to ...
Negative feedback has usually positive effect.

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Sun Dec 18, 2016 12:48 am

AtariZoll wrote:What a waste of forum space. But I expected that U will again do same as always.
So, shortly: I traced loader code in all those laserdisk games, and I know exactly how it goes - afterall I made hard disk adaptations, which are complete. So, track data is 6048 bytes in all tracks with 6x 1K sectors. 6144 bytes just can not fit reliable. All what that Kryoflux SW shows is just a mess, confusion. They did not listen when I told them some things, and here is the result. Should stick to Amiga together with you, when act like here - totally ignoring people with much more Atari experience. I think that it was last from me to you and about Kryoflux here. Really no sense to talk to ...


It's not a waste, that's the kryoflux topic. So that's perfectly fit. What you don't seem to understand, is that we DON'T care about the way the loaders are coded on the software side, we take care of the physical side.

If the physical side is perfectly recorded, then the loaders will do their job ! This is as simple as rain falling !

6144 bytes can perfectly fit on a double sided floppy disk. But you need a trace machine to do that. That's impossible to do with a regular ST FDC.

Just remember the ST FDC is interpreting the datas (exactly like the CPC and the PC). CPC or Atari ST is the same thing, both share 95% of the same protection systems.

What do you want to tell to Istvan that he doesn't know yet already ?
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

ijor
Hardware Guru
Hardware Guru
Posts: 3095
Joined: Sat May 29, 2004 7:52 pm
Contact:

Re: News games checked.

Postby ijor » Sun Dec 18, 2016 1:01 am

Can you post the raw dumps, or a link to them?

User avatar
kodak80
Captain Atari
Captain Atari
Posts: 444
Joined: Sat Nov 09, 2013 12:05 am
Location: Brisbane, Australia
Contact:

Re: News games checked.

Postby kodak80 » Sun Dec 18, 2016 1:38 am

As it was my dump, here is a link to the KF RAW dumps that dlfrsilver was checking for me:
viewtopic.php?f=95&t=30878#p307813
Last edited by kodak80 on Tue Dec 20, 2016 5:34 am, edited 2 times in total.
Atari Falcon 030 | Atari 1040 STE | Atari 1040 STFM | Atari 1040 STF | Kryoflux & Supercard Pro Flux boards
Admin of Atari ST Review Magazine Archive: http://www.ataristreview.com

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Sun Dec 18, 2016 8:11 am

kodak80 wrote:As it was my dump, here is a link to the KF RAW dump that dlfrsilver was checking for me:
https://mega.nz/#!8ck2jCDZ!oWu1xNCPxcJ3 ... SAC5DwswZo

Please note that this is the 512kb boxed version and disks look original.

Please don't turn this post into a flaming session guys.


Don't worry it won't turn in any flaming wars :) Things only have to be repositioned and explained.

Thanks for these informations, i'll check the new dumps.

EDIT : now catch 23 is good ! it was just filth :) however for Total Eclipse, this new dump is worse than the first one, i can't even see the Copylock ST / long sector type protection on track 0 side 0.

Can you make multiple redumps of this track and upload them please ?
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

User avatar
kodak80
Captain Atari
Captain Atari
Posts: 444
Joined: Sat Nov 09, 2013 12:05 am
Location: Brisbane, Australia
Contact:

Re: News games checked.

Postby kodak80 » Sun Dec 18, 2016 8:58 am

Thanks. I have dumped Total Eclipse track 0 three times using the original floppy drive and the 7z files is in the re-dump folder. The original re-dump was done on another floppy drive which I suspect is on its way out.

The CTR of the original dump works fine in Steem SSE and the original disk works fine on my 1040STFM (TOS 1.02). Steem was using TOS 1.02 as well. The original dump also looks very clean with AUFIT.
Atari Falcon 030 | Atari 1040 STE | Atari 1040 STFM | Atari 1040 STF | Kryoflux & Supercard Pro Flux boards
Admin of Atari ST Review Magazine Archive: http://www.ataristreview.com

AtariZoll
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 2798
Joined: Mon Feb 20, 2012 4:42 pm
Contact:

Re: News games checked.

Postby AtariZoll » Sun Dec 18, 2016 9:06 am

kodak80 wrote:...
Please don't turn this post into a flaming session guys.


I don't think that posting some facts and clues about how some SW is placed on floppy is flame war. And I clearly said that will not discuss with DrIknowEverythingBest anymore - it was too much of pointless talk and ignorance already.

"we DON'T care about the way the loaders are coded on the software side, we take care of the physical side." - that explains a lot.
And if some image of floppy is enough accurate then that would be OK. But then, why we have several titles what can not write on floppies back ?
So, I'm sure that information about how SW loads it are welcome, useful. But not for WeKnowAllItBest kind people.

And according to this poll: viewtopic.php?f=104&t=30807
83% of Atari people (at least those who visit this forum) prefer good cracks instead faithful floppy copies. So, I go back to my preferred activities rather than discuss with smarthead who can not even write 3 English word title properly :D

Anyone knows how successfully this ReadySoft titles (Space Ace, Dragon's Lair) can be written back to floppies using SCP HW and SW ?
Sorry, not flaming war - just wanna know am I right when expect that it can do it. Maybe some poll about ? :mrgreen:
Negative feedback has usually positive effect.

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Sun Dec 18, 2016 9:55 am

kodak80 wrote:Thanks. I have dumped Total Eclipse track 0 three times using the original floppy drive and the 7z files is in the re-dump folder. The original re-dump was done on another floppy drive which I suspect is on its way out.

The CTR of the original dump works fine in Steem SSE and the original disk works fine on my 1040STFM (TOS 1.02). Steem was using TOS 1.02 as well. The original dump also looks very clean with AUFIT.


Yes, the CTR works fine under steem. But i have noticed that Saint Dragon, which is using the same copylock variant was a problem. I got some dumps of this game, and if the dump is not good enough, the IPF in output just doesn't work.

Hopefully one contributor sent me a good and clean dump, that i have been able to pass in IPF, fully working on my ST computer and also under steem.

I'll check the redumped tracks.
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Sun Dec 18, 2016 10:43 am

I don't think that posting some facts and clues about how some SW is placed on floppy is flame war. And I clearly said that will not discuss with DrIknowEverythingBest anymore - it was too much of pointless talk and ignorance already.


Saying that somebody is ignorant and what not because you don't have any good argument yourself is just reaching the godwin point.

Before the kryoflux board existed, and also before Dr coolzic tool Aufit was available, the physical side of the disks were impossible to see.

Let me explain. Most commercial disks were mastered on trace moutain machines, or on Philips machines. Those machines are tracing the signal on the disks in write track, NEVER in sectorial.

The problem with the ST, CPC and PC is that the upd765/WD1772 floppy disk controllers have only a limited read track command. But most of the time they read the disks per sectors, not per track.

The thing is some protections are layed on the disks in a way that the ST, CPC , PC FDC just can't see exactly HOW it's really written physically on the disk.

Since we do preservation, we're not trying to get ONLY SECTORS, we want TRACKS ! Because that is how the disks were mastered in the first place :D

Your view is the following : just image the sectors with the size requested by the internal game loaders. On the amstrad CPC, we have the eDSK format for this. On ST we have the STX format (it has however much advanced features than the eDSK format, and i would be pleased if one day this format could be used on the CPC, would be nice).

Both formats are however Sectorial ones. What we do is that we prefer the original way used by duplication operators : write track / read track.

If we went for the sectorial way, then the originals would be not identical anymore, it would then just be lower grade copies.

Sectorial = tampered = not suitable for preservation. Easy to get ? :D

"we DON'T care about the way the loaders are coded on the software side, we take care of the physical side." - that explains a lot.
And if some image of floppy is enough accurate then that would be OK.


Ppera, listen, the loaders are working because the physical datas on the disks are corresponding to them. Enough accurate is not enough for preservation. Once again, preservation can't be done with sectorial storage.

But then, why we have several titles what can not write on floppies back ?


Now you bring a very good question. Several titles can't be written back on floppies for multiple reasons. Let's see those :

1) All the masters back in day used a description format, with track length/sector size, bitcell size, timings, etc. Without those informations, you're basically doing what i call blind disk replication. This is exactly the worst way to follow. Every idiot in every country could do that, and that's not how a duplication process should be done (no description = no checking = possible errors).

Just for the record, i have read on a website (i don't remember where), that a company duplication operator did blind replication on 5000 disks, in blind mode. All the 5000 disks in the end were faulty !

Another example : New York Warriors for CPC 128k. The programmer gave the master to the operator, and the operator just did a blind replication without checking. Result : all the copies sold have the disk B never master mastered on the disks. Epic fail.

2) Because some duplication machine were really crap. For instance, the spanish companies were using Philips unix machine for replication.
Those were making poo mastering, as a result, the analyser see them as copies and not as duplicated disks.

Most of the time, the master disk containing the program was written on an Atari ST, PC or Amiga depending the plateform, and it contained an already written protection track. Problem : those machine were used to do blind replication, so it means that when i analyse a spanish game, the analyser sees that the disk was written on a computer instead of the Philips trace machine.

The CTA is made to differenciate a disk written on atari ST, and a disk written by a duplication machine. This explaining that.

3) Most of the time, the titles running on Atari ST (or any other machine by extent), use protections needing accurate description, in order to make a precise written, required in the end by the game loader to pass. if you just write back as it is, and since the disks are quite frequently dirty, there can be errors added, bad bits, and so on. That why the IPF in output are the datas checked and passed, without any errors.

You can then be sure that what you write back on disk is perfectly working.

4) Because like in the good old days, the physical disk formats have to be accurately described in the analyser in order to recognize what we feed inside.

So, I'm sure that information about how SW loads it are welcome, useful. But not for WeKnowAllItBest kind people.


We don't need that. As explained, we can't base ourselves on the ST FDC. It's doing interpretation of the datas.

I'm not MisterIknowAll. I have asked questions, i have read documents. However as i said, your software view is useless for preservation.

This because if the physical datas are exactly how they were mastered when the softwares were sold, the loader(s) will do their job.

That's as simple as that. This is also why i told you to do what you know best, and let us do what we do best on our side.



Oh yes ! Your famous polls ! :lol: People answered to you that they mostly want both : original and deprotected releases.

83% of Atari people (at least those who visit this forum) prefer good cracks instead faithful floppy copies.


I will tell you exactly the same thing that i've said to the CPC people communauty : We can't have this computer and only have cracked, hacked, modified, cutted down versions of the softwares.

I will say exactly the same thing to you : the ST communauty deserves better than just be considering a horde of cracking/hacking Hoboes !

The ST original softwares must be preserved. And most of all the original allows for better deprotected versions, repairing faulty cracks, and so on !

So no, nobody can just agree with your "let's only go for the cracking route !".

So, I go back to my preferred activities rather than discuss with smarthead who can not even write 3 English word title properly :D


Indeed, go deprotecting the titles, you don't need to care about preservation, that's our job :)

From my actual view, the disk format has to be described. Written back as it is in "blind mode" can only just be error prone.
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

AtariZoll
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 2798
Joined: Mon Feb 20, 2012 4:42 pm
Contact:

Re: News games checked.

Postby AtariZoll » Sun Dec 18, 2016 11:05 am

dlfrsilver: stop with this nonsense. We (people dealing with cracking/adapting) know well what is track image and how to deal with. You explain such basic things. That just proves what I think -- your knowledge is poor, all you can is to use SW analyzer of floppies. That SW is just not good enough. But could be better if ... Please reply in PM if have something new or constructive to say. No need to spoil thread completely.
Negative feedback has usually positive effect.

ijor
Hardware Guru
Hardware Guru
Posts: 3095
Joined: Sat May 29, 2004 7:52 pm
Contact:

Re: News games checked.

Postby ijor » Sun Dec 18, 2016 2:44 pm

kodak80 wrote:[EDITED} Link removed. Sorry. PM me if you need the dump.


Oops. Why not make it public? Did you removed all your other dumps as well?

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Sun Dec 18, 2016 3:22 pm

AtariZoll wrote:dlfrsilver: stop with this nonsense. We (people dealing with cracking/adapting) know well what is track image and how to deal with. You explain such basic things. That just proves what I think -- your knowledge is poor, all you can is to use SW analyzer of floppies. That SW is just not good enough. But could be better if ... Please reply in PM if have something new or constructive to say. No need to spoil thread completely.


This is not non-sense. If you're not able to understand what i've explained, then i can't do anything on this matter.

My knowledge is rich, richer than yours. I'm dealing with many platforms when you're stuck with only one. You're just focused on the ST, i'm focused on the ST, Amiga, CPC, PC, Thomson TO machines (last dumps i had to deal with).

Basically dealing with the ST is like dealing with the CPC. Both machines use the same FDC, and as such i know the CPC like my back pocket. So guess the ST is in the same range.

My task as an checker and operator consist to recognized the protections physically written on disk. I don't need specific ASM knowledge for that.

Aufit is a great tool, and the CTA minoring the unsupported formats has no equivalent on the market or in any software available.

I say what i want in this thread, that's our thread, not yours.
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

User avatar
kodak80
Captain Atari
Captain Atari
Posts: 444
Joined: Sat Nov 09, 2013 12:05 am
Location: Brisbane, Australia
Contact:

Re: News games checked.

Postby kodak80 » Tue Dec 20, 2016 1:46 am

This link is to the games mentioned above and includes KF RAW and CTR 7zip files.

https://mega.nz/#F!QQ0WiJhZ!IBxYTFW9uCSG2JIQBW25cA
Atari Falcon 030 | Atari 1040 STE | Atari 1040 STFM | Atari 1040 STF | Kryoflux & Supercard Pro Flux boards
Admin of Atari ST Review Magazine Archive: http://www.ataristreview.com

ijor
Hardware Guru
Hardware Guru
Posts: 3095
Joined: Sat May 29, 2004 7:52 pm
Contact:

Re: News games checked.

Postby ijor » Tue Dec 20, 2016 8:55 pm

kodak80 wrote:I have dumped Total Eclipse track 0 three times.
...
The CTR of the original dump works fine in Steem SSE and the original disk works fine on my 1040STFM (TOS 1.02). Steem was using TOS 1.02 as well. The original dump also looks very clean with AUFIT.


The dump is good and clean. I don't see any problems with track 0 either. Creating a Pasti image from the dump also works.

Note that it doesn't work with STE TOS 1.6X. Which means that probably is not STE compatible. But works fine under Steem as long as you config Steem to use TOS 1.02.

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Tue Dec 20, 2016 11:32 pm

ijor wrote:
kodak80 wrote:I have dumped Total Eclipse track 0 three times.
...
The CTR of the original dump works fine in Steem SSE and the original disk works fine on my 1040STFM (TOS 1.02). Steem was using TOS 1.02 as well. The original dump also looks very clean with AUFIT.


The dump is good and clean. I don't see any problems with track 0 either. Creating a Pasti image from the dump also works.

Note that it doesn't work with STE TOS 1.6X. Which means that probably is not STE compatible. But works fine under Steem as long as you config Steem to use TOS 1.02.


The dump looks good indeed. The problem on my side is that i can't generate a working IPF out of the dump. The sector check fails each time, and the emulator crash.
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

ijor
Hardware Guru
Hardware Guru
Posts: 3095
Joined: Sat May 29, 2004 7:52 pm
Contact:

Re: News games checked.

Postby ijor » Wed Dec 21, 2016 12:57 am

dlfrsilver wrote:The dump looks good indeed. The problem on my side is that i can't generate a working IPF out of the dump. The sector check fails each time, and the emulator crash.


Well, if you want to PM me the failing IPF I can take a look. It might not help you to produce a working one. But I should be able to tell what's wrong and why the check fails.

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Wed Dec 21, 2016 12:17 pm

ijor wrote:
dlfrsilver wrote:The dump looks good indeed. The problem on my side is that i can't generate a working IPF out of the dump. The sector check fails each time, and the emulator crash.


Well, if you want to PM me the failing IPF I can take a look. It might not help you to produce a working one. But I should be able to tell what's wrong and why the check fails.


Ok, i'll PM you.
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !

coolhaken
Atariator
Atariator
Posts: 18
Joined: Mon Dec 19, 2016 11:50 pm

Re: News games checked.

Postby coolhaken » Sat Dec 31, 2016 3:52 pm

Hi all,

There seems nobody want/can check IBM-PC games uploaded on retrobackup.com.
I and NewRisingSun have checked the following dumps.

[SCP-IBM PC] ISHAR III - SEVEN GATES OF INFINITY - IBM PC - (C) 1994 SILMARILS.7z
[SCP-IBM PC] JOE & MAC CAVEMAN NINJA (ELITE SYSTEM - EURO version) - IBM PC - (C) 1991 DATA EAST - ELITE SYSTEM LTD.7z
[SCP-IBM PC] PRINCE OF PERSIA 2 THE SHADOW AND THE FLAME - (C) 1993 Jordan Mechner - Broderbund - Electronic Arts.7z
These are corrupt image files; in particular, Joe and Mac even makes HxC freeze.

[SCP-IBM PC] Prehistorik - (C) 1991 TITUS Software.7z
The keydisk check sometimes not work. Data stored in the protection track is corrupt.

[SCP-IBM PC] ANGEL NIETO POLE 500 - IBM PC - AUTOBOOTER - (C) 1990 OPERA SOFT.7z
The sectors on all tracks have Sector IDs that say Cylinder 0. This will not work even on a real machine.

To dlfrsilver, those dumps seems uploaded by you, right? Can you redump them using a Kryoflux board ? Thanks a lot.

JimDrew
Atari Super Hero
Atari Super Hero
Posts: 586
Joined: Mon Nov 04, 2013 5:23 pm

Re: News games checked.

Postby JimDrew » Sat Dec 31, 2016 4:13 pm

I looked at Joe and Mac, and a few of the other images. Whoever uploaded these needs to throw the drive away. These are some of the worst images I have ever seen. Besides having really dirty heads, there is a severe drive speed problem. So, either the drive is bad (which I believe is the case) or the power supply providing the 12v/5v power is bad. Joe and Mac is probably a bad or really dirty disk.
You do not have the required permissions to view the files attached to this post.
I am the flux ninja

coolhaken
Atariator
Atariator
Posts: 18
Joined: Mon Dec 19, 2016 11:50 pm

Re: News games checked.

Postby coolhaken » Sun Jan 01, 2017 3:44 pm

Checked the two dumps :

[SCP-IBM PC] DR DOOM'S REVENGE - (US Version) - IBM MS-DOS - (C) 1989 Marvel Ent. Group - Paragon Software - Medalist Int.7z
This is a cracked copy. I don't think it makes sence to dump a pre-cracked game.
There are too many cracked versions floating on the internet.


[SCP-IBM PC] PREHISTORIK 2 - XT AT PS - VGA - (C) 1993 TITUS.7z
This one contains bad files in it and they'll cause display issue at the beginning.
It is strange that I can't get crc error while decoding it.
This is one of the worst status for me because all files become un-trust-able.

JimDrew
Atari Super Hero
Atari Super Hero
Posts: 586
Joined: Mon Nov 04, 2013 5:23 pm

Re: News games checked.

Postby JimDrew » Sun Jan 01, 2017 5:53 pm

It's not uncommon to see bad files with good CRCs. This occurs with some disk copiers that pull as much valid data as possible and they write that data back with correct CRCs.
I am the flux ninja

User avatar
dlfrsilver
Atari God
Atari God
Posts: 1415
Joined: Mon Jan 31, 2005 1:41 am
Contact:

Re: News games checked.

Postby dlfrsilver » Sun Jan 01, 2017 10:18 pm

coolhaken wrote:Checked the two dumps :

[SCP-IBM PC] DR DOOM'S REVENGE - (US Version) - IBM MS-DOS - (C) 1989 Marvel Ent. Group - Paragon Software - Medalist Int.7z
This is a cracked copy. I don't think it makes sence to dump a pre-cracked game.
There are too many cracked versions floating on the internet.


[SCP-IBM PC] PREHISTORIK 2 - XT AT PS - VGA - (C) 1993 TITUS.7z
This one contains bad files in it and they'll cause display issue at the beginning.
It is strange that I can't get crc error while decoding it.
This is one of the worst status for me because all files become un-trust-able.


The Doctor Doom's Revenge US version was a sealed copy i bought in USA, it was a leftover from a software shop. I have unwrapped/unsealed myself the game, and i never try to deprotect the game.

Prehistorik 2 is perfectly working. Both original disks are OK. So i don't know why you've found these errors.
Now SPS France representative since the 19th of June 2014. Proud to be an SPS member !


Social Media

     

Return to “Kryoflux”

Who is online

Users browsing this forum: No registered users and 1 guest