zago27

Apparently my last post wasn't the end of it. I was able to get no network at all on said laptop. Basically, I installed Windows XP Pro SP2 (the only I have which works with OEM keys), installed WLAN and LAN drivers, then updated to SP3. And that's what broke both WLAN and LAN: the 2200BG scans for networks, asks for password, fails to connect, then enters a loop of disabling the card, retrying and failing to connect over and over. New player now: the PRO/1000 MT Mobile, which gets disabled by the WiFi driver and can't be reenabled at all. Or, at least, the only way I can make it work is to disable the WiFi card from Device Manager, then reboot. Now the 2200BG cannot interfere anymore and I can at least get Ethernet connection. Driver version: 9.0.4.37 for 2200BG, 8.10.1.0 for PRO/1000.

Final update. Installing a clean SP3 did the trick: I used the same drivers and now everything works. I've spent the last two years dealing with broken WiFi and now everything works just fine. (I probably have some driver god against me, this isn't the only case of misbehaving drivers on my computers) I will install the remaining drivers and updates and I will check if KB4089694 gets in the way.

Yes, I have. It's integrated with the modem card. By default is disabled and it still is. I didn't install any driver, so nothing should interfere. I already did it: I have a Broadcom 4318 card salvaged from another laptop and I tried it on the T42. I applied the no-1802 patch, installed the driver and used it for a while, but the signal strenght was really poor. That's why I wanted to revert back to the original 2200BG. In the process I also cleaned up the entire laptop and I've taken care of the pins with contact cleaner.

Sorry for the wait, I'm preparing for an exam for university. I prepared my ThinkPad with a clean install of Windows XP Professional SP2, just the plain OS with no drivers nor updates applied. Then, I set up some WiFi access points: one configured for WPA2/WPA, one for WEP, a third one for open auth (none of which was connected to the Internet). For checking the connection stability, I pinged 50 times the current gateway. I got some other versions to try out (thanks @ED_Sln for the upload), installed them and rebooted as soon as the driver applied. Here's what I ended up with: - 9.0.2.25, 04/29/2005 - 9.0.4.8, 01/17/2006 - 9.0.4.13, 04/05/2006 - 9.0.4.36, 04/04/2007 - 9.0.4.37, 07/25/2007 Every driver I used gave me the same result. Site scan ok WPA/WPA2: network type not recognized, refused to connect WEP: network type not recognized, refused to connect Open: connected, got IP from DHCP, ping ok I've never seen such a pattern: site scan went fine each time I tried, but I could only connect to unencrypted networks. That's somewhat of a win, because most of the times it would straight up fail to even detect a single network and it usually did once in a while. However, the complete refusal to connect to even a WEP AP is really strange: I might be missing some needed encryption update. I will try with a clean SP3 install to see if I get any improvement.

I have problems even with vanilla SP2 and vanilla SP3, and I never tried getting POSReady updates on any of my machines. Also, the problems come up as soon as I install the driver, before any update gets applied at all.

Hi there! I'm working on an IBM ThinkPad T42 and I'm trying out some hardware/software configurations on it. All seems to be working fine, but the WLAN adapter is starting to p*** me off. It's an Intel PRO/Wireless 2200BG card. I tried a different drivers from the Lenovo support page, from thinkpads.com driver listing and from Intel Download Center, but the only results I got were always the same: unstable connection, sudden dropouts, site scan with no networks detected. The problems were so stubborn that I thought the card itself was EOL, until I tried a Linux distro on the machine and VOILA', the thing is more stable than Ethernet. Windows XP is the main OS I'm going to use on this laptop, but I also installed Windows 2000, Windows Vista and Linux Mint 19.3 trying to figure out what was wrong. Vista and Linux worked fine. XP and 2000 were a hot mess. Here are the drivers I tried: 9.0.4.39, dated 12/19/2007 9.0.4.37, dated 07/25/2007 9.0.4.8, dated 01/17/2006 Original driver included with IBM Rescue & Recovery CD set, dated January 2005 (sorry, didn't get the INF version) A quick Google search revealed a ton of problems since the early days of this card, but I guess there's a driver/chip lottery going on here, I can't explain myself what is wrong with that. If anyone has a stable driver, please let me know what version is it! Thanks a lot!

Right now I'm having a strange behaviour with my Win10 1809 desktop. A week after the update, I noticed that it didn't delete all my files, nor it broke audio or network. I guess I had a bad version downloaded from WinUpdate. All of that while I'm updating Win8.1 on my non-Win8.1-compatible main laptop which I'm always carrying around.

