Serious issue with 2.41 drivers on A7N8X...am I alone?

[Nuke209]

Just installed the 2.41s on mine, including the IDE driver, and it all works flawlessly - no problems whatsosver.

The new IDE driver is *very* nice - CPU usage when burning a CD at 52X, is now sod-all

Same here

[Salem07]

BTW, windows was so screwed up after the drivers I HAD to rebuild it.....I am not a neophyte but a network admin who builds PCs for a living and I am tellign you XP was MESSED UP! (Not to mention that I was getting a must activate in 3 days note from MS because my hardware had supposedly changed.....although it hadn't).

I read something about 2.41 made the IDE drives show up as scsi or something so I am wonderng if it somehow is related to my SCSI raid.

All I know is I will be rebuilding tonight and will try it without the SW IDE drivers....

Bob

So much for getting rid of IDE drivers

As a network admin, you should know how to handle such problems (scared of faulty NVata ?),and prevent those drivers from loading to say the least.
Years of DOS taught me that some command lines are always better than a full OS re-installation.

I tried to install the full package at least 3 times on my personal system.No luck for me.But not a single time did i thnk about re-installing the OS...

WinXP screwed ? Unless the drivers messed up your current partition, i dont see how you couldnt solve the problem.

PS:Norton Ghost 2003 is the admin's best friend

PS2: Can i have your job ?

[StoolPusher]

Try booting up with just the drive that has the OS on it. I had sort of same problem but with 2 ide drives installed. After takeing out my 2d drive i could get into windows and after studying my 2nd drive I noticed that one of the pins was bent so I straightened it out and njow I can boot into windows with both drives but funny thing was that with oud ide drivers it didnt matter that the oin was bent and i had no trouble booting into windows but with new driver It would allways freeze in middle of starting windows on microsoft windows splash screen. Glad I found the problem because this new driver rocks and it does list my diamond max 133 as a UDMA 6 drive and the performance is very noticeable I feel. Hope this helps someone even though I know not everyone is gonna have a bent pin but maybe by working with just the one drive then they can pin point the problem.

[The Unibonger]

I too got the whole slew of errors wehn updating to this driver.. Windows loaded to the startup screen then took another 2 min to load in afterwards.. Plus I had absolutely no sound.. My only fix was a complete system format.. And yes I did completely uninstall all previous drivers before installing the new ones... And the second time right after.. from a completely fresh windows Xp install.. The very first thing I installed were the updated drivers.. Now this Time I did not get the boot lag or anything.. But My pc would still not recognize my system had any audio at all.. So then I reinstalled again.. and installed the asus drivers from the cd and havent touched a d*** single thing since then.. And yes I am still putting up with all these damn static and hissing errors when my mouse moves and my hdd's read.. However im beginning to suspect that this is mearly a grounding issue and had nothing to do with asus at all... I will try a few things and post back on my status.

[McCloud9]

I installed the drivers too, worked ok except it would no longer recognize my CDrom/DVDROM, I had created a restore point in xp so just restored system and all is fine. So much for trying nvidia SW IDE drivers, phooey. Oh and after I installed even tho it seemed to work fine my bench marks dropped a little.

[Gekotek]

BTW, windows was so screwed up after the drivers I HAD to rebuild it.....I am not a neophyte but a network admin who builds PCs for a living and I am tellign you XP was MESSED UP! (Not to mention that I was getting a must activate in 3 days note from MS because my hardware had supposedly changed.....although it hadn't).

I read something about 2.41 made the IDE drives show up as scsi or something so I am wonderng if it somehow is related to my SCSI raid.

All I know is I will be rebuilding tonight and will try it without the SW IDE drivers....

Bob

You may be a network admin, but you don't know NT very well. I am also a network admin and build systems for a living. All you had to do is choose "Last Known Good Configuration." Works everytime on driver issues. I had the same problem. Everytime I installed the new driver, my system would not boot. I recovered w/ "Last Known Good...." each time. Finally, I manually installed the drivers one at a time, then rebooted, then did a full install. I also deleted the Display driver files in the Display folder and replaced them with the drivers I wanted to use before manually kicking off the install.

See here for more details on what I did:
http://www.nforcershq.com/forum/viewtop ... 784#126784

But I wrangled w/ it for over an hour....not sure EXACTLY what I did to get it going, but it's going now.

[Gekotek]

Just curious here....seems like the IDE SW driver is causing issues w/ some ppls systems and not others. Please post if you had trouble and what brand drives you have. I'll start.

I had trouble.
60 GB IBM
20 GB WD

[TekWorm]

Forgive my insolent but humble opinion...
I think the Obvious common denominator is bein' overlooked (as it nearly always gets a pass)..

Seems to me, the most commonly shared thing, in many, many problem threads is "XP"!

I realize the majority of folks are runnin' it, accounting for a higher ratio of system illness, comin' from it's users.. But I really would luv to know what a balanced ratio would turn out to be.

Actually, I miss why folks don't connect that it's little more than a slipshod bit of MS engineered spyware, geered at Bill's passion for control!

I built two of these, now....
Mine built on Win2k Pro (see sig)
and a friend's on 98SE.

Mine's been running, day & night, for .. what(?) 2 months+..
The other for a couple weeks.

Both setup without a hitch & have run flawlessly.
Only update was My BIOS from 1001c to 1002A-U and the last (not newest) ASUS Probe.
Everything else off the Installation CDs.
I frankly don't understand the underlying 'drive', here, to always move to the latest update.. even on perfectly stable systems that are runnin' like rockets(?)!

Then.. I reckon I'm a oddball & ol' fart, so....

My WD drives run fast & fine in Cable Select or Master/Slave config.
My onboard Sound is Great.. no fuzz, buzz or snap, crackle & pops!
No BSODs, hangs, slow boots... I don't get it.

I'm an amateur!
I'm not a Network Admin.... or such.

Guess I'm jes' One Lucky bastid!
Or jes' lucky not to have bought into "XP"(?)!

[True]

I never uninstalled any drivers. Maybe that is everyones problem? All work well for me, minus non-ASPI support and HD spindown on restart (luckily I dont restart often)...

[Osm3um]

You may be a network admin, but you don't know NT very well. I am also a network admin and build systems for a living. All you had to do is choose "Last Known Good Configuration." Works everytime on driver issues. I had the same problem. Everytime I installed the new driver, my system would not boot. I recovered w/ "Last Known Good...." each time. Finally, I manually installed the drivers one at a time, then rebooted, then did a full install. I also deleted the Display driver files in the Display folder and replaced them with the drivers I wanted to use before manually kicking off the install.

See here for more details on what I did:
http://www.nforcershq.com/forum/viewtop ... 784#126784

But I wrangled w/ it for over an hour....not sure EXACTLY what I did to get it going, but it's going now.

Gekotek, I thought of alot of smart ass comments regarding your statement above.....but I am civil.....So in response...

I am a single IT person in an office with 10 W2k Server, 60 W2K workstations, E2K, 2xSPPS, 2xSQL, 2 sites/subnets, running AD, Citrix, and a firewall.

I did perform a last good, I did use safe mode, I repaired XP from a boot CD, etc. In the end it was screwed up. Post repair, I had mutiple driver issues, installations of software were not working correctly etc. So, I could live with a hacked up version of XP or gut it and start from scratch.

Then, I once again got it unbootable....so instead of wasting anymore time..I used Winternals admin pack to boot from CD and moved my data to another HD, booted into the raid controller and rebuilt my raid 0 config from scratch.

So, I would caution you about making judgemental calls about someone's abilities simply based on a question as to whether others have had troubles with a current driver.....

Thanks for you suggestion however,
Bob