Thursday, June 14, 2007

I gots my favicon back

A while back, this blog was updated to the new Blogger and I was the custom icon that was displayed with my blog.  And of course, I forgot where I had hosted the icon.  I came across an blog posting for MyFavatar, a free site for hosting favicons for blogs.  I decided to give it a shot and it's one of those things that just plain works.

They made it pretty simple.  You register for an account, upload an image, and they create the .ico file from the image.  They even provide the html to enable favicons in your blog.

Enabling Database Diagrams in SQL Server 2005

I was working on a spec for a new feature in our flagship application, when I wanted to included some simple database diagrams.  I was adding some new schema and I wanted to reference them in the spec.  I figured I would just do the schema changes in a spare database and make a database diagram.

I opened up MS SQL Server Management Studio (SSMS)) and connected to the database on a box running SQL Server 2000.  I selected the database and then selected "Database Diagram".  SSMS got huffy about how the database diagrams in 2000 were nothing like the feature in 2005 and it wouldn't touch it.  Gee thanks,  Microsoft.  The SQL Server team should have borrowed Raymond Chen for a while.  That wouldn't have happened on his watch.

I connected to a SQL Server 2005 box and made my schema changes in a scrap database.  I selected database diagram and got a lovely error dialog with the following message:

Database diagram support objects cannot be installed because this database does not have a valid owner.  To continue, first use the Files page of the Database Properties dialog box or the ALTER AUTHORIZATION statement to set the database owner to a valid login, then add the database diagram support objects.

So I took the error message literally and took a peek at the owner.  I was the owner, and I have admin rights on that box. [Insert annoyed grunt here].  So I tried making sa to the owner, same error.  That obviously wasn't the problem.

After a wee bit of googling, I came across the root cause of the error.  It was not an ownership issue, it was a database version issue.  We support both SQL Server 2000 and 2005, all of our databases are version 2000 compatible.  You can't have 2005 database diagrams in a 2000 database, even it it's attached to a 2005 server. 

There are a couple of ways to change the database, I opted for the T-SQL method:

EXEC sp_dbcmptlevel 'MyDataBase', '90';

The sp_dbcmptlevel is documented here.  The value "90" corresponds to the version number of SQL Server 2005. I ran that command and I was able to add database diagram support to the database.  You can also make the change via SSMS with the following steps:

  1. Write click on database.
  2. Click on Properties.
  3. Click on Options.
  4. Change the Compatibility level to desired compatibility.
  5. Click OK.

After doing all of that, I really disliked the look of the tables in the database diagram.  It looked like the tabled editor from Access '97.  So I ended up doing what I should have done in the first place, created a database diagram in Visio and copied that into my spec document.

Tuesday, June 12, 2007

When other people host your data....

You are at the mercy of your hosts when they hold your data.  Using an online feed reader like Bloglines or Google Reader means that someone else is backing up your feed subscriptions.  This is usually a good thing, except for when they accidently delete all of your subscribed feeds.  That happened to Steve Tibbet today.  And not just Steve, it happened to a bunch of people.

It looks that problem has been fixed, but I immediately went and exported my subscription list to an OPML file.  I wonder if you can create a PowerShell script to automate that export.  The URL is a static link, http://www.google.com/reader/subscriptions/export.

I, for one, welcome our new Google overlords. Even so, things break and you can't rely on them to back up your data.

The $51 server.

It's been 6 months since I installed FreeNAS and it really has been like an appliance.  I back up my machine and my wife's machine with just a few batch files, based on robocopy.  I could get fancy with remote backup tools and so forth, but simple works.

I've been calling it $51 Server .  It started out as a white box pc that that I had custom built by MWave a few years back.  I had needed a Netware box for some Sybase Adaptive Server Anywhere testing and we bought a Dell Server with Novell Netware 5 on it.  It's an interesting story of how I ended up with that box, but if you want to skip the story, just jump here.

