Xref: utzoo rec.audio:15277 rec.music.cd:4504 gnu.misc.discuss:268 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!apple!bionet!ig!arizona!kline From: kline@arizona.edu (Nick Kline) Newsgroups: rec.audio,rec.music.cd,gnu.misc.discuss Subject: Re: DAT copy protection Message-ID: <14054@megaron.arizona.edu> Date: 16 Sep 89 00:20:04 GMT References: <3041@quanta.eng.ohio-state.edu> <1989Sep15.134921.14736@talos.uucp> Reply-To: kline@arizona.edu (Nick Kline) Organization: U of Arizona CS Dept, Tucson Lines: 24 In article <1989Sep15.134921.14736@talos.uucp> kjones%talos.uucp@uunet.uu.net writes: >This raises some questions: > >1) Presumably the DAT recorder will keep an internal table of (CD-ID, > copy-count) pairs. (Just marking copies won't work: a copy of a > copy could be stopped, but you could still make unlimited copies of the > original CD.) How much memory in the DAT recorder will be devoted to > this table? No, you can still make as many copies of an *original* as you want. It does not limit this. Now really, how could you keep track of what cds you had already copied? There is the possibility of being billions of different cds available and there is no organization that assigns id numbers (that I know of, and I do know that you can go to independant orgs and get a cd pressed). The limit is on the number of copies of copies you can make. -Nick --- "Computer Scientists are at the top of the nerd heap" - Curtis Dyreson Nick Kline, Univ. of Az., Computer Science, Tucson, AZ 85721 (kline@arizona.edu -or- {noao|allegra|cmcl2}!arizona!kline)