Archive for the ‘Windows Vista’ Category

h1

Monaday #3

December 24, 2007

powershell logo I may have done PowerShell a disservice in previous posts in the Monaday series. It seems it isn’t really aimed at the private user at all.  It looked like it was intended as a replacement for the DOS command prompt but maybe the latter is not quite ready for pensioning off.

PowerShell, it would appear, is a scripting tool for administrators. I guess Microsoft envisaged that IT departments running large numbers of servers will use PowerShell scripts to automate common tasks, and it will in general be a specialist tool for professionals.

That is certainly the impression I had from Paul Thurrott in the latest episode of the Windows Weekly podcast, and is confirmed by this website.

On that basis I am ending the Monaday series at #3. I have no particular use for PowerShell at the moment and plenty more useful toys to play with.

AddThis Social Bookmark Button

h1

No end to the Vista hate mail

December 19, 2007

Vista busy cursor Following on from CNet UK dubbing Vista one of their “Top ten terrible tech products”, PC World have declared Vista their “Biggest Tech Disappointment of 2007“.

I can’t argue with that given the scale of the product, the long wait and Microsoft’s own hype.

I don’t agree with everything PC World say about Vista. In some cases they’ve been too nice about it:

“… the Aero interface is as whizzy as it gets …”

No way! There’s far more “Wow!” to be had from Mac OS X, even, or Ubuntu Edgy in harness with Beryl/Xgl. Aero Glass delivers little more than could have been achieved under the XP CPU-centric user interface. Putting the graphics card’s 3D capabilities in charge of the UI should have yielded more than some semi-transparent window borders and a gimmicky flip 3D window selector that you play with once then never bother with again. Utterly devoid of flair and imagination, and above all playing it “safe”. That is what I call truly disappointing.

“Despite its hefty hardware requirements, Vista is slower than XP.”

Erm … surely it’s because of its hefty hardware requirements that Vista is slower than XP. Vista demands more resources so on the same machine it runs slower.

Well, some of the points made in the article were right. Who knows? Maybe PC World are top of Microsoft’s list of “disappointing journalists of 2007″. Or more likely second behind CNet UK.

AddThis Social Bookmark Button

h1

What’s a business’s business case for Vista?

December 18, 2007

Vista busy cursor It was mentioned to me just recently that one of the world’s largest global firms is actively planning to roll out Vista during the course of 2008, in at least one major territory.

Now I’m sure there are businesses which have moved to Vista but the word on the street is that uptake of Vista by business is barely evident.

You have to ask the question. Why would a business migrate from (in general) XP to Vista? The decision process is unlike for personal or domestic use. There has to be a business case. You have to show that the change benefits the company in terms of one or more of:

  • More money in (more sales, better productivity)
  • Less money out (reduced costs, efficiency savings)
  • Less risk (contingencies that could reduce income or increase cost)

We’re talking here about the OS on computers used by employees: desktops or more commonly laptops. This is not about servers or other infrastructure.

Remember also that Windows is even more dominant in the business world than in the domestic environment. Increasingly, people buying computers for personal use might consider a range of options: Windows, Mac, Linux. Which OS happens to be the most fashionable or has the biggest “Wow!” factor comes into the reckoning.

Not so with business, where very nearly everyone uses Windows and choices are governed by what is good for revenues and profit.

With all that in mind, I say again – why would a business migrate to Vista? What’s in it for them? Let’s examine this under our three key headings.

More money in

The case for extra productivity from Vista is pretty thin. The fundamental raison d’etre of Vista is to mark the advance from a CPU-centric to a GPU-centric user interface. That is, use the graphics card to take responsibility for what the user sees on the screen, in the fashion of a 3D computer game, to escape the limitations of the 2-dimensional graphics world. This was going to happen to Windows sooner or later, but it is clear Microsoft were rattled by the fact that the Mac OS X got there first and by a margin of some years. All the same, the Mac is not (yet) a serious threat to Windows in the business arena. And how important is a whizzier OS user interface in the world of business? Specially when it is only imperceptibly whizzier. Vista’s GPU-centric UI barely makes use of the new 3D graphic possibilities unleashed by the technology change.

