Search options (Page 11 of 14)

No, sbi2sub should not be added, this is generated subs and not the REAL subs. Therefore useless in a preservation sense.

Actually I wouldn't bother checking mode 2 discs at all in cdmage, it's probably a bug in it. There is no error info to check on mode 2 form 1. These discs rely entirely on CIRC for error correction, which is not contained in the user data area. I doubt the disc has any errors in reality. =]

There is a bug with EAC and discs with 2 tracks (1 data, 1 audio), it fails to detect the pregap of track 2. Dumps those discs with Perfect Rip if you can, or dump the pregap manually.

I've been promoted to mod, I will try to get to stuff when I can, I lack a lot of time, but I WILL get to things.

WE lack enough mods in general, not just PC...

You should add what the "header" is, and where to find it, and how to examine it. I have absolutely no clue what you mean.

:EDIT:

Ok figured out is it sector 0 on the disc viewed in ISOBuster

Sorry for late reply, wasn't notified the thread was replied to.

Yes lets discuss what should be done and in which ways. Please put your idea's and opinions up for discussion, got to get the ball rolling.

PLEASE don't resign, your input and experience is very valuable and needed!

I'm not familiar with Dremora's model, enlighten me please.

Yes we need more people and knowledgeable ones, I'm trying to recruit such people, and have at least one now who will work behind the scene's at least, see other new sub forum.

So my thoughts on what to keep on the db, are list of error sectors for safedisc/cd ring protect/laserlock. That data is easily kept as a list, and doesn't violate any kind of copyright. Some research needs to be done into if the sectors are just plain bad on purpose, contain some meaningful data which can be extracted through a different unscrambling process, or unknown?

For sub code, maybe just a hash of that data to check if they match another disc, and only blue when matched once and green with multiple matches (fireball's suggestion).

For topology data, I don't even know where to begin with that, you say you have experience with starforce, please elaborate on what it checks for. I have some with securom and tages, and they are checking seek times. I am not entirely sure how the data is on the discs though, if they are doubled sectors or just constant/angular velocity changes or what. Certainly need more research into that.

Agreed about the LiteOn, mine can read damaged discs that my Plextors cannot and the hashes match db.

Well if I set the speed below 4X in various tools (EAC/CloneCD/Alc) and even in Plextools Professional the drive spins up and slows down constantly and it really makes read times crazy, like hours and hours. I tried it here today with the 1210 I got and it works no problem. Probably a firmware bug.

The PX-W1210A should be a real plextor also.

These older drives don't have Mount Rainier capability according to AIDA64. Also the 1210 didn't have C2 support with firmware v1.07, but I updated it to 1.10 and it then did.

Yeah I started the thread to list the known real plextors, and also to post experiences with the different ones and the capabilities each one has.

Have to agree with f1reb4ll, subject should be closed and topic locked.

Themabus:

My intentions with the first post were not to cause conflict or infighting, but only to spur communication and consensus. I can see where it can be viewed as a bit childish, I will redact it. That can be settled and on with the important stuff rather than communication style...

Yes most of us are aware that this project started and grew from PSX database, that's a good thing and efforts are surely appreciated and attractive to people wishing to preserve whatever is in their interest and leads them here to begin with.

Please elaborate on what you mean by "oddities are examined and defined in db (ASCII field)". I'm not entirely sure what you mean by that.

I'm all for that, but what should we be documenting? Should we be documenting just anomalies in sub code? topology? user data? protection mechanisms? conflicts between sub code and TOC? <insert anomaly here> ? all of the above? Do please be specific, as we should all be really interested to know what it is we should be focusing on, rather than just conservation as you say.

Some of these things are fairly easy to document, others would require a great deal of investigation and documentation. I myself do that on other platforms so am not averted to such things, but certain aspects of it may also garner unwanted attention from various entities. However I believe that should not stop it from being done.

An interesting point indeed, but how should such information be collected and stored, again please elaborate on it. As for the last part with safedisc and also laserlok, a list of sectors is easy enough to generate. But I think the contents of those sectors should be examined more closely for possible meaningful data which may be contained therein. There is conflicting opinions about that dating back to the first appearance of them, and maybe it's time someone investigate that and figure out exactly what is true or false about such theories.

Your last point I can understand completely, so it need not be discussed any further. As I said I will redact the first post.

Also thank you for maintaining some interest in things even through differences in opinion and sometimes conflict and heated discussion. Also please try to understand that some people are quite passionate about this, and there is no intention of stalling the project or creating dissent. Only to better preserve. =]

Jackal:

The point of such topics is discuss opinions and make decisions which in turn create the general policy and procedures, without it, any project would stagnate and become a dead carcass. I feel important topics and discussions should be stickied as it makes it easier for newcomers to get an idea of what goes on, and also as reference points for reflection by experienced users. IMO there are many relevant posts in this forum that SHOULD be stickied which are not.

Well it's a bit too late to do anything about that now, the cat is already out of the proverbial bag.

I don't want to talk with ripper about anything, and you know damn well he is very arrogant, and condescending. Also as themabus mentioned in his post, is this about preservation or conservation. That needs to be worked out first before any other discussions about formats and other things take place. Also ripper is not the be-all end-all of information about what's on various discs, the fanboi-ism is getting a bit annoying actually. I don't want this to just end up in a bickering session though, so if you have information about such things rather than tell us to go ask so-and-so about it, post it up here for all to know. Isn't that the whole point?

Indeed there are many questionable things, who decides what though, and based on what... again I think "current standards" are not even defined at this point. Except for only certain systems like PSX and PS2 where that has already been decided, but could change if the need to is founded.

- Nexy

As far as I know there is no tools which can deal with such an image, unless you know of one. That makes it a custom disc image format =] Just semantics I know.