Slashdot videos: Now with more Slashdot!

View

Discuss

Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

An anonymous reader links to Ars Technica's report that (quoting) "Microsoft today announced that Windows 7 and Windows Server 2008 R2 have hit the Release to Manufacturing (RTM) milestone. The software giant still has a lot of work to do, but the bigger responsibility now falls to OEMs that must get PCs ready, Independent Software Vendors (ISVs) that are testing their new apps, and Independent Hardware Vendors (IHVs) that are preparing their new hardware. The RTM build is 7600, but it is not the same one that leaked less than two weeks ago (7600.16384). We speculated that Microsoft may end up recompiling build 7600 until it is satisfied, but it only took the company one more shot to get it right: 7600.16385 is the final build number. Microsoft refused to share the full build string, but if you trust leaks from a few days ago, it's '6.1.7600.16385.090713-1255,' which indicates that the final build was compiled over a week ago: July 13, 2009, at 12:45pm. This would be in line with the rumored RTM date but it is also the day Microsoft stated that Windows 7 had not yet hit RTM. Although the final build had been compiled, Microsoft still had to put it through testing before christening it as RTM."

No, if they REALLY wanted to rip off Apple they would cut the price of Win 7 down to almost nothing, but then force you to run it on hardware that would have been cutting edge last year that you can only buy from them at nearly twice it's value.

Because it is a troll; there are changes in the core, many, now there are not as many dependencies and it features a modular design (check the add and remove windows features dialog, you can get rid of everything there and leave only the core os); also UAC was changed, the ribbon is included in the core as an API, performance was enhanced so much that it can run on old Pentium CPUs and netbooks, etc. etc. In fact the thing that less changed was the UI (Still using the same glass Windows).

So lets see here. UAC was changed, thats no different than changing SELinux or Apparmor on Ubuntu, not a major change. Modular design, again, not a huge change just severed a few ties between IE and core system libraries. Ok, so there are a few new APIs, still, not a huge change. As for performance? That should be natural progress of development.

http://www.tomshardware.com/news/windows-graphics-desktop-multicore-cpu,7643.html [tomshardware.com]
In Windows Vista, a single application could hold a system-wide lock on the GDI, basically creating a bottleneck, especially if there are other applications waiting in line to access the graphics stack. While such a design decision may have been okay in the past, it's been re-engineered for Windows 7.
"This work also resulted in better rendering performance of concurrent GDI applications on multi-core CPUs. Multi-core Windows PCs benefit from these changes as more than one application can now be rendering at the same time," Chitre said, adding that the improvements worked to reduce response time issues. "Without the Windows 7 GDI concurrency, the rendering throughput of these applications is effectively limited to the performance of a single CPU core. Since only a single application can acquire the global exclusive lock while the others are waiting, this scenario doesn't benefit from multiple CPU cores. This demonstrates that GDI applications in Windows 7 are now much less dependent on one another."

IIRC, they also offloaded most of the GDI rendering to the GPU. In Windows XP and previous, all drawing and compositing was done on the CPU. Vista added GPU compositing, but which is what Vista uses to implement the frosted-glass effect. The problem is that, since drawing was still done by the CPU and the system does compositing on the GPU, it keeps two complete GDI buffers for each window. On laptops where most integrated cards use system memory this was doubling the amount of system memory required for the GDI. Windows 7 changes this so that both compositing and drawing are done on the GPU, eliminating the need for a CPU window buffer. One of the things this does is cut total memory consumption in half, and eliminates CPU memory consumption by the GDI subsystem entirely. The other advantage is power- Vista's use of the GPU for compositing means more recent graphics chips are much better behaved when it comes to power consumption than they used to be. By doing the drawing and compositing on the GPU, Win7 doesn't draw as much power on modern laptops since the GPU can do that for less power than the CPU.

Is not a design flaw when you don't multicore cpu's; and that's when GDI was designed. You can think of it as an update to GDI to make it current again, which is a good thing and a new feature, not a correction of a flaw.

