OT: downloading of a file

[snip...snip...]

For large files *especially* when they're over a dodgy connection (e.g., dial-up, sorry) you really should, whenever possible, check that the file's hash matches the hash value from the originator. MD5 and SHA1 are the most common. MD5 can be compromised (spoofed) and SHA1 may also be vulnerable (see a recent article on el Reg, IIRC) but using either is orders of magnitude better than click and hope it runs.

The algorithms for the hashes are available if you're up to coding your own. Several executable implementations are out there, as well. For Windows GUI,

formatting link
is a possibility.

If the publisher doesn't supply hash values, write 'em a nasty note. In the meantime, here's what I get for

formatting link

$ fsum -md5 -sha1 NV8269.exe

SlavaSoft Optimizing Checksum Utility - fsum 2.52.00337 Implemented using SlavaSoft QuickHash Library Copyright (C) SlavaSoft Inc. 1999-2007. All rights reserved.

; SlavaSoft Optimizing Checksum Utility - fsum 2.52.00337

; ; Generated on 01/11/09 at 09:38:24 ; dbf6c51f447c2f491c37d74c8a0fba3a *NV8269.EXE

22aa3954ab226291ad356dd19b50a04460e604a7 ?SHA1*NV8269.EXE
--
Rich Webb     Norfolk, VA
Reply to
Rich Webb
Loading thread data ...

If I remember, a lot of servers our there limit the amount of time a socket is to stay alive regardless of what it's doing.. This of course , stops the slow people to help prevent a clogged server.

formatting link
"

Reply to
Jamie

If you decoded the emails manually, it's quite possible that you snipped one character too many somewhere along the line, or pasted two parts in the wrong order, or one of the emails got munged in transit.

If you still have the original email messages, you might try using a different decoder. Most of them accept entire email messages, and will ignore any parts which don't look like UUE.

The file should have a size of 15260160 bytes and a CRC of 7761EF6F.

If the size is correct but the CRC is wrong, two (or more) parts probably got swapped. If the size is too low, something went missing; if it's too large, something got duplicated or something that isn't UUE got decoded as such.

Reply to
Nobody

Thanks; so fr i have not seen it - but i am not russian (not in a rush).

Reply to
Robert Baer

That wierd "$ fsum" etc indicates a unix-type system, and donut (hole and all) work on WinDoze. Not too useful as almost nobody gives checksum for their files (not even M$), and if it fails, then what? In this case, i got the file in encoded ASCII 500K pieces that i stitched together then ran UUDeview to (sucessfully) decode.

Reply to
Robert Baer

That is *exactly* what happened in at least one attempt.

Reply to
Robert Baer

At my end it looks as if it's gone through. Possibly your mail service provider has junked it as being too big.

If it doesn't show, I could split the file into bite sized pieces and make them available to you to download separately.

Sylvia.

Reply to
Sylvia Else

That is exactly the size i got; will look for a sympel program to cross-check that checksum. Thanx.

Reply to
Robert Baer

Well, i got FCIV from M$, and it gave: // // File Checksum Integrity Verifier version 2.05. // MD5 SHA-1

-------------------------------------------------------------------------

3ae59c352dcf54947d7bf6e36489cc65 ec7c888446b08d9602d2f8d1fdf7c5546e8329eb nv8269.exe

So, it seems what i have is trash. GURR!

Reply to
Robert Baer

Not received. Nada in the inbox or in the spam folder; have 25Mbytes space which is more than enough. I have always seen if a provider sees something as too big, it sends back a reply to that effect. On rare occasions, it can take a day or two for an e-mail to filter thru the net. Retry, verify spelling of name? snipped-for-privacy@localnet.com

Reply to
Robert Baer

I've put the file in pieces on a web site, and emailed you a link and instructions. You may need to use the "Save Link As" popup menu command to save the files rather than getting garbage displayed on the screen.

Sylvia.

Reply to
Sylvia Else

