You can run any of the Vista OS's in a VM, there is no restriction preventing it. What you can't do with the lower end versions is run the same copy on both a physical machine and a VM at the same time. You would need two licenses to do that. With the higher end versions you are allowed to run a VM using the same copy that you are using on a physical machine. So if you have ultimate on your PC, for example, and you want to also run it in a VM you won't have to buy a second Vista Ultimate license. If you have Basic you will have to buy a second license (to be legal at least) to do the same thing.
Cheaper in the Microsoft/corporate license world. I guess I should have been more specific. MS doesn't want companies using XP or Vista instead of 2003 Server or Longhorn as file/print servers.
You forgot the bit about VM's. The EULA forbids the use of a second copy of the same product (under a single purchased license) running on a VM. Since MS does allow this for the higher-end licenses they probably wanted to be clear about where it was not allowed.
Line his pockets?! On 1 dollar per sale?! Even if every student in every one of his classes bought every lecture it would add up to only a few thousand a year, and after taxes much less. I really doubt the massive $1 profits are a motivator here.
Or you could look at it like this. Say you want to go to a movie but your leg is broken, you could have your buddy go with a video camera and buy two tickets.
Seriously. He is doing this as a service to the students. Most professors wouldn't. It's $2.50 for crying out loud. That's what, 2.5 dew's from a vending machine for the convenience of being able to hear a lecture if you have/choose to miss one?
Am I the only one thinking that this technology could also be used to solve the blue-hair problem? Would renaming the company Soylent Energy be too obvious to them?
That's Power over Ethernet (when you send power over your data link). I think he is talking about Ethernet over Power, when you send data over your home's electrical system.
So wait a minute here. Lack of experience on your part with Windows software development and the failure of the MySQL ODBC client project you used to update their software to a not-over-six-year-old POS development platform and not use proprietary components is somehow a failure of Windows!?
Microsoft gives away Visual Studio Express, which is perfectly capable of support most OSS projects. Documentation is available for download, is available online (for free), and is available in print.
I like the ribbons, but I guess it's more a personal preference. I do wish they would make the apps so that you could switch between the ribbons and a more "classic" style. I can see some people being confused by the new interface.
Looking at the list of restriction on what the service can be used to pay for can you actually buy anything with it?
https://checkout.google.com/seller/content_policie s.html
I mean I can understand not allowing illegal items and such but "offensive materials" and "occult" items?! Infomercials?! "Regulated Goods", by their definition, would cover damn near every consumer product in existence (for example anything regulated by the FCC which would be pretty much all electronics).
I'm in the same boat. I live in a 'burb of a big city and the light pollution from the city (~ 20 miles away) is so bad that that I usually don't even need the lights on outside at night to see in my yard: the yellow-orange haze from the city is more that sufficient illumination. It's like a perpetual sunset. I would have to drive for hours to get far enough away from the city and surrounding suburbs to find a "dark" area to stargaze.
Try it. Setup Autorun on a USB disk and plug it into a fresh XP SP2 machine and see what happens.
I do agree that most likely (hopefully) a credit union would have autorun disabled on their PC's and most likely the employees just started opening files on the disk.
That is 100% incorrect. USB drives (and ANY removable drive including usb/firewire hard drives) can be used for autorun. Most likely the reason the parent could not get it to autorun is because autorun had been turned off.
If you want a great example of autorun look at Pass2Go from the Roboform guys. It sets up autorun on the USB drive it is installed on. The Microsoft wireless network setup wizard (the one the also exports the WEP/WPA keys of an existing connection on an XP machine as plain text) also sets up a USB key to autorun the wizard.
Yea, I draw the line between something someone uses for themselves and something that starts to get spread around to other people. If it is important for a group in the company to use then it should go through a development team. Of course, again, I can rant until the end of time about the (lack of) quality of most internally developed software. That just goes to the idea of the iron workers designing the bridge though.
See, here is the problem. It's not just enough to solve the problem with a software project. One of my customers was a manufacturing company. They had this guy at one of their plants. He knew a little clipper and wrote some apps to do calculations and such. Seems harmless enough, right? The problem was the company grew. And grew. And grew. All the while these little clipper apps became more and more and more important. The problem was they were not being updated as the OS changed the apps became more difficult to keep working. Eventually these little apps became so critical that when the company (now a good size enterprise) did their last upgrade they decided the clipper apps had to go. Problem was they had to keep them running while they replaced them. In the end those little clipper apps burned up over $30,000 in consulting time getting them installed and working (because the author had since retired) while the replacements were written by another company.
There is a reason to hired skilled trades when you are doing any project. Programming is no different. Now, granted, it's not easy to find skilled programmers (you should hear me rant about 6-figure vertical apps that look like they were written by monkeys on dope).
The tone of your post tells me you are one of those end users who has no formal education in software design, computer science, or even a tech college programming class. I have no problem with some end user writing a quickie app to solve some simple, quick problem for themselves. What I have a problem with is when that end user begins to think that he/she is a software developer and starts trying to write full fledged applications. Then you get crap apps. Then I get to spend hours of my customer's time (and money) trying to get those POS applications to work in a multi-user environment. Had the programmer taken the time to actually learn how to actually do the job they were pretending to do it would be a snap. However since that usually isn't the case I end up having to force the OS to conform to the application, instead of the other way around (aka: the right way).
To put it another way: I'm sure you could probably build a somewhat functional bridge. You'll just have to pardon me if I don't drive over it.
"Don't knock modular configuration that can be changed/transferred/backed up by simply handling a file. The Windows apps I like the most are the ones consisting of a binary, some support files and a config file. They don't need to be "installed" which usually just means implanting the same config into the atrocity that is the registry."
The parent that I replied to implied it. In most cases that is also how they are (mis)used. Yes, you would put an INI file in each user's profile directory or home directory if the software author did their job correctly. Too bad that's usually not the case. INI files are supposed to be broken into two parts: computer and user specific. Just like the registry with Local Machine and Current User. Like with the registry however, many programmers treat INI files as one entity and stuff everything into one file. To make matters worse they usually access it as a text file instead of using the built in APIs (if you work with Terminal Services or Citrix you understand why this is a problem) and they store it in the program directory. It works on their machine so it must work on everyone else's, right?.
...and that brings us full circle back around to my original post: if programmers actually followed Microsoft's design users would not need admin rights to run most applications.
That I have to agree with you on. VB6 and the programming mentality it fostered did a lot of damage to the quality of Windows software. MS released a very easy to use, very popular language and IDE without giving it the ability to use the system properly. For example it had very limited support for using the registry.
That's great. That also means that every user most likely needs write access to that INI file. What if more than one user needs to use it? Do they keep overwriting each others settings. What if more than one user needs to use it concurrently?
There is nothing atrocious about the registry. If developers would learn to put stuff where it belongs and to clean up when they uninstall it works perfectly. That said, there is a proper way to use ini files in Windows and that means you don't open/close it as a text file and you don't store user settings in a single ini file located in the program directory.
Windows provides API to handle global and user ini file information and if used properly you don't run into issues like the ones I stated above.
Slashdot Mirror
You've apparently been the victim of the infamous "Microsoft mind trick".
You can run any of the Vista OS's in a VM, there is no restriction preventing it. What you can't do with the lower end versions is run the same copy on both a physical machine and a VM at the same time. You would need two licenses to do that. With the higher end versions you are allowed to run a VM using the same copy that you are using on a physical machine. So if you have ultimate on your PC, for example, and you want to also run it in a VM you won't have to buy a second Vista Ultimate license. If you have Basic you will have to buy a second license (to be legal at least) to do the same thing.
Cheaper in the Microsoft/corporate license world. I guess I should have been more specific. MS doesn't want companies using XP or Vista instead of 2003 Server or Longhorn as file/print servers.
You forgot the bit about VM's. The EULA forbids the use of a second copy of the same product (under a single purchased license) running on a VM. Since MS does allow this for the higher-end licenses they probably wanted to be clear about where it was not allowed.
The MS "workstation" OS's have always had this kind of restriction, mainly to prevent their use as cheap file/print servers. Nothing really new here.
He did:
An OEM version of Windows XP Pro is ~$140.
Line his pockets?! On 1 dollar per sale?! Even if every student in every one of his classes bought every lecture it would add up to only a few thousand a year, and after taxes much less. I really doubt the massive $1 profits are a motivator here.
Or you could look at it like this. Say you want to go to a movie but your leg is broken, you could have your buddy go with a video camera and buy two tickets. Seriously. He is doing this as a service to the students. Most professors wouldn't. It's $2.50 for crying out loud. That's what, 2.5 dew's from a vending machine for the convenience of being able to hear a lecture if you have/choose to miss one?
Good idea. He can just tack that on to the costs and raise the price a bit more, still keeping his dollar.
Am I the only one thinking that this technology could also be used to solve the blue-hair problem? Would renaming the company Soylent Energy be too obvious to them?
That's Power over Ethernet (when you send power over your data link). I think he is talking about Ethernet over Power, when you send data over your home's electrical system.
So wait a minute here. Lack of experience on your part with Windows software development and the failure of the MySQL ODBC client project you used to update their software to a not-over-six-year-old POS development platform and not use proprietary components is somehow a failure of Windows!?
Microsoft gives away Visual Studio Express, which is perfectly capable of support most OSS projects. Documentation is available for download, is available online (for free), and is available in print.
I like the ribbons, but I guess it's more a personal preference. I do wish they would make the apps so that you could switch between the ribbons and a more "classic" style. I can see some people being confused by the new interface.
Looking at the list of restriction on what the service can be used to pay for can you actually buy anything with it?
e s.html
I mean I can understand not allowing illegal items and such but "offensive materials" and "occult" items?! Infomercials?! "Regulated Goods", by their definition, would cover damn near every consumer product in existence (for example anything regulated by the FCC which would be pretty much all electronics).
https://checkout.google.com/seller/content_polici
I'm in the same boat. I live in a 'burb of a big city and the light pollution from the city (~ 20 miles away) is so bad that that I usually don't even need the lights on outside at night to see in my yard: the yellow-orange haze from the city is more that sufficient illumination. It's like a perpetual sunset. I would have to drive for hours to get far enough away from the city and surrounding suburbs to find a "dark" area to stargaze.
Try it. Setup Autorun on a USB disk and plug it into a fresh XP SP2 machine and see what happens.
I do agree that most likely (hopefully) a credit union would have autorun disabled on their PC's and most likely the employees just started opening files on the disk.
That is 100% incorrect. USB drives (and ANY removable drive including usb/firewire hard drives) can be used for autorun. Most likely the reason the parent could not get it to autorun is because autorun had been turned off.
If you want a great example of autorun look at Pass2Go from the Roboform guys. It sets up autorun on the USB drive it is installed on. The Microsoft wireless network setup wizard (the one the also exports the WEP/WPA keys of an existing connection on an XP machine as plain text) also sets up a USB key to autorun the wizard.
No. Workstation is geared to developers/testers. For example it supports VM teaming and multiple undo snapshots.
Yea, I draw the line between something someone uses for themselves and something that starts to get spread around to other people. If it is important for a group in the company to use then it should go through a development team. Of course, again, I can rant until the end of time about the (lack of) quality of most internally developed software. That just goes to the idea of the iron workers designing the bridge though.
See, here is the problem. It's not just enough to solve the problem with a software project. One of my customers was a manufacturing company. They had this guy at one of their plants. He knew a little clipper and wrote some apps to do calculations and such. Seems harmless enough, right? The problem was the company grew. And grew. And grew. All the while these little clipper apps became more and more and more important. The problem was they were not being updated as the OS changed the apps became more difficult to keep working. Eventually these little apps became so critical that when the company (now a good size enterprise) did their last upgrade they decided the clipper apps had to go. Problem was they had to keep them running while they replaced them. In the end those little clipper apps burned up over $30,000 in consulting time getting them installed and working (because the author had since retired) while the replacements were written by another company.
There is a reason to hired skilled trades when you are doing any project. Programming is no different. Now, granted, it's not easy to find skilled programmers (you should hear me rant about 6-figure vertical apps that look like they were written by monkeys on dope).
The tone of your post tells me you are one of those end users who has no formal education in software design, computer science, or even a tech college programming class. I have no problem with some end user writing a quickie app to solve some simple, quick problem for themselves. What I have a problem with is when that end user begins to think that he/she is a software developer and starts trying to write full fledged applications. Then you get crap apps. Then I get to spend hours of my customer's time (and money) trying to get those POS applications to work in a multi-user environment. Had the programmer taken the time to actually learn how to actually do the job they were pretending to do it would be a snap. However since that usually isn't the case I end up having to force the OS to conform to the application, instead of the other way around (aka: the right way).
To put it another way: I'm sure you could probably build a somewhat functional bridge. You'll just have to pardon me if I don't drive over it.
Did you even bother to read my post?
"Don't knock modular configuration that can be changed/transferred/backed up by simply handling a file. The Windows apps I like the most are the ones consisting of a binary, some support files and a config file. They don't need to be "installed" which usually just means implanting the same config into the atrocity that is the registry."
The parent that I replied to implied it. In most cases that is also how they are (mis)used. Yes, you would put an INI file in each user's profile directory or home directory if the software author did their job correctly. Too bad that's usually not the case. INI files are supposed to be broken into two parts: computer and user specific. Just like the registry with Local Machine and Current User. Like with the registry however, many programmers treat INI files as one entity and stuff everything into one file. To make matters worse they usually access it as a text file instead of using the built in APIs (if you work with Terminal Services or Citrix you understand why this is a problem) and they store it in the program directory. It works on their machine so it must work on everyone else's, right?.
...and that brings us full circle back around to my original post: if programmers actually followed Microsoft's design users would not need admin rights to run most applications.
That I have to agree with you on. VB6 and the programming mentality it fostered did a lot of damage to the quality of Windows software. MS released a very easy to use, very popular language and IDE without giving it the ability to use the system properly. For example it had very limited support for using the registry.
That's great. That also means that every user most likely needs write access to that INI file. What if more than one user needs to use it? Do they keep overwriting each others settings. What if more than one user needs to use it concurrently?
There is nothing atrocious about the registry. If developers would learn to put stuff where it belongs and to clean up when they uninstall it works perfectly. That said, there is a proper way to use ini files in Windows and that means you don't open/close it as a text file and you don't store user settings in a single ini file located in the program directory.
Windows provides API to handle global and user ini file information and if used properly you don't run into issues like the ones I stated above.