Qun Mang

Can anyone tell me how I can add resolutions with refresh rates lower than 60Hz to Win2000/XP? I can do it on Windows98, but if I add any resolution with a refreshrate lower than 60Hz to the registry, the system ignores it. In case you're wondering how this relates to games, it is MAME that I'm trying to set custom resolutions for. I added many resolutions (256x256, 256x240, 384x224, and so on) to the registry (using advv 6.1 to determine timings) but only the 60Hz modes (didn't add any higher than that) show up as usable. There is a MODES key in the Windows98 registry where you can set the refresh rates, but it is not in the 2000/XP registry- only the TIMINGS key is, which is where I added the custom resolutions. I tried adding this key, but it didn't have any effect. If I haven't lost you yet, then do you have any ideas? Thanks.

Thanks for your reply. I looked over there, but they seem to be more about arcade monitors than anything else when it comes to video. I'll try posting there, but I fear I will get pretty much the same help as I did at the MAME and MAME32 forums. I was hoping that a Windows 2000 forum could give me some advice, as this is really a Win2000 (and probably WinXP) question as opposed to a MAME question.

Hmm... I've been using my Iwill's integrated sound since I upgraded my system what with all the SB Live problems with W2K. Maybe it's finally time to put my X-Gamer back in?

The first line on http://www.voodoofiles.com/3928 says "1.07 must be installed first!" Now, maybe I'm just stupid, but isn't the highest Voodoo3 driver version for Win 2000 1.04? If you go here: http://www.3dfx.com/downloads.htm you will see that the ONLY version 1.07 drivers are for Win98/ME. So, to use these CA Win2000 drivers, I must install Win98 drivers first? Does that sound wrong to anyone else? If anyone knows anything about this, please enlighten me. Thanks. P.S. Are these drivers any good?

So the win2000 beta drivers (Voodoo_Win2k.exe) dated 3/22/01 are the 1.07 drivers that need to be installed first ( http://www.voodoofiles.com/3872 )? [This message has been edited by Qun Mang (edited 11 April 2001).]

I just purchased an IWill KK266 motherboard, a 1.1GHz Tbird, a new case with 300W PS (Enlight), and a stick of KTI 128MB PC133 SDRAM. A few of the problems I'm running into include: sometimes POSTs, sometimes doesn't, particularly on a reset. Sometimes I have to hold the reset button for about 10s then releasing it before it will POST. When attempting to install Windows 98 or Windows ME, Scandisk will detect a FAT error and then lock up when I try to fix it. I didn't try installing Win 2000; I want to get Win 98 or ME working first (I don't care which, as it will only be used as a secondary OS, anyway). Iwill suggested a possible power supply problem, but I don't see how unless it's just defective. I am trying to run just a minimum system when installing: video, 1 HD, 1 CDROM, floppy, keyboard, mouse, 1 stick of RAM, 3 fans (tried with only the CPU fan, but it still failed). They alterately suggested a video card problem. Does anyone know of incompatibilities between a Voodoo3/3000 and this board? Could an incompatibility here cause problems with the hard drive? Naturally, when trying to load the already-installed Win 98 or Win 2000 OSs, they both failed. Win 98 kept complaining of a corrupt registry, then restored an old one, rebooted, and did the same thing. Win 2000 just came up immediately with an error say some file (forget name) was corrupt. I expected the OSs to not load, but I really expected them to install fresh. Am I going to have to reformat everything? I have several data and program partitions, and the only way to start fresh using fdisk is to get rid of everything (have to get rid of the extended partition to redo the C partition). I have been successful in the past just deleting the Windows and Program Files directories with Win 98 (never tried reinstalling Win 2000, I only started using it last October). Actually, I did try fdisking then reformatting the 10GB HD (see below), but it is possible that this HD has sector errors. I would've tried checking and marking out bad sectors, except Maxblast and Scandisk both crash. I am really at a loss here. Any help will be greatly appreciated. Hardware tried with new system: Compaq CDROM drive (also tried with Pioneer DVD-114) Maxtor UDMA/33 10.0GB HD (also tried with 30GB HD (UDMA/66) and 13.0GB HD (UDMA/33) together) Voodoo3 3000 AMD 1.1GHz Athlon w/Vantech fan IWill KK266 motherboard (non-raid version) When checking the vital stats (voltages & temp), everything seems normal, except the 2.5v line read 3.35v, though IWill says that's normal. The CPU temp was 40 deg. C. V_core was something like 1.6 or 1.8v. 3.3, 5, and 12V lines were pretty close, as well.

Powerdesk 4 all the way. The only real problem I have with it under W2000 is that the FTP client sometimes crashes PD, but I normally use CuteFTP or SmartFTP for FTP anyway. PD really doesn't need that feature. Other than that, it works great

Well, it seems a fear of mine has been realized. I called SMK, where I bought the board and CPU, and the tech there was absolutely certain the problem is the CPU. The problem is, the warranty clearly states it is void if ANY thermal compound is found anywhere but on the core. Even though I tried to put on as little as possible, it still ran off once I put the heatsink on. The paste itself is barely past the edge of the core, but there is a stain reaching (or very close to) the jumpers on one side. Even if the paste (which came with my Vantec fan) is conductive, could the STAIN reaching the jumpers really be shorting them? Also, if all the paste that's needed is a tiny drop on the core, then WHY does the Vantec include about 1000X that much? Thanks Brian for all your help.

Ok, I checked again, and v_core reads 1.92V, even after I go to the Smart Settings and change the v_core to 1.700V. I didn't try a lower v_core setting to see if it would read lower, though. I also re-fdisked and re-formatted the HD on another computer, and now scandisk doesn't crash. However, Windows setup has, twice. The first time, on copying setup files (froze), and again as soon as the GUI loaded (multiple errors- closed one error dialog, another would open). I am convinced Windows is not the problem, as MaxBlast also had problems. I don't think it would be a video card issue, either given these errors. Please correct me if I'm wrong. The RAM module works fine in my other system, so I'm sure it's not that, and swapping hard drives and CDROMs didn't work. What's left is the motherboard itself, or the processor. I heard that this board also has a problem with factory-unlocked Athlons. How can I tell if mine is one of these? What is the nature of this problem? I didn't buy mine in the retail box, so I think it's possible, even if not likely, that I could have been sent an ulkocked CPU. Again, thanks for any help you can give.

I'm not entirely sure what the V-Core voltage read, I just know it was 1.something. I'll have to look at it again. As for the IDE settings, what did you have to change? Right now, it autodetects the hard drives, and the detected UDMA settings seem correct. It can also read the hard drive just fine, even boot from it, so it would seem that the sector/cylinder settings are detected right, as well. The reset problem, though, seems to be an indicator of something serious. I'll probably just exchange the board and see if the problems go away.

Well, I guess it's a good thing you found a method that worked before I posted my idea, then. I guess I didn't remember correctly, after all...

Just out of curiosity, did your IRQ change on the reinstallation? That was going to be my suggestion. If I recall correctly, IRQ 9 (could be another IRQ, but I'm pretty sure it's 9) is an ungrounded IRQ which causes problems with some devices. I had an issue before with my modem; it was always "in use" and couldn't be opened. I changed the IRQ from 9 to something else, and it worked. You might want to remember this for future reference (if I am remembering right myself), in case you add a card or something later and your modem's IRQ gets bumped...

I'm looking to get a new motherboard, and I have my eye on Abit's KT7A board (along with an AMD 1GHz Thunderbird). I see from previous there are a few problems with ATA-100 and Win 2000 with this board. Do those problems extend to other UDMA modes? I have two Maxtor hard drives, one UDMA/33 and one UDMA/66, I will be using. Are there any other problems? And, will larger CPU cooling fans fit? If you have this board and love it (or at least have no problems with it), please let me know that, too. Thanks.

Inferno2000: A part of the emu community, I see... Microsoft would put it "All your computer are belong to us."

Can anyone post some info on Athlon mobos that don't have this problem? Or does this happen with all of them that have Via's chipset?

Yes, I get this error all the time, too. Often here on NT Compatible when just READING the forum messages. As a matter of fact, I am using Opera right now because IE crashed yet again. ANY help on this matter will be greatly appreciated.

Is anyone having this problem with the non-RAID model? I was thinking about getting the KT7A without RAID.

I want to upgrade to probably a Thunderbird 1.1 GHz, or a PIII/933 if there are still problems with Win 2000 (and Nvidia drivers) and AMD (I could use some opinions on this, as well). Does anyone have suggestions for a good motherboard/processor combo? One trick is, I'd like to go with a baby-AT form factor, if possible, as my current case holds a baby-AT, and I would like to stay away from yet ANOTHER case floating around (I have three - an old Compaq case and Acer case in addition to the one I'm using now). Also, is a 250 Watt power supply sufficient for these newer processors/motherboards? Thanks. [This message has been edited by Qun Mang (edited 14 February 2001).]