User interface apart, there is precious little else new in Vista you could point at and suggest it will make people more efficient or productive. Maybe the better indexing and search for finding documents, but there are solutions for this which avoid an OS upgrade.

Less money out

With Vista we’re looking at a case of more money going out, not less. There is an overhead involved in moving to Vista, starting with the IT department. A lot of testing is required to identify impact on other applications and technologies used in the business. It is well known there are plenty of applications which work in XP but not in Vista, so there will also be costs in knock-on upgrades of other software or work-arounds/fixes.

There is a hardware cost. Vista needs a decent graphics chip (not always included in laptops), an up to the minute dual core processor and plenty of RAM. Even if Vista is only provided on new or reimaged PCs, the standard hardware spec will need to be beefed up, with associated cost.

To the extent that Vista misbehaves from time to time (lock-ups, disk-thrashing, slow response) there will be an impact on productivity, but this should not be a significant issue if the IT department have done their jobs and the hardware spec is right.

Managing and implementing the whole migration will itself give rise to an overhead.

Less risk

Vista is claimed to be “more secure”. Well there is User Account Control (UAC) but it is poorly implemented and tends to cause more annoyance than it’s worth in terms of security benefits. Maybe UAC needs to be accounted for under lost productivity due to the related nuisance factor.

Other security features such as Data Execution Prevention (DEP) and built-in firewall are already available in XP.

Given that most big firm IT departments already have security well handled under XP it is questionable whether Vista adds anything much.

I would argue that introducing Vista is far more likely to increase risk. Anything which disturbs a settled, mature, well-understood status quo is only going to add risk. In a real corporate IT situation, with elaborate infrastructure and myriad complex applications and information interconnections, there is a real risk that something somewhere will go awry when you make a change of OS of this magnitude, however well you’ve done your homework.

In favour of Vista, there is the argument that Microsoft will not support XP forever. But they have already extended support once (under pressure from businesses – what a surprise!) and may have to extend the deadline again. The replacement for Vista, Windows 7 (codename “Vienna”) will probably be launched before support for XP is finally pulled.

- 000 -

Based on all of this the business case for Vista is just not there.  On the other hand, the case against is well nigh bullet proof. Little wonder businesses have been less than enthusiastic about making the switch.

So what about this big company I referred to at the top of this post? Beats me. Maybe they think it’s the natural thing to do. Move with the times and all that. Maybe Microsoft are offering them an attractive deal? Who knows. That would certainly have to come into the reckoning.

Maybe they think embracing Vista makes them look like they’re in step with technology. I’d suggest they would make a better impression, as a business to admire, if they made it clear they had done their homework and established a clear business case for sticking with XP.

AddThis Social Bookmark Button

h1

Monaday #2

December 17, 2007

powershell logo At first I was quite enthusiastic about PowerShell. Far better to have a modern scripting shell, made of the same fabric as current versions of Windows, than some stale leftover from 16 bit DOS.

Having taken my first few tentative steps, I set about creating the PowerShell equivalent of a DOS batch file. It would be an interesting learning process to, say, migrate my command line solution for video encoding to the new scripting medium.

I soon discovered the PowerShell equivalent of the .bat file is the .ps1 file. Simple experiment: put a PowerShell command such as “get-process” in a text file, save and rename so it has a .ps1 extension, double-click and it should run. But it just opens as a text file.

A bad sign. The .ps1 extension does not become associated with PowerShell when you install the latter. You can of course associate .ps1 with PowerShell manually. I tried that, double-clicked, PowerShell opened …. (yes! yes!) … then a load of red error messages appeared for a couple of microseconds and PowerShell closed again.

Apparently there is no way to run a PowerShell script by double-clicking a script file in an explorer window. You have to launch PowerShell manually and then run the script explicitly, giving its full pathname. This is for security reasons. It’s all explained here and is all about preventing “command hijacking”.

