Announcement

**SCompRacer1** · 19 August 1999, 16:07

xevious,

If you want to free up some more IRQ's, disable one of your serial (com) ports in BIOS, if you are not using them. Alot of computers with internal modems are set up like this.

As far as SB 16 emulation, if you do not play any DOS games, disable it in device manager.

**xevious** · 19 August 1999, 16:21

Thanks, SCompRacer1, but I need both of my COM ports and I also need SB16 emulation.
Thanks anyway.
-Matt(xevious)

**OrangeJulius** · 19 August 1999, 16:25

Have you tried booting with JUST the bare essentials?

Maybe it's that AMD chip.. :/

**Kruzin** · 19 August 1999, 16:26

If it's showing 2 IRQ holders, there is probably some remanants of something hanging onto that IRQ.

Boot into safe mode, and check your device manager. All of it. Especially mobo and pnp type things. Stuff will show up in safe mode that doesn't in normal mode. Look for duplicate entries, or things listed that are no longer in your system, or disabled. Remove both copies of all duplicates, all errant devices listed, and let Windows redetect the hardware. If there are lots of duplicates, you may want to edit your registry, and delete the entire ENUM key. This will remove all hardware drivers, and let windows rebuild them from the ground up...

**Buuri** · 19 August 1999, 16:44

I think it's those VIA chips. I had this shitty SS7 board with VIA chips when I bought my G200. I had same kind of a troubles, and I was never able to fix before I bought an Asus board (with ALi chips).

Oh, but then again it should work with bus mastering disabled, but I don't think you want to settle with that. Also try to disable "read around write" and other that kind of settings from BIOS.

B

**xevious** · 19 August 1999, 16:52

Kruzin - thanks. I went into safe mode and it said there was a secondary ide controller.
I tried to remove it, but it said it belonged to a parent device. The window said something about "the following parent device" and then didnt list anything. Which Enum thing should I delete in the registry? All of them?

Thanks.
-Matt(xevious)

**RD Gumby** · 19 August 1999, 16:53

Hi there fellow AMD user...

You just described all the problems I'm
currently having with my system better
than I could have done myself

It's common problem with Super Socket 7
mainboards, but no-one (at least in this
forum) has been able to solve it (yet).
(big thanks for all the effort anyway!)

I'm using ASUS P5A mainboard with the Ali Aladdin chipset, and the symptoms are just the same: First, the Setup doesn't seem to
copy any files anywhere, and then Windows
crashes at reboot.

