Running last posted beta pack I ran into a bluescreen during a rush project; not sure if it was the machine or the package that caused it. Machine was an acer am3450-ur30p listed as having a radeon hd 4250 running 64bit windows 7 (likely without a service pack). During the rush I filtered down which drivers I applied and am pretty sure I only had graphics pack A and B but removed mobile from the attempt. watching the files passing through the MS tool i looked to be in the graphics section and though I do not remember the file, ati started off the name and graphics were not setup upon reboot after the memory dump. I ran an ati installer I had a separate copy of successfully; isn't this the save version that the pack includes?. I didn't have a chance to collect better details or look into it more thoroughly but if others have installs going through successfully, I'd likely write it off as trouble with the machine instead of the pack.
Files used with md5sums:
SAD3-130507/NT6/x64/DP_GB_x64.7z = ee10a095694519479cd03f24a6232a03
SAD3-130507/NT6/x64/DP_G_A_x64.7z = b51dde3c099306228d368c6b1fc46b38 (Changelog makes me think this has the driver)
SAD3-130507/NT6/x64/DP_G_M_x64.7z = d278fa16bb6145b40027921e8e428f7e (likely was not present in the install run)
13-1-legacy_vista_win7_win8_64_dd_ccc.exe = 757dc261b26ada0ac15b98615ecd34f3
Why have the file names been shortened so much instead of saying 'graphics' and why not something more descriptive than 'A' and 'B'. I did have to add 'DP_' to the front to get SAD3 to even pick up the files as packages to extract. I 'think' that it was part of the 'A' package, but how to people really read through the package to see what is in there to be applied to a specific device (and shame on me for not snagging machine IDs; I was that rushed).
Thank you to all involved in th work on these packages.
Last edited by mirror176 (2013-07-13 04:52:09)