No wonder the .ps1 file extension does not get associated with PowerShell. There’s no point if you can’t run a script by clicking on the file.

Well I’m delighted that PowerShell is so secure, but less thrilled that it’s so inconvenient to use. So inconvenient as to make it all but useless. What is the point of a scripting language if you can’t use it to make life easier by replacing a series of commands with a simple click? Am I missing something?

I’m well aware of the security issues, including command hijacking, but there must be a better way to stop hackers dead in their tracks than crippling the scripting system to the point where it’s more trouble than it’s worth to use it.

What is Microsoft’s strategy here? Do they want to promote the new and safer PowerShell and phase out the old DOS box? You’d think so. To achieve that they need to encourage users to adopt PowerShell by promoting it and making it easy to use. But there is scant publicity and the security lock-down is a killer. Meantime the DOS box is still there with all its security vulnerabilities.

Which of the two do Microsoft expect real people to use? How does releasing a technologically up to date, secure but inconvenient new scripting system, while leaving the old insecure but easy to use system in place, help anyone migrate towards safer practices? Or reap any benefits for that matter?

I’m in two minds whether to bother with Monaday #3 et seq. If the DOS box is dead then PowerShell may soon be joining it in the same coffin.

AddThis Social Bookmark Button

h1

Vista Temperature Check

December 11, 2007

Vista busy cursor Judging by the search strings which bring visitors to this website, the pattern of problems encountered by Vista users is changing. There are still people looking for solutions to slow performance and freezes, but there are far larger numbers more concerned with specific issues, such as how to enable the audio “what you hear” channel (which Microsoft deliberately crippled in Vista) or why it is almost impossible to do any kind of video encoding in Vista without something major crashing.

Here is a selection of “Vista problem areas” (in order of number of relevant hits on this site) and the related search strings:

COM Surrogate and Windows Explorer Crashes Associated with Video encoding

Description:
Tendency for the “COM Surrogate” process to crash when encoding video, and for drag/drop operations on video files to crash Windows Explorer where certain video codecs are used.

Related posts:
Vista’s Video Nasties

Search strings:
Host Process of windows services stopped, folder containing video crashes explorer, vista avisynth avi fail, com surrogate, program crash opening avi file in vista, what is COM Surrogate, windows explorer crash dllhost.exe, dllhost.exe com surrogate + vista, xvid com surrogate, recycle bin explorer crash windows vista, avi encoding pc crashes vista, explorer crashes when moving folders, recycler bin explorer crash windows vista, Vista crashing a lot com surrogates, buffer overrun while running mp4 content, mp4 crashes vista, vista and video crashes, DllHost com surrogate vista, why is video playback so bad in vista, Video crashes explorer vista, buffer overrun while running mp4 content, dllhost com surrogate vista, dllhost COM Surrogate in the DEP

“What You Hear” Disabled

Description:
Disabling of “stereo mix” or “what you hear” audio channels

Related posts:
With Vista what you hear is not what you get

How to get what you hear

Search strings:
recording what you hear on vista, “what you hear” in vista, vista audio capture what you hear, stereo mix vista, what you hear sound driver, vista disabled audacity streaming audio, enable what you hear in vista, what you hear audacity, “Stereo Mix” o “What you hear” vista, what you hear windows vista, “what you hear” vista, audacity “what you hear”, vista record what you hear

Nero 6 does not work with Vista

Description:
Nero 6 does not install or does not work correctly in Vista

Related posts:
Nero Burning Rage
ImgBurn the answer?

Search strings:
fix for nero 6 in vista, nero will not work on vista, nero burning update for vista, problem nero 6 not working in vista, Specified host adapter invalid nero, nero burning on vista compatibilty

MS Visual Studio 6 does not install correctly on Vista

Description:
Installation of Visual Studio 6 on Vista does not complete correctly so that service packs cannot be installed

Related posts:
Getting Visual Studio 6 to install on Vista

