jaclaz

Yep, the idea (to be tested) being: 0) install the driver 1) (re-)boot with /basevideo (VGASAVE) 2) automatically (login script or similar automatic start) uninstall and reinstall the driver (and set the right resolution) 3) loop to #1 jaclaz

Yep, they are two separate approaches. 1) be happy with the VGASAVE set at 1366x768 even if a bit slow (but again it is only a secondary OS, so it should be bearable) 2) try experimenting with the (crappy) ATI/AMD driver, I don't know, but maybe if you set it to a "standard" resolution (like - say - 800x600) it may actually boot without BSOD and then (if any of the tools work) you can change the resolution after boot (if it won't BSOD then). As a side note, there are chances that the current issues are with the "whole" Catalyst package, whilst "only" the driver maybe works. In the meantime I found a report (Russian, use Google translate) http://gallery.ru-board.com/topic.cgi?forum=81&active=11&topic=5327&start=720 which is very similar to your experience, BUT - maybe - if the driver works at "first install", we can find a way to install it at boot and uninstall it at shutdown? jaclaz

Can't you go back in time to this point? If you can have 1366x768, the VGASAVE with acceleration level 5 should be bearable, as a secondary OS. Try also: http://qres.sourceforge.net/ https://www.nirsoft.net/utils/multi_monitor_tool.html or NIRCMD setdisplay: https://nircmd.nirsoft.net/setdisplay.html jaclaz

Naah, they were on ATI/AMD site allright: http://web.archive.org/web/20150525015957/http://www2.ati.com/drivers/windows-xp-amd-catalyst-9.00.300.3005-dec9.exe jaclaz

Only to let you know how dinosaurs simply love green text on black background BUT they cannot see blue on black. jaclaz

No you cannot! That's the WHOLE point of taking sides . What you are experiencing is not entirely unlike having an alien parasite (symbiote/klyntar) taking possession of your body (and mind). (minus the increased strength and mental and healing powers) They are creepy, slimy and very, very dangerous, see: https://en.wikipedia.org/wiki/Symbiote_(comics) jaclaz

If it is a dual core, then those APU's are maybe right, leave 'em alone. I still have some doubt on motherbaord resources, but leave 'em alone. I would try deleting the monitors and see what happens. jaclaz

Whenever I see duplicated items in device manager I suspect that there is some cleaning to be done. You surely don't have three monitors, and I doubt you have two "Motherboard resources" and two "AMD A4-1200 APU. etc." jaclaz

Latest should be this one: https://ftp.webtent.net/pub/windows/Make_PE3_48.exe jaclaz

I doubt it. It is more likely that it is the file ati2dvag.dll jaclaz

Check: https://bearwindows.zcm.com.au/vga.htm jaclaz

Another (random ) idea. What if you replace all files (but the .sys driver) with the Dud? http://www3.telus.net/_/dud/ jaclaz

Try this one: https://forums.guru3d.com/threads/display-driver-uninstaller-thread.379505/ I am not too sure that latest is XP compatible, maybe you will need to dig up an older version. jaclaz P.S.: (about Covid-19 situation in Italy) The situation is (apart a small number of areas in the North where it is still dramatic ) relatively under control, in the sense that everyone is actually staying at home (people are largely respectful of the current rules) and the number of new cases is increasing at a much slower pace than it was until a few days ago, actually the curve has flattened, see: http://nrg.cs.ucl.ac.uk/mjh/covid19/#rates Consider how now is almost three weeks from the initial (more "light") lockdown, so we are now seeing the effects of that one, the "new" (tighter) lockdown was only 5 days ago (and actually fully effective only since 2 days) so we'll need another full week at least, very likely two, to start seeing the effects of the latter.

