1650

[SufferWell1396]

okay so i have an ATI 1650 pro
what do you think i should do
for starters
the drivers for it in XP are CRAP
and i havnt gotten them to work yet
im using an nVidia TNT2 32 mb card now
and going from 32MB to 512 is a huge upgrade
so should i drop Windows Me (no 9x drivers)
and use this card, or what do you recommend?

[Diwiak]

Got the same problem, please help us! :)

in this review (http://www.hardwarezone.com/articles/view.php?cid=3&id=2044) they say it have 98 driver, but Idont beleive it..

let me know if you find something

[saphalline]

Wait... huh? :confused:

You're saying that you're still using WinME? Like for a Radeon X1650 vid card?? That doesn't work! :p No drivers!

You could probably get it to work using basic Windows drivers or with an older driver for a previous vid card, but the Win9x kernel was abandoned long ago. I'd recommend you upgrade your OS to Win2K or WinXP or something. You'd probably have better gaming support, too!

[SufferWell1396]

sorry i was misleading in my last post saph :p

what i mean is

i have a dual boot, XP and ME
the drivers for XP suck, and the computer crashes when i try to install them
and there arent any drivers for Windows Me for it, so is it really worth all the hastle?
my current card is an nVidia TNT2 32MB AGP4x card

[saphalline]

the drivers for XP suck, and the computer crashes when i try to install themI'm not really sure why that is. I haven't had any trouble with official WHQL graphics drivers since 2004! The X1650 is a very recent vid card - you shouldn't be having any problems whatsoever. Are you certain that everything else is updated? Windows updates and DirectX and all that? Latest BIOS version for your mobo? No errant settings in the BIOS?

As for WinME... WHY?? :p Why are you still using that? What purpose does it serve?

[mjc]

He's stubborn?

I've been asking him that same question for a verrrrrrrry long time...:D

[saphalline]

Oh geez... :rolleyes:

Dude, seriously! WinME is like a black hole in your hard drive! Get rid of it and run something useful on that partition, like Linux or something! When it gets to the point that new hardware doesn't work anymore, it's time to dump an OS!

Tell ya what, I'll make you a deal. I'll get that X1650 running in your WinXP partition, and you dump WinME. OK?

[SufferWell1396]

He's stubborn?

I've been asking him that same question for a verrrrrrrry long time...:D

Dude, seriously! WinME is like a black hole in your hard drive! Get rid of it and run something useful on that partition, like Linux or something! When it gets to the point that new hardware doesn't work anymore, it's time to dump an OS!

haha i like Windows Me =]
i just tweaked it, and its really stable.
anywoo
on the XP subject
k saph its a deal
but you know me, ill probably find some work around for Me :D

heres what happens when i install the drivers for it in XP
it says its gonna run some diagnostics
so it does its little thing
my monitor looses a signal
eventually the signal comes back
i get a bsod, and then it reboots
i have no choice but to select "last config that worked" on startup for XP
so what is it with the card?

[saphalline]

I have an idea of what it might be, but first I need that BSOD error! WinXP, System Properties, Advanced tab, Settings button under Startup and Recovery, uncheck the Automatically restart checkbox underneath System failure.

Do it again and copy that BSOD error. (Press the NMI reset button on your case to reboot.)

[SufferWell1396]

heres the message
i got it in the file
ATI2DVAG

Stop:0x000000EA

The device driver got stuck in an infinite loop

[Fruss Tray Ted]

Are you sure the error said:
The device driver got stuck in an infinite loop

and not this?:

STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER

When you are asked for the exact message, state the exact message please. It's quite easy to tell you wrote it by "got stuck" and "infinite loop"... :rolleyes: ;)

