Recommended Posts

Drivers should not be at beta stage by now. It goes RTM in a months time for heavens sake!

if the operating system still has 1400+ bugs, what makes you think that most of those bugs aren't affecting drivers? you can't have stable drivers until you have a final os.

You really can't expect every vendor to release optimized drivers for every card for a pre-release OS. I'd expect the final driver package to be one of the last components to get signed off on.

You'll want to go troll over to your vendor's support structure and rant there, if you want to place the "blame" where it exists.

There's a good reason why beta software is not often released to the general public, every self-proclaimed "power user" starts predicting the end of the world.

Uh, when we are less than one month away from RTM, I expect things to be pretty well finished. Are they supposed to wait until the first day of RTM to release a proper driver, so we can all be the testers on a final product, instead of during beta when such things are supposed to be tested?

If we were in early beta and there were no drivers, it would be somewhat more acceptable. A month from final product? Drivers should be top notch and in tons of peoples hands testing them for the final release.

What are you going to say when you have Vista RTM and your video driver is a buggy piece of crap because nvidia didn't get around to releasing it beforehand so it could be TESTED during TESTING STAGE? Then people will complain.

It's microsoft's fault NVIDIA don't make correct working driveres. DAMN YOU MICROSOFT, DAMN YOU FOR NOT LETTING NVIDIA MAKE GOOD DRIVERS!

</Sarcastic>

anyway, it's up to the hardware makers to support in drivers, not microsoft :)

True, much of the blame lies on nvidia/ATI, but it's also up to Microsoft to ride these guys and tell them "Hey, we are damn near finished with this thing. Get a working driver out there so people can test it before we release!"

Some of you guys act like as long as the driver is out the day of release that's acceptable, but we aren't supposed to be beta testing SLI support for the first time after beta is over.

I didn't have the privilege of a XP-capable computer back in 2001, so how were the drivers like right before October 25, 2001?

In respect to drivers, it's acceptable for my system configuration. The Vista ForceWare drivers are clearly unoptimized compared to XP, and Creative's drivers like to pop up a 'Busted App' message on first install (nice message, lmao). I also had minor problems figuring out how to get my Promise SATA controller to work, and my Canon scanner. Both the controller and scanner installed fine with XP drivers.

True, much of the blame lies on nvidia/ATI, but it's also up to Microsoft to ride these guys and tell them "Hey, we are damn near finished with this thing. Get a working driver out there so people can test it before we release!"

Some of you guys act like as long as the driver is out the day of release that's acceptable, but we aren't supposed to be beta testing SLI support for the first time after beta is over.

ye I agree very much with your point there but I think MS does tell them but somehow NVIDIA/ATI/Creative won't release a newer driver more often. For Creative, as some guy mentioned in a post above, MS change the whole sound system over and over I think they get a bit tired with rewriting stuff for every build :p

Oh well, let's wait for tomorrow :D

What I hope gets fixed is:

- Internet connection drops (Common problem on NForceX)

- cdrom.sys fixes so daemon-tools/clonedrive work again (without hacks)

- More compatibility for certain new GFX cards

- Opening recording devices (right mouseclick on speaker->Recording Devices) no more error

Vista has changed the sound system over and over again on Creative, to the point now where it is RADICALLY different than what it is in XP. Drivers have to be totally redesigned, and made to work with a product that was reverse engineered to work with XP Drivers and privelages thereof.

Where did you get this bull**** from. MS hasn't changed the sound system "over and over". They made a new sound stack and that's it. Sure maybe the API has had some minor changes since the sound stack was introduced but the new stack has been well documented for a long time now (just read Larry "MS's audio guru" Ostermans blog). After the API and stack was finalized they have made bug fixes and little else. Nothing get's rewritten multiple times over the course of a program as big as Windows Vista.

It's true, since the sound stack is entirely new, that Creative might be cut a little slack but hell, most of the Video Driver was changed as well and you don't seem Nvidia and Ati slackin as much. At least their drivers aren't timebombed and only 50% functional (if you get them to function at all) like Creative's.

