| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | OS/2 4.0 |
PE> Now what you see here is that the compressed sizes are different!!! PE> If it was a disk read error (or disk cache read error), it would have PE> created a different CRC, because the data would be different. FM> I don't know which ZIP you use (I use PIP 2.04g) but I have seen this. FM> It depends what zip finds in the way of operating system, hardware, etc. FM> eg if it finds a more competent processor it will use the appropriate FM> instructions. In your case it's probably found a different amount of FM> memory, enabling it to build a bigger table when it could. Cant be that, doesnt explain the SAME CRC in the two files. THAT indicates that whatever is doing the CRC sees all the data fine, but it doesnt all get into the file created. Let alone produce the result where using the dud file gets a complaint about the CRC coz the file has some missing bytes. FM> In my example, the exact same file zipped using the FM> exact same program on my machine here cf the one at work, FM> gave different file sizes (it usually does in fact). Sure, different say ram available could well produce that result, BUT that is very unlikely to produce the SAME CRC. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 712/610 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.