Netware was installed, but it needed to be configured.  The first thing it asked for was it's designation.  I considered naming it "One", but precious few would have caught the reference.   Usually when I get a server, I'll ask a random co-worker for the first one word that comes to mind.  I was talking to one our tech support staff and his word was "pumpkin". 

This bugged our IT manager to no end.  Normally, IT handles all of our server installs, and the server gets the name of some sort of predator.  Since I was the only one who knew Netware (which was a scary thought on many levels), the care and feeding of Netware box was my responsibility.

Getting back to Pumpkin.  After running it for a week, we had a somewhat urgent need for another Windows 2000 Server for a temporary remote access situation.  I wiped Pumpkin clean and IT installed Windows 2000 Server and named it Viper.

Temporary turned into permanent (about 6 years at this point) and I still needed a Netware box.  And of course, we did't have any more money in our budget for another server.  But we did have enough money to have a cheap whitebox built.  So for a couple of hundred, we got a Celaron 1ghz box with 256MB memory and a 20GB drive.  Video and sound were on the motherboard and we had a 3Com ethernet card that had outlived it's prior owner.  Using the usual method of selecting a server name, one of the QA people volunteered "moo" as the name.  She likes cows and it was short enough that you could easily type it with one hand with moving the hand.

Moo lasted 5 years without issues.   We used it test Sybase and it did was asked.  Our support for Sybase ended last fall and so ended our need for dedicated Netware Server.  The company sold it to me for $1.  I spent $50 on a 250GB hard drive and installed FreeNAS on it.

So for the whopping sum of $51, I have a NAS box that is completely managed by a simple web interface.

 

Technorati tags: , , , ,

Friday, June 08, 2007

User specific connection strings

Steve Harmon has a good tip on how to use ASP.NET 2.0's configSource to store connection strings in a file outside of the web.config.  You keep the user specific file out of source control and you eliminate conflicts when people use their own connection string settings.  He's not the only one to come up with that idea.

Shawn is dragged kicking and screaming into the year 2004

Shawn Gwin finally has a real blog.  As the president of the Tech Valley .Net Users Group (TVUG), it was about time that he started blogging.

Tuesday, June 05, 2007

TestDriven.NET and Visual Studio Express

There's been a lot of blog postings about Jamie Cansdale's legal issues with Microsoft in the last few days.  Jamie has a product called TestDriven.NET that integrates unit testing within the Visual Studio IDE.  The problem is that Jamie has integrated TestDriven.NET within Visual Studio Express and Microsoft would like him not to do that.

Visual Studio Express is the free version of Visual Studio 2005 intended for the hobbyist/student programmer.  Because it's free, Microsoft took a few steps to prevent VS Express from taking away sales from the other members of the Visual Studio product line.  Basically, you are not allowed to extend Visual Studio Express with additional functionality.

Jamie found to register TestDriven.NET so that it would work withing VS Express.  Jamie stated that he used published API calls, everything was above the board.  Information posted by Dan Fernandez (Lead Product Manager for Visual Studio Express) would indicate otherwise:

The TestDriven.NET product is implemented as a Visual Studio Add-In.  In the Visual Studio Standard, Professional, and Team System SKUs, TestDriven.NET is installed as an Add-In and gets loaded into the IDE through the Add-In Manager.  In the Visual Studio Express SKUs, because we disabled extensibility (macros, Add-ins, and VS Packages), the Add-In Manager is removed and therefore Add-Ins are not detected or loaded.  Jamie has created additional components specifically for the Express SKUs to work around this technical limitation.  He takes advantage of an extensibility point that allows user controls (such as a button class) to customize entries in the Properties window.  When his property extender gets called, he executes code that finds, loads and injects the TestDriven.Net assembly into the Express SKU’s running process, thus replacing the functionality of the removed Add-In Manager.  This explains why he instructs Visual Studio Express users to open the Properties window in order to enable TestDriven.NET.  Once his code is injected into the Express SKU’s running process it can add menu items, enable features that were disabled, and in general take over that instance of Express. These special loading mechanisms that Jamie has built exclusively for the Express SKUs are unauthorized workarounds to the SKUs’ technical limitations.