It's funny that whenever linux or FreeBSD removes a Giant lock it's hailed as major news here, like the transition from 2.4 to 2.6 because they are actually huge leaps forward. However, when MS does it it is just regarded as a bug fix. Essentially, all code is just a bug fix then, as it's all written one line at a time and relies on the the years of work to the code base that preceded it.

There are huge improvements on Windows 7, like multitouch support, etc. It's a really nice OS akin to XP. The problem with the zealots is that they create a list of complaints about MS and then when they fix it, you guys complain even more. MS actually pays their devs salary so they have to charge for their OS. Suck it up, if you don't want to buy it don't.

IMHO, the RC is more stable than Vista. I've been using it as my primary dev platform since a few weeks after it was released, and have had no BSODs yet even running mostly Vista drivers with it. It's rock solid and FAST and the new features are definite improvements.

But the commitment to quality that is present in Win7 and was sorely lacking in Vista should be applauded by all.

If anyone in the dev community has seen further, it is because we stood on the shoulders of giants.

Yes, but in some cases there were still multiple CPU sockets available on one board, which logically is what a multicore CPU is. So it follows that the reasons to make GDI multi-threaded have been present since NT 3.5. On the other hand, if XP had a multi-threaded GDI implementation, Vista may have dropped that feature. Vista endured a total redesign of the graphics stack in order to simplify the graphics stack and make the stack more "stable".

Not really. Back when Windows was designed SMP was rare. There wasn't need to have the GDI subsystem support 8+ CPUs, since none of the rest of the OS supported that many. A global GDI lock doesn't matter much when it's never running on more than 2 cores.

SMP may have been rare when the original Windows was designed. But the crew from DEC (led by David Cutler) that Gates hired to write Windows NT knew SMP back to front. During the 1980s DEC software engineering learned more and more about SMP and how to nurse the best performance out of SMP servers and even desktop clients.

So Microsoft has had the know-how to fix this type of problem for over 15 years.

The included MS Media Player is the best one yet, and works flawlessly and plays most formats. It doesn't play.mkv files though, so I can also report that vlc v.1 runs beautifully! The improvements are especially visible if you have multiple monitors.