Search strings:
Is Visual Studio 6 compatible with Vista, vb6 vista ole error, vista & vs6, visual studio 6 vista compatible, “Visual Studio 6″ Vista, visual studio 6 setup fails, visual studio ver 6 vista, install visual studio 6 on vista

Confusing UAC messages caused by some startup programs

Description:
Vista repeatedly blocks some programs that launch on start-up (eg Adobe Update Manager) because they trigger User Account Control

Related posts:
Now UAC it, now you don’t
Vista: Confusion, alarm and annoyance all rolled into one

Search strings:
vista blocking adobe update manager, vista startup items always ask, vista startup programs safe to stop, adobe update manager and windows vista, adobe update manager vista startup

Vista’s Slow performance & Tendency to Freeze

Description:
Vista tends to perform sluggishly, particularly on lower end machines, and can lock up altogether with some applications

Related posts:
Vista and the Curse of the Rotating Blue Bagel
What’s so great about Vista that it’s worth crippling my PC for?

Vista’s Morning Sickness
Vista’s voracity for RAM
The suckiness of Vista was evident long ago
The majority of Vista PCs being sold right now aren’t powerful enough to run Vista
Well worth the upgrade from Vista to XP
Dipping my toe back in

Search strings:
Performance/freezing issues with iTunes iTunes runs slow on vista, itunes vista freeze, itunes slow launch vista, does itunes slow down vista, itunes causing vista to freeze Relevant posts Vista performance, resource requirements vista runs like a dog,”windows vista runs slow” “cpu”, superfetch sucks, 1gb enough vista Relevant posts Vista freezes vista freeze, why does vista freeze right up, busy cursor freeze vista

AddThis Social Bookmark Button

h1

Monaday #1

December 10, 2007

powershell logo The DOS box is dead, long live the DOS box!

Except we now call it Windows PowerShell 1.0. Originally codenamed “Monad”, Windows PowerShell is a replacement for the old familiar cmd.exe DOS prompt. It provides a command line interface with Windows but is claimed to be a major advance.

PowerShell works with both Vista and XP SP2 but is bundled with neither. It is though freely available for download from Microsoft here.

This is an old-ish article on Monad, but still interesting background.

I’ve decided to start a series exploring PowerShell, weekly on a Monday, so I’m calling it the Monaday series. Quirky, I know, but it will remind me to post a new item on time.

So far I’ve not got much further than downloading and installing it. But I have made a useful discovery. The old DOS commands (think of dir, cd, etc) seem to work on PowerShell so Microsoft appear to have had the good grace to make it backwards compatible. Still, we’re supposed to get used to the new style commands with a verb-noun format (eg get-process) because that will make use of PowerShell more intuitive as we get into it more. The clever bit is that if you use the get-help command with an old DOS keyword it will give you the new format equivalent, as in the example below:

windows powershell monad

The old DOS box is still available but I’m hoping to learn, over the coming weeks, whether PowerShell genuinely is the more modern and technically superior alternative.

AddThis Social Bookmark Button

h1

Vista’s Video Nasties #4: H.264 recipe revealed

December 4, 2007

Vista busy cursor Here is the promised magic recipe, the complete solution, for automated H.264 encoding on Vista (or XP for that matter).

(Note that since I first published this post I have found an alternative, direct way to embed video into blogs where the video quality is as high as I wish. Details are here.)

Scenario

Input: The video to be encoded is an avi file in DV format, such as you might capture from a camcorder using Windows Movie Maker or other video editing application. The video may have been edited, so long as the edited footage has then been saved in DV format in an avi file. Audio content is assumed to be in PCM (uncompressed) format, typically with a 48,000 Hz sampling rate.

Output: The encoding process results in an mp4 file containing H.264 encoded video and AAC audio. The output file is suitable for uploading to on-line video hosting services such as youTube or vimeo.

Defaults: The default settings are video resolution of 448 x 336 and H.264 encoding quality of 26. These can be overridden by changing the relevant lines in the video.avs and video.bat files (see below).

Preliminary