Edit: Quoted the wrong person at first.

Interesting line on the RC2 download page. Goes with what is being said about 5744 being RC2 in name only.

"Please note: This build may not have the same level of support or servicing via Windows Update as RC1"

If it were a true RC2 build, would it say that?

Well "supposedly", from everything that was said before, Microsoft was supposed to support RC1 with lots of patches, updates, fixes, through Windows Update for some time to come. However, I have yet to see this. There haven't really been any major fixes/updates to RC1, except for 5728 :p

Interesting line on the RC2 download page. Goes with what is being said about 5744 being RC2 in name only.

"Please note: This build may not have the same level of support or servicing via Windows Update as RC1"

If it were a true RC2 build, would it say that?

I think thats just there as a precaution from MS's part. RC1 was a full public beta, with a lot of people downloading it (a lot of those, probably shouldn't be messing with beta OS's). So they have to provide a fair amount of support. But with this RC2, its only gonna be available to a limited amount of the public, so its less chance of the idiots getting it.

Also, I think all the interim builds made available to the public have said that.

Where did you get this bull**** from. MS hasn't changed the sound system "over and over". They made a new sound stack and that's it. Sure maybe the API has had some minor changes since the sound stack was introduced but the new stack has been well documented for a long time now (just read Larry "MS's audio guru" Ostermans blog). After the API and stack was finalized they have made bug fixes and little else. Nothing get's rewritten multiple times over the course of a program as big as Windows Vista.

It's true, since the sound stack is entirely new, that Creative might be cut a little slack but hell, most of the Video Driver was changed as well and you don't seem Nvidia and Ati slackin as much. At least their drivers aren't timebombed and only 50% functional (if you get them to function at all) like Creative's.

Edit: Quoted the wrong person at first.

ROFL i like how you say "Where did you get this BS" and then you pretty much state my point for me, Thanks!

Why would anyone buy this knowing there are 500 bugs still present (if that is the case)? Would the same people buy a TV knowing that it may shut off at any minute? Or a video/DVD recorder that didn't always record the full program.

I know all software has bugs, but 500 known bugs at release is a bit much.

Why would anyone buy this knowing there are 500 bugs still present (if that is the case)? Would the same people buy a TV knowing that it may shut off at any minute? Or a video/DVD recorder that didn't always record the full program.

I know all software has bugs, but 500 known bugs at release is a bit much.

500 is a target number (which I agree is a little scary), so we don't know what the actual number of known bugs will be at release. And how many known bugs do you think XP had at RTM? I think that if XP has taught us anything, it's that we should be worried about the unknown number of bugs/security holes that might be found in Vista post-RTM.

Why would anyone buy this knowing there are 500 bugs still present (if that is the case)? Would the same people buy a TV knowing that it may shut off at any minute? Or a video/DVD recorder that didn't always record the full program.

I know all software has bugs, but 500 known bugs at release is a bit much.

Actually, for an operating system, 500 bugs is very few. Do you realize how long Vista would be in testing if they had to iron out every last bug. That is almost impossible, I know because I am a software developer. You can't expect to get all of the bugs out and still get the product out before 2008 or 2009. Honestly, we would be waiting that long in this case if they had to work out every bug. It is not feasable from a business standpoint as long as the bugs are not serious. :)

ROFL i like how you say "Where did you get this BS" and then you pretty much state my point for me, Thanks!

How exactly did i state your point? Minor API changes and bugfixes are not considered "changing the audio stack over and over" like you said. It's been changed exactly once. And i dear say that Creative has had access to the new audio driver API's/requirements for over a year now. After that, if Creative can't keep up with minor API changes and bugfixes, they should simply stop making Windows hardware.

Although it seems pretty obvious to me that they simply didn't give a **** and didn't start creating these drivers until pretty recently. The state of the Creative drivers is horrendous compared to pretty much all other drivers especially considering the marketshare they have. Creative simply dropped the ball on this one big-time and the blame is definitely not Microsoft's. Hell, they can't even release proper drivers for XP either.

