jaclaz

Yeah, sure, let me know where you teach thermodynamics so I can carefully avoid them lessons. There are setups with fans blowing and setups with fans sucking air, which one is better depends on a number of factors, the case, the other fans, the specific heatsink, the type of fans and what not, here the topic is about a PC that has been modified, with (from what I can understand) changing heatsink and fans so checking that the fan blows in the correct direction (whatever this direction is) is important. jaclaz.

AND... The actual 13-12_win7_win8_32_dd_ccc_whql.exe downloaded from https://www.amd-drivers.com/download-RadeonHD8180-mobility-driver-for-WindowsVista-32bit.html has not the .inf files "declared": CB162200.inf CE162200.inf but rather these: CB166389.inf CW166389.inf CE166389.inf I checked around, and there are (from other sources) other files named 13-12_win7_win8_32_dd_ccc_whql.exe around, identical to the above, but I also found one with different .inf's, like: CB165817.inf CE165817.inf CW165817.inf jaclaz

It seems like (in order to put into practice what they learned in the mentioned courses) the good AMD guys used in 13.6 Beta a structure *like*: \Packages\ \Packages\Drivers\ \Packages\Drivers\Display\ now this would normally get them an F, so they use something like: \Packages\Drivers\Display\W8_INF and \Packages\Drivers\Display\W86A_INF in order to muddle the waters, possibly the first is 64 bit and the second is x86 , but the real touch of genius is that inside that folder, there is more than one .inf, *like*: \Packages\Drivers\Display\W86A_INF\C7158083.inf and \Packages\Drivers\Display\W86A_INF\C8158083.inf and of course a folder with a completely not connected name *like*: \Packages\Drivers\Display\W86A_INF\B157935 containing the actual driver files. The nice quirk (what made them get a B) is that the C7158083.inf and the C8158083.inf are almost identical but the first is for 7 and the second is for 8[1], and actually at the beginning of each .inf there is its human readable name, respectively atiiw7ag.inf and atiiw8ag.inf. In order to get the A for the 13.12 version the driver you just posted a link to 13-12_win7_win8_32_dd_ccc_whql.exe has two .inf's: CB162200.inf and CE162200.inf where the human readable name has been removed. The first has: [Manufacturer] %ATI% = ATI.Mfg, NTx86.6.3, NTx86.6.0, NTx86.6.1, NTx86.6.2 BUT ONLY: [ATI.Mfg.NTx86.6.3] and the second has the SAME: [Manufacturer] %ATI% = ATI.Mfg, NTx86.6.2, NTx86.6.0, NTx86.6.1, NTx86.6.3 BUT ONLY: [ATI.Mfg.NTx86.6.2] So, I have my doubts that it is Vista compatible. Unless they play some other tricks. jaclaz [1] And the 7 one has: [Manufacturer] %ATI% = ATI.Mfg, NTamd64.6.1, NTamd64.6.0 [ATI.Mfg.NTamd64.6.1] and the 8 one has: [Manufacturer] %ATI% = ATI.Mfg, NTamd64.6.2 [ATI.Mfg.NTamd64.6.2]

Ok, first thing leave alone that stupid amount of bloat and get just the display driver: https://driverpack.io/it/hwids/PCI\VEN_1002%26DEV_9834?os=windows-xp-x86 this should be the "base", files seem like the same ones, but downloading and storing some 33 MB instead of 200 is already a bettering. jaclaz

