Joe H
2007-11-16 16:12:04 UTC
It's really crap to have the close button disabled on the installer --
especially before it's really done anything. That is unacceptable and
really angers me. I can see doing it once un-reversible changes start
happening, but to disable close before the "start install" begins is
unreasonable. I had to reset my machine when the install screen opened
and sat there doing nothing to the dvd or my hard drive for more than
ten minutes.
I have xp-pro with 2 gig of ram, d2007 installed with update 3. That
was a problem since I started the update on dialup and discovered it
was going to take me till the next century before I could work again. I
ended up downloading the entire file at a business associate's office
and updated from there. I only lost 6 hours of work on this.
Because of the new help update, I decided I had better install the
studio upgrade before I got the help update. This time I spent an hour
making backups of my c drive and my work drive before starting to
install the studio update I received by mail.
Anyway, I started to install and got to the point where I selected
"upgrade" from the menu and it took a while then said it couldn't find
update 3 files and was asking me to determine where to save them. The
install help file on the cd said that running setup upgrade from the
command line would only install d2007 for win32 update 3. Well I
already have that installed and working. Rather than have it try to
download 700 megs again by dialup, I called support (they're busy and
haven't gotten back to me yet) and finally cancelled the install. Then
I decided to try again with just "install" instead of update but it
just hung on the first window with the close button greyed out. I
finally had to hard shutdown my machine to get rid of it.
What the hell do I have to do to upgrade to studio? Do I need to backup
the codegear registry settings, then uninstall, then do a complete
re-install, then restore the registry settings?
especially before it's really done anything. That is unacceptable and
really angers me. I can see doing it once un-reversible changes start
happening, but to disable close before the "start install" begins is
unreasonable. I had to reset my machine when the install screen opened
and sat there doing nothing to the dvd or my hard drive for more than
ten minutes.
I have xp-pro with 2 gig of ram, d2007 installed with update 3. That
was a problem since I started the update on dialup and discovered it
was going to take me till the next century before I could work again. I
ended up downloading the entire file at a business associate's office
and updated from there. I only lost 6 hours of work on this.
Because of the new help update, I decided I had better install the
studio upgrade before I got the help update. This time I spent an hour
making backups of my c drive and my work drive before starting to
install the studio update I received by mail.
Anyway, I started to install and got to the point where I selected
"upgrade" from the menu and it took a while then said it couldn't find
update 3 files and was asking me to determine where to save them. The
install help file on the cd said that running setup upgrade from the
command line would only install d2007 for win32 update 3. Well I
already have that installed and working. Rather than have it try to
download 700 megs again by dialup, I called support (they're busy and
haven't gotten back to me yet) and finally cancelled the install. Then
I decided to try again with just "install" instead of update but it
just hung on the first window with the close button greyed out. I
finally had to hard shutdown my machine to get rid of it.
What the hell do I have to do to upgrade to studio? Do I need to backup
the codegear registry settings, then uninstall, then do a complete
re-install, then restore the registry settings?