Right after VS 2005 was released, Microsoft contacted Jamie asked Jamie to remove support for VS Express from TestDriven.NET.  After many rounds of email and phone conferences, Jamie complied for a while.  Eventually he re-enabled support for VS Express and Microsoft is now using their lawyers to enforce their request.  You can read most of the emails and the legal correspondence here.

When I first read about this, my initial thought was Microsoft was sticking to the little guy.  That's really not the case here.  Microsoft spent a considerable amount of resources developing the Express line of Visual Studio products and it was clear from the start that you were not supposed to extend the architecture of the tool.  For that limitation, you have a powerful development environment that you could develop commercial applications with.

People have been making the argument that it's OK to extend the functionality because Microsoft is already doing it by releasing additional products (like Popfly) designed for VS Express.  That has nothing to with MS's requirement that third parties are prohibited from extending Express.  This isn't unique to Microsoft.  CodeGear does the same thing with Turbo Explorer lineup.  You can't install third party components into Turbo Delphi Explorer

Jamie appears to be stuck on the what specific part of the EULA is being violated.  I don't think it matters.  The request to pull VS Express from TestDriven.NET was a reasonable one and he should complied with it.

postscript...
It's entertaining to read the comments posted on Dan's blog, especially here.  While I'm not surprised by the number of people who just don't know the facts, there were many postings by people saying that MS vs Jamie was a reason to dump MS and only use open source tools. 

Give me a break!  If you are making decision on what tool to use over a clear cut EULA violation, you have rocks in your head.  You should be making that type of decision based on it being the right tool for the job.

Friday, May 18, 2007

Why is this man laughing?

 

There’s a story behind that picture and it’s pretty much what you would think it is.

Dave Anthony toasts his achievement after driving his truck on top of a Kent house he was demolishing. Anthony said "it was a hell of a way to kick off the Memorial Day weekend."

Somehow, it's not too surprising that alcohol was involved.  The full story can be read here.   I wonder how close he came to being a candidate for a Darwin Award?  At the very least, he should get an "Honorable Mention" for this stunt.

It gets better with the followup story:  Driving your pickup truck onto the roof of a house and getting your picture in the newspaper doesn't make a whole lot of sense when police want to talk to you about a $2,800 set of tires purchased with a stolen credit card.

Courtesy of Raymond Chen from The Old New Thing.

Tech Tags:

Time to get a new PC

My home PC died last Friday and I'm waiting for it's replacement to show up. I've had the machine for years and it's been running 24/7, something was bound to fail. The fan on the video card was starting to lock up and I'm pretty sure that the main hard drive is toast. It was a decent machine back in 2002, an Athlon XP 2000 with fast memory and drives.

The new box will be dual cores with lots of memory and RAID 5. I've lost 4 drives in the last year, I wont use another desktop without RAID. I looked at getting Dell, but I really didn't want to spend a lot of money. You can get cheap boxes from Dell, but not with what I wanted.

I like spec'ing out the components, you never know exactly what you will be getting from Dell. I've had good luck with custom boxes built by MWave. I basically picked out the components that I wanted and they assembled it and burned it in for me for a small fee. It's already been shipped, I should have it early next week

