May 2004 - Posts
Recently published was my brief article to Developer.Com on the Longhorn Speech API, and how to do some basic recognition and synthesis. Code sample included!
The Longhorn Speech API, an Initial Glance
During college, the book that got me into developing client/server apps, and in fact the book that I learned Java with was
Advanced Java Networking by Prashant Sridharan. Now I learn that in the meantime, he has since
moved to MS from Sun, worked on the J++ team, and migrated to Product Manager on the C# team...Very cool!
I've been looking into the inner workings of Longhorn 4074, and have discovered there's much more here than meets the eye (or keyboard). I'm sure a lot of this is under wraps because it's not MS' way to put forth something that's not usable yet (see the hidden windows manager command for an example of this -- it's cool, but it's not working for all video cards, slow, etc...but still in development).
The c:\windows\microsoft.net\windows\v6.0.4030\ folder contains some gems... For those who regularly read my blog, you know just how much the Longhorn Speech API is intriguing me. Enter "MS.Internal.Hoolie.dll". Extended information teases "Microsoft Managed Speech Desktop SpeechServices", but the real gems are exposed with Lutz Roeder's Reflector (I just can't say enough about that little tool; every developer I know of extols the virtues of that app).
By looking inside this dll, I found icons and methods, and windows, and alternate spellings etc. for a speech interface. In fact, by digging further, I believe "Hoolie" is the codename this windows component is going by. There is in fact an install file at "C:\windows\inf\hoolie.inf". I just wonder how to install it in 4074, if it's even possible...
My saga with how to fix your network connection after it goes haywire in Longhorn.
This is how I fixed mine; I hope it will be some help to others as well!
http://weblogs.asp.net/jnadal/articles/143503.aspx
I say “optimization” because this may remove features that could be important to you if you are a developer, but the authors of the pdc Longhorn Optimization Guide, under the noms de plume Chris123NT and Nighthawk, have written another one for build 4074.
The guide is located here, and another called a Tweak Guide here; they again carry the risk of removing some things that you might want, like say Internet Connection Firewall... I'm just saying :)
Visual Studio 2005 Team System Documents
MS has just published a cache of useful info about visual studio team system 2005; check them out!
As Wally McClure
posted first, the MS speech sdk version 1 is released, and is available
here.
The download ran me 295mb, and contains extensions for VS2003, enabling users to create SGXML (speech grammar xml files) therein.
With 4074, Terminal Services doesn't get it's own element in add-remove programs. However, since IIS is not installed by
default, you'll have to add the Terminal Services web access application yourself. Here were my steps to getting Remote access
working for me.
1. Control Panel - Add/Remove Programs:
Add or Remove Windows Components
Check IIS 7.0, run details
Go into details for WWW Service
Make Sure WWW Service and Remote Desktop Web Connection are checked.
Hit all OK's
2. Control Panel - System
Remote Tab
Check "Allow users to connect remotely to the computer"
Click "Select Remote Users" and add your user to the list
3. You're good to go... Add a magic packet tool, and you can remote access in style.
Microsoft has entered the translation business with the announcement of “Microsoft Application Translator (MAT)”. The announcement is intriguing. The betaplace guest id is: MATGuest (case sensitive). This will allow applications to change their localized language on the fly, without the developer having to do the legwork.
Check out this link for more information!
The best part? From the FAQ:
How much does MAT cost?
MAT is completely free of charge and is provided as a resource to ISVs, developers, and Windows users.
More Posts
Next page »