![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
|
![]() |
#1 | |
Navy Seal
![]() Join Date: Apr 2005
Posts: 5,501
Downloads: 19
Uploads: 0
|
![]() Quote:
The second thing is it appears that you're not using a download manager. On dialup, this is pretty much essential. Unfortunately, the longer you are exposed to file downloading the more likely the file will get corrupt. If you are on time based, or limit based dialup plans, even moreso. I know someone here who I think was pulling his hair out trying to get the bigger mods like NYGM and GW to work, before finding out that the problem was a constraint imposed by his ISP. Nothing anybody else can do about that. Both download sites are "trusted" and have 100% verified files. I regularly run checksum comparisons against the source files in addition to regularly d/l and re-testing on my machine. From looking at the error messages you posted, it looks like TGW11a-2.bin is the corrupted file. Your options: -redownload TGW11a-2.bin -contact Neal Stevens, make a donation to Subsim, and have GW1.1a posted out to you on DVD. -hope that a kind hearted Australian reads your plight and sends it to you on DVD/CD. EDIT: Could this already be the case? ![]() I'd also say upgrade to broadband, but you seem pretty much against that (it's really not that much more expensive than dialup if you shop around). It's boils down to simply being that 670mb of files and dialup do not go well together. Short of a) stripping out 90% of GW or b) splitting the source d/l files into sizes no more than 4mb, there's no easy, foolproof solution to d/l via dialup. I know this isn't what you want to hear. Last edited by JScones; 07-05-06 at 03:07 AM. |
|
![]() |
![]() |
![]() |
#2 |
Admiral
![]() Join Date: Apr 2005
Location: Australia:- Sydney
Posts: 2,049
Downloads: 68
Uploads: 0
|
Thankyou sir for your feedback and help
![]() |
![]() |
![]() |
![]() |
#3 |
Admiral
![]() Join Date: Apr 2005
Location: Australia:- Sydney
Posts: 2,049
Downloads: 68
Uploads: 0
|
The first thing is that you are comparing kilobytes to bytes (the FAQ specifically says *byte* sizes). Compare bytes to bytes and you'll get a better "quick" indication of possible corruption. Simply right-click a file and select "Properties"; the size in bytes will then appear.
After JScones informed me of my incompetence ![]() |
![]() |
![]() |
![]() |
#4 |
Navy Seal
![]() Join Date: Apr 2005
Posts: 5,501
Downloads: 19
Uploads: 0
|
![]()
A byte size comparison is a mechanism to quickly identify corrupt files, for if byte sizes differ, there's no doubt that the file is corrupt.
But, same byte sizes do not necessarily mean that all is OK. There are many reasons why a d/l file will report the same byte size but still be corrupt. The only true way to tell is to do a checksum comparison, ie a comparison of file *contents*, not just size. The installer does this as it runs, hence the error messages. The error messages will indicate which "piece" is corrupt, as the files are stored within the installer in alphabetical order. File extensions... .000 to .bik in TGW11a-1.bin .bik to .mp3 in TGW11a-2.bin .mp3 to .tga in TGW11a-3.bin .tga on in TGW11a-4.bin |
![]() |
![]() |
![]() |
|
|