After restarting the download 7 times, I finally got Win10 build 1709 on my main desktop. And it also upgraded from Win10 Pro to Win10 Education. What the heck, M$!? However, nice to see that all my devices are still working correctly and the updating process took less than 30 minutes on my "slow" system (FX-8320, 8GB DDR3-1866, Patriot 256GB SSD). The previous major upgrade took something like 1 hour and 45 minutes...

There are some applications that shouldn't, couldn't and wouldn't be running on small size/high PPI monitors. Unless they will become smart enough to auto-render and auto-resize ALL the controls on EVERY kind of display, apps like Photoshop, Premier Pro and all other media oriented software won't be small-screen-friendly. However, web browsers, instant messaging apps, some games, media content viewers are less big-screen-friendly. (I tried only once to read a plain text mail on a 24" 4K display without DPI scaling, I wouldn't recommend doing like that). On that side, DPI scaling in Win10 is one of the less crappy thing that has got implemented, even if software developers are going to wait for adding OS-controlled scaling features. P.S.: Previous OSes also got DPI scaling, but don't you remember that ugly font resize with no ClearType resizing?

I did it the first time on my previous laptop, but I don't remember exactly which version I used. I remember that it was the latest version for Windows 7 x86 compatible A8-6410 and the integrated graphics chip, I think I did it in March 2016, but I'm not completely sure... I also did it second time with a Radeon R7 360 with CD driver version 15.20.1062 (2015/07/25). I noticed that I had more problems on x64 drivers than x86 ones and Crimson are less compatible than older Catalyst. Maybe there is a different WDDM implementation.

I didn't notice any slow down, compared to 98 or 2000. I'll do it anyway, I know it is very unreliable. Actually, just before you wrote the post, I did a clean install. Nothing changed at all, it seems like it doesn't like this card. I can't use a machine without 3D acceleration, so I think I'm downgrading to Win98SE, which is always working fine. Well, I think that I just confirmed another "feature" brought by Windows Mistake Edition...

Well, actually it isn't an extremely difficult mod. The only thing needed is a notepad (I use Notepad++ because of syntax highlight and better string research). I usually extract the package in a folder and navigate until I find the video INF file. Then, I edit it by changing all the "NT6.1" strings to "NT6.0". I did it successfully on several AMD Radeon GPUs, but never tried on nVidia ones. Another thing. I saw the GPU-Z graphs up there on other drivers. The 0% fan speed and consequent low performance, I think it can be fixed by using software like MSI Afterburner or SpeedFan, which can change manually or automatically fan speed. SpeedFan also can be configured with custom speed curves in order to achieve a silent system when possible and better cool it down when needed.

Don't know if it can help, but I managed to run a Radeon R5 off a A8-6410 on Vista by editing Win7 INF files. It all worked fine on 2D and 3D, software and hardware renders. Maybe, modding official Win7 drivers may work fine on Vista's WDDM kernel.

Hi! I've just installed Windows ME on a Pentium III 1GHz with a GeForce4 MX440 graphics card. Just before, I had Windows 98 SE, but I didn't upgrade it, it's a clean install. I've installed also Half-Life and Quake II. These games, which ran seamlessly on Win98, are now really really slow on WinME. When I launch DXdiag.exe and I run video tests, the 3D one fails on every DX level, from 7 to 9. DirectDraw 2D tests work fine. I downloaded the latest driver from nVidia website, which was working fine on Win98 and also Win95, and DX9.0c (August 2006) from Microsoft Download Center, and also this was working good on Win98. Previously I had a Matrox Millenium G450, but it performed really bad on OpenGL rendering (even worse than the Ati Rage 128 Pro!), so I uninstalled the driver and the video card, and then swapped it with the GF4 MX440. Now, I have potato performance on either OpenGL and DirectX, only Software rendering works fine, but a very low resolution. Is that a WinME "feature"? Or have I did it in the wrong way? Zago

I always use the DX setup files from the Microsoft Download Center and it is a Zipped file after all. As usual I ran dxsetup.exe, but it works only once and, as I could see, it doesn't work properly. The second time I used it, it was stuck at the initialization stage and it never started the copying stage. I used the DX7 setup only to check if I had any Win98 problem, but that one worked fine. After that I tried the "manual way" and it is currently working with DX9. It's the first time I've ever seen this issue. I've been working on Win9x for about 5 years and it always worked fine. At least, I managed to fix it easily. I think I may create a batch file in order to register all the INFs and skipping the stock setup.