Internally, we plan to upgrade all Vista laptops to Win7 as soon as we get an official version (all of our users hate Vista, but we haven't had the stomach to downgrad

I have an MSDN Universal account and have played with each version of Win 7. I do like it much better than Vista. In fact, I have never used Vista for production work. Win 7 is a nice clean update and I give three cheers to MS for that.

However it is not anything revolutionary. Drag and drop a video? I am sure that WMV will be preferred. As others stated, VLC could do this for a long time now.

The MAJOR thing that pissed me off and made me wipe Win 7 was when I put a DVD (a real one I bought) in to

I have Win7 RC installed and I haven't experienced this. My monitors are connected with standard DVI, and don't support HDCP. The Vista/Win7 protected path isn't even enabled unless you're playing Blu-Ray (not DVD). Your problem is most likely caused by a bug in pre-release video drivers or in Windows Media Player. WMP has had some of its codecs rewritten.

Sounds like you had an issue with interlacing and/or the anamorphic video... VLC configures that stuff automatically when you watch a DVD - just compare, say, untweaked Media Player Classic and VLC, playing the same DVD. Media Player Classic has the wrong aspect ratio and shows a bunch of scanlines, whereas VLC is crystal clear.

People make this shit up at the drop of a dime. This is NT 6.1, simple as that. The "Windows 7" tag is meaningless bullshit, that bears no relation whatsoever to the NT version. The Windows version naming scheme had a little bit of meaning, up through NT4.x and Win98. Starting with Windows 2000 and WinME, Microsoft broke the naming scheme, intentionally, to confuse the public.

Trying to make up reasons for a new bogus naming scheme is only going to make people look stupid.

I suppose it's true to the idea that 7 is "just a Vista service pack," but still seems odd.

Not at all. Vista has taken the punches, got a fat lip and two black eyes - so Microsoft rebrands it and it loses the bad name of Vista. I just installed Windows 7 RC - and it's nicer. There is new programming under the hood, particularly the UI and feels speedier - although I have to question whether that speed was all a result of improved programming or attribute some to the fact that it was a clean install of Windows erasing a cluttered and used OEM Vista install.

But given the driver model is the same, the lack of noticeable bumps on the alpha, beta, and RC compared to Vista woes - I can only assume it's really a service pack with an UI overhaul. Which is okay; Ubuntu and OS X both operate on the idea of short upgrade cycles that allows them to focus on goals and be a lot more evolutionary in a short time instead of trying to be revolutionary (longhorn) and failing miserably.

I just don't like paying full price as if this were brand new windows. Ubuntu is free and OS X license is relatively cheap, especially family packs. I'll pay $50 for Windows 7 as a 2-3 year upgrade to Vista, but don't forsee $100 as being inherently fair at all.

I read that the speed of Windows 7 is a result of some under the hood programming. They implemented concurrency in the drawing component of GDI, which in theory allows for smoother graphics when multiple GDI apps are running. The old way of doing things was a single lock, and the time it took to lock/unlock is what seems to have caused past responsiveness issues.

Win7 is lighter on system resources, to be sure, but the real catch was the OEM bit. OEM Vista installations were uniformly absolute shit. All kinds of pre-installed crap that ran at startup (including things which are practically impossible to cleanly remove, like Norton Internet shitware), some truly retarded default settings (yes, worse than the Microsoft defaults), and poorly-tested replacements for Microsoft binaries (usually functionally the same, but OEM branded and typically shadowing or outright removing the built-in software) made the OS run MUCH worse than a clean install on the same hardware would. Hardware troubles and beta drivers aside, I have not (in almost 3 years since RTM) seen Vista BSOD or otherwise catastrophically fail on a clean install. Yes, it happens on OEM copies. It would might happen if you installed a trojan or something retarded like that. Barring such stupidity, however, Vista is an extremely stable OS that performs quite acceptably on systems with 1 GB of RAM and a 1.8GHz single-core CPU (my initial Vista machine, a laptop over a year old by Vista's RTM).

That said, Win7 is definitely a major improvement in many areas. Vista, especially at RTM, really did have some truly stupid bugs.

I know you're just trolling, but in case anyone thinks there's truth to this, it's worth pointing out that editing conf files and compiling packages hasn't been necessary in Linux for a few years now. I haven't compiled a package or hand edited a conf file once on my 2 month old laptop, and don't expect ever to have to. Also, installing XP (It came with Vista, which I didn't want) and making it work properly with all the necessary drivers took about 3 times as long as installing Ubuntu, and was much more difficult and stressful.

The idea that Linux is harder to use than Windows is really pretty ridiculous.

For those that don't know and didn't want to RTFL, it will be available to MSDN subscribers on August 6th as well. If your company didn't pony up for one of the subscriptions, but does have Volume Licenses for Windows with a current Software Assurance, it will be available on August 7th.

Since they didn't release any other deskop OS version on Dreamspark (only server versions), I'd be hesitant to believe that they'd start now. I think the better question is whether they'll offer an "Ultimate Steal", where students can get the ultimate version for like $49 or something else like that.

Compare this to the retail cost of Windows 7 Ultimate ($319) and Office 2007 Professional ($499) and it's quite a deal, especially since retail Windows 7 won't be available until October 22nd, whereas TechNet Plus subscribers get it August 6th.

Why would ANYONE pay retail for Windows or Office when TechNet is available?

I don't know about TechNet, but for MSDN subscriptions, the license to the software does NOT expire when the subscription does. In other words, even if you don't renew, any software you downloaded during the subscription period will still work, and the product keys will still be valid.

Besides, I have two computers (my main machine and a lightweight tablet for classes or meetings) that I need to keep up-to-date. If I didn't have an MSDN subscription (interns get some pretty sweet stuff) the TechNet subscription would be a pretty awesome deal.

The build timestamp is the timestamp in the source control system used to sync all the files to. When compiling, one chooses a time slightly before when you started the process, or a time slightly in the future. Then the automated build process starts up, waits for the time to arrive, then syncs to the given timestamp, then runs the build process.

However, trust me, Windows takes well more time than even Gentoo to compile...

IANAMFB (I am not a Microsoft fan-boy), but I have to admit that so far, it looks like it is at least a bit exciting (especially from the rock-solid RC). Pretty much what Vista should have been.

As a true technologist, I try to stay technology-agnostic because good things often come out of the strangest places. Truthfully, many flavors of Linux are great, Mac OS is great, and Windows 7 looks like it should be great. Considering all these various flavors of greatness, I'd say it's still as good a time as any to be a techie! Maybe I'm just tired of all the negative slant the world puts on everything and am being overly optimistic.

Let's enjoy this new tech, welcome it, evaluate it and let it find its place in our toolbox, like every other tool before.

What "new tech"? So far I haven't seen anything in Vista or 7 that would make me say, "I gotta have that tech!"

To be fair, I haven't seen much in linux lately that would make me say that, either.

let's be honest: OS "tech" has hit maturity for most users. There really isn't anything truly exciting coming out - because there really isn't anything exciting left to be done unless the whole OS/UI undergoes a severe paradigm shift.

Unfortunately that's not going to happen because there's too much invested in the current tech.

I'm going to see how the adoption rates are for 7. I see a rocky road for MS; people are happy with XP, it's stable, and for most of us it's a f*cking desk. No amount of hype is going to convince me that I have to get a shinier pressboard and formica office desk; the one I have works just fine.

It has hit a state of complete lack of new ideas, because of laziness.

Windows imitates Macs, Linux imitates Windows (I love my Linux systems, but unfortunately this is the truth), and Apple no reason to innovate MacOS X, because they are already better. At least this is what they think. ^^

In reality though, Linux (or the Linux desktop environments) could shine more than anything else. Because its openness allows for things that just arent possible with commercial applications.What I mean is how Linux works on the shell: You can combine and recombine all your small tools, using the file system, and small scripts, piping data, etc.Now imagine this for the desktop. Imagine that all the functions you can reach trough all the apps of your GUI desktop, were not one application, but small, fast, little widgets and tools. Then add a set of view and control apps to it. In a way it would be like the extensions of firefox combined with a photohshop without the main window.You could endlessly recombine the tools from one package with that from another one, and use a document viewer/controller from a third package. (Where "package" would be, what we call apps today.)

Imagine taking the brush from photoshop, and the formula renderer from your calculator, and paint the formula into an arbitrary document. Things like that.Interoperability would work trough standardized data structures (think xml or ebml chunks/streams with mime type headers).

And this is only one idea.You see, GUIs still have a long way to go, to get even close to optimal efficiency (where "efficiency" is power multiplied with simplicity).:)

And as you also see, shiny but pointless 3D desktops are more likely the opposite of this efficiency.

There are innovations in OS X. For me, one of the most useful is iDisk, which is a seamless UI on top of RSync (or something similar). All of my smallish documents (not video edits etc.) are now on iDisk and sync perfectly between my laptop and desktop whether I'm at home or on the road. If I don't have my laptop I can use the web interface on any Mac or PC to get to my files. It's pretty simple, but for me has massively improved my ability to work on the move. Nothing revolutionary under the hood, but

Hopefully I won't get flamed for this (from both sides of the spectrum..lol). Regarding your comment about combining and recombining tools in the OS: What your describing in regards to scripting OS apps together to form new tools sounds like PowerShell for Windows. I'm actually excited that it will be included in Windows 7 from an IT perspective. I've had to program in it heavily for our Exchange 2007 migration and I've actually come to admire this tool. We were able to migrate 40,000 users to Exchange 2007 all in a fully automated fashion using load balancing on the target servers and totally seamless to the end user. It allows piping of just about anything, and it hooks extensively into the OS. It also supports plugins (although I've only had experience with the Exchange plugin). It makes it easy to pick up and hard to put down. Even doing something as simple as a directory info (DIR) and piping that output into a hash table becomes simplicity itself ($mydir = dir c:\). From there it's extremely easy to parse the $mydir hash for individual properties like filenames, access dates, file size, etc. The same is true for grabbing system tasks using Get-Process. Everything is exposed in a hash table with a single command and that easily piped into yet another command to mangle to your hearts content. After years of starving for a good shell, I think MS finally got this one right. If you haven't looked at it yet and you work in an MS IT shop, your missing out.

I can't say that I'm overly impressed with Windows 7 (yet...time will tell). It seems to run on par with XP performance wise, which in itself isn't necessarily a bad thing. It does so with more security at least. I don't really care about the UI changes as they mostly seem cosmetic in nature. A few things moved around or a tad easier to navigate to or around, but nothing I'm finding is a must-have. The RC I've been using has been flakey in regards to bluetooth support, but generally the OS has been stable overall. I'm sure the bluetooth will be solid by release. I'm taking the same approach as I'm sure many folks who were burned with Vista are doing.. Wait and see. That said, the price seems very steep for a more secure XP with some window dressing. Make no mistake that although the feature set may be extensive for the techie crowd (depending on what articles you read), for the typical Joe User who only knows what he can see and feel, it's a more stable 'Vista'. Again that is not necessarily a bad thing (think Windows 2000/XP).

Arguably, with the right software and hardware, XP could be secured for typical use of browsing and e-mail leaving only the GUI changes lacking for Joe User on XP. It just seems extremely costly for all of these changes that the basic home user probably won't care about.

Typical Joe Users just wants to check their e-mail and get to their online poker game going with their buddies or what not. My only decision going forward will be if I want to continue to invest in Microsoft at home (work is a given at this point), or switch the last of my Windows machines to Mac. The pilot Mac I bought for my family has actually done rather well and the adjustment wasn't nearly as difficult as I thought it would be. It makes me want to take a harder swag at Linux as well given the easy transition I've had with Leopard. If Vista accomplished anything, it was to make people more aware of alternatives which is never a bad thing.

Meh, there's a few things in Win 7 that IS actually pretty cool and not just eye candy. The home group thing looked interesting, for example. I find some of the UI differences very intuitive and a lot easier to work with than (dare I say it) my Ubuntu 9.04 install on my laptop.

I'm not one of the MS Windows 7 software engineers so I don't know what, if anything, really changed under the hood, but it's the above-the-surface stuff that typically will make applications work well (or just *feel* like they work well) or not. Example that's very ready on my mind: GnuCash. I'm looking for a home finance program (just to keep track of budget vs. expenses, pretty much). GnuCash does everything but has, IMO, an awful and very user-unfriendly UI. It'd be a great program if the UI was less confusing and less cluttered.

If nothing else, Win 7 has done a good job with that part of user-friendliness, which isn't just for John Doe at home. Even a programmer/software tester/whatever like me enjoys using an easy-to-use OS when I don't need a unix style shell but just need a text editor, a word processor, or want to play a game.

I'm going to see how the adoption rates are for 7. I see a rocky road for MS; people are happy with XP, it's stable, and for most of us it's a f*cking desk. No amount of hype is going to convince me that I have to get a shinier pressboard and formica office desk; the one I have works just fine.

Application bloat will save the day for MS. It's already hard to manage a desktop of intensive apps and data on 32 bit XP limited to 3.5GB of RAM. 64 bit Windows 7 will allow larger apps and more data as the bloat continues to escalate.

I'm happy with XP, too (for the stuff I need Windows for anyway) but I'm also happy that Win7 might be a chance to upgrade without getting a crap OS instead. XP is actually a good OS after the SPs, it's stable and it does stuff. But it's nearly 8 years old and that's starting to show. There's tech out there that XP simply doesn't support. I'd like to enjoy my games in DirectX 10 since I have a video card supporting that but XP doesn't support DX10. I'll want to get myself >4 gigs of RAM sooner or later a

Built-in transparent full-volume encryption is pretty cool, especially when you can encrypt a flashdrive (on Win7) then still access the contents (with passphrase or other key source) on an older computer running XP or similar.

Strong two-way firewall with good configurability means no more spending time and possibly money on third-party firewalls. That saves system resources too. Vista had this too, and I've seen no sign of it being vulnerable to penetration.

UAC makes running as a standard user a lot easier to deal with (it's a bloody pain on XP, and frankly running as Administrator is just bloody idiotic). Win7 has added more configurability to UAC and made it less in-your-face by default.

Integrated instant search. I simply can't stand to use XP for any length of time due to the simple fact that it lacks this incredibly convenient feature (which every other major OS has as well).

Gadgets. Yep, I use them. Very handy for a lot of things, like Pandora, a simple calculator, or at-a-glance traffic info. Several substantial improvements here compared to Vista.

Automatic driver installations and updates. WinXP's plug-and-play driver collection is horrifically outdated (it's an 8-year-old OS) and a lot of modern hardware requires manually installing drivers. On Win7, those drivers are already present on the system and get installed immediately, or Windows will check online, find your drivers, and download/install them for you (signed and certified binaries only, of course). Win7 will also check for updates to existing drivers, and allow you to download the updates with a single click.

These are very much things that "most users" will find superior to XP. The hardware requirements are undeniably higher, but you can get computers for under $400 that are quite capable of running Win7, and mid-to-high-end new machines have more RAM than a 32-bit OS can utilize anyhow.

Built-in transparent full-volume encryption is pretty cool, especially when you can encrypt a flashdrive (on Win7) then still access the contents (with passphrase or other key source) on an older computer running XP or similar.

As this feature was trivially available with free third-party software, I don't see it being a huge improvement.

Strong two-way firewall with good configurability means no more spending time and possibly money on third-party firewalls. That saves system resources too. Vista had this to

I'd agree with this. I'm somewhat of a Linux fanboy myself, as I use Arch almost exclusively - but I wiped my Vista partition a couple of days ago and put Win7RC on there (build 7100).

I'm impressed. It boots fast, it runs fast, the new taskbar is clean and useful - it seems to be an all around good product. I don't see it pulling me away from Arch - I'm running ScrotWM these for coding, and nothing Windows does let it compete with a tiling WM from a productivity standpoint - but I see myself booting to Windows 7 more often when I just want to surf the web or check email. I never did that with Vista.

They aren't built-in, but there are plenty of programs to do "virtual desktops' on Windows. The one I like most (solid, nice features, sufficiently lightweight, and open source) calls itself Vista/XP Virtual Desktop Manager:http://www.codeplex.com/vdm [codeplex.com]

IANAMFB (I am not a Microsoft fan-boy), but I have to admit that so far, it looks like it is at least a bit exciting (especially from the rock-solid RC)Sure it's "exciting", given that Slashdot is hyping Windows 7 with some "News" every two weeks. Or every single week, more like it.

Yeah but I remember the Windows ME beta and RC was better than the RTM version. So you really cannot tell by the beta and release candidate if the RTM version will have different issues. Windows ME was based on Windows 98 like Windows 7 is based on Windows Vista.

But then again Windows XP was based on Windows 2000, and at first it had issues but the service packs seemed to make it good enough for use. Which is why Vista users downgraded to XP in the first place.

This sounds like a security disaster waiting to happen. Basically at boot time it opens a hole in your firewall/NAT directly to your machine - without you even having to log in. If there's a flaw in that service, people behind NAT/firewall/routers are going to be vulnerable rather than 'safe from internet worms by default' like with many other vulnerabilities.

You realize DirectAccess is just a machine level VPN rather than a VPN controlled by the user... right?

You realize that having that connection always on is not a good thing when you get infected with some silly virus that wants to probe everything it can talk to and infect, right?

There are about 50 billion reasons why this is a retarded idea, and about 3 for why its good. Considering VPNs can be configured to auto connect already its really silly that you're all excited over another VPN package made by MS, which has traditionally had an absolutely shitty track record for providing a secure connection.

So go ahead, be excited that you have Direct Access, but just try to get a clue and realize its just another form of VPN which you need to watch for security issues and requires you to be locked into MS due to the use of a non-standard protocol.

Go read up on IPSEC if you'd like to catch up to how everyone could do this 10 years ago, including Windows with 3rd party software.

Windows xp went RTM August 24, 2001 so not exactly ten years ago but with XP IPSec VPNs have been supported from the beginning. I hate to sound like a prick but when coming up against such sheer ignorance its hard not to.

1. IPsec requires a ton of ports being available and open which just isn't the case as often anymore when going to a hotel. Hence why a lot of corporations are looking at things like SSL-VPNS. Direct access overcomes this limitation by tunneling all their IPv6 traffic in standard HTTPS packets which is pretty universally allowed.2. You can configure your vpn to connect to automatically but what if i have a public web server that I want to connect to and split DNS (or DNS client views) so the internal and external zones are the same. I don't want my stupid VPN client trying to connect every time I go to www.slashdot.org with direct access you specify internal zones or internal servers that it should connect for while allowing it to route all other traffic normally.3. Microsoft's best practices on direct access say to use Network Access Protection to isolate the clients and force security scans just like most modern VPN clients except now its completely transparent to the user which saves time and money.

AIUI VPN's are basically just Ethernet proxy systems. (Sometimes it works at the tcp/udp layer instead), simulating being plugged directly into that network, while actually plugged in someplace else. The naming is absymal, but this is really useful for enterprises. Services can be blocked at the edge firewall, and off-site employees access them through the VPN. That is nice for several reasons, such as security, and the ability for employees to remotely access devices that would never be publicly exposed to

The problem case could be addressed by using a DNS names instead of IPs, I'm not familiar enough with what they are pushing to know if this is what they are proposing or not. That being said allowing access to your enterprise network before the user supplies credentials seems like a very bad idea.

One place this scheme will probably fail is if the company uses a private IP address range which is the same as the privcate IP address range the employee is currently connected to - in this case, the routing has to fail to connect to machines in one or other subnet - but thats the problem with nat...

Heh
That thing happened me today when trying to connect to my Windows machine at work through a PPTP VPN connection. My office computer moved to another subnet: 192.168.1.0 which is the same subnet in my home network.
I had to add a routing rule in NetworkManager to route my workstation IP through the VPN.(I spent like 3 hours with someone over the phone, before I figured out the problem).

Of course it does.. once you have a tunnel there is no client and server, you just route whatever you need over it.

Depending on the layer of the tunnel you may be limited to IPv4/6 or you may be able to get more imaginative.. I prefer GRE tunnels for that reason.. you can send dynamic routing over the links and get quite sophisticated with it.

- Win7 is marginally faster than Vista, and it will run on far faster, more capacious hardware (on average).- The beta/RC was a huge try-before-you-buy program, which lends itself to a more positive view of the product.- It finally fits on a netbook, and those will be the rage once they start becoming really sexy.- $99 just isn't what it used to be.

Anyone worth half a karma point here will recognise 16384 as a power of two.

In my years of software development, numbers like this jump out at you, usually while debugging something that has crashed due to overwriting something, and suspicious powers of two just scream 'BUG' at me.

Perhaps this move to manufacturing has simply been caused by microsoft not allocating enough bits in the build number, and one more recompile has tripped the manufacturing release...

I've been using the public beta since it came out, and the RC1 since the public beta expired, and all in all, it's pretty good. Takes forever for me to figure out how to do anything anymore, since I'm so used to XP (stripped down to non-flashy mode; more like W2K in use), but that's no biggie.

The big question in my life as a web developer is: When is IE gonna be a good browser? How many versions is it gonna TAKE?

I take solace in the fact that anyone upgrading to Wndows 7 is going to be forced to go with IE8 or some non-MS browser. No more IE 6 or 7. *whew* Hopefully the critical update and the enterprise migration tool thingy for IE8 coming soon will get rid of a large percentage of the remaining IE 6 users that aren't on something older than Windows XP. Win2K/ME/98/95 users, well, tough luck. Time to for you or your administrator to either upgrade to a netbook or install Firefox/Opera/whatever. Way PAST time, really. But if someone in your company was stupid enough to develop something requiring ActiveX, I guess IE8 is it for you. If you want the Gecko renderer from Firefox, but your system can't handle the overhead of a XUL browser, try K-Meleon.

Even real life highways have minimum speeds, you know. Get your Model T off the information superhighway, you're dangerous.

Actually, Internet Explorer 8.0 is a pretty good browser--I've seen a lot o stability improvements over IE 7.0 under Windows Vista Home Premium (SP2). I'd like it to be a tad faster, though.

As a web developer, I can tell you that IE 8 *does* compete very well with Firefox... v1.5. It's standards support was outdated before it started development. And it's interface! Gag. IE 3 had a better interface.:(

No WGA Everyone is a thief because its free and they cant be caught. We don't care. No Secure Audio Path We hold the electron path between the users CPU and soundcard as sacred. No Secure Video Path We don't care what you watch. The license Manager (CACL) checker doesn't do anything when you hook a printer up without a CACL We don't care how many connections your computer has. To make Windows users at home Cron will launch a desktop/men

Back in the days of PARC, they had a device that you could manipulate the input on screen using your fingers. It was called a "Capacitance-Activated Tablet" or "CAT" for short. A few months later, someone developed a device that used a rolling ball and sensors on an X-Y axis to move the cursor, and pressing a button to initiate the action. Because of it's looks, and since they already had a CAT, they called it a MOUSE.

Unless the mechanism of the patent in question is different from the capacitance array, or unless this company bought the patents from Xerox, it seems that Xerox holds a patent on prior art. I'd like to see the working model they submitted with their patent...

Touch-screen technology at the time required little lamps around the bezel of the screen, and the location was done using the interference of the X-Y coordinates of the intersecting beams of light. Light-pens gave feedback to the actual pixel grid on the (phosphor based) screen.

I seriously doubt that they did a full regression test that quickly. More likely, they tested the areas which had recently failed tests, and were recently fixed.

That's how we do it at my work. Our product has around 90,000 test points that are tested in each 3 month release cycle. A full regression test takes approx 2 months. As bugs are found, they are fixed, and the fix is tested while the full regression test continues. The last month only fixes are tested.

Microsoft has greatly approved their testing process, with automated regression testing on literally thousands of machines. Full regression tests that used to take 3 weeks now take 4 days, with three of those days being failure investigation. You can read the Windows 7 team blogs for information on the process, but one key component is that daily builds off the main branch should be of very high quality, as close to release quality as feasable.
This, along with the improved testing, allows regression tests to be run on virtually all desired interim builds and integrations, so that by the time RTM testing is hit, there are very few surprises.

I'm guessing the same reason every new kernel release is slashdot news...

Nerds/geeks/whatever can use Windows, too.

Which makes an RC for what is looking like a pretty popular OS a pretty good candidate for slashdot news. More-so than, say, a statistic that says game sales for an extremely specific and narrow genre are declining.;)

I think most of the bad Vista rap was due to its minimal specs was what it was put on initially, it made it seem horrible. I personally got a copy of Vista pre-sp1 to test and it wasn't that bad on my gaming rig.

I had Vista x64 for a while and now the RC1, too. Quad core, 8gb ram... I did notice a performance increase between Vista x64 and 7x64. Not a whole lot, but boot times and program startup times definitely improved, if nothing else.