mirror176
Forum Replies Created
-
Posts
-
I recall badpointer would make versions of snappy with debug symbols to help him track down problems he couldn’t reproduce on his side. I think it either provided a stack trace or complete program memory dump when it crashed so it could be later analyzed on a different system.
Not sure why installing that 2020 driver would get you a 2016 driver. Your current install isn’t listing the signature line; I would try a remove(+reboot)+reinstall of the driver or try using ddu (=display driver uninstaller) to see if it will start properly listing the signature line. It is rare, but I have ran into instances where things didn’t (or rarely but sometimes did) list correctly on the current install and still showed as something I could install. Seems even the main title line changes form specifying its a 620 to just a generic graphics with no model even though it lists the same version.
I’d also pay attention to where you got your current driver: Intel website, Windows updates, Snappy, or driver disc from computer (definitely not the case as the driver wasn’t many months to years old).
Does expanding the list of installable graphics drivers (double down arrow at the right side of that line) list something matching your current driver closer?
If you download the DP_Video_Intel_NT package, you don’t need to worry about downloading the index and if the related file in the index folder is deleted/missing the index will autorebuild the next time snappy is opened. Does it still then give a weird listing?I recall some of the newer AMD installers (therefore more up to date version tags show up when indexed) install an older version than what they say they are. Similar issue happens to me on some Killer network drivers if I recall. If I recall, v15.7.1 is buggy on different cards+operating systems.
I would find+use a newer or older version if you find any system issues. I think the beta had issues with some opengl or other advanced features not working right when I tested but 15.7.1 issues manifested in more obscure ways like out of memory when trying to play a video with windows media player and other random system bugs. Going up (yes, some v15 existed for some cards+operating systems even though they are not commonly found now) even if to the beta or going down to an older version would dodge those.
You could also get in touch with samlabs to see if they can do something on the packaging end to get that invalid detection to stop.General driverpack communities attitude toward XP x64 seemed to be ‘you are on your own’. I’d report install issues, especially if installing on x86 produces it. I keep old AMD installers around as I found 4xxx series cards bluescreen if not using official installers but Snappy and the old SAD+related packages both worked after the official installer had been ran. Not sure if I ever reported one of them.
Line 31 contained that error first. Perhaps more verbose logging could reveal something useful? Running the snappy executable from command line with the -failsafe paramater is supposed to skip reading that area.
Does the file actually exist and is readable? Regedit searching for that filename may help figure out if a copy is in a driverstore folder and what the file should have belonged to. Running the snappy executable from command line with the -failsafe paramater is supposed to skip reading that area.I know of some of the history but feel like I missed out on parts. adi is sound_adi package which was merged into sound_others. That is why it hasn’t been receiving updates for a long time as it is no longer separate at upstream’s work and doesn’t show when having snappy check their torrent. I noticed stuff like that when trying to check over package differences since I thought I recalled badpointer0 used to do some of his own packaging different from upstream. Removal likely requires adding a delete of all of that package instead of all but the newest. I had some reports of missed dialogs that should have been autoclicked and such but not sure what I may still have around that would be relevant. Are SDIO donations shared with the driver packager? Any guess if the nonorigin version of the program has any driver processing differences? any reason for no support or discussion areas on sourceforge pages?