Why would anyone buy this knowing there are 500 bugs still present (if that is the case)? Would the same people buy a TV knowing that it may shut off at any minute? Or a video/DVD recorder that didn't always record the full program.

I know all software has bugs, but 500 known bugs at release is a bit much.

They aren't showstoppers, they're the 500 most obscure bugs found (as in problems in localization, etc), not something thats going to bring down your system. I'm sure Windows XP, Server 2003, and 2000 all had a similar target - you have to ship the software eventually. If you didn't set a realistic goal (see Longhorn project pre-2004) you'll never get there.

And if you look at it this way - there's about 50,000,000 lines of code in Vista. On average, thats a bug every 100,000 lines of code. Pretty good I'd say. A hell of a lot better average than most software out there.

Well "supposedly", from everything that was said before, Microsoft was supposed to support RC1 with lots of patches, updates, fixes, through Windows Update for some time to come. However, I have yet to see this. There haven't really been any major fixes/updates to RC1, except for 5728 :p

rc1-betawuphis.PNG

Uh, when we are less than one month away from RTM, I expect things to be pretty well finished. Are they supposed to wait until the first day of RTM to release a proper driver, so we can all be the testers on a final product, instead of during beta when such things are supposed to be tested?

If you ask the hardware people, they expect you to do exactly that. Why should they be required to hit a moving target, just so you can play with it unofficially. This is a beta of an OS, if you want to be a beta hardware tester, once again I'd suggest you go bug the vendor. "real" testers know the difference between hardware driver issues and OS bugs, and if there's a problem with one driver, they go to a known working one and continue development of the OS.

IOW, stick with VERY common hardware for pre-release OS testing.

