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

    • ...but you're Johnny, from Australia?    
    • Glow 26.9 by Razvan Serea Glow provides detailed reporting on every hardware component in your computer, saving you valuable time typically spent searching for CPU, motherboard, RAM, graphics card, and other stats. With Glow, all the information is conveniently presented in one clean interface, allowing you to easily access and review the comprehensive hardware details of your system. Glow provides detailed information on various system aspects, including OS, motherboard, processor, memory, graphics card, storage, network, battery, drivers, and services. The well-organized format ensures easy access to the required information. You can export all the gathered data to a plain text file, facilitating sharing with others for troubleshooting purposes. No installation needed. Just decompress the archive, launch the executable, and access computer-related information. Glow runs on Windows 11 and Windows 10 64-bit versions. Glow 26.9 changelog: New Features The processor hardware detection engine has been significantly enhanced beyond traditional Intel and AMD architectures. Native support is now available for modern platforms such as Apple Silicon (M-Series) and the newly introduced NVIDIA Spark. In addition, all ARM-based processors can now be accurately distinguished between ARM32 and ARM64 architectures, providing precise hardware reporting. This marks a major milestone for Glow's hardware detection capabilities. The RAM manufacturer identification algorithm has been expanded. JEDEC vendor codes for popular brands such as Patriot, PNY, Team Group, GeIL, Lexar (Longsys), and Asgard/Gloway have been integrated into the database. This significantly reduces the likelihood of incorrect or "Unknown Manufacturer" results and improves overall hardware detection accuracy. New Public IP Address and Internet Service Provider (ISP) features have been added to the Network section. To ensure reliability, this information is retrieved from the trusted service ipwho.is. When Hiding Mode is enabled, no requests are sent and these features remain hidden, as they may expose sensitive information. The search engine used in the Installed Drivers, Installed Services, and Installed Applications sections has been enhanced. You can now perform more flexible and accurate searches using initials, partial matches, and loosely arranged character sequences. The TS Preloader loading bar has been rebuilt using our modern TS Custom Controls graphics library, developed entirely in-house. As a result of this infrastructure upgrade, the loading bar now features smooth rendering and rounded corners that align with the visual style of Windows 11. [TS Updater] A new validation algorithm has been added to check whether the target application is currently running before the update process begins. Bug Fixes Resolved a condition that could prevent TS Preloader from shutting down safely during rare application crash scenarios. Fixed a text alignment issue in the Network section affecting the display of DNS addresses. Alignment is now rendered correctly. [TS Updater] Fixed an issue that could prevent the updated application's executable "*.exe" file from being located after the update process. [TS Updater] Fixed a bug that could leave outdated "*.sha256" files in the application directory after an update. [TS Updater] Fixed a rare issue that could cause subfolders to be moved into the root directory after an update. [TS Updater] Fixed an issue during the first launch that could cause flickering and a temporary white window appearance due to Windows Defender interactions. Changes A small improvement has been made to the internet connectivity detection algorithm. Connectivity checks are now performed in the background with minimal impact on the user interface thread. The keyboard shortcuts in the top menu have been reorganized and simplified to provide a consistent experience across all Türkaysoft applications and to avoid potential conflicts with standard Windows shortcuts. The TS Preloader splash image has been updated with a Türkiye-themed stadium design to celebrate Türkiye's qualification for the 2026 FIFA World Cup—its first appearance in 24 years. Congratulations, Türkiye! The TS Custom Controls module has been updated to version 26.6, delivering improved stability and a more polished visual appearance. [TS Updater] The application icon has been redesigned to provide a more modern and refined look. Note: Always unzip the program before using it. Otherwise you may get an error. Download: Glow 26.9 | 1.8 MB (Open Source) Links: Glow Homepage | Screenshot | Github Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • DWARF mini review: the world's smallest smart telescope for night and day sky captures by Steven Parker DWARFLAB reached out to me asking if I was interested in checking out the DWARF mini, which is a portable astronomy telescope designed for amateur astronomers. Why do I say it's for amateurs? Well, for starters, it's not what you'd call "high end"; it's more of a professional-grade starting point for amateurs serious about capturing what's up there in our night and day skies. A typical amateur astronomer is most likely thousands of dollars deep into the hobby, and I will make no claims that this DWARF mini (at a fraction of the cost) could replace it all, okay? Well, if you read on, it will be clearer what I am trying to convey. Disclosure: DWARFLAB provided a free sample without any editorial input or review pre-approval. I have always been interested in looking up and observing the night sky. I see satellites crossing the sky above my garden most nights, and I am always looking at the moon. Yeah, I have a 200MP camera on my phone, but at 200X zoom, AI takes over and makes the pretty moon pictures that I snap, the DWARF mini does not, you get an actual true picture of what you can barely see with the naked eye. Before we start, let's share the highlights of the DWARF mini in bite-sized format: Pocket-Sized & Ultra-Lightweight Weighing just 1.85 lbs (840g), the DWARF mini easily fits into a backpack or large pocket. Its all-in-one, compact design makes it the ultimate grab-and-go digital telescope for hiking, camping, or traveling to dark-sky locations. Intuitive App Control & Built-in Sky Atlas Go from unboxing to your first shot in just 3 minutes! The DWARFLAB App provides a seamless experience with an interactive star map. Simply select your target and start exploring without the steep learning curve of traditional setups. Auto GOTO & 360° Pivot Freedom Enjoy pinpoint automated tracking with full 360° rotation. Powered by a high-sensitivity Sony IMX662 sensor (1/2.8-inch, 2.9μm pixels), it captures amazing, low-noise astro details, bringing faint nebulas and star clusters to life with stunning clarity. Pro-Level EQ Mode & Long Exposure Unlock advanced deep-space imaging with Equatorial (EQ) Mode. Supporting impressive single-frame exposures up to 90 seconds and featuring built-in light pollution filters, it easily cuts through city glow to reveal intricate celestial structures. Smart Cloud Processing & All-Ages Fun Effortlessly enhance your raw data with integrated cloud processing for professional-grade results. Perfect for beginners, kids, and adults, this telescope makes exploring and sharing the wonders of the universe an exciting, family-friendly adventure. The packaging is a pretty minimal affair with the outer box opening like a flap to reveal the plastic mould of the DWARF mini sitting in it. Below, the Sun filter, charging cable, cleaning cloth, and documentation can be found. DWARFLAB also provided a Mini Hydraulic Tripod ($89.99), and I highly recommend getting it if you plan on purchasing the DWARF mini, as it fully supports the motorized tracking feature of the telescope; plus, at 840g, the weight of the telescope, you will need a tripod that supports more than the weight of a smartphone anyway. What's in the box DWARF Mini Smart Telescope × 1 Sun Filter x 1 Type-C to Type-C Cord x 1 Cleaning Cloth x 1 User Guide With that out of the way, here are the full specs: DWARF mini Dimensions (DWH): 60.70 mm x 100.38 × 183.61 (2.39" x 3.95" x 7.23") Weight: 840g (1.85lbs) Aperture diameter: 30 mm (telephoto), 3.4 mm (wide angle) Image Sensor: SONY IMX662 1/2.8" (Telephoto) OmniVision OS02K10 1/2.8" (Wide-angle) Focal length: 150 mm (telephoto), 6.7 mm (wide-angle) Equivalent focal length: 1016 mm (telephoto), 45 mm (wide-angle) Shutter Speed: Tele - 1/10000-90s, Wide - 1/10000-30s Maximum exposure time: 90s (telephoto & wide-angle), Both in EQ mode Rotation range: Lens: 225°, Base: 360° Effective Pixels: 2.07M Maximum Resolution: 1920 × 1080 (Telephoto & Wide-angle) Built-in filters: Astro, Dark, Duo-Band (Telephoto), Astro (Wide-angle) Output: JPG, FITS, TIFF, MP4 Shooting Mode: Photos, Videos, Astronomy, Burst Shooting, Time-lapse Photography Storage: 64 GB Battery: Built-in 7000 mAh, supports external USB charging Charging Port: Type-C NPU: 1 TOPS Features: WiFi, NFC NFC One-Touch Connection Astronomy Post-Processing/Appointment Shooting/Astronomy Mosaic Wi-Fi Transmission Range: 15m (open environment) Color: Black Compatibility: iOS & Android smartphones/tablets Warranty: 2-years (24-months) MSRP: $399 Design Charge port On/off button Lens On the DWARF mini itself, it is a pretty minimal affair. On one side, there is a Type-C USB port to charge the non-removable 7000 mAh battery, and on the other side, a large button to power on or off the telescope. The button is flanked by an LED that is green when connected via the DWARFLAB app, or lights up red when being powered off. Below the button, there are four LEDs that indicate battery power. The DWARF mini does not have any sharp edges as all sides are rounded off; it has a good heft to it, but the weight of it feels quite balanced in the hand, so it isn't top or bottom-heavy. On the front there is the DWARFLAB logo which is quite small and there are no other markings on it. The tripod offers full 360° rotation of the motorized base, which allows for tracking for the time-lapse mode, but also for the 90-second captures of nearer objects in the sky, such as the Sun or the moon. Usage To get started, simply power on the DWARF mini and open the DWARFLAB app, tap on Connect, and it will scan for the DWARF mini over the Wi-Fi network. The device supports both 2.4 GHz and 5 GHz Wi-Fi, as well as Bluetooth for discovery, so connection issues were minimal in my experience with it. As previously noted in the specs, the DWARF mini will stay connected with a phone or tablet up to 15 meters in an open environment, such as a backyard. Lighting status Powering on: The green circular light will rotate and breathe in turn Powering off: The red circular light is gradually extinguished Connecting: Green light strip rotating Connected: Green light strip solid/always on 4 lights 1= 0-25%, 2= 25-50%, 3= 50-75%, 4= 75-100% battery power To view the full lighting status, such as tracking mode and connection failure, you can check the user guide on the official DWARFLAB page. DWARFLAB app Above, you can see the steps undertaken to connect the DWARFLAB app to my Galaxy S26 Ultra. Weirdly, I got an alert that a firmware update failed to get uploaded to the DWARF mini the first time, but upon retrying, it worked. Then place the DWARF mini outside, make sure your smartphone or tablet is connected to it, and then head back inside, because you can manage it from the comfort of your home. Simply enter the Atlas tab in the app and search for what you want to capture, and then tap on the camera icon; the DWARF mini will then attempt to track the object and give you a live view right on your connected device. Results I've had the DWARF mini since April, but even though my garden is south-facing, I had a lot of trouble trying to capture a good image of the moon. In the end, it was possible after I took it with me on a trip to my parents in Southend, UK, at the end of May. Here is a capture of the moon, resulting from 20 stacked images over a 90-second exposure. What you are seeing here is not AI-assisted. A good example of what I mean is the latest flagships with their 200MP cameras claiming to capture things like closeups of the moon, and while they are not as good as the above example on the DWARF mini, the resulting image on smartphones is actually AI-assisted above 30X zoom. Here is an example of a similar shot at the moon at 200X zoom using an HONOR Magic8 Pro. The difference is clear. Next, here we have a shot of the daytime moon. Here is a shot of Arcturus, the red giant star, which is the fourth brightest in the night sky. As previously mentioned, it could be a bit clearer, but clouds passing in front of it muddied the shot a bit. The Sun The DWARF mini also ships with a sun filter, meaning you can take great shots of the sun as well. Tracking Sun Resulting (stacked) shot Live zoom The pictures themselves are limited to Full HD, and some of the examples actually came out in HD (1280x720), but this is because the standard telescopic result is in 720p while "Wide" is in 1080p. Above you can see how in the app the Sun is tracked, the resulting capture, and Live zoom. I have only scratched the surface of what is possible with this telescope; I found several examples online of shots of the Milky Way, among others, such as nebulae and galaxies. All of this requires patience and knowledge, although if you know what you are looking for, simply enter it in the Atlas tab in the DWARFLAB app, tap the camera icon, and the telescope will attempt to track it. Conclusion The good The DWARF mini definitely places itself in a price point that makes astrology accessible to anyone looking to get started in the hobby. Say you want to have a closer look at the moon, simply enter it in the Atlas, and the Live view also lets you zoom in and snap pictures. The bad Some issues I came across while operating the DWARF mini were that it sometimes failed to connect unless I held my smartphone right next to it, and finding and tracking sometimes took several attempts to get it calibrated. I discovered that it helped if I sort of positioned and pointed the telescope in the general area it was supposed to detect, but this obviously wouldn't work with objects you can't see with the naked eye; more testing is required for that. Another bit of advice is to ensure that the lens is clean. While making the examples of live zooming on the sun, I discovered that the telescope lens and sun filter were not completely clean, and only after cleaning with a microfiber cloth was I able to get a decent shot of the sun. Where to buy and a coupon Okay, $399 is not cheap for a side hobby, but nor is a $1,500 smartphone flagship that you'll most likely have for a couple of years. This is a one-time entrance into astrology, and it won't become obsolete in one year like a smartphone. It's a thumbs up from me. The DWARF mini is available to buy right now in the U.S. and U.K. at the links below. DWARF mini for $399 on the official site DWARF mini for $399 on Amazon U.S. Use the NEOWIN5OFF coupon code for an additional 5% off at checkout (expires June 21) As an Amazon Associate, I earn from qualifying purchases.
    • Adobe Acrobat Reader Dis Continued
    • The name, you mean? If so, it's actually the objects common name. There's another one called NGC 7293 which is also known as Helix Nebula (because we're looking at a helix structure top down) but other times also known as the Eye of God. You'll understand when you see it
  • 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
      504
    2. 2
      PsYcHoKiLLa
      270
    3. 3
      Skyfrog
      75
    4. 4
      +Edouard
      75
    5. 5
      FloatingFatMan
      70
  • Tell a friend

    Love Neowin? Tell a friend!