File CRC mismatch

[wuaizui]

Hi:

I am learning to use setup factory 5.0. I have got a problem.

1. I created a setup.exe and burned it on a cd. This setup.exe contained an executable Mdac_typ.exe.

2. I tried the burned installer on a Win98 machine and I succeeded.

3. Then I tried the same burned installer on a win95 machine and I got the following message:
-----------------------
C:\program files\...\Mdac_typ.exe
A decompression error has detected (#7)
File CRC mismatch - Data integrity error
------------------------

Any help is appreciated.

I noticed that there was a topic on a similar problem (CRC failed ...). The suggested solution for this is to disable CRC check. I even do not know how to do this. Could somebody give me a hand?

Thanks.

-Sunny

[Mark]

Re: File CRC mismatch

Hi,
Basically what happened is something changed in your SETUP.EXE file. Something probably happened to your file when you burnt it, so now the CRC checking fails. I suggest that you try burning your SETUP.EXE again, and see if that solves the problem.

mark.

[intertexts]

Re: File CRC mismatch

What is the latest on the CRC mismatch issue, which seems to be a bug involving the decompression of files into folders? I am getting it consistently on Setup files used in Windows NT and 98, copying Director files.

The conclusion in early 2000 seemed to be that disabling CRC checking eliminated the problem; must we do this for every file, and if so how? I have not gotten the 1.1 update yet, but the most recent posting suggested that the update did not address the issue.

Thanks, Barry Schneider

[intertexts]

Re: File CRC mismatch

One other thought: I assume that altering a file before copying it to CD, but not refreshing the file information in Setup Factory could generate a CRC error when the file is copied from the CD on setup. Is that true?

If so, this might explain the errors I've gotten.

Thanks, Barry

[Mark]

Re: File CRC mismatch

Hi,
Yes that is exactly what would cause the CRC errors. The reason that this occurs is because SUF keeps track of the files old information, which does not correspond to the new file information. That is where the error is occurring.

mark.