This is what I ordered:

  • Asus M2N-SLI Deluxe: A decent motherboard with everything I need on it, including RAID. The onboard sound board isn't the best one, but it will do for my needs. I'll probably salvage the Audigy card out of the dead machine if I need a better sound card.
  • AMD Athlon 64 X2 4800+ (Brisbane): Two cores and energy efficient. I never get the fastest CPU, I always bring down a few notches. The difference in speed will not be perceptable and I can spend the extra money on more memory, which will make the machine faster.
  • 2 GB Ram: With Vista, 2 GB is the bare minimum. I'll probably bump it up later
  • GIGABYTE GV-NX86T256D GeForce 8600GT 256MB 128-bit GDDR3 PCI Express x16 Video Card: It's fast, it's cheap, and it's got a big honking heat pipe to cool the card without a fan. Not having a fan means a quieter PC and one less moving part to break.
  • Maxtor 250GB SATA-300 drives: MWave had these drives fro $60, so I bought three of them for the RAID 5 array. With Maxtor's purchase by Seagate. it looks like these products were being discontinued.
  • Lite-On LH-18A1P 18X DVD RW drive: I've had good luck with Lite-On drives before and it was a good price. It's not their fastest writer, but it will be fast enough for the media that I'll be using for it
  • No floppy. The only time I have used a floppy in the last box was to flash the BIOS of the motherboard. If I can the new one to boot from a flash drive, I wont need the floppy. I may end up installing one as it's the typical way of installing RAID drivers when you do a Windows install. I could grab the floppy drive from thedead PC or get one that also has a memory card reader
  • Antec Sonta II case: I'v always liked Antec cases and power supplies and the Sonata is the right case for me. It's big enough to make working in the case easy, and it's very quiet. The main fan is 120mm, instead of 80mm. It can run slower (less noise) and push out more air than the 80mm fans. Another nice feature is that the fans and the hard drives are mounted on rubber, that really cuts down on the vibration noise.
  • Vista Home Premimum: I have mixed feelings about this one. I need more Vista hands on experience, but the horror stories are starting already. I could always install XP, if this OS is truly that awful, but I would prefer to work with Vista. This will also be my first experience with a "Home" labelled OS. I've been using XP Pro at home, but I rarely use the Pro functionality. I'm staying with the 32-bit version, even though the processor will support the 64-bit OS

Fortunately, the important files have been backed up. I put together a FreeNAS box a couple of months ago and I've been backing up source code and documents to it. The next time you buy a new PC, take the old one and toss FreeNAS on it. It just works.

Thursday, May 10, 2007

Is Microsoft Dead?

I was reading Mike Gunderloy's new blog, A Fresh Cup, and I came across a link to an article titled "Microsoft is Dead", by Paul Graham.  Paul's view is that Microsoft is no longer relevant and we live in "Web 2.0" world that Microsoft doesn't know how to play in.  He states that there are four things that killed Microsoft: Google, "the desktop is over", broadband Internet, the rise of Apple.  He's just plain wrong.

I'll give him Google.  Microsoft has never been able to catch up to Google in the search engine game.  I stil don't see how Google being the king of the hill for search engines means that Microsoft is dead.  That's like saying because apples are red, oranges suck.  It doesn't work that way.

People have been saying that the desktop is over for years.  Sun has been saying that, in one form or another, for the last 20+ years.  That has always felt like wishful thinking than future reality.  Lots of applications are well suited to run as web applications, but not all of them.  The desktop experience is just so much more richer in terms of the UI and the access to the machine than the browser experience.   Today's PC's have so much horsepower that it boggles the mind.  Why would you not want to use it?

Paul states that the rise of broadband Internet means that you have less of a need for desktop because you will faster access to the server.  All it really means is that your applications that get data from the Internet will run faster.  I use SourceGear's Vault for source control.  Vault runs a web service, but the client is a fat app.  When I changed my home ISP from TW RoadRunner to Verizon FiOS, I saw a decent performance boost when I used Vault from home to access files from the office.  Being a fat client, it can cache a lot of the data and save many round trip requests for data.  If it was a web only client, it would have been much slower, plus have all sorts of security headaches because the file system interaction. 

I have yet to see the "Web 2.0" equivalent to PhotoShop.  Silverlight opens the door to more robust web applications, but it still has limitations.  Oh wait, that's a Microsoft technology, better leave that one out.  What about office productivity applications.  Microsoft Office is a giant fat client, but so is Open Office.

What about the rise of Apple?  With the move to Intel CPU's and updated operating systems, the Apple Macintosh market share has increased over 38% within the last year.  Heady stuff and good for Apple.  Still, we are talking about going from roughly 4% of the market to around 6%.  When you view their rise in those terms, it's less of a threat to Windows.  He mentions Apple and then writes something that is just so wrong on many levels:

