> SP1 is out now ... so before you install it:
> 
> Be DAMN SURE you have enough disk space on your C, or the installation
> will backtrack the *whole* thing, even there was 6 minutes left out of
> a gazillon. No. No retry button.
> FYI, I had more than 2 GB free on my C. I still do not know how much I
> need, but I will move thing around to have double that.

        I had this too (2.3 GB free), I actually did get a retry button when a 
dll failed to copy, but when I clicked it, it crapped out on me with an 
internal error... 

        When I retried, it again took 35 minutes to 'gather information' with 
100% cpu usage (what's that thing doing? Calculating pi till the 1/0th 
decimal?) but it then installed successfully on 8GB free of diskspace. I 
checked, it eats away at least 1.5GB of diskspace. I have NO idea why, so be 
prepared for this. 

        Also be VERY SURE you've UNinstalled Web Application Projects add-in 
because it will rollback if you haven't. The SP1 contains this addin also, and 
as this SP1 installer is the most retarded piece of software I've ever seen, it 
can't figure out to simply skip that part so it has to rollback. 

> Oh, and if the installation fails, it will leave the whole .msp
> sitting in c:\windows\installer and when you start over, it will copy
> it *another* time.

        yeah, I saw this too. Amazing how silly this whole thing is. 

> Ah, and it loads every single bit of the patch in RAM. Yep, that's 450 MB.

        heh, yeah, you really wonder why it then still needs 1.5+ GB of 
diskspace for eh... 

> Really, I don't know what to say ...

        Me neither. This installer is by far the most stupidist piece of 
software I've ever encountered. There are simply no excuses for this. Taking 
over 35 minutes WITHOUT diskactivity to 'gather information' with 100% CPU 
usage is stupid. 
        
        Also the progress bar after all files have been copied is really funny 
(well, it's actually pretty sad, but after a while you can only laugh about 
this thing): it just sits there for over 5 (!) minutes with 'Time remaining: 0 
seconds'

        If your time left calculation routine is that buggy, simply avoid 
displaying time left. :/

        Anyway, it's installed, vs.net 2005 still runs, it opens projects as 
slow as before but that's OK. I only hope a lot of the things I ran into are 
fixed now. Haven't had any quircks yet... :)

                FB

===================================
This list is hosted by DevelopMentor�  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to