VS2005 July CTP under Virtual PC - shortcutCLTDbg32.txt can't be read
I've been trying to install the
July CTP of VS2005 Professional under
Virtual PC SP1 which is running
Windows Server 2003 SP1 and it invariably fails towards the end of the main install trying to read
D:\VS\Program Files\Microsoft Visual Studio 8\SDK\v2.0\GuiDebug\shortcutCLRDbg32.txt telling me the file was not found and offering me the choice of Retry (which loops failing with the same message) or Cancel (which does a rollback).
That file is on the disk and appears to be a multi-stream file. It can be opened in Notepad in the host operating system (Windows XP SP2) ie outside the VPC with no problems. Notepad displays its contents as "This is a plae holder. Do not Delete". But any attempt to open it with Notepad in the VPC gives an error dialog which says "Cannot open D:\VS\Program Files\Microsoft Visual Studio 8\SDK\v2.0\GuiDebug\shortcutCLRDbg32.txt file. Makes sure a disk is in the drive you specified" (which explains why the VS installation fails I guess!)
Has anybody successfully installed the VS Professional July CTP under VPC (not the VSTS one - I have installed that on another VPC but my laptop where I want to install a copy has only 1GB memory so the VSTS build is not possible). Any suggestions as to what the problem might be or how I can get round it?
I also have a second problem which is more to do with VPC than with VS install but since I'm here I'll aske anyway.... I can get internet access using Internet Explorer but activation always fails with an error about not having connectivity. Any idea how I can do an internet activation of the VPC installed operating system?
Thanks in advance for any suggestions.
[1744 byte] By [
irascian] at [2007-12-16]
Are you installing from a CD/DVD or did you copy the bits locally?
If you are installing from a CD/DVD, try copying the files locally and then try running the install.
Also, if you downloaded the ISO from MSDN, make sure you burn the ISO using long file names.
Hope this helps.
I'm installing from a DVD ISO image burnt from MSDN Universal downloads. Yes, I'm using long file names. Unfortunately I don't have the disk space spare to copy the image and do the install - space is unfortunately pretty tight on this laptop.
My issue really is that VPC seems to have a problem with the file where a "real" OS doesn't. To me that seems like a bug in VPC. After all why should a file that reads perfectly well from the host O.S. give a "Not found, insert a disk" message when trying to do exactly the same thing from within a VPC.
And yet I'd been lead to believe most people were installing the beta and CTPs under VPC.
Thanks for the feedback anyway.
As an aside, I've duplicated the problem. My situation is that I HAD it working and then something else went wrong. Now after uninstalling VS and Team Explorer, I get the same error when I try to reinstall VS. I can find the file on the DVD from within the VPC using Windows Explorer, but for some reason the install fails.
I'm going to try a few variations and if I find anything I'll let you know.
--
Update: I tried several things and got it to install. My theory: VPC 2004 
SP1!
I originally built the image on a VPC with SP1 and then had problems that I thought were unrelated on a different PC w/o SP1. After several variations I got the same problem. After updating the VPC to SP1, it worked.
This may be circumstantial evidence, BUT IT DID WORK!!!!
irascian - if you ever get a chance to try it again, maybe this will help. Good luck!
I had the same problem, but solved it by accessing the dvd from the pc where I have vpc installed.
1, Share the dvd drive on the host.
2, Access it from within the vpc os with windows explorer 'My network places' or \\hostname\dvdshare.
Worked just fine for me.
/Janne
Hello folks,
I am having this exact same problem ( same file ) trying to install the VS2005 Release Candidate under Virtual PC. I have installed all the VS2005 alphas and betas on multiple machines under Virtual PC with no problems anywhere and now I run into this. Has anyone else run into this with the Release Candidate and has anyone found a solution.
Thanks for any help. It would be much appreciated.
