Windows 7 Beta
Windows 7 Beta
Anyone else trying this out? I'm downloading it right now.
http://www.microsoft.com/windows/windows-7/default.aspx
http://www.microsoft.com/windows/windows-7/default.aspx
What specs do you need to run Windows 7? I'm in the market for a new laptop (I'm leaning towards a Satellite U400/M00 (Link: http://www.cybershop.net.au/Notebooks/U400M00.shtml) but I really don't want to be stuck with Vista - if the machine won't run it, then I'll get something else instead (suggestions welcome Budget is circa $1,400 AU.)
As far as i know, it requires the same as Windows Vista (and according to reviews, even with the same hardware it runs better than Vista).
[Pumo software main website] - Pumo Mines current release: v1.1 (12 Levels) -- [Official R.a.M. Land's website] (You can find my music here)
- Aus-RED-5
- DBB Friend
- Posts: 1604
- Joined: Fri Apr 23, 2004 7:27 am
- Location: Adelaide, South Australia
- Contact:
Minimum recommended specs call for:
1 GHz 32-bit or 64-bit processor
1 GB of system memory
16 GB of available disk space
Support for DirectX 9 graphics with 128 MB memory (to enable the Aero theme)
DVD-R/W Drive
Internet access (to download the Beta and get updates)
And yes, like anything tech-related, these specs could change.
...................................................
Watch the calendar. The Beta expires on August 1, 2009. To continue using your PC, please be prepared to reinstall a prior version of Windows or a subsequent release of Windows 7 before the expiration date.
- captain_twinkie
- DBB Ace
- Posts: 222
- Joined: Sun Mar 07, 2004 3:35 pm
- Location: Orem, Utah
Re:
That's unfortunate. I think after the debacle that Vista became, MS can NOT afford to F this one up.Sniper wrote:The interface updates have been made in the wrong direction.
- CDN_Merlin
- DBB_Master
- Posts: 9781
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Capital Of Canada
Re:
Thanks Red. Any word on how well older programs run on it? the most recent software I run was released in 2003 (Acrobat 6.0)Aus-RED-5 wrote:Minimum recommended specs call for:
1 GHz 32-bit or 64-bit processor
1 GB of system memory
16 GB of available disk space
Support for DirectX 9 graphics with 128 MB memory (to enable the Aero theme)
DVD-R/W Drive
Internet access (to download the Beta and get updates)
And yes, like anything tech-related, these specs could change.
...................................................
Watch the calendar. The Beta expires on August 1, 2009. To continue using your PC, please be prepared to reinstall a prior version of Windows or a subsequent release of Windows 7 before the expiration date.
Re:
Correction: It's the same OS, but with changes.Spidey wrote:Just Great, another OS for everyone to whine about.
- SirWinner
- DBB Fleet Admiral
- Posts: 2700
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Oklahoma City, Oklahoma, United States of America
- Contact:
Not quite correct.d3jake wrote:Correction: It's the same OS, but with changes.
The Windows Vista "Virgin Stack" problem was a major step backwards... Instead of taking a known and very much working copy of the "Windows XP Stack" they reintroduced issues that had been resolved already in Windows XP!
- See http://www.grc.com/securitynow.htm (Episode #51 for August 3, 2006)
They really messed up a lot of core processes and many other things in Windows Vista... See my note below about recompiling programs to run under Windows Vista!
Some of the major issues were fixed with Service Pack 1 but not the issue where programs that work great under Windows XP ... may not won't work properly or at all in Windows Vista!
---
Oh really?Capm wrote:Now IS the time to whine about it, while it is in BETA. So they can change it
I have too many things to handle at the moment at work concerning updating my existing software products to work on Vista PC's.
First, I have to take those existing program's source code for each and upgrade it to use Microsoft Visual Studio 2005 or higher then use an external step to modify that EXE to bypass DEP (Data Execution Prevention) just to get the SAME EXE's that work without an issue on Windows XP to work on Windows Vista.
See: "editbin /nxcompat:no " + (full path and executable name)
- This disables the DEP check in all versions of Windows.
See these 2 links:
http://msdn.microsoft.com/en-us/library ... S.80).aspx
- Copy the WHOLE line above for the first link!
http://blogs.msdn.com/ed_maurer/archive ... piler.aspx
Secondly, One of the issues that I have to deal with is a problem in Windows Vista where my program checks for conflicts with other programs in one of my suite of programs to prevent: (1) Interoperability issues between the programs; AND (2) more than ONE copy of the same program executable from running at the same time.
If either condition above is detected, then my programs' startup code will automatically unloading the program.
This code has to be slightly changed to work properly in Windows Vista.
---
If I get the time and a new Hard Drive for my Home PC, perhaps I could check "Windows 7" out later!
Too many programs that work great on Windows XP refuse to work on Windows Vista now... who is to say whether our favorite programs that work on Windows XP will work on code name "Windows 7"?
If my current "games" (such as Descent, Freespace, etc) programs don't work on "Windows 7" then "Windows XP" will be on my Home PC for a long time into the future!
*** Sigh! ***
---
I wrote off any hope of playing Halo 2 for the PC since it literally FORCED people to upgrade to Windows Vista just to play that ONE game... Gee Microsoft... NO !@#$%^&* (1-8 on the keyboard in uppercase) thanks!
- SirWinner
- DBB Fleet Admiral
- Posts: 2700
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Oklahoma City, Oklahoma, United States of America
- Contact:
Re:
Halo 2 was just one reason that I didn't want to upgrade to Windows Vista!Sirius wrote:Halo 2 isn't really worth upgrading for anyway, from what I understand.
It kind of rings alarm bells if you're having to disable data execution prevention in the first place, by the way. Wouldn't this mean the code is insecure?
As to the DEP disabling, there is NOTHING in my code that executes any data... that is why I was confused as to WHY DEP intercepts my programs and won't let them run in Windows Vista!
The issue ISN'T DEP but something deep inside of Windows Vista!
The same programs don't have DEP issues in Windows XP!
- Warlock
- DBB 3D Artist
- Posts: 3370
- Joined: Wed May 12, 1999 2:01 am
- Location: Midland, Tx, U.S.
- Contact:
I got it installed on my 2nd computer and I'm liking it so far. Had some driver issues but with a little work I got the XP drivers to fix the problem.
One issue I'm have is with windows update not liking my WSUS server and causeing exploare to crash but then I just log on to the local account and not the domain account it runs fine so it could b that I'm still running WSUS 2.0 and not 3.1 but eh that's not a show stopper for me cause how many people run a WSUS server at there house.
One issue I'm have is with windows update not liking my WSUS server and causeing exploare to crash but then I just log on to the local account and not the domain account it runs fine so it could b that I'm still running WSUS 2.0 and not 3.1 but eh that's not a show stopper for me cause how many people run a WSUS server at there house.
Re:
yup. quite right there. pay over $100 to play a game that's already 2 years old (at the time)?? I think not. I echo the other responces already made in regards to this.Sirius wrote:Halo 2 isn't really worth upgrading for anyway, from what I understand.
- Foil
- DBB Material Defender
- Posts: 4900
- Joined: Tue Nov 23, 2004 3:31 pm
- Location: Denver, Colorado, USA
- Contact:
I'm with a couple of others here - I've been using Vista on both a laptop and my gaming machine for well over a year now, and haven't had any issues with it. In fact, I'm about to upgrade my media box to Vista, as it has better ClearQAM support for the tuner card I'm getting.
Haven't seen the Windows 7 Beta yet; I'll probably wait for the usual driver issues to be more resolved.
-------
P.S. Halo 2 Vista was awesome.
Haven't seen the Windows 7 Beta yet; I'll probably wait for the usual driver issues to be more resolved.
-------
P.S. Halo 2 Vista was awesome.
Re:
Same here. Vista on my laptop has been running just fine, no problems. Which is a drastic difference from when I installed it when it first came out.Foil wrote:...I've been using Vista on [my] laptop machine...and haven't had any issues with it.
I'll probably wait for the usual driver issues to be more resolved
Friend here @ work has Windows 7 installed and is using it in his dev environment. Has had a few issues with everyday things not being supported
- Warlock
- DBB 3D Artist
- Posts: 3370
- Joined: Wed May 12, 1999 2:01 am
- Location: Midland, Tx, U.S.
- Contact:
Re:
Well any i have ren across i used the vista driver and for my IDE Raide i used the XP driverFoil wrote:Haven't seen the Windows 7 Beta yet; I'll probably wait for the usual driver issues to be more resolved.
Re:
Forgive me, I work at Microsoft.SirWinner wrote:First, I have to take those existing program's source code for each and upgrade it to use Microsoft Visual Studio 2005 or higher then use an external step to modify that EXE to bypass DEP (Data Execution Prevention) just to get the SAME EXE's that work without an issue on Windows XP to work on Windows Vista.
If you're getting DEP failures in your program, you should attach the debugger and see where it's failing. Generally when the CPU executes code on the heap it isn't the original intention and is the cause of a lot of exploits. DEP prevents this by killing the program before it can execute what appears to be injected code.
Yah, it does break compatibility with older programs, but this isn't unique to Windows. Many operating systems now support the NX bit and will have the same kinds of issues. And this isn't unique to Vista, DEP support was added in XP SP2.
- SirWinner
- DBB Fleet Admiral
- Posts: 2700
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Oklahoma City, Oklahoma, United States of America
- Contact:
Topher,
Thanks for the feedback.
If it is a DEP Failure in Windows Vista, then is there a particular reason that my executable program doesn't have the same DEP Failure with DEP ON in Windows XP using the SAME executable?
At the time when I did the DEP workaround, the program had to be used for a potential customer.
I have been so busy since then that there hasn't been time to find out the root cause.
---
One of the other issues that bothered me a lot was calling a Standard Windows call to get the Processes / Programs that are currently running would crash in Windows Vista for no apparent reason.
I found a workaround that let the logic work in Windows XP and Windows Vista while allowing the program to get the Processes List.
The reason that I use the call to get the Processes List is to allow me to check on how many copies of my existing program are running as well as to check for any programs within my software suite that might conflict with another program within that suite.
If either one occurs during the Form Load Process, then the program automatically unloads itself before finishing the loading process.
I also use the same logic to prevent launching a program that is already running.
Thanks for the feedback.
If it is a DEP Failure in Windows Vista, then is there a particular reason that my executable program doesn't have the same DEP Failure with DEP ON in Windows XP using the SAME executable?
At the time when I did the DEP workaround, the program had to be used for a potential customer.
I have been so busy since then that there hasn't been time to find out the root cause.
---
One of the other issues that bothered me a lot was calling a Standard Windows call to get the Processes / Programs that are currently running would crash in Windows Vista for no apparent reason.
I found a workaround that let the logic work in Windows XP and Windows Vista while allowing the program to get the Processes List.
The reason that I use the call to get the Processes List is to allow me to check on how many copies of my existing program are running as well as to check for any programs within my software suite that might conflict with another program within that suite.
If either one occurs during the Form Load Process, then the program automatically unloads itself before finishing the loading process.
I also use the same logic to prevent launching a program that is already running.
- Krom
- DBB Database Master
- Posts: 16137
- Joined: Sun Nov 29, 1998 3:01 am
- Location: Camping the energy center. BTW, did you know you can have up to 100 characters in this location box?
- Contact:
I always disable the built in zip support in any version of Windows, I prefer the way 7-zip's shell extension handles it and the speed is just a bonus.
Although much to my annoyance the simple command to remove built in zip support doesn't work in Vista, no more \"regsvr32 /u zipfldr.dll\". But deleting a couple registry entries and rebooting accomplishes the same thing, although not as quickly or easily.
The other shell extension I always kill is wmpshell.dll, rid yourself of all the annoying \"play/queue/burn/etc with windows media player\" clogging up your folder context menus.
Although much to my annoyance the simple command to remove built in zip support doesn't work in Vista, no more \"regsvr32 /u zipfldr.dll\". But deleting a couple registry entries and rebooting accomplishes the same thing, although not as quickly or easily.
The other shell extension I always kill is wmpshell.dll, rid yourself of all the annoying \"play/queue/burn/etc with windows media player\" clogging up your folder context menus.
- Admiral LSD
- DBB Admiral
- Posts: 1240
- Joined: Sun Nov 18, 2001 3:01 am
- Location: Northam, W.A., Australia
- Contact:
I've been running this as the main OS on my Athlon x2 for a few weeks now. I had a slight mishap with the original XP install forcing me to reformat it anyway so I figured I'd throw it on instead of dual-booting. The best way to evaluate something is to throw yourself into the deep end, right? Anyway, I'm liking it so far. I went for the 64 bit version as I had the hardware and I figured Win7 would be an appropriate time to make the jump.
I'm liking it so far. It actually feels faster than XP on the same hardware. I'm not sure whether that's because it's 64 bit or if it's the result of any performance tuning MS have done but I like it. A number of the annoyances I had with the Vista betas have been toned down or fixed entirely which is nice. It's not entirely flawless though. UAC still has its quirks, antivirus software needs to be updated to support something about the new OS (I had near-constant BSODs in tdx.sys until I removed AVG though internet research indicates other A/V software has similar issues) and full screen OpenGL needs sorting out but for a beta it's still surprisingly usable.
I'm liking it so far. It actually feels faster than XP on the same hardware. I'm not sure whether that's because it's 64 bit or if it's the result of any performance tuning MS have done but I like it. A number of the annoyances I had with the Vista betas have been toned down or fixed entirely which is nice. It's not entirely flawless though. UAC still has its quirks, antivirus software needs to be updated to support something about the new OS (I had near-constant BSODs in tdx.sys until I removed AVG though internet research indicates other A/V software has similar issues) and full screen OpenGL needs sorting out but for a beta it's still surprisingly usable.