XP Mode or Hyper-V, without the VT switch on, it will just laugh at you.
Actually there was an update early this year that removed the limitation, presumably because plenty of cheapo Dell PCs (for example) don't even expose the VT switch in their BIOSes (even though the CPU supports it).
I haven't noticed any speed difference in XP Mode or VirtualBox with or without VT.
Oh, I certainly agree, WINE is quite an achievement. My point was that it's much too soon to celebrate an open-source DX11 implementation because they haven't started doing the hard part yet; look at how long it took WINE to get accelerated DX9 to a "mostly working (with limitations)" state...
Yes. It seems very likely to me that an open-source implementation of a Microsoft API, and implementation "in its infancy", will soon surpass Microsoft's own offering.
I was about to post the same thing. The summary is amazingly hasty in its conclusion... I mean, WINE has been at it for what, 10 years? They still don't have it working as well as the original. Not dissing WINE, but I mean, implementing the entry points of a published API is easy. Making it do the correct things under the hood is the hard part...
That being said, I can certainly applaud the effort, but this should be news once it's working otherwise it's meaningless.
Then we are in violent agreement
Some people at work haven't learned this yet and only put bug numbers in their code/checkin comments, so I didn't pick up on the shorthand.
Cheers!
Amen. The best practice I ever adopted was adding comments like "As per bug #1351", so that a year later I can remember why I picked took a seemingly screwy approach
I agree with the sentiment, but I prefer to be a bit more verbose than "bug #1351". Bug trackers change, projects change, access levels too. When bug #1351 in project ABC refers to a bug database that is no longer available, you'll still know what it refers to. No need for being excessively verbose, but just a simple explanation can help tremendously.. e.g. "bug #1351 - state ptr can be NULL when reloading". In my case we frequently re-use code from other projects, but seldom have access to their bug databases (and often they no longer exist).
Same thing for checkin comments - just telling me the bug number won't help me if I wasn't on your team.
164
Surely you'll remember that screenshots were often from the Amiga version. There was a single box for all versions of the game, and a sticker telling you which platform was inside...
103
[...] I'm pretty sure you can just transfer your profile, saved games, arcade games to a regular old USB flash drive and then transfer all that stuff to a new console.
It's gonna take a while doing it manually.... More importantly, some content and some saved games cannot be moved to another storage device. If you use the transfer cable, everything is moved to the new hard drive in a single operation, including stuff that you cannot move manually.
It's too bad you can't replace your Xbox hard drive with a USB external drive (well you can, but you're limited to 16GB!), that would have been amazingly convenient.
The whole purpose of a robotics environment like this is so that robotics builders can concentrate on actual robot stuff, whereas MSRDS makes you waste so much time learning their proprietary formats & techniques that you could easily loose the fun in learning robots!
(disclaimer: not a robotics guy, I just messed around with an NXT set last year)
My main issue with their environment is that the resulting robot doesn't actually do any of the thinking, you need a PC running MSRDS connected at all times. All processing is done on the PC, and commands are sent down to a slave program running on the robot. Other development environments supporting the NXT (like NQC) target the brick directly and give you a fully-independent robot, which is (to me) much more interesting.
Their realtime 3D simulation environment looked like a big selling point, but then I couldn't make it do anything myself besides running built-in samples. As you said, MSRDS focuses on the wrong thing, because NQC (or even the built-in Lego software!) was a lot more fun.
+1. I also remember playing
When I saw/heard the Amiga, I instantly sold my PC (286 12MHz) and bought an A500. One of my first games for it was Turrican II, I used to listen to the main menu music all the time...
Before I heard the Amiga, I was amazed hearing the sounds in Links (the golf game -- don't remember which version had digitized sound) on the PC speaker. Oh how far we've come...
Devkits can run unsigned code - retail PS3s cannot (except in Other OS mode). Having just a few won't help you.
Not every store scans the serial numbers, for example Costco. I've swapped defective consoles that were past their warranty over there, if you do it once it's no big deal.
I've seen some posts earlier suggesting that this is scamming the store, but if you've ever worked at retail, you know that the store does not deal with the consoles - everything is done through a supplier, who deals with the manufacturer. Returns do get to the manufacturer eventually, at no cost to the store.
Yes, I realize that it's an abuse of the system, but I only did it as a last resort (e.g. before Microsoft extended the warranty on RRoD 360s).
"Ninety percent of baseball is half mental." -- Yogi Berra
