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

    • Apple reluctantly forces strict new age checks on Texas users starting today by Paul Hill Apple will begin enforcing the Texas Age Assurance Law (SB 2420) following a recent court ruling that lifted an injunction on SB 2420. Starting June 4 (today), Apple will enforce strict age-verification and parental-consent rules for new Apple accounts created in Texas. This move will affect children under 18 who go to download apps or attempt to make in-app purchases. Apple previously expressed privacy concerns related to this law, but compliance is now mandatory for the company, nevertheless. Apple will use several APIs to follow the law. Principally, the Declared Age Range API will fetch the specific user age bracket (Under 13, 13-15, 16-17, or 18+) and a verification method. The Significant Change API (PermissionKit) will trigger a system dialog for parental consent if an app gets a major update or an age-rating shift. There is also a new property type in StoreKit that allows developers to automatically check when their app’s age rating has changed on a user’s device and then use the Significant Change API to request parental consent. Finally, App Store Server Notifications can be configured to tell developers when a parent revokes consent, blocking app launches. To ensure they are ready for these changes, developers must immediately use Apple’s sandbox testing environment to validate these APIs in their apps. For any developers out there finding this to be inconvenient, get used to it. Other regions, such as Utah, Louisiana, and Brazil, are looking at, or have implemented, similar rules.
    • They should show the onedrive recycle bin in a searchable manner and on app not just on the website
    • You looking at a phone or something? On my 4K HDR monitor it is frikking spectacular.
    • The Surface Pro 7+ already has a USB C port which can be used for everything you mentioned, except for eGPUs. Meanwhile, microsoft have gotten rid of ALL of the following that are present in the Surface Pro 7+:
  • 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
      484
    2. 2
      PsYcHoKiLLa
      230
    3. 3
      Skyfrog
      72
    4. 4
      FloatingFatMan
      60
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!