The September CTP of SQL Server 2005

is not available and I'm sure lots of people have downloaded it. I

actually grabbed it the night before it was announced, got some

pre-release info :), and got it burned onto a CD. Or I got the

downloaded EXE burned at least.

You see I tried to expand the .EXE and put it on my workstation,

thinking I'd burned the setup to CD and have it ready. However my C:

drive is low on space, down to about 900MB and so when it asked for a

path, I chose the E: drive, which has about 6GB.

And about 10 minutes into the process I got a "not enough space on c:"

message and it failed. And cleaned up, so no files on E:. So I clean

off some space, kill temp files, etc and I'm at about 1.1GB. Same thing

happens, which #@%#$%#$%'d me off and I just burned the image.

I'd held off installing it, however, or at least I held off once I

verified the upgrade from June didn't work. Mostly because I'm tech

reviewing a book and wasn't sure if June or Sept would apply. I got the

news a couple days ago that Sept is fine, so I ran the Build cleanup

wizard and removed SQL Server 2005 and .NET 2.0. Then I tried

installing and got ".NET 2.0 components, beta components, error" and it

failed. I remembered I had VS2005 setup, so I uninstalled that,

rebooted, and tried again.

C'mon guys. No space on the c: drive when I specified another one?

Cleanup and uninstall not working because of some proper order!! These

are rookie mistakes, Windows 3.1 or 954 mistakes. I'm annoyed and

disappointed that this type of stuff is still occurring in MS products.

It makes the Linux guys, for all their craziness with packages and dependencies, look good!