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. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

5 Neutral

About zago27

  • Birthday November 27

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

1,492 profile views
  1. 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.
  2. 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...
  3. 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?
  4. 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.
  5. 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...
  6. 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.
  7. 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.
  8. 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
  9. 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.
  10. Well, I managed to successfully upgrade to DX9.0c. I located an older DX7 setup from my Half-Life CD and I got DxDiag to see at least DX7. Then I extracted all the CABs from the DX9 folder and manually installed all the INF files. Rebooted and reran DxDiag, finally detected DX9. I needed help because I'm in a hurry preparing some machines for a retro LAN party, but I solved my problem easier than I expected.
  11. Hi, I'm trying to benchmark with 3DMark suite a bunch of old Windows 98SE machines. I've tracked down all the latest applications available to Win98SE, including DirectX 9.0c (August 2006) and 3DMark2001 SE. The last one, however, refuse to install. The error says that it needs DX8.1 or newer, but I've already installed DX9.0c. So, I took a look to DxDiag: it is actually detecting DX6.1!!The point is that nVidia Control Panel (I'm using a GF4 MX440) is detecting the latest DX9.0c. I really don't know what to do. Can anybody help me? Zago
  12. After 10 months of Win10 on my AMD FX machine, I went back to Win7. It was really annoying having tons of useless notifications that it needed new information about my Microsoft account, which was working just fine. Then, the permanent communication to the Internet: I didn't care about how much bandwidth it was using, but WHY it was using it! After the last major update, RAM usage went from 1,2 GB to 2,2 GB, all used by new svchost.exe processes, which only two of them were AMD related services! Now, with Win7, no more useless and unknown CPU and RAM used by a huge OS. Note: I disabled WinUpdate because it used to fulfill RAM (10GB) and CPU (8 cores at 4.2GHz). I had Win10 even on my 13-inches MacBook Pro from 2010, but after Creators Update, BootCamp drivers went all bad: I couldn't use built-in keyboard or trackpad and it kept going Blue Screen every time I turned on the laptop. Now, with WinXP (yep, the one which uses 70MB at the first startup, not 700MB!) I have no problem at all, it works like a charm. IMO, Win10 is being crappier every time I turn it on!
  13. Problem solved. In the 4th slot, there was a bent pin that was shorting with the opposite one. Once fixed, the computer boot up successfully. Now, it is working fine. Actually, I am using 2x512MB DDR2-533 non-ECC sticks.
  14. @Tripredacus Thanks, I didn't pay attention at that section on the user guide. The RAM plugged in was a non-ECC unbuffered. If I'll found an ECC stick, I'll try it. If it still won't work, I'll put inside the case something new.
  15. Hi, I've just got an old Acer Altos G320 server from a computer technician. It is based on Intel SE7320NH1-E motherboard, Intel Pentium 4 HT 631 CPU, integrated ATi ES1000 video controller, DDR2 memory. During POST, screen wouldn't switch on, system fans spinned at max speed and I heard 3 beeps from internal speaker. I took a look at the board troubleshooting guide: 3 beeps - RAM error. I changed the 2GB DDR2-667 module with another known-working module, a 256MB DDR2-533. It still didn't properly boot up. Tried all 4 slots in single and dual channel. Still no luck. CPU power is provided via a standard 8 pin 12V connector, but after I saw how was the board layout, I think that 4 pins power the CPU and the others power the 4 memory slots. The original Acer 8 pins power supply unit was changed with a standard 4 pins unit, the technician who gave me the server told me that the last time he used it, it was working. I put on a 8 pins PSU, on-going 3 beeps at startup. I had a faulty motherboard that beeped when it hadn't RAM sticks plugged in and when it was plugged in, it simply didn't boot up. It worked until 5 minutes before. May I have to heat up the board and restore some solder points? Or simply throw it away?
  • Create New...