...Their victory is so complete that I'm now surprised when I come across a computer running Windows. Nearly all the people we fund at Y Combinator use Apple laptops. It was the same in the audience at startup school. All the computer people use Macs or Linux now. Windows is for grandmas, like Macs used to be in the 90s. So not only does the desktop no longer matter, no one who cares about computers uses Microsoft's anyway.

There are some seriously flawed statements there.  Just because the only people you see are using Macs, that doesn't apply to the entire population.  It just means that your sample set is not representative of the whole population.  I'm a computer guy and I have a few Macs and some Linux boxes.  I'm also a Windows developer and that's where most of my computer usuage occurs.  There last few lines are just insulting and are remarkably fact free.

Why do people get stuck in the useless us versus them argument?  The whole "Microsoft is Evil" argument is tired as well as the monoply charges.  There's enough room in the market place for various operating systems.  Just because you prefer one, doesn't mean it's the right choice for everyone else.

I usually ignore these types of articles, but this guy was just so wrong, it just jumped out at me.  It's clear he has an anti-Microsoft bias.  There's nothing wrong with that, but his reasoning had nothing behind it.  Paul, it's time to venture out of your "Web 2.0" bubble and see that the world is big enough everyone to play in.

Monday, May 07, 2007

Jeremy Clarkson does more than laugh at rice

I really wish I could get "Top Gear" here.  I can just watch that show for hours.  The only way I get to see any episodes is through YouTube.   I just came across this little gem:

 

Where Jeremy Clarkson destroys the worst modified car on the planet. He does more than laugh at rice, he takes action.

Friday, May 04, 2007

Ed Dague's blog has a new home

This is old news, but still worth mentioning.  Ed Dague's blog has moved from Blogspot to a new location hosted by the Albany Times Union.  If you want to learn how local news stations work, his blog is required reading.

Thursday, May 03, 2007

Domain name change

As of today, the address of this blog is now http://anotherlab.rajapet.net/.  The old name, http://anotherlab.blogspot.com, still works but you'll see the new name in your browser's address field.   I made the change after signing up for Google Apps.  I wanted to have a personal email address with my own domain and Google Apps will do that for free.  I've had rajapet.net parked at GoDaddy for the last few years (for a side project that never got off the ground), I figured I might as well use it.

After going through the steps with my domain registrar to map my domain name to Google's mail servers, it was then a trivial matter to add a CNAME Record to rajapet.net have it point back to ghs.google.com.  Once I verified that the registration had been posted to that series of tubes, I went in to the Blogger Admin page and assigned anotherlab.rajapet.net to the blog.

I signed up for Google Apps mainly for the vanity email address, but now that I have it, I want to use more of the features like the Calendar.

I'm using more and more of Google these days.  Their Google Browser Sync extension was the feature that made me switch from Opera to Firefox for most of my web browsing needs.  I bounce back and forth between six machines between the office and home and I have the same bookmarks on each machine and Google takes care of it for me.  I have been an Opera fanboy for the last few years, it took a lot to make me switch.

My blog is run on Google (Blogger).  I have a GMail account and I use Google Talk to interact with one of our remote contract programmers.  After playing around with a few desktop based RSS Readers, I switched to Google Reader.  I for one, welcome our new Google Overlords. 

 

Monday, April 30, 2007

Fun with COM and console Delphi applications

I try to make my setup projects upgradeable in place through Windows Installer.  This means that if a previous application has already been installed, the installer will do a silent uninstall before installing the new version.  The fun part is saving the current user settings across the uninstall/install divide.  Depending on the application being installed, the settings could be in the registry, a web.config files, or some other location.

What I end up doing is making a copy of the settings before the old app is removed, then restoring the settings after the new app has been installed.

Windows Installer is pretty good about firing off the save settings and restore settings actions at the appropriate time.  It's not so good at handling the actual save and restore bits.  I wrote a couple of Delphi console applications to handle that work.  With a just a few command line options, they know which application to save the settings from and how to restore them.  My installers write the app's installed location to the registry to make things like this easier.