Well, the Kabini is mentioned here (as an example): https://www.amd-drivers.com/amd-ati-mobility-drivers.html I have no idea what Temash or Kabini actually mean, nor if it has any particular consequence. From the little I can understand the HD 8180 exists in THREE forms (belonging to "Radeon Mobility" or "Mobility Radeon" family), one "discrete" (series HD8000M), one in "real" laptops (series HD8000G) and one in tablets or tablet like laptops/Notebook (APU A4-1200m HD 8180 only), see: https://www.amd.com/en/support/kb/release-notes/rn-cat-win-13-9 It is evident how the good Elantech guys and the good AMD/Catalyst ones studied at the UNI on the same course "Misnaming things, how to confuse other people by naming the same thing with various different, random or semi-random names and using the one or the other (or yet another one just invented) as casually as possible". And of course they also took the optional other course "Monolithic bloat: how to make a single driver covering ALL your hardware BUT leaving a few devices unsupported (without documenting which) to entertain your customers and have them busy many hours besides the lengthy download before they discover the driver won't work". The "latest version" of 14.4 (possibly 14.10.1006) seems like minimum Windows 7 : https://www.amd.com/en/support/kb/release-notes/rn-rad-win-14-4 you will appreciate how in the above there is also this: but NO release date to compare with. Very likely there is an "earlier version" (still 14.4) XP compatible (maybe, or maybe not). jaclaz

Well, go back to the driver that installs (once) without BSOD. Post a link to that one. Side notes (maybe relevant, maybe not). 1) is this the stupid laptop? https://www.youtube.com/watch?v=uH70uz9X9ZY 2) it seems like (whatever it means) the processor/whatever is "Temash" and not "Kabini" (no idea if it can change anything) https://www.notebookcheck.net/AMD-Radeon-HD-8180.93729.0.html https://www.notebookcheck.net/Radeon-HD-8180-vs-Radeon-HD-8240_4602_4604.247598.0.html jaclaz

These are likely suitable Windows 7 x64 drivers (might need to experiment): https://www.win-raid.com/t4348f52-Win-x-Coffee-Like-UHD-Video-driver.html Or: https://www.texpion.com/2018/06/Intel-7th-and-8th-generation-processor-graphics-driver-for-Windows-7-8-8.1.html This might also do : https://drp.su/en/hwids/PCI\VEN_8086%26DEV_3E98?os=windows-7-x64 jaclaz