If we were in early beta and there were no drivers, it would be somewhat more acceptable. A month from final product? Drivers should be top notch and in tons of peoples hands testing them for the final release.
The common one's are, the less common and rare hardware should get less attention, and does. If your hardware is new enough and common enough, you can bet there'll be decent drivers already in the works. Once again, the blame isn't Microsoft's. I encourage you to contact your hardware vendors and question them yourself, then feel free to post whatever you get back for a response.
True, much of the blame lies on nvidia/ATI, but it's also up to Microsoft to ride these guys and tell them "Hey, we are damn near finished with this thing. Get a working driver out there so people can test it before we release!"
ALL of the blame lies with the hardware vendor. If everyone here can get a decently current copy, so can they. It's not up to Microsoft to ride the vendors, it's your job! Vote with your feet and your wallet, or go pro-active and kick up a fuss, but not here!
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • It's amazing that anyone still uses this bloated trash.
    • @Sayan...I have defended you at various points as I hope you know. This headline however is utter trash...shame on you sir!
    • An actual cosmic "Eye of Sauron" had been looking straight at us all along by Sayan Sen Image by Kovin P. Vasquez via Pexels | Not representative An international team of researchers has solved a long-standing mystery surrounding a distant blazar known as PKS 1424+240, helping explain why it produces some of the brightest high-energy gamma rays and cosmic neutrinos ever observed despite appearing to have a relatively slow-moving jet. The findings were published on June 6 in Astronomy & Astrophysics Letters. The study addresses a broader challenge in astrophysics: understanding how extreme cosmic objects accelerate particles to very high energies and produce very high-energy (VHE) photons and neutrinos. PKS 1424+240 is located billions of light-years from Earth. It has attracted attention for years because it is both a powerful source of VHE gamma rays and the brightest known neutrino-emitting blazar in the sky, according to observations by the IceCube Neutrino Observatory. It is also associated with one of the strongest peaks in IceCube's nine-year neutrino sky map A blazar is a type of active galactic nucleus powered by a supermassive black hole that pulls in surrounding matter and launches jets of plasma moving close to the speed of light. What makes blazars unique is their orientation. One of their jets points almost directly toward Earth, making them appear exceptionally bright across the electromagnetic spectrum and allowing scientists to study some of the most extreme physical processes in the Universe. The scientists exclaimed it's like the 'Eye of Sauron' in deep space. Usually, the brightest gamma-ray-emitting blazars are expected to have jets that appear to move very quickly. However, radio observations of PKS 1424+240 suggested that its jet was moving much more slowly, creating a contradiction that became part of a long-running problem known as the "Doppler factor crisis." To investigate, researchers analyzed 15 years of observations from the Very Long Baseline Array (VLBA), a network of 10 radio antennas spread across the continental United States, Hawaii and St. Croix. Using a technique called Very Long Baseline Interferometry (VLBI), astronomers combine signals from widely separated radio telescopes to create a virtual Earth-sized telescope capable of revealing extremely fine details. The team combined 42 polarization-sensitive radio images collected between 2009 and 2025, creating a much deeper and more detailed view of the jet than had previously been possible. The observations were carried out as part of MOJAVE (Monitoring Of Jets in Active galactic nuclei with VLBA Experiments), a long-running program that studies the brightness, polarization and magnetic field structures of jets produced by active galaxies. The project aims to better understand how activity near supermassive black holes is linked to high-energy radiation and neutrino emission. “When we reconstructed the image, it looked absolutely stunning,” said Yuri Kovalev, lead author of the study and Principal Investigator of the European Research Council-funded MuSES project at the Max Planck Institute for Radio Astronomy. “We have never seen anything quite like it — a near-perfect toroidal magnetic field with a jet, pointing straight at us.” The image revealed an unusual geometry. The researchers found that Earth lies almost directly in line with the jet, with a viewing angle of less than 0.6 degrees. In simple terms, astronomers are looking almost straight down the jet. This turned out to be the key to the mystery. Because the jet is aimed almost directly at Earth, a relativistic effect called Doppler boosting dramatically increases its apparent brightness. The study found that this effect boosts the emission by a factor of about 30 while also making the jet appear slower than it actually is. “This alignment causes a boost in brightness by a factor of 30 or more,” said Jack Livingston, a co-author at the Max Planck Institute for Radio Astronomy. “At the same time, the jet appears to move slowly due to projection effects — a classic optical illusion.” The nearly head-on view also gave scientists a rare look at the jet's magnetic field. Using polarized radio signals, they detected a clear toroidal, or doughnut-shaped, magnetic field component. The observations suggest the jet carries an electric current and that its magnetic field helps launch, shape and stabilize the flow of plasma. Researchers believe this magnetic structure may also play a key role in accelerating particles to energies high enough to produce both gamma rays and neutrinos. “Solving this puzzle confirms that active galactic nuclei with supermassive black holes are not only powerful accelerators of electrons, but also of protons — the origin of the observed high-energy neutrinos,” Kovalev said. The research was conducted under the MuSES (Multi-messenger Studies of Energetic Sources) project, which investigates how active galactic nuclei accelerate particles and generate different cosmic signals, including light and neutrinos. Scientists say understanding how protons are accelerated and linked to neutrino production remains one of the major unanswered questions in astrophysics. The findings help explain why some blazars can appear to have slow jets while still producing extremely bright high-energy emissions. More broadly, the study strengthens the link between relativistic jets, magnetic fields, gamma rays and high-energy neutrinos. Researchers say the results provide new clues about how some of the Universe's most powerful natural particle accelerators work and offer important insights for multimessenger astronomy, which combines different types of cosmic signals to study extreme events in space. Source: European Research Council, EDP Sciences This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Gotenks98 is right... Outlook (new) is absolute trash. Doesn't Mozilla have an Enterprise Version of Firebird?
  • Recent Achievements

    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
    • Reacting Well
      X-No-file earned a badge
      Reacting Well
    • One Month Later
      pestcontrol46 earned a badge
      One Month Later
    • Week One Done
      pestcontrol46 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      510
    2. 2
      PsYcHoKiLLa
      273
    3. 3
      Skyfrog
      75
    4. 4
      +Edouard
      72
    5. 5
      FloatingFatMan
      69
  • Tell a friend

    Love Neowin? Tell a friend!