One of the applications is an ASP.NET application.  The new version uses the .NET 2.0 Framework version, it's replacing a .Net 1.1 version.  The web config files have changed substantially, I can't copy the web.config from the 1.1 version and use it with the .NET 2.0 version.  Since I only need to save a couple of settings, I'm just having my Delphi console app ({$APPTYPE CONSOLE}), read those settings from the old web.config and update the new web.config.   I'm creating a couple of instances of IXMLDocument and reading from one and writing to the other.

To keep the size of the console app down, it doesn't use forms.  Since IXMLDocument uses the MSXML parser, it requires that the COM runtime be initialized.  That's all and good, I just call CoInitialize(nil) and match it with CoUnitialize.  When I started testing the new code, the call to CoUnitialize would crash the app, but only outside the debugger.  Those are the fun ones to debug.

Calling our trusty friend Google, I was able to quickly find a useful link.  I needed to call Application.Initialize as the first statement in the project files.  That's standard for most applications, but not usually used for console apps.  I added that line (plus the references to forms) and the error went away.  Very nice.  It added 300k to the size of the executable. Not so nice.  I looked at the source code to Application.Initialize and it consisted of just the following line:

if InitProc <> nil then TProcedure(InitProc);


So I made that the first line of code and removed the reference to forms.pas.  Everything worked, and the file size didn't take the 300k hit for code it really didn't need.  There's a lot to be said for having the source code to your runtime libraries.


Friday, April 13, 2007

SQL UPDATE from another row in the same table

My SQL skills are getting rusty.  I have some code where I needed to quickly copy a field from one row in a table to another row in the same table.  Bascially, a self-referencing UPDATE. I knew I could so it with a simple UPDATE statement, but I forgot the ANSI syntax.  Self-joining UDPATE statements can be a little squirrelly, so it's best to follow the ANSI standard.  So I went looking for the Master, Mr. Joe Celko.

I did a quick google through the newsgroups on celko update "sql Server", and I found what I was looking for on the third match.  If you really want to learn SQL as a language, Celko's books are very good.

This is what I ended up using:

UPDATE mytable
   SET filterdata = (SELECT src.filterdata
                       FROM mytable src
                      WHERE src.keyid = 5)
 WHERE keyid = 1

The table and field names have been changed to protect the innocent.

Tuesday, April 10, 2007

Understanding SQL Server error 18456

I came across an odd problem with SQL Server Express.  We have a test server with various versions of SQL Server installed for QA to use.   Of the QA techs was unable to connect to the instance of SQL Server Express when he used a SQL Server login.  The code was not returning an error error code, so I decide to take a look at it.

I tried connecting to Express from MS SQL Server Management Studio under that account.  SSMS returned an 18456 error, basically it couldn't connect.  That was just slightly more useful than what I had before, but it provide two things.  It ruled out the app as cause of the problem, and it gave something that I could google with.

The best match I got was Understanding "login failed" (Error 18456) error messages in SQL Server 2005, on the SQL Protocols blog.  Basically, the error 18456 error is purposely vague to prevent nasty people from trying to hack into your server.  To figure out why the login failed, you need the "error state".  Error state is not returned to the client, but it's written to the log file.  That file will be in the LOGS folder of that instance of SQL Server under the name ERRORLOG.   From the log file, you'll get more information about why the login failed:

2007-04-10 09:54:45.14 Logon       Error: 18456, Severity: 14, State: 8.
2007-04-10 09:54:45.14 Logon       Login failed for user 'youridhere'. [CLIENT: 10.0.0.1]



From the first line, we get the eror state.  Yay, it's 8.  So what does that mean?  The states are documented in the blog posting reference above, but I couldn't find it in my copy of the BOL.  It is documented in the online version (and probably in the latest BOL) at SQL Server 2005 Books Online.  Here are the documented states:


































State Description

2


User ID is not valid.


5


User ID is not valid.


6


An attempt was made to use a Windows login name with SQL Server Authentication.