On second thought, maybe I'd better rethink that Abit board. I just read the topic: HighPoint kt7a woes with win2k (help)

Hmm... I never thought about having them work together by overclocking the PC100 module. My memory is from PNY, one of the higher quality companies, so it's definitely worth considering. As for the mobo, I am REALLY leaning toward the Abit KT7A with a 1GHz Athlon. Has anyone had problems with this board and a Voodoo3 or SB Live? I just want to make sure everything goes all right with my upgrade.

Also, how much faster is PC133 memory than PC100? I have a 128MB module I want to retain use of. I don't suppose PC100 and PC133 memory work together (probably a stupid question)?

I was afraid I'd have to get a new case; All the mobos I've seen listed were ATX, but I thought someone may know of an AT somewhere anyway... Thanks for all the recommendations. Currently, my video card is a Voodoo 3, but I know that will need an upgrade very soon, which is why I mentioned NVidia, but of course my next card, while not being a 3DFX for obvious reasons, doesn't HAVE to be an Nvidia. Anyone else with suggestions, please post them. I'll continue reading them. Again, thanks.

I downloaded and installed the Via busmaster driver from http://www.soltek.com.tw/downloads/drivers/580_3011.exe to get one of my Maxtor drives to work in UDMA mode (the other already worked fine). Well, it fixed that problem, but first time I tried to create a CD with Nero, I found the new driver caused it to fail. At the moment it would try to write to the CD, an error would be generated. I tried the latest version of Nero to no avail. Uninstalling the new driver fixed the problem, but now the one drive is back in PIO mode. Has anyone else experienced this? Any help would be appreciated. Pertinent specs: - FIC VA-503+ mobo with Via MVP3 chipset. - K6-III/450 - Two Maxtor hard drives on the primary bus, one UDMA/66 (operating just fine in UDMA mode 2) and one UDMA/33, the one that won't run in UDMA mode without the 580_3011 driver. - Plextor Plexwriter 8x4x32 as secondary master - Pioneer DVD-114 drive as secondary slave - Win 2000 Professional

Same problem here. One of my HDs wouldn't run in UDMA mode, so I installed the new, apparently beta, drivers. When I went to use Nero, same thing, so now I'm back to the old drivers with one HD in PIO mode. Oh, well. Anyway, here's a link to the topic on the hardware board: Via BM driver 580_3011 affects CD writer software. [ December 31, 2000: Message edited by: Qun Mang ]

Actually the Plexwriter does support DMA. It's even required to dependably write at 8X. For whatever reason, though, the driver just isn't compatible, like you said. I am back to the old driver, as a slower drive is better than a non-working one.