Problems with Indesign 2.0 pre-releas version

I have a work, that was made with Adobe Indesign 2.0 pre-release version.
Now I have Indesign CS. But I have one problem.
I can't open my file with Indesign CS.
Is there any way to open it? Any cracks or may be converters?
Thank's

see thread: Thread818-758053

Cracks, converters?  Stop using pirated software, you dullard.  Tek-tips is not a forum for software piracy.

Beta users are bound by a strict licensing agreement.  You obviously did not follow this agreement and now must pay severely by exposing your foolishness on this forum.  True licensed beta users are given a utility that can convert beta documents to final retail documents.  True licensed beta users are also not foolish enough to do full production work on beta software.

Tell Adobe Customer Service about your problem.  They should have something for you.

- - picklefish - -
Why is everyone in this forum responding to me as picklefish?

The members of the pre-release beta program received a version of ID that migrated documents from the pre-release format to the final release format. Anyone who was actually a member of that program got that build. That's the only way to convert those files into something that CS can open. Customer service doesn't send that build to people for obvious reasons. Ask whoever built the file if they have that migratory build...

Quote:

Ask whoever built the file if they have that migratory build

Tim, please don't enable this kind of silly behavior.  Beta users are well aware of how the system works.  Whoever built the file (whether Vaf or another) would know about converting documents to the final retail version.  I directed Vaf to Adobe Customer Service so that he could expose his silliness directly to Adobe.  Adobe will not help pirates and neither should anyone on this forum.

- - picklefish - -
Why is everyone in this forum responding to me as picklefish?

Hi Jim...not trying to enable any silliness...just expose it for what it is. It's often the case that users that ask this question have received the file from someone else.

I understand... I just find it odd that even if 'someone else', a real beta tester would know not to pass on beta documents to non beta users.  Something smelled really fishy about this.  Vaf's use of the word 'cracks' led me to believe that he/she is not really legal.

- - picklefish - -
Why is everyone in this forum responding to me as picklefish?

It's often the case that the 'someone else' is using something illegitimately obtained and a service provider or someone else later in the workflow gets this surprise.

So you are saying that the service provider must continue this illegal use of software, even if they did not originate the problem?  

I'm all for making a buck but if I'm handed a document that I know is created with bootlegged software, I'm not going to be jumping through any extra hoops to satisfy a criminal.  I would be billing the client the full cost to rebuild the document in a legally licensed retail version.

Vaf knew this was a beta document so the element of surprise does not exist here.  Is it typical that law abiding service providers seek cracks?

I apologize if my first post was a little heavy-handed but someone specifically asking for cracks gets under my skin and fuels all sorts of suspicion.

- - picklefish - -
Why is everyone in this forum responding to me as picklefish?

No, I'm saying that service providers can be taken by surprised by this, and shouldn't be spinning their wheels trying solve a problem for someone who doesn't have a legitimate copy of the software. Legitimate users had a way to migrate their files. They illegitimate ones don't.