(note: updating the Ali AGP drivers fixed
the odd behaviour of the setup-program for me, but not the reboot problems. Don't know about the VIA chipset)

One difference: I've never even been able to get the 640*480 desktop with 5.13 drivers.
It's either all garbled graphics or a total system freeze with a black screen.

All earlier drivers work without problems.
I'm starting to suspect a conspiracy here...

Another problem for me is that I was planning
to upgrade to G400, but now I have second thoughts because of this driver-issue. If the drivers do not work with G200, there is a chance they do not work with G400 if the actual problem really is in the SS7 mainboards. I'm actually concidering
getting a Voodoo 3, can you believe it !
(it's still the most SS7-compatible solution if I'm not mistaken) And TNT2 is worst of the lot with SS7-boards.

Yes, I've been told to switch to Intel-based
mainboards, but as a student I have a limited budget, and upgrading the processor/mainboard/G400 combination at once is a bit too much. I prefer the better price/performance ratio offered by AMD.

I've lost track of the point I was
trying to make...

------------------
System ----------------
AMD K6-2 300@350
ASUS P5A b1007
Millenium G200 b2.6
Sound Blaster 16 ISA
128 mb RAM
Windows 98
Hyundai DeluxScan 15Pro
Ali AGP driver v1.6
4.33c certified driver

**Buuri** · 19 August 1999, 17:06

That's weird because I had no problems in updating from 4.51 to 5.13 and I have P5A too.
Did you remove the old drivers properly? Do you have the latest AGP driver for Win98 and motherboard BIOS?
(The latest BIOS is 1007A and available from <a href="ftp://ftp.asuscom.de/pub/ASUSCOM/BIOS/Socket_7/ALI_Chipset/ALI_V/P5A/">ftp.asuscom.de</a>. The AGP driver lurks in <a href="http://www.ali.com.tw">www.ali.com.tw</a>)

B

[This message has been edited by Buuri (edited 08-20-1999).]

**RD Gumby** · 19 August 1999, 17:39

My driver versions are hidden somewhere
in the system information
in the signature

But seriously, yes, bios version is 1007.
I have the matrox uninstaller and I've been using it. My AGP driver is v1.6. I got it from www.acerlabs.com/ -something, but it looks like the same. There can't be so many of them... Are there other Ali Aladdin related drivers I should be aware of?

This 1.6 version seems to be the first one
to actually do what it says (i.e. solve compatibility problems with G200). The earlier versions generally froze my system within 30 seconds after starting windows.

Other than this, I'm quite happy with my
P5A-mainboard

------------------
System ----------------
AMD K6-2 300@350
ASUS P5A b1007
Millenium G200 b2.6
Sound Blaster 16 ISA
128 mb RAM
Windows 98
Hyundai DeluxScan 15Pro
Ali AGP driver v1.6
4.33c certified driver

**Buuri** · 19 August 1999, 17:42

D'OH!

Well.. anyway about other drivers, there are IDE drivers as well at www.ali.com.tw
It's recommended to use them.

I just noticed that you are using 4.33c, but have you tried 4.51? You should try them in order to find out if you are experiencing a problem with PD5 series or is it somewhere else.

B

[This message has been edited by Buuri (edited 08-20-1999).]

**Kruzin** · 19 August 1999, 17:53

xevious - I would only delete the ENUM key if I has lots of duplicate devices. You will probably not be able to get rid of that IDE controoler, since it's a part of the same parent device as the other IDE port. But if you where go this way, just delete they entire key. But expect hours of rebuilding all of your drivers...

Can you force the Net card to that IRQ through the pci/pnp settings in the bios? Then the G400 should fall into a better IRQ...

**sixpac** · 19 August 1999, 18:00

you might wanna try and get rid of those 5.13
drivers and download them again plus the latest drivers from via which i believe are the 4 all in one drivers take everything out
ofyour system except the video card and reformat your hard drive and do a clean install of winblows after setup is done install the via drivers first then dx6.1
then the 5.13 drivers and see if that works
if that does the trick install the rest of your stuff one at a time.hope this helps.no
matter what i install new i always reformat and do a clean install and i've never had any problems with my ss7 Good Luck

------------------
Amd K6-2 350@452,Fic 503+ 1.2a,64mb Mushkin Samsung GHcas2,Maxtor 8.4gb,G200 Mill.8mb Sgram,Yamaha sound

**sixpac** · 19 August 1999, 18:07

Also remember to disable write cache pipeline
and read around write in your bio's

------------------
Amd K6-2 350@452,Fic 503+ 1.2a,64mb Mushkin Samsung GHcas2,Maxtor 8.4gb,G200 Mill.8mb Sgram,Yamaha sound

**RD Gumby** · 19 August 1999, 18:13

I'm using 4.33c because the 4.51 version
(as well as those old 4.2x versions) give
me corrupted textures and such in some games I'm currently playing. Mainly Colin McRae Rally and Thief and Unreal. I see no visible difference in speed, but with 4.51 there seems to be all kinds of small errors in graphics. The only occasion I'm using the 4.51 is when playing Half-Life (not often), in order to see something undervater.

Downloaded the IDE driver. Gotta try when I get home. (been typing this at work )

My current IDE driver is from the ASUS installation CD, from august '98, so its quite old... can't remember the version.

Until recently, I did not have any special
AGP-drivers at all (since they brought only trouble). At least not visible in the ADD/REMOVE program section. Just a clean install of win98 and the drivers from the ASUS CD (minus the AGP driver, v1.2 which is a disaster), directX6.1 and the matrox drivers. Everything worked just fine, games, everything. It's only after this PD5.13 -issue I've started to fiddle with these special AGP-drivers, mostly with very pathetic results. Only this v1.6 seems to work. For now. I'm no expert in these issues, and far too cynical to think one new patch could solve everything.

I think I'm also typing too long posts...

Announcement

PD5 royally f***s up my system.

PD5 royally f***s up my system.

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment