Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Platinum Sponsor
  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


Dave-H last won the day on February 21

Dave-H had the most liked content!

Community Reputation

337 Excellent


About Dave-H

  • Birthday 03/31/1953

Profile Information

  • OS
    XP Pro x86
  • Country


  • Country Flag

Recent Profile Visitors

12,618 profile views
  1. OK, further thoughts! The file quoted on the BSOD is not the actual driver file, which is ati2mtag.sys, it's ati2dvag. Looking in the registry, that appears to be the name of the driver, and all the settings and configuration parameters are set under it. I'm now wondering if it's doing some operation on boot, which is looping and causing the crash, which it doesn't do when the driver is started from within Windows. I did think it a bit odd that even after installing the driver from scratch, it didn't insist on a reboot after the installation finished, in fact it just worked. Only on a subsequent boot does it fail, but I suspect that it's not the actual driver loading that's causing the problem. If it was it would crash when being enabled when Windows is running. Does that make any sense?
  2. @dencorso Thanks Den, I restored the "Service Installation" section to the INF file, and it did then install, but couldn't start, the ubiquitous "code 10"! @RainyShadow Thanks, that was good thinking! I did the install again, everything was great, the display looked really good, and the refresh rate was fine. I then disabled in Autoruns everything related to the driver, when I rebooted as expected it reverted to the VGASAVE driver. I then enabled just the ATI driver (ati2mtag.sys), and nothing else, and it rebooted to the usual BSOD. I think we're running out of options here, unless anyone else has any suggestions. It looks as if the driver itself will not load on booting up, so unless I go through the rignarole of disabling the adapter before I shut down, and then re-enable it once the system has booted, which does work, I see no way around it. Such a shame, it seemed to be so close to working! BTW, I now have 1366x768 resolution with 32 bit colour in Safe Mode, which is something I never thought I would ever see, certainly not on XP!
  3. Thanks @jaclaz, that has helped quite a bit! Now I don't know whether to just use this as it is, or still hold out to see if a better driver is possible. The fact that the ATI driver did work, although it wouldn't stay working over a reboot, leads me to think that it must be possible. I imagine it's just a matter as we said of pruning the INF file down to just install the driver and nothing else. If it won't work like that then it's probably time to give up! I did try removing all the "Service Installation" and "Software Installation" sections from the INF, but when I tried that it said it wasn't an XP compatible driver, so I must have removed something which has to be there!
  4. OK, it seems it's now using a driver called "VGASAVE", which I'd not heard of before. Apparently it's the Windows driver it falls back to if there is no other graphics driver installed, or the system is in Safe Mode. I must say I had always assumed that the basic VGA driver was exactly that though, a VGA only driver, so I'm still surprised that it seems to be able produce higher resolutions than basic 640x480 with 8 bit colour.
  5. OK, curiouser and curiouser! I had run Autoruns in the past on my main machine, but never on the netbook. When I ran it, it found quite a few orphaned registry entries, mainly where the files they referred to were no longer on the system. I cleaned it all up and everything was fine. I still had the extra tabs in the Display Properties advanced settings window though. I finally looked more closely at the error logs from when they crashed, and it turned out that the culprit was "emgdgui.dll", which of course turned out to be the Intel graphics user interface! Once that was gone and removed from the registry, the tabs were gone. So, I now had a machine clean of any graphics drivers. All the Intel and ATI/AMD files and registry entries had gone. Now here's the strange bit! On a whim I decided to try the resolution control on the Display Properties window, and to my amazement I found I could change it to a higher level (1366x768 with 32 bit colour) and it worked! The resolution changed, and it stuck. Even after a reboot, the resolution setting was still fine. The only thing I could find wrong was that the refresh rate seemed to be poor. So, how can that work when I have no graphics drivers loaded?! The Display Adapter still shows a yellow exclamation mark in Device Manager, and it says there are no driver files loaded and it's not using any resources. So, surely it should be stuck in VGA mode, as it was before? Any thoughts? I can probably use it like this, although the refresh rate is an issue when scrolling or moving things around on the screen, but AFAIK it shouldn't be working at all with no driver! Cheers, Dave.
  6. What a great idea @jaclaz! Certainly worth a try if all else fails, but @RainyShadow has prompted me about something. I had already looked up EMGD and seen it was something to do with Intel, which I thought was strange as I thought I'd purged the system of all Intel-related files and registry entries, which were from when the system drive was in my old netbook, which was an Intel-based machine. Of course I've now realised that the crashing tabs on the Display Properties window are in fact the tabs from the old Intel graphics driver. Why they are still there I have no idea, but I certainly intend to find out! They may well be nothing to do with the AMD driver crashing, but it's one more thing to eliminate. I already have Autoruns, so I will deploy that and see what it shows. Cheers, Dave.
  7. This is what I'm seeing, nothing in the sidebar except the block of links that are normally at the bottom of it.
  8. I'm afraid I didn't have any luck at all with the Display Driver Uninstaller utility. As soon as I told it to uninstall the driver it immediately crashed every time, both in normal mode and Safe Mode ("....has run into a problem and needs to close") and apparently it was a "system exception". The Windows Application event log is full of .NET 4 exception errors. I guess I could try with an even earlier version. I then tried with Driver Cleaner Pro anyway, which I already had a copy of. That seemed to be more successful, but I manually removed any residual files and registry entries anyway. Unfortunately commenting out the HKLM lines in the INF file doesn't do the trick. The crashing tabs are still there on the Display properties, and the driver still crashes when the machine is rebooted. I'll have a look trough the INF file and see what else i think can be taken out, hopefully just leaving the basic driver install.
  9. On Firefox 74 on Windows 10, I've noticed that collapsing the sidebar no longer removes it completely, it now collapses to a row of icons. I guess that's the code change which has stopped it appearing completely in Firefox 52 ESR.
  10. I downloaded version of the utility, which is the last that works on XP, and later versions need .NET 4.5 apparently. I'll let you know how it goes! Thinking of you all in Italy. We've only been in full lockdown here in the UK for six days. I guess it will be weeks before we know if it's working or not.
  11. My sidebar with the list of my subscriptions has disappeared again from YouTube on Firefox 52.9 ESR. It's just showing the information links that are normally at the bottom of it, but nothing else.
  12. Thanks @jaclaz. I have no normal uninstallation option for the driver, so do you think I can uninstall it using the INF file with the necessary command? The file has [Uninstall.CopyFiles] and [Uninstall.AddReg] sections, but no [DefaultUninstall] section. BTW I am horrified at the awful news coming from your country. I do hope you and yours are still OK.
  13. Yes, I wonder if some pruning of the INF file might do the trick. I'm not interested in any of the "bells and whistles". As long as the driver will go into the mode I need, and is stable, that's all I'm hoping for. I've attached the INF file here in case anyone with more experience of customising these types of drivers has any suggestions. Thanks for any input. oem39.inf
  14. Another update. I think I can now definitely say that the driver can work, if only at a basic level. If I boot into Safe Mode and disable the display adapter, when I then boot into normal mode and re-enable it, the driver loads and I can set higher resolutions (including 1366x786) without any problem. The display is good, although there is no acceleration. The display control panel still crashes if I try and use any of the tabs added by the AMD driver. However, that's usable as far as I'm concerned, at least it isn't stuck in VGA mode! It still won't survive a reboot though, it just blue screens again, and I have to then go into Safe Mode again and repeat the whole procedure. So, why will the driver apparently load OK when the machine is already up and running, but won't load when booting?
  15. Apparently UBO 1.74 isn't being supported any more, whereas UBO 1.16 is, specifically for legacy browsers. See here and the subsequent posts. I use 1.16 now and it seems to work fine and auto-updates.
  • Create New...