What I would try first (it should cost nothing or next to nothing) would be: 1) Uninstall the driver 2) modify the .inf REMming all Registry HKLM entries (i.e. open the source .inf and replace "<CR+LF>HKLM" with "<CR+LF>;HKLM" or, if you prefer, place a semicolon in front of any line that starts with HKLM) 3) Reinstall the driver This should remove all Winlogon, Autostart, etc. entries for the non-strictly-the-driver files. Will it work? No idea , but if it does it is quick (and dirty ). jaclaz

Maybe there is a way to only load/install the basic driver without the AMD "utilities" and the *whatever* that adds tabs to the display control panel. jaclaz

Possibly of use: jaclaz

Yep, this is what Tripredacus and I tried telling you since the start, possiby we were not clear enough, you need a device inserted/connected BEFORE attempting to change boot order and/or choosing device via F12. jaclaz

Ow, come on, what's in a name? Wouldn't a huge pile of manure smell as sweet by any other name? jaclaz

It greatly depends on the expert, Armand Gracious (JFYI): https://www.dedoimedo.com/computers/experts.html jaclaz

Good. I love it when a plan comes together. jaclaz

No, you are intending "wrong". Who cares if it is newer? Hint: once you manage (hopefully) to boot in AHCI/SATA mode, you will reasonably be able to update the AHCI/SATA driver. Do follow the given advice first: https://msfn.org/board/topic/181337-cannot-set-new-boot-option-in-bios/?do=findComment&comment=1179280 that one is JUST the AHCI/SATA driver AND seemingly it is in a format compatible with driverinjection tool. jaclaz

Look, I am trying (with some difficulty) to understand what you have done from the (scarce) feedback you provide. Where we are (according to my understanding of your reports): 1) you installed a bunch of drivers from IN1VDO11WW1.exe 2) the IN1VDO11WW1.exe contains BOTH a "plain" driver \\Packages\Drivers\SBDrv\hseries\MINI_IDE\XP\, from now on AmdIde.sys, AND: 3) a "RAID" (actually also AHCI) driver \\Packages\Drivers\SBDrv\hseries\RAID\, from now on ahcix86.sys 4) I suspected that what you have installed, together with the bunch of drivers in #1 is the Amdide.sys (since you installed it in IDE mode) AND: 5) suggested you to try using the driverinjection to try installing the Ahcix86,sys 6) RainyShadow suggested (correctly) to try installing instead the ahcix86.sys that is in the file IN1AHC20WW1.exe 7) You failed to report whether you actually followed the suggestion in #6 and went astray with uninstalling VBEMP (hey. look. that is a squirrel ) So the questions remain: a. Did you actually follow RainyShadow's suggestion (per #6 above)? b. If yes, what happened? c. If not, what are you waiting for? If you actually did follow RainyShadow's suggestion (per #6 above) AND upon reboot AND with BIOS set as AHCI you still get a 0x0000007b, then we can move on from this with further troubleshooting steps, namely comparing what you now have in the Registry with the information in the .reg file here: https://answers.microsoft.com/en-us/windows/forum/windows_xp-hardware/how-do-i-change-widows-xp-from-ide-mode-to-ahci/7819a905-cfd9-4966-b2aa-67afc80a31d8?page=8 (post by D J Roff) jaclaz

More like : jaclaz

It is the "assuming it's on the system" assumption that is - at the moment - only an assumption. Did you actually install the driver RainyShadow pointed you to? jaclaz

Yep. If you have a "spare" USB stick, you could use Rufus to make it surely UEFI bootable. https://rufus.ie/ It doesn't really matter *which* payload you use, you can try the SuperGrub2: https://www.supergrubdisk.org/category/download/supergrub2diskdownload/super-grub2-disk-stable/ https://sourceforge.net/projects/supergrub2/files/2.04s1/super_grub2_disk_2.04s1/super_grub2_disk_hybrid_2.04s1.iso/download which is small and simple and *universal*. Right now we don't know if the issue is the format of the *whatever* device you tried till now or *something else*, so we need to test with a surely UEFI compatible/bootable device to see if it makes a difference (it is a rare occasion, but it is possible that it could be a *random* firmware/NVRAM issue). jaclaz