It makes sense to create a folder on your PC where you will keep the relevant programs and working files. For the purposes of the post I will assume this is c:\videoenc

What you need to download and install

AviSynth

AviSynth 2.5 is a frameserver which we use here to perform the preliminary processing such as cropping and deinterlacing. Download the file Avisynth_257.exe from here. Run it to install AviSynth. Accept all defaults.

Smooth Deinterlacer

Get it from here and save the file smoothdeinterlacer.dll to c:\videoenc. Be sure to select the version designed to work with AviSynth 2.5x not the older version for AviSynth 2.0x.

x264

This is the H.264 encoder program itself. You can get it from here*. Click on any of the mirror links, e.g. mirror 01, next to x264.exe in the table of encoder download options. Save the x264.exe file to c:\videoenc. You don’t need to install anything. The file just needs to be in that folder.

[*Update 5 Dec 07: The link above appears to be down or unreliable. I have found another source for the x264.exe file here but have not yet had the opportunity to check its origin, version or to test it]

MP4Box

MP4Box takes the raw compressed video file and places it in an mp4 container file. The program is available from here. I downloaded version 0.4.4 compiled 3 June 2007. Again, you just need MP4Box.exe to be in the folder c:\videoenc.

MPlayer

You can get this from here. Download “MPlayer 1.0rc1 Windows” (not the GUI version) from any of the mirror site links. You need MPlayer to extract the uncompressed audio from the DV video file, so it can then be compressed as AAC audio. You only need the mplayer.exe file. Put it in c:\videoenc.

faac

The utility that compresses your extracted audio in AAC format. Available from here. Download the faac-1.26.1.zip file. Place the faac.exe file in c:\videoenc.

Creating the text files that automate the process

Within the c:\videoenc folder create a text file called video.txt. Open it and copy the following text into it:

LoadPlugin(“SmoothDeinterlacer.dll”)
DirectShowSource(“c:\videoenc\video.avi”)
SmoothDeinterlace(tff=false, doublerate=false)
LanczosResize(448,336)
converttoyv12()

Close it, saving the changes. Change the filename to video.avs.

Next create another file called video.txt. Open it and copy the following text into it:

@ECHO OFF
x264.exe –fps 25 –qp 26 –progress –output video.264 video.avs
MP4Box -flat -add video.264:fps=25 -v -new video.mp4
mplayer -vc null -vo null -ao pcm:fast video.avi
faac -b 128 –mpeg-vers 4 audiodump.wav
MP4box -add audiodump.aac video.mp4
PAUSE
CLS
EXIT

Close it, saving the changes. Change the filename to video.bat.

NOTE: The commands in video.bat as shown above assume a PAL DV source hence a frame rate of 25 fps. If your source video is in NTSC format you need to modify lines 2 and 3 to refer to a frame rate of 30 fps.

Encoding a DV avi file

Just save your raw or edited DV file to the c:\videoenc folder. It has to be called video.avi so save it under that name or rename it as applicable.

Double click the video.bat file in the same folder.

That’s it. The whole encoding process will now run from beginning to end under control of the commands in that file. You can go and make a cup of coffee.

Meantime a DOS box will open and display lots of stuff. Eventually, the display stops changing and the bottom line reads “Press any key to continue …” When you do that the DOS box disappears.

You can then find your encoded file, containing H.264 encoded video and AAC encoded audio, in c:\videoenc. It is called video.mp4. You can now upload it directly to youTube, vimeo, veoh, whatever.

Changing settings

The default resolution is 448 x 336 pixels. If you want something different just change line 4 of the video.avs file. You can just open the file with Notepad to make the changes. You must though ensure that both the horizontal and vertical resolutions are multiples of 16.

The default H.264 encoding quality is 26, on a scale from 1 to 51, using single-pass encoding. You can modify the quality setting by changing the “qp” parameter in line 2 of video.bat. Lower values for qp improve quality but increase the bitrate and filesize, vice versa for higher values.

