Click to See Complete Forum and Search --> : VS.NET Installation on XP Home


galathaea
December 9th, 2002, 05:42 PM
My company just procured a copy of VS.NET to check out for our product development. The only machine we have available for the tests is a 2 GHz Pentium with 128 MB running Office XP Home Edition (yes, one of them HPs...). Its not the most robust, I know, but the requirements seem to at least fit. It also has a student version of Office XP installed that one of the team members uses.

Now, I have installed the Component Update. When I try to install the actual suite, however, it begins installation and reports an error after a few minutes. The error message is

Error 1335: cabinet file '_92_OfficeShared10.msm' corrupt. This may be a network error, error reading CDROM, or a problem with the package.

The error appears when the setup is working with MSO.DLL in the shared microsoft office folder (the one we us for accessing certain COM interfaces and such). I was surprised to see the error message, but am even more confused as to why VS.NET would even need to update this module.

I have tried several options. First, an internet search revealed this discussion (http://www.byte.com/tangledthreads/thread.jsp?forum=69&thread=4201) and the related MSDN link, but none of those solutions seem to work for me. I have even moved MSO.DLL to a different temp directory to see if the installer would just put its own version in, but that did not work as well. I was hoping someone out there has had this problem and found a solution that works for them. Of course, any assistance would be greatly appreciated, even just "educated guesses" for me to try, as we would really like to get this working ASAP.

From what I have read, it may be a CD access problem or a memory problem, but I cannot figure out any way to overcome the issue I have. Thank you for your time and any help!

[Edit: I have searched the forums extensively for any help, and have even gone through the past year and a half posts in this thread, to try to find anything similar, but to no avail. If I have missed anything pertinent, I would appreciate a link as well!]

Kdr Kane
December 14th, 2002, 05:34 AM
I'd suggest more RAM.

System Requirements (http://msdn.microsoft.com/vstudio/productinfo/sysreqs/default.asp)

Take note of limited functionality if you're using XP Home Edition.

You can also take a look at KB Article Q314810.

galathaea
December 15th, 2002, 10:13 PM
I've been coming to much the same conclusion. We can't put this on a bigger machine right now, but we are expecting to be able to upgrade this machine over the next month. We should be able to upgrade the memory to a half gig and the OS to XP Pro. It is important we look to updating, because some of our programming needs to have better ANSI c++ support for better design support. In the meanwhile, we have Comeau and are begining to quite enjoy it...