You are not logged in. Please login or register.
DriverPacks.net Forum » Feedback and Support - DriverPacks Base » Downloaded driver pack file sizes not valid
yesterday I updated all my driver packs. Funny thing happened. The file sizes were way out of whack. I was getting Graphics B as 2630KB, Graphics C as 3790 KB CPU as 37 KB.....etc., etc. I went to my neighbour's to download the files again, and the same thing happened. I only noticed this when trying to unzip the files and noticed the error and immediately saw the file size of the 7z. that seemed too small. Anyone having the same problems?
It is working for me now... but the server has been chokeing over the last week or so...
it's been reported to the host.
thanks for the update. Strange how the driverbase log didn't indicate any problems with the zip files during integration
that is strange i would expect if the files sizes were wrong that 7zip would have errored on their checksum
they integrated well according to the log file, and with and unattended install of XP as well. Guess the main program is busted somehow and doesn't check the hash
Hi
consider this.. IF DriverPacks BASE was to check hash, then users could not edit DriverPacks, and they can.
An online check? Even the update checker is optional. (you don't have to check before stream), and if we were to use the hash of a pack it would have to be online (not hardcoded in DriverPacks BASE which was done very very long ago, which required Base was updated each time a pack was updated..), and all hashes of all older packs would have to be online as well. And then what? Make Base tell user 'this' pack was edited/tampered with?
After that, what's to stop you from inserting a pack in the OEM folder? (which some users do.. because you don't have to stream.. you add a pack in the folder and presto, it will extract along with the other if the naming was done right.)
During streaming I would think 7zip will throw an error when the archive is invalid.
(If you replaced an archive.. it would throw an error during setup too, but I do not know if it would immediatly become apparent it was a bad archive.. files missing, perhaps.. maybe.)
btw, I once looked at a way to include the hash in the 'overview' page.
I agree the packs are always in a state of flux both by the team and by our users.
It is not feasable or desireable to include a hash check.
We rely on 7zip to report invalid archives. which obviously is not 100% foolproof. but what is...
I think that crippleing the ability of the user to customize the packs is not a good idea...
Even if there is an occasional problem.
should be fixed now http://forum.driverpacks.net/viewtopic.php?id=521
i cant understand why all the packs arent delivered in the download area with crc32 or md5 hash'es so one can check his packs on the harddrive himself. e.g. you download the packs, the lay on the hdd, perhaps they get changed (by what ever) , so one could generate some .md5 file with all the filenames/hashes and check with those handy tools out there.
isnt there such a problem to add this to the overview page. or just add some file-link to each download section of the pack with all the recent hash'es inside . like some .sfv file of a "scene" release....
I think we can find a way to post the hash, so you at least see it before you download.
you could easily include it in the change log / overview...
lets do that from now on...
fine thanks. like ubcd4win and nero.com , all include the md5 hash in the download section
the current main DriverPacks have the checksums in changelog now.
Excellent. I'll try to make real improvements to the download system this weekend.
improvements were added ahead of schedual we should be working 100% (holds breath)
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.018 seconds, 12 queries executed ]