In principle it should be possible to obtain better quality for the same filesize by using 2-pass or 3-pass encoding. So far I haven’t seen much improvement in my experiments with multi-pass encoding but it’s early days. I’ll report on my discoveries in a future exciting episode of Vista’s Video Nasties.

Credits

I found this very helpful when I was getting started with a command line solution for use of x264. It seems to be part of an encoding guide that looked highly promising but was abandoned years ago. Shame.

The rest of it was down to trial, error and slog.

AddThis Social Bookmark Button

h1

Vista’s Video Nasties #3

November 30, 2007

Vista busy cursor I promised in #2 of the Vista’s Video Nasties series that I would publish a complete Vista-compatible solution for producing decent quality H.264 mp4 videos from camcorder DV footage, for uploading to on-line video hosting services such as youTube and vimeo.

I have my solution sorted and it will appear shortly as #4 in the series.

What gets me is that I have had to resort to DOS-style batch files, having had no joy with Windows user interfaces for x264 such as meGUI.

The batch file approach is not so bad. Once all the right command line instructions are in place you can double-click your batch file and the entire encoding process is pretty much automatic from there.

It does though seem ironic that despite two decades of successive versions of Windows, each supposedly a step forward from its predecessor, the technology is still so rickety that you can find yourself having to resort to the world of DOS when things get too complicated.

AddThis Social Bookmark Button

h1

The public lambasting of Vista goes on

November 28, 2007

Vista busy cursor More public criticism of Vista courtesy of CNet UK. This time Vista’s qualities are celebrated by inclusion in CNet’s alarmingly alliterative “Top ten terrible tech products” parade, alongside all time venerated designs such as the Sinclair C5 and Amstrad’s E-m@iler Telephone.

From CNet’s Crave column:

“Any operating system that provokes a campaign for its predecessor’s reintroduction deserves to be classed as terrible technology. Any operating system that quietly has a downgrade-to-previous-edition option introduced for PC makers deserves to be classed as terrible technology. Any operating system that takes six years of development but is instantly hated by hordes of PC professionals and enthusiasts deserves to be classed as terrible technology.

Windows Vista conforms to all of the above. Its incompatibility with hardware, its obsessive requirement of human interaction to clear security dialogue box warnings and its abusive use of hated DRM, not to mention its general pointlessness as an upgrade, are just some examples of why this expensive operating system earns the final place in our terrible tech list.”

I really can’t argue with any of these points. They are borne out by my own experiences and conclusions as reported in this blog.

The best thing you can say about Vista is that not everybody hates it. Hardly “The WOW Starts Now!”

AddThis Social Bookmark Button

h1

How to get what you hear

November 25, 2007

Vista busy cursor In a comment to my previous post, Jay of vistasucks fame pointed out that Microsoft deliberately disabled the “what you hear” and “stereo mix” audio input options in Vista to stop people using software such as Audacity to strip DRM from audio content.

It makes a lot of sense. You could play back an encrypted song on say iTunes while recording it off the “what you hear” channel using Audacity. The resulting sound file would be a new, unencrypted recording.

I guess there would be some loss of quality because the recording is capturing the signal after conversion from digital to analogue for playback over your loudspeakers. Still, many users wouldn’t care too much about that.

Jay is probably right about Microsoft crippling part of the audio functionality in Vista deliberately to thwart DRM circumvention and please the record labels. He is not alone in being of that view. It would be entirely in keeping with the pandering to the studios that has led to the elaborate copy protection systems built into Vista for HD video playback.

Happily, Microsoft’s dabblings are not terminal. All you have to do is flush out Microsoft’s DRM friendly audio drivers by installing the drivers provided by the soundcard manufacturer. In most cases, the proprietary drivers will support “what you hear”. The low down on the whole process is described here.

In my case that meant downloading and installing the Asus AudioMAX drivers for my on-board sound chip. I could then enable “what you hear” and “stereo mix” from the Sound applet in the Windows Control Panel as described in the Audacity link above.

I call this the Silk Purse solution.

AddThis Social Bookmark Button

Follow

Get every new post delivered to your Inbox.

Join 383 other followers