Wait a minute. Which way does the fan spin? I mean usually (but not always) fans are made to extract blow air from towards the heatsink, not to blow extract air on from it. in this case that black conical thingy attached to the side panel is an exhaust intake and not an intake exhaust or viceversa it could have been (originally) an intake exhaust and now due to the changes in the heatsink and fan it has become an exhaust intake. My two cents (actually only one): DO NOT do that, i.e. DO NOT EVER run a processor without thermal paste (or a good thermal pad[1]) between it and the heatsink (it might take some time (from several seconds to a few minutes) to have two perfectly matching surfaces warp and become non-matching due to thermal expansion but it may happen (it may also not happen, of course). jaclaz [1] which is what you call a "sticker" in the photo, I am confused, you said you had put some thermal paste before (you don't use BOTH a pad AND thermal paste).

Naah, I only wanted to test what your politically correct version of it would have been . The archive and its contents look like fine to me . jaclaz

Surprising . jaclaz

Yes and no, only for the record., They are ALSO numbered consecutively, BUT the stupid board software has removed the ability to directly link to them (besides not showing it). Example (this was a ) valid link to post #529 on the given thread (the given number is an offset, so it is post #-1): hxxp://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page__st__528 If you try going to it: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page__st__528 You will see in the browser address bar that the address is converted (stupidly) to: https://msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page/36/ what happens is that the post number is divided by 15 (the numbers of posts on each page per current settings) BUT for *some* reasons the operation is on integers so all you get is post #526< (35*15=525+1): https://msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?do=findComment&comment=832857 while the post actually originally linked is 3 (528-525=529-526=3) posts later: https://msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?do=findComment&comment=832876 Ahh, the good ol'times, when a link *like*: hxxp://www.msfn.org/board/index.php?showtopic=128727&st=10 was meaning 11th (10+1) post on thread 128727, which now is: hxxps://msfn.org/board/topic/128727-cant-access-repair-my-pc-option-via-f8-startup/?do=findComment&comment=828512 So many bytes wasted at each request ... jaclaz

FireVox can use Sapi5 but can also use the Java FreeTTS engine, and also Orca: http://firevox.clcworld.net/voices.html (again installing/setting it up for these other sinthetizers may need some work) In 2008 the Firefox around should have been around version 3: https://en.wikipedia.org/wiki/Firefox_early_version_history#Firefox_3 So, since even the FireVox page mentions XP and Vista, most probably a VM running either of XP or Vista (and with a suitable Firefox install) might be the "best" test environment. jaclaz

Maybe because it was overlooked to add it in the list of supported OS? Anyway, it does support Windows 10. jaclaz

Retrozilla should support .xpi Firefox extensions. Are you sure-sure you attempted installing Firevox "properly"? From the officail page/with official instructions? http://firevox.clcworld.net/ AFAICR the Retroilla extensions installs is particularly finnicky: https://msfn.org/board/topic/181416-retrozilla-community-edition/ So maybe you need to do it in two steps: 1) install the extensions on a surely compatible version of Firefox 2) IF the extensions work/solve your problem then proceed with Retrozilla and - if needed - adapt the extensions to it. jaclaz

Yes. https://jdebp.eu/FGA/questions-with-yes-or-no-answers.html Of course it depends on what kind of help you are looking for, like: 1) having the whole batch written by some member of the board or: 2) ask for a code snippet here or there to solve a specific problem you encounter or: 3) advice on what approach and tools are better/more suitable Essentially: 1) forget about it 2) just ask 3) Nowadays a Windows 10 install is essentially the booting off a PE of sorts and applying of a .wim file, and we casually have here a very good program to this scope: https://msfn.org/board/topic/149612-winntsetup-v421/ so maybe you want to have a look at it and get familiar with the options it offers, and then ask questions on the batch/batches needed to automate it as much a possible ... jaclaz

Traditionally, when something of possible general use comes out as the result of a looong thread, a new thread is made for the "release" and the "working thread" is kept separate as "history". This way, if new issues, questions, etc. come out it is easier to understand the context and to not get confused by pages over pages of temporary files, tests, side issues, failed attempts, etc., whilst what happened is still kept accessible in case of need. In this case it would be even worse as this thread started only for the graphic card issue. And since Dencorso offered to have the driver hosted directly here, it would be much better, bar your (nice BTW ) idea about Archive.org, commonly used hosting sites tend to have issues before or later, and more often than not files hosted externally tend to go poof over time. jaclaz

Yep , you were maybe a tad bit too optimistic, I don't think you would need a 32 bit number to count people that use a Spreadtrum Phone on a nlited XP. Seriously with nlite you can (that is the idea) make big holes in an XP install, so your suspect may be correct. Which EXACT (there are 4 files on that page) driver(s) did you download and install? What do you have in SetupAPI.log? (though more often than not error/warnings in it are not accurate, sometimes they offer a hint at what is happening). If there is nothing of interest there, then your next attempt should be to trace the install. jaclaz P.S. Try also the UMDF drivers, some people reported that WMP11 alone wasn't good ( or good enough) on some machines/installs: https://forum.xda-developers.com/galaxy-s3/help/windows-xp-install-usb-drivers-t1874508/page2

I guess we will never know for sure. Actually it is officially designed for XP and later, and may partially work on Windows 2000: https://web.archive.org/web/20080916191023/http://www.nvda-project.org/documentation/nvda_0.6p2_userGuide.html#2 What about Fire-Vox/MLFire-Vox? http://firevox.clcworld.net/ It is an abandoned project: https://web.archive.org/web/20120301224425/http://visilab.unime.it/~filippo/MLFireVox/MLFireVox.htm But was seemingly continued in Click/Speak: http://clickspeak.clcworld.net/features.html NO idea if it can be made to work on pre-XP and with Retrozilla. jaclaz

Yep, maybe it is better to put the batches and the howto in a .zip within the driver .zip, so that they remain "grouped" until (if) they are used, ot they could be also a separate attachment. If you think that the how to is OK you can start a new thread with a minimum of background/history and the actual files attached, you will probably need to contact Dencorso for attachment size limits you may encounter. There is very little I can check, besided the list of needed files (that we already checked) and their versions (should you have misplaced anything) as the only "real" test/check is whether it works (and only you can test it at the moment), jaclaz

I don't get it. How are extended support dates related? From the links I posted, version 2.0 is 98 onwards, but earlier versions are Windows 95. So, IF the NVDA requires 2.0 OR IF a suitable earlier than 2.0 version is not found THEN it won't work OTHERWISE it may. Most probably this is last version working with 95: http://physics.fme.vutbr.cz/sea/download/ http://physics.fme.vutbr.cz/sea/download/win9x/msaardk.exe jaclaz

Ah well, not knowing what you attempted not the actual error(s) you get, nor the actual hardware involved, it will be a bit hard to provide you with any detailed assistance. You will need to provide some more exact report. AFAICR the "more complete" MTP drivers shipped with MediaPlayer 11. Generally speaking a VID/PID addition might be needed to the .inf for specific hardware: http://www.rimweb.in/forums/topic/36886-do-it-your-self-your-phones-mtp-drivers-for-windows-xp-sp3/ I won't go with the endless "Have tried this?" "Yes, I did and it didn't work" "Ok, and have you tried this other thing?" "Yes but it failed" ... Detail what you have done till now and the exact errors you got, hardware in use, etc., standard litany, please: https://jdebp.eu/FGA/problem-report-standard-litany.html You may also want to check and post relevant contents of the SetupAPI.log: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/setupapi-logging--windows-server-2003--windows-xp--and-windows-2000- jaclaz

This one confirms that MSAA came with Windows 95. https://docs.microsoft.com/en-us/windows/win32/accessibility/accessibility-legacy BUT this one places it (maybe the current downloadable version?) on Windows 98: https://docs.microsoft.com/en-us/windows/win32/winauto/microsoft-active-accessibility or maybe it works but it is not anymore supported (or it was not anymore supported at the time the page was written) It seems like up to 1.3 was Windows 95 and starting from 2.0 it is later OS: https://books.google.it/books?id=cf0Hh3soHVUC&pg=PA258&lpg=PA258&dq=msaa+"windows+95"+version+1&source=bl&ots=dRpaAWuLHU&sig=ACfU3U3lHEXYXs4h8tjn9UXMVYwiUJzlUQ&hl=en&sa=X&ved=2ahUKEwiGjeDh3L3qAhWKDxQKHWMwC5MQ6AEwAXoECAcQAQ#v=onepage&q=msaa "windows 95" version 1&f=false https://web.archive.org/web/19991129040953/http://www.microsoft.com/enable/msaa/download.htm It has to be seen if the earlier copy of msaardk.exe is the right one: https://web.archive.org/web/20000819044325/http://www.microsoft.com/enable/download/msaa/msaardk.exe jaclaz

A Quick How To will suffice. jaclaz howtobatches.txt

I would say that everything is ready for "release", what has to be decided is whether to leave the ;# REMmed lines and section or remove them alltogether. (I would leave them, as they might be useful to someone with different hardware and willing to do experiments. As well, it is to be decided if the 6 (please read as 7 ) small batches are to be included or not. Naaah, a parrot happily jumping around will suffice . jaclaz

Sure, when Yzöwl writes something, it works. Yep , it was just something to try, I don't think anyone will miss the function , but it is logically very similar to the 4 finger, so whether it works or not (and/or it "confuses" it with a 4 finger click/tap) may also depend on some other setting, *like* Palm, STV (sensibility) or - still say - it needs to have Four Finger Move Function disabled. Until I found the flash video I never thought that "Cover" was a gesture, I thought that it was something connected with "lid" , and the default action was something like a "privacy" action of sorts, you close the lid (cover) all windows minimize showing the desktop and when you re-open it there is no risk that any sensible data is on screen. jaclaz