7


Login is disabled, and the password is incorrect.


8


The password is incorrect.


9


Password is not valid.


11


Login is valid, but server access failed.


12


Login is valid login, but server access failed.


18


Password must be changed.


Any other error state is considered to be an internal error.


So it boils down to the password being incorrect, which in this case it was. 


Friday, March 23, 2007

Aero Glass on my ancient GX400

My latest video card arrived this morning and installing it was a much better experience than what I went through with the Diamond card. I have a Dell Optiplex GX400 that is about 5 years old. I installed Vista Ultimate on it so I could test apps under Aero Glass. That had ruled out VMWare. The GX400 has 5 empty PCI slots and an AGP4x slot. Since most new cards are PCI-Express or AGP8x, I tried a PCI based card. That experiment failed and I ordered a BFG GeForce 7600GS OC. It claimed to work with just about any AGP slot.

When it came in, I removed the old card and plugged in the BFG card. I turned on the PC and booted Vista up. Vista recognized the card and installed the GeForce 7600 drivers that apparently come with Vista and requested a reboot.

After the reboot, I was in 640x480 hell, but after a little twiddling I had a decent resulution and refresh rate. I did have to refresh the Windows Experience Index. It was at 1.0, hel back because of the video card. The graphics rating went from 1.0 to 5.9, and Vista enabled the Aero Glass theme automatically. The overall number was 2.7, but the CPU was the weak point, memory and HD access were 4.1 and 5.3. Good enough for what I need to do.

The BFG card was cheap in cost ($150+), but it came with a decent feature set. It will drive two monitors and I didn't have to install any drivers. It has 512MB of it's own memory and fully supports DX9. Not bad, not bad at all.

Thursday, March 22, 2007

Fixing Wise Installation System 9 problem with shortcuts in Vista

We were testing one of installers under Vista and the dreaded "User Account Control" dialog was being launched for every shortcut that was created by the installer.  Running the applications referenced by the shortcuts did not through the UAC, just the shortcuts.

I took a look the shortcuts and they didn't have a direct link to the apps.  Instead they looked like this:

"C:\Program Files\Company\App\UNWISE.EXE" /W1 "C:\Program Files\Company\App\INSTALL.LOG"


This was Wise 9's attempt to mimic the self-repair feature of Microsoft's Windows Installer.  If you are using Wise 9 Professional, you can fix this by opening the shortcut action in the setup editor and clearing the self-repair checkbox.  If you have the Standard version, you'll have to edit the installer script (.wse) with a text editor.  For each shortcut, you would remove the line of script reading 'Flags=01000000' from the Create Shortcut script action code block.  This is documented in the Altiris Knowledgebase as article 23832.  I found that article by searching the Altiris support forums and I came across this message thread.


Wednesday, March 21, 2007

I'm not impressed with Diamond Multimedia support

I have a older PC that I just installed Vista. I want to make sure that our apps place well under that OS and I don't want Vista as my primary OS just yet. Usually I do that kind of testing under VMWare, but you don't get the full experience of the OS when it's virtualized.

This PC is older, a Dell Optiplex GX400 and has a NVIDIA TNT2 video card. It's a perfectly OK card, but Microsoft and NVidia are not doing a Vista driver for that card. So Vista is running it with the Standard VGA Graphics Adapter driver. The SVGA driver is better than I thought it would be, but it's slow and is running at 60 hz. I'm not terribly concerned over the speed, but the flickering is driving me nuts.

I got the OK to get a new card, and that's when the fun began. To get Vista's Aero Glass theme, you need a decent video card that has DX9 support. The GX400 has an AGP 4X port and a bank of PCI slots. No one is making AGP 4X cards anymore, it's AGP 8X or PCI-Express these days. I looked up the specs on a BFG card that claimed to be AGP 8X/4X, so I fired off an emaill to them to see if their card would work with my ancient PC.

