Recommended Posts

Just to clarify something about the current times in the uk and redmond.............

PST = GMT -8

PDT = GMT -7 <----- Current Redmond Time Zone

GMT = 4PM

BST = GMT+1 <----- Current UK Time Zone

PST = 8AM

PDT = 9AM <----- Current Redmond Time

BST = 5PM <---- Current UK Time

PST = Pacific Standard Time

PDT = Pacific Daylight Time

BST = Britsh Summer Time = GMT +1

People are getting current UK time (BST) mixed up with GMT and wrongly stated it as the same. We go back to GMT on the 25th of October.

Edited by lee26
Just to clarify something about the current times in the uk and redmond.............

PST = GMT -8

PDT = GMT -7 <----- Current Redmond Time Zone

GMT = 4PM

BST = 5PM <----- Current UK Time Zone

PST = Pacific Standard Time

PDT = Pacific Daylight Time

BST = Britsh Summer Time = GMT +1

People are getting current UK time (BST) mixed up with GMT and wrongly stated it as the same. We go back to GMT on the 25th of October.

So, if release time is 1000 PDT, that is 1700 GMT and 1800 BST.

I'm wondering, is this just a kind of "MS haters" thing? People desperately wanting this product to fail?

In a word: NO. It's a very real bug that Microsoft managed to miss through the rushed beta and release candidate phases of development.

Nobody is hating on MS because of this. Windows 7 is going to be the product that drives Mac sales (already tiny) down by significant numbers. But we might have to wait for the first service pack before it's safe to use in the real world.

This seriously got 9 pages? I was think two pages max of people posting different times but 9 pages?

You know no one ever stays on topic especially when it comes to Win 7 release lol.

Download speeds will stink. Thank god i have installing office 2007 on all our staff machines here at the library to keep me busy while the slow download goes through . lol (we even have a 100/100 fiber line but with technet that doesnt help).

Just to clarify this is a great example of why Governments suck and just make life way to complicated. You are telling me we can't have a time system that never changes(as in DST not earth slow down changes) and is the same for everyone?

We're all on the same fu*kin planet!!! why can't we all have the same time!

Just to clarify something about the current times in the uk and redmond.............

PST = GMT -8

PDT = GMT -7 <----- Current Redmond Time Zone

GMT = 4PM

BST = 5PM <----- Current UK Time Zone

PST = Pacific Standard Time

PDT = Pacific Daylight Time

BST = Britsh Summer Time = GMT +1

People are getting current UK time (BST) mixed up with GMT and wrongly stated it as the same. We go back to GMT on the 25th of October.

In a word: NO. It's a very real bug that Microsoft managed to miss through the rushed beta and release candidate phases of development.

Nobody is hating on MS because of this. Windows 7 is going to be the product that drives Mac sales (already tiny) down by significant numbers. But we might have to wait for the first service pack before it's safe to use in the real world.

LOL MS have said its a issue with a driver a manufacturer supplied and it has occured very very very few times!

Its really really really not a huge deal.

In a word: NO. It's a very real bug that Microsoft managed to miss through the rushed beta and release candidate phases of development.

Nobody is hating on MS because of this. Windows 7 is going to be the product that drives Mac sales (already tiny) down by significant numbers. But we might have to wait for the first service pack before it's safe to use in the real world.

Rushed beta and RC? Do you know how many people have been using RC on their main systems since it was released? Do you know how many felt RC was good enough to be final and that MS was taking too long to finalize it? Do you think another beta or RC2 would have squashed this "BIG" bug, considering that fact that the RC has had one of the largest base of users/testers and no one reported this bug or the "severity" of it until now?you

If you aren't happy with it, don't use it or wait till a patch has been released. If a patch is never released because it's a driver issue as MS states, then you might want to rethink your stance.

Just to clarify this is a great example of why Governments suck and just make life way to complicated. You are telling me we can't have a time system that never changes(as in DST not earth slow down changes) and is the same for everyone?

We're all on the same fu*kin planet!!! why can't we all have the same time!

Just to clarify something about the current times in the uk and redmond.............

PST = GMT -8

PDT = GMT -7 <----- Current Redmond Time Zone

GMT = 4PM

BST = 5PM <----- Current UK Time Zone

PST = Pacific Standard Time

PDT = Pacific Daylight Time

BST = Britsh Summer Time = GMT +1

People are getting current UK time (BST) mixed up with GMT and wrongly stated it as the same. We go back to GMT on the 25th of October.

Go ahead and get on that, and good luck with that, in the mean time, it's called GMT.

In a word: NO. It's a very real bug that Microsoft managed to miss through the rushed beta and release candidate phases of development. "Millions of Windows 7 downloads and no one had this bug, seems like people don't use chkdsk anymore" :devil: maybe that should be the point here.

Nobody is hating on MS because of this. Windows 7 is going to be the product that drives Mac sales (already tiny) down by significant numbers. But we might have to wait for the first service pack before it's safe to use in the real world.

I used it on an external Hard drive and it crashed on Windows 2003 R2 64-bit after 8 hours of trying so Windows 7 chkdsk crashing isn't new.

Rushed beta and RC? Do you know how many people have been using RC on their main systems since it was released? Do you know how many felt RC was good enough to be final and that MS was taking too long to finalize it? Do you think another beta or RC2 would have squashed this "BIG" bug, considering that fact that the RC has had one of the largest base of users/testers and no one reported this bug or the severity of it until now?

+1

Okay, there's a (possible) bug with chkdsk. Or chipset drivers (I'm inclined to say the latter, since I, too, have been unable to duplicate this behavior on 3 different systems). Now, there ARE bugs I've seen on the RC that I'm still concerned about (likely also chipset-related), but this is not one of them.

I've seen no "showstopper".

Just to clarify this is a great example of why Governments suck and just make life way to complicated. You are telling me we can't have a time system that never changes(as in DST not earth slow down changes) and is the same for everyone?

We're all on the same fu*kin planet!!! why can't we all have the same time!

Ever heard of the "sun"? :rolleyes:

Funny I was refering to Daylight savings time (DST) and the stupid changes our Government keeps doing to us. Of all things shouldn't TIME be simple?

Go ahead and get on that, and good luck with that, in the mean time, it's called GMT.

but RC was 7100 and RTM is 7600 thats alot of bug fixes and changes.

+1

Okay, there's a (possible) bug with chkdsk. Or chipset drivers (I'm inclined to say the latter, since I, too, have been unable to duplicate this behavior on 3 different systems). Now, there ARE bugs I've seen on the RC that I'm still concerned about (likely also chipset-related), but this is not one of them.

I've seen no "showstopper".

If you aren't happy with it, don't use it or wait till a patch has been released. If a patch is never released because it's a driver issue as MS states, then you might want to rethink your stance.

Thanks. I won't use it until the issue is fixed. If Microsoft never fixes the bug, we won't ever use the OS in production.

Thanks. I won't use it until the issue is fixed. If Microsoft never fixes the bug, we won't ever use the OS in production.

and if it turns out to be a driver bug and not to do with MS?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Nobody is buying a PS5 only for playing Until Dawn 2. Their loss.
    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      232
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!