Windows Vista Beta 2 Available for Download

[MyndFyre]

x86] link=topic=6145.msg73694#msg73694 date=1150047953]
Or maybe..just maybe..it's your hardware? You know when it works for millions and millions and not for a select few..then can we question it being the hardware?

Therein lies the problem. What hardware is it? Linux has yet to error out on me or blame any problems on hardware.

Windows would not tell me either. It would just restart.

There is the difference. Linux doesn't. I think Linux can handle my hardware better. ;)

See, this is just you not understanding how to diagnose XP.  There is a boot-up option menu called "Disable automatic restart."  This is also an option in the System Properties dialog (Advanced, Startup and Recovery, Automatically Restart).  I arm myself with WinDbg (free) and a full kernel dump (as opposed to a minidump, which is the default option for XP Home/Pro), and find out very quickly what the problem is.  This is an example of your ignorance causing you to blame Windows as problematic as opposed to your driver.  You can't determine which driver is the problem because you're not educated enough.

Athlon 2200+
768 MB RAM
Geforce 5600
Is that good enough? It's my dad's computer that's all I can remember off the top of my head.

That should be enough.  Aero scales back automatically and should disable glass (transparency) with that I believe.

[Warrior]

Ok... I think I got to not crash... here's a REAL SS from an actual user. Not those professional SS that Warrior posts :D

Ouch that Vista is crying.
Anyhow, those SSes are taken from someone doing a review (He has badass hardware though, like 3GB of ram, a killer processor and a 7900GTX)

[Ergot]

x86] link=topic=6145.msg73909#msg73909 date=1150103609]

Athlon 2200+
768 MB RAM
Geforce 5600
Is that good enough? It's my dad's computer that's all I can remember off the top of my head.

That should be enough.  Aero scales back automatically and should disable glass (transparency) with that I believe.

Too bad it didn't eh?

[deadly7]

They've clearly managed the technology to support GPU rendered graphics.  Why the hell would the choose to not use it for less complicated themes?  "Sure!  Let's load the graphics card with a bunch of shit, but then not use it at all when the user switches to a simpler theme!"  Think about what you're proposing...

It IS Microsoft, and I have been royally screwed by them before.  I wouldn't doubt that at all.

[Warrior]

They've clearly managed the technology to support GPU rendered graphics.  Why the hell would the choose to not use it for less complicated themes?  "Sure!  Let's load the graphics card with a bunch of shit, but then not use it at all when the user switches to a simpler theme!"  Think about what you're proposing...

It IS Microsoft, and I have been royally screwed by them before.  I wouldn't doubt that at all.

I give up.

[Warrior]

Aero is built on the new desktop composition engine called Desktop Window Manager, adding support for 3D graphics, translucency, window animation and other visual effects. This mode is also known as Aero Glass.

    * Intended for mainstream and high-end graphics cards.
    * 64 MB of graphics memory recommended for 1024x768, 128 MB for 1600x1200+.
    * At least 32 bits per pixel.
    * 3D hardware acceleration with capabilities equal to DirectX 9.0c.
    * A memory bandwidth of 2 GB/s is recommended.
    * Capable of drawing ~1.5 M triangles / second, one window being ~150 triangles.
    * A graphics card that uses AGP 8X or PCI Express x16 bus.
    * Windows Display Driver Model (WDDM) Drivers.

http://en.wikipedia.org/wiki/Windows_Vista#Graphics

[MyndFyre]

I have some installation screenshots:

Dynamic update for setup?
Install type: upgrade or custom?
Install to which partition?
Installing...

I just want to know: why does MS feel that it's important to make a fucking ISO image at 1mb/s of copying from the DVD in order to install?  WTF?

[Newby]

Why do you need to be connected to install? That's fucking stupid. What if you are mass deploying and all of them accessing the internet at once will cause world chaos?

x86] link=topic=6145.msg73909#msg73909 date=1150103609]
See, this is just you not understanding how to diagnose XP.  There is a boot-up option menu called "Disable automatic restart."  This is also an option in the System Properties dialog (Advanced, Startup and Recovery, Automatically Restart).  I arm myself with WinDbg (free) and a full kernel dump (as opposed to a minidump, which is the default option for XP Home/Pro), and find out very quickly what the problem is.  This is an example of your ignorance causing you to blame Windows as problematic as opposed to your driver.  You can't determine which driver is the problem because you're not educated enough.

I realize you can disable it. I don't think I could read kernel dumps so eh?

[MyndFyre]

Why do you need to be connected to install? That's fucking stupid. What if you are mass deploying and all of them accessing the internet at once will cause world chaos?

x86] link=topic=6145.msg73909#msg73909 date=1150103609]
See, this is just you not understanding how to diagnose XP.  There is a boot-up option menu called "Disable automatic restart."  This is also an option in the System Properties dialog (Advanced, Startup and Recovery, Automatically Restart).  I arm myself with WinDbg (free) and a full kernel dump (as opposed to a minidump, which is the default option for XP Home/Pro), and find out very quickly what the problem is.  This is an example of your ignorance causing you to blame Windows as problematic as opposed to your driver.  You can't determine which driver is the problem because you're not educated enough.

I realize you can disable it. I don't think I could read kernel dumps so eh?

Holy fucking shit.  It's SO EASY.

Windbg - Open Crash Dump (find the file, usually Windows\MEMORY.DMP)
!analyze -v

It tells you the faulting module 98% of the time.

GFG

---

As for why you need to be connected for the install, it's to download dynamic updates.  If you're mass-deploying you'd probably use the preinstallation environment or something similar.

[Newby]

x86] link=topic=6145.msg74157#msg74157 date=1150170032]
Holy fucking shit.  It's SO EASY.

Windbg - Open Crash Dump (find the file, usually Windows\MEMORY.DMP)
!analyze -v

It tells you the faulting module 98% of the time.

GFG

Well EXCUSE ME for not having any experience (ok fine, damn near none, I tried debugging a game once to hack it :P) with WinDbg.

Maybe someday I'll try that. Heh. I'd swear it was my sound card, though.

x86] link=topic=6145.msg74157#msg74157 date=1150170032]
As for why you need to be connected for the install, it's to download dynamic updates.  If you're mass-deploying you'd probably use the preinstallation environment or something similar.

Hooray! Kill M$'s bandwidth!

[MyndFyre]

Ahh, here we are.  This is my desktop:

[Newby]

Now I've got your real name, and I can hunt you down and kill you!

(At least I am not the only one who uses their full name for their login name on Windows... heh.)

[MyndFyre]

Now I've got your real name, and I can hunt you down and kill you!

(At least I am not the only one who uses their full name for their login name on Windows... heh.)

James T. Kirk is not your real name, Newby.  :P

[Newby]

:(.