While I was waiting for a reply, I saw an article on The Inquirer about companies releasing Vista ready PCI cards. Diamond had released a PCI card based in ATI's Radeon 1300 chipset and it sounded like it would do the job. After a few days of no response from BFG, we ordered the Diamond card. Immediately placing the order, a reply came from BFG that said their card would work.

The Diamond card came in today and I tried installing it. I removed the Nvidia card from the AGP slot and put the Diamond card in a PCI slot. There are 5 PCI slots, all of them were available. The machine wouldn't recognize the card. I tried a number of things (telling the BIOS not to expect an AGP card, moving the Diamond card to another slot, putting both cards in. With both cards in, the machine would not recognize either card.

Either it's something flaky with the Diamond card, or more likely, it's Dell building a PC that only works with AGP cards. Past experience with Dell has led me to the conclusion that the card slots on a Dell motherboard are purely decorative. I decided to call Diamond technical sipport to rule out their card.

Almost immediately, I was connected to technical support person. I forgot his name, let's refer to him as "Stan". Stan was not very helpful. It was clear that he was reading from some sort of script and deviations from that script were verboten. I explained that the PC would not make it past POST when the Diamond card was installed. He asked what OS was installed. I said "Vista, but that's not important right now". He asked what driver was installed. I told him that Vista did not support the current card and was using the SVGA driver that comes with Vista.

He asked me to uninstall the SVGA driver. I asked why and he said that having the wrong driver was a common cause of video card problems. I declined to do so for the following reasons:

  • The problem occurs at boot time, video drivers are not loaded until the OS loads. My machine was nowhere near that point.
  • It's the standard VGA driver that comes with Vista. It's the driver that gets loaded when you uninstall a vendor video driver.
  • I doubt that Vista would let you uninstall it in the first place.
  • The Diamond card had to work with SVGA driver or you would be unable to install Diamond's driver.

Since I declined to uninstall the driver, Stan's demeanor and he basically said there was nothing more he would do. I thanked him for his time and hung up.

This card is being sent back and I doubt that I would ever buy another Diamond Multimedia product. The BFG card is on order, hopefully that will be a better experience.

Tuesday, March 20, 2007

Notes on installing Delphi 2007

I got the email yesterday from CodeGear. It was a link to download the newly released Delphi 2007. I will be getting the DVD from CodeGear as part of the Software Assurance that I have, but I wanted to try the new installer. This is their first release using installer technology from InstallAware. As it happens, I'm considering switching from Wise For Windows Installer (WFWI) to InstallAware, so it's a good oppourtunity to see their installer in action.

The installer is a minimal (4MB) installer. It grabs the bits that it needs from the Internet from the bits that it needs and the bits that you want. It took a while to download the installer. There were three options, HTTP, FTP, and Galileo. From my office, none of them worked. Once again, our SonicWall firewall has safely protected me from downloading stuff that I need. After a few attempts, I went to Plan B. That was my home PC. I remoted into that box, immediately downloaded the installer without any grief and copied the file back to my office PC.

Once I had the installer, I ran it on my Vista box. The Vista box is my backup PC and I just put Vista in it to test our apps under a hostile environment. The first thing installer did (after I answered "Continue" to the ever present UAC) was to announce that it needed the .NET 2.0 SDK and it was going out to get them. It transferred about 360MB or so of .NET parts and then installed them.

After about 30 minutes or so, I got the "Welcome to the InstallAware Wizard for RAD Studio Setup" page in the setup dialog. Which led to the EULA and registration pages. Oddly enough, it defaulted to "CodeGear" as the company name. Come on folks, that value can be read from the registry. The "Next" button flickered as I typed into each field. I don't know that that's Vista, Windows Installer, or InstallAware. I'm guessing it's Vista's non-support for my ancient NVIDIA TNT2 card that it treats as a standard VGA device.

Then I was prompted for what features to install. I have the Enterprise version, there were many features. It wanted about 1GB and called itself "CodeGear RAD Studio". After one more confirmation prompt, the installer went back to the mothership to download the bits it needed.

It was done after 90 minutes. Now comes the fun part. How many of the Delphi 2006 components will work as advertised?