Now see the MS article about that error here (http://support.microsoft.com/kb/293078)

[SufferWell1396]

actually
the message did say
The device driver got stuck in an infinite loop

and only said 0x000000EA and nothing beyond that but a few more error codes.
but i will try what it says

[saphalline]

Yes, there really is a BSOD error that says that. And no, it's not a good thing.

*sigh*

Ok, I need to know your mobo's chipset & BIOS version, all BIOS settings related to AGP (speed, sideband addressing, fast writes, etc), and whether or not you've completely removed the TNT2 drivers (ie, in Safe Mode).

[SufferWell1396]

CHIPSET:Intel Brookdale i845
BIOS:Award Medallion (8/28/01)
AGP:Speed: 145MHz for the TNT2
and i dont know what the others mean.
and no, i just use the ones that shipped with Windows.

[mjc]

Before Saph posts back...I can tell that you have a real driver mess on your hands. In some ways, it may be easier to scrap this install and start over, with all the correct drivers on hand before beginning.

It isn't absolutely required to start over...just, in the long run, it would probably be the easier way to go about it.

You will need, at least, the proper Intel chipset drivers, the current ATI drivers for that card, sound and NIC drivers...it probably wouldn't hurt to check out if there is a BIOS update for the board...who made the board?

[SufferWell1396]

Asus made the board
Model No. P4B-LA

i have all of those drivers ready

[saphalline]

I'll look up the rest of that mobo's specs tonight. But in the mean time, I NEED that AGP info from the BIOS! It will be a prime factor in determining if this is a configuration problem or faulty hardware!

[SufferWell1396]

--------[ EVEREST Home Edition (c) 2003-2005 Lavalys, Inc. ]------------------------------------------------------------

Version EVEREST v2.20.405
Homepage http://www.lavalys.com/
Report Type Report Wizard
Computer H5Z5M6
Generator Howard
Operating System Microsoft Windows ME 4.90.3000 (WinMe Retail)
Date 2007-10-02
Time 21:08


--------[ GPU ]---------------------------------------------------------------------------------------------------------

[ AGP 4x: Asus AGP-V3800M ]

Graphics Processor Properties:
Video Adapter Asus AGP-V3800M
GPU Code Name NV5M64
PCI Device 10DE / 002D
Process Technology 0.25u
Bus Type AGP 4x
Memory Size 32 MB
GPU Clock 125 MHz
RAMDAC Clock 300 MHz
Pixel Pipelines 2
TMU Per Pipeline 1
Vertex Shaders Not Supported
Pixel Shaders Not Supported
DirectX Hardware Support DirectX v6.0
Pixel Fillrate 250 MPixel/s
Texel Fillrate 250 MTexel/s

Memory Bus Properties:
Bus Type SDR
Bus Width 64-bit
Real Clock 143 MHz
Effective Clock 143 MHz
Bandwidth 1144 MB/s

Graphics Processor Manufacturer:
Company Name NVIDIA Corporation
Product Information http://www.nvidia.com/view.asp?PAGE=products
Driver Download http://www.nvidia.com/content/drivers/drivers.asp

nVIDIA GPU Registers:
nv-000000 20154000
nv-100000 00000028
nv-100200 007B2000
nv-10020C 7C7EEF7D
nv-101000 800054C7
nv-680500 0001E30D
nv-680504 00000A01
nv-680570 0000011C
nv-680574 E0000000
nv-68057C 00000000

[SufferWell1396]

BIOS wouldnt provide me with anything,
and thats all Everest Home reported about my GPU ^^^

[saphalline]

Oh cr@p... that's an HP system isn't it?

The model number was MIA on Asus' site, but a quick Google search pulled up some HP info. If that's the case, we may be defeated here. Work-arounds for that error code rest almost entirely on being able to manually adjust SBA, fast writes, and AGP speed in the BIOS. Without those options, you are SOL! (Also, the other possibility of that error code is a faulty vid card, which I was going to try and establish through the BIOS options. Now it's pretty much a guaranteed return.)

I'm afraid that vid card simply isn't compatible with that HP-conscripted mobo. No wonder you're running WinME on that thing! :rolleyes: It came with that HP, didn't it? Geez...

[SufferWell1396]

nah this HP had XP installed by default
this thing is the fastest thing i can get my hands on
so i use it :)

it may be the card is faulty, because its very loud.
ill find another mobo to run it on to see if it is the card.