Install VS6.0 on Windows XP Embedded -error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm trying to install Visual Studio 6.0 on Windows XP Embedded /w SP1 including full components of software category
Inserting Install CD into CD-ROM drive, setup.exe automatically starts and initial setup window appears
But once I clicked "next" button, setup.exe immediately terminated without any error message
Originally, License Agreement confirmation window should appear after initial window

After some times retry, it happened to proceed and seemed processing successfully
But it was terminated with some error like DLL registering to registry, and failed to install
IDE seems working but some function didn't work properly.

If on Windows XP Professional, I can install and work on VS6.0 properly, even after installing VS .NET

What's wrong
Please give me some advise.
 
Mike,

Your XPe image does not seem to have all the dependencies necessary to run
VC. You will need to figure out them. You may use tools like Dependency
Walker, Regmon, FileMon.
Read more:
http://groups.google.com/groups?hl=...a=group=microsoft.public.windowsxp.embedded.*

Also, ask yourself a question - do you really need VC running on the target?
To debug your application you can perfectly use VC Remote Debugging feature.
Or use WinDbg/KD. Some info here:
http://msdn.microsoft.com/library/d...ry/en-us/dnembedded/html/embedded02182003.asp

KM
I'm trying to install Visual Studio 6.0 on Windows XP Embedded /w SP1
Click to expand...
including full components of software category.
 
KM

Thank you for quick reply
I imported all of software components into my image and surely executed dependency-check
confirming that no dependency problem had been remained

Remote debug
Well, first, we have not so many engineers who understand the method of remote debug,
and our system is not designed as enabling remote debug, so I don't take it into one of the choices

OK, I'll check the dependency of setup.exe referring to the articles you presented
Thanks

Mik

----- KM wrote: ----

Mike

Your XPe image does not seem to have all the dependencies necessary to ru
VC. You will need to figure out them. You may use tools like Dependenc
Walker, Regmon, FileMon
Read more
http://groups.google.com/groups?hl=...eta=group=microsoft.public.windowsxp.embedded.

Also, ask yourself a question - do you really need VC running on the target
To debug your application you can perfectly use VC Remote Debugging feature
Or use WinDbg/KD. Some info here
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnembedded/html/embedded02182003.as

K
I'm trying to install Visual Studio 6.0 on Windows XP Embedded /w SP
Click to expand...
including full components of software category
 
Mike,

Come on this is not a rocket science.

But in few lines.

Make component that will copy all files from.
C:\Program Files\Microsoft Visual Studio .NET\Common7\Packages\Debugger\

Also make it so that XPe executes msvcmon.exe.
Make basic network support in your XPe image.

And you are done with XPe setup for debug.

In VS select remove debug and name of computer that you want to debug.

And more or less you are ready to debug your image from VS without
interfering to XPe functionality.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/htm
l/vctskInstallingRemoteDebugMonitor.asp

Good luck,
Slobodan

PS:
I probably can't be objective on this subject since I practicaly live with
debuggers constantly active.
 
Mike,

I completely agree with Slobodan on the fact that Remote Debugging is not hard at all. It does not really have much new compared to
regular (local) debugging. The same code, the same breakpoints, the same debug output technics.
At some point it is even better debugging solution than the local debug as you influence the application being debugged very little.

Personally, I think you will spend much more time making component out of the VC 6.0 to run it on your target rather than just copy
a few files to the target to start the VC Monitor and get familiar with the Remote Debugging feature.
 
Back
Top