Put the knife down and take a green herb, dude. (c) Ruffin Bailey 2001-2021

Upgrading a user to Windows Vista from Windows 2000 | User Support | TechRepublic.com:

For this option, when you try to activate the software, you’ll be told, The Software Licensing Service determined that this specific product key can only be used for upgrading, not for a clean install. At this point, all you’ll have to do is install Vista again, but this time you’ll be upgrading to Vista from Vista. That sounds strange, I know, but it’s true. When you install Vista a second time, you’ll want to do it from the new installation of Vista, not by booting from the DVD. You do want to enter the product key the second time around, and you do want to choose the upgrade option.

Labels: os x, problem solved, vista, windows

From Microsoft's press release about Office for Mac:

The group also is providing a glimpse at the road map of Office for Mac by announcing the return of Visual Basic for Applications (VBA) in the next version.

You've got to be kidding me. After all the crap that went up on the MacBU blog about how vba was dead and the requisite flaming from the Littles that vba was make or break, it's the MacBU that caves. I'm so confused.

* Why take the PR hit by saying vba was gone?
* Why bother with replacing vba with AppleScript in the most recently released version of Office for Mac?
* Why not just have updated the old Office for Mac with new Office formats and saved the brand new AWESOMEO 3000 engine for when vba was ready?

(You know, I never really understood why it was so impossible to port vba to this new Office for Mac. Isn't the whole point of .NET that it's easily deployable on new platforms? .NET is, in many ways, Java for Windows, with interpreted code running in a sort of Virtual Machine. And if M$ is eating their dog food, shouldn't much of the vba engine for Windows be written in .NET? Borrow the Mono project's compiler and off you go... It should be easier to port a vba engine from scratch now than ever before, right?)

Right choice or no, this is a cluster. I'd argue this seems emblematic of Microsoft in general since they decided to go Vista. They're chasing cash now more often than making smart decisions.

Labels: .NET, business, microsoft, office, vista

title: Put the knife down and take a green herb, dude.	descrip: One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!! Back-up your data and, when you bike, always wear white. As an Amazon Associate, I earn from qualifying purchases. Affiliate links in green.
x MarkUpDown is the best Markdown editor for professionals on Windows 10. It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support. Features you won't find anywhere else include... MarkUpDown Multiline Table & Bootstrap Grid support. Beautiful Easy Actions that keep the Markdown flowing. HTML paste to paste HTML source into your documents. You've wasted more than $15 of your time looking for a great Markdown editor. Stop looking. MarkUpDown is the app you're looking for. Learn more or head over to the 'Store now!

Sunday, November 29, 2009
Magic Mouse works in Vista -- scrolling too When I first tried Apple's Magic Mouse in Vista, I only got right and left clicks, and had to hold it slightly skewed to get it to move the mouse accurately. Now, not only does it work in 10.4 (minus scrolling), it works in Vista with scrolling, horizontal and vertical, no problems. Nice little upgrade. I'm assuming the most recent Apple auto-update added that little holiday gift there. Neat mouse. Labels: apple, mouse, vista posted by ruffin at 11/29/2009 09:57:00 PM

Wednesday, June 10, 2009
Installing Vista Upgrade on OS X? Maybe. Upgrading a user to Windows Vista from Windows 2000 \| User Support \| TechRepublic.com: For this option, when you try to activate the software, you’ll be told, The Software Licensing Service determined that this specific product key can only be used for upgrading, not for a clean install. At this point, all you’ll have to do is install Vista again, but this time you’ll be upgrading to Vista from Vista. That sounds strange, I know, but it’s true. When you install Vista a second time, you’ll want to do it from the new installation of Vista, not by booting from the DVD. You do want to enter the product key the second time around, and you do want to choose the upgrade option. Labels: os x, problem solved, vista, windows posted by ruffin at 6/10/2009 02:30:00 PM

Wednesday, May 14, 2008
VBA back for Mac Microsoft Office From Microsoft's press release about Office for Mac: The group also is providing a glimpse at the road map of Office for Mac by announcing the return of Visual Basic for Applications (VBA) in the next version. You've got to be kidding me. After all the crap that went up on the MacBU blog about how vba was dead and the requisite flaming from the Littles that vba was make or break, it's the MacBU that caves. I'm so confused. * Why take the PR hit by saying vba was gone? * Why bother with replacing vba with AppleScript in the most recently released version of Office for Mac? * Why not just have updated the old Office for Mac with new Office formats and saved the brand new AWESOMEO 3000 engine for when vba was ready? (You know, I never really understood why it was so impossible to port vba to this new Office for Mac. Isn't the whole point of .NET that it's easily deployable on new platforms? .NET is, in many ways, Java for Windows, with interpreted code running in a sort of Virtual Machine. And if M$ is eating their dog food, shouldn't much of the vba engine for Windows be written in .NET? Borrow the Mono project's compiler and off you go... It should be easier to port a vba engine from scratch now than ever before, right?) Right choice or no, this is a cluster. I'd argue this seems emblematic of Microsoft in general since they decided to go Vista. They're chasing cash now more often than making smart decisions. Labels: .NET, business, microsoft, office, vista posted by ruffin at 5/14/2008 11:27:00 AM

Friday, March 14, 2008
Thanks for the reboot, Vista Quick note to say I wasn't real impressed to see that Vista had installed updates and rebooted without asking last night. This morning, all the browser windows I'd had opened, the documents I was editing, etc, were no longer open. Why not save what was going on into memory somewhere? Understanding that the updates make it hard to boot into exactly what you were looking from before, I still have to think the machine could keep some track of, say, my MS Word docs that were open. Firefox does a good job remembering "sessions"; why can't anyone else? Labels: vista posted by ruffin at 3/14/2008 09:34:00 AM

<< Older \| Newer >>