Do not bother. After an hour of downloading (and preventing disconnect), i finally got a file that corresponded with the MD5 and SHA1 checksums. Followed directions in C:\\TEMP and it worked, giving a bunch of files including Setup. Now get this: ran Setup and it stated "unable to locate any Nvidia graphics chip on the system". Bit..but..motorbut.. My video card is a Nvidia GeForce 8400 GS, supported for Win2K and up by the CD that came with it! Then when the wizard quits, it states "..sucessfully installed Nvidia display drivers"; restart computer. OK; Do so and so i am a little peeved to say the least and use Device Manager and force it to use the driver(s) in the C:\\TEMP directory. WinDoze does not like it, saying that it does not match the hardware, but i force it anyway. Well, la-de-da, the *best* i can squeeze out of it is 640x480 16 colors (ugly!). So, i go back to SVGA driver which WinDoze does not like either, and restore 800x600 16 colors which is the best i have been able to do so far. N A S T Y! Now, the motherboard has its own video chip, disabled in the BIOS so that the video card can work. Methinks that the verdammdt software (M$ and Nvidia) only looks at the motherboard and seeing something, stops looking and thus that is why no progress. Comments? Any work-arounds?

Reply to
Robert Baer

Any particular reason you're trying to use that file rather than one downloaded from nVidia's site?

Sylvia.

Reply to
Sylvia Else

The RAR and ZIP formats both record the CRC32 of each file in the archive, so you can put the file into an archive (disable compression for speed) then open it to see the CRC32.

Reply to
Nobody

[snip...snip...]

Negatory, good buddy. The '$' prompt just indicates that I use a better command interpreter than MS's CMD. A quick click over to SlavaSoft shows that fsum is indeed for "OS: Windows 95/98/Me/NT/2000/XP."

--
Rich Webb     Norfolk, VA
Reply to
Rich Webb

Rich Webb wrote:

There's also a scad of Unix-y stuff that can co-exist with Windoze stuff (adding command-line power) e.g.

formatting link
*-*-*-backward-slashes+disclaimer+wget+dd.exe
formatting link
)

Reply to
JeffM

The only files available from Nvidia support Win2K and up; zero support for Win98SE. What i failed to mention was that i tried their

81.98_forceware_win9x_english.exe which is for the 6 series (not what i have) and it also complained that there was *no* Nvidia chip. The drivers created by that also had the same complaint.
Reply to
Robert Baer

I got FCIV from M$ and used that; the file i finally managed to download complete from mdgx.com passed. Thanks for the checksums.

Reply to
Robert Baer

So far, i am forced to use the SVGA driver which Win98SE does not like either, and restore 800x600 16 colors which is the best i have been able to do so far. Now, the motherboard has its own video chip, disabled in the BIOS so that the video card can work. But it seems that Nvidia drivers do not see the GeForce 8400GS daughter board, and so stops looking when it sees the motherboard chip (unknown type so far). The NV8269 driver does support the GeForce board in Win88SE, but does not see it and if forced, does not give anything better than 640x480 16 colors (ugh!). By using an old DOS version of AMIDIAG i found that VESA mode 103 (600x800 256 colors) *is* supported. But the universal driver from Anapa Corp, giving VBE Miniport SVGA etc types of support *also* does not give anything better than 640x480

16 colors (ugh!). So, i am back to the WinDoze SVGA driver. Now, there is UNIVBE.DRV which i could try, but how does one tell the driver to "default" to mode 103? Or do i continue to bumble along, load it "plain" and HexSpearmint?
  • Any suggestions? Thanks.
Reply to
Robert Baer

You and i have worked reasonably well together before. My respect for you and how you act in this ng gives you a substantial friend score. So my offer is like this: You want a file, email me and physically send media; RW or extendable strongly preferred, and i send it back with the requested files on it. I have rewriters all the way to dual layer DVD (9GB). Part of the idea is to reuse the media, may be foolish versus postage though.

Reply to
JosephKK

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.