Could anyone tell how to increase sizes of files in the TOC of a CD image so when the files are copied to the HD they couldn't be burnt to another CD because of size limitations?
Thanks for any help.

ALAIK this is employed in some MS discs.
If I remember correctly 3-4 years ago I hd seen a program doing it. Unfortunately, I do not remember it right now...

(in reply to weaver)

quote:

---

Originally posted by sp

ALAIK this is employed in some MS discs.
If I remember correctly 3-4 years ago I hd seen a program doing it. Unfortunately, I do not remember it right now...

---

If my poor memory serves me correctly, MS did indeed use fake TOC / cross-linking files on some of their CD's. When CD was copied to HD, some files were copied multiple times and instead of 650MB you ended up having over GB of files. There were duplicate files in several directories, but because of cross-linking of files in original CD, those duplicates could not be removed before burning. Without removing them, it was impossible to stuff all those files into one CD. Yes, there was some software(s) allowing to make such modifications to your own CD's as well, but after that is where my memory fails, too. [:I]

(in reply to weaver)

MS is doing it, and I think under a good reason, for including multiple versions of their corporate editions of it's operating systems under a single CD.

This way the overlaping files (over 95%) get recorded onto the disc once, but show up 3 or four times.

By the way, one can back up a single OS version by deleting on the hard disk the duplicates.

(in reply to weaver)

All I can remember, it was not an OS CD and there was only one version of application, when I first run into this years (and years) ago. Deleting duplicates rendered backup unusable. Some CD copy softwares were also unable to copy that CD, as they thought there was not enough room in destination. I don't think current softwares even see such a problem, so this kind of "protection" is quite unusable - Even for personal usage. I guess someone could achieve similar effect by using (logical) linking of files with *NIX before burning?

(in reply to weaver)

What is NIX?

(in reply to weaver)

Try TZ Copy Protection 1.5.5

http://wave.prohosting.com/~tzcp/TZCP155FullInstall.zip

Have Fun!

(in reply to weaver)

quote:

---

Originally posted by sp

What is NIX?

---

Erm... *NIX, not NIX. Common name for UNIX clones - For example, Linux. Don't tell me you've never heard that? [:0]

(in reply to weaver)

The latest unix flavor I used was coming with the slackware 1.x distribution, years, too many years ago:)))

(in reply to weaver)

quote:

---

Originally posted by sp

The latest unix flavor I used was coming with the slackware 1.x distribution, years, too many years ago:)))

---

And the latest Linux was...? [:p]
Oh, I don't personnally care, as I'm not using any of those and I just wanted to point out it's common name for all those unusable OS variations: UNIX, Posix, Linux, whateverX. [:I]

(in reply to weaver)

No problem. I haven't touched a NIX keyboard for the last 9 years. Or so.
I would do so if I had some spare time. I think $MS$ developer products are superior to those available on the NIX platforms.
I think the war was lost when gates bought Heilsdberg from Borland in '97 and IntraBuilder, a fantastic program for its time, was burried due to borland's ignorance and incompetence.

(in reply to weaver)