Visual Studio 6.0 Installation on XPE

[alpha]

Hi,

I've got an error message when installing VS 6.0 (Enterprise Edition)
It prompt out at the first screen of the installation wizard (screen with
the "view readme" button)
when I press the "Next>>" button:

The instruction at "0x77f58cf1" referenced memory at "ox000000fd". The
message could not be "read"
Click on OK to terminat the program.

Am I missing some XPE components or something wrong?

Thanks.

[Gareth Hendry]

I have the same problem as well, but the referenced memory changes depending
whether you use the mouse to select the "Next" button or the keyboard (space
or enter button).
Don't know how to get around it either!

"alpha" <yal...@hotmail.com> wrote in message
news:O00YzizA...@TK2MSFTNGP11.phx.gbl...

[Freddy Ben-Zeev]

I managed to overcome this problem by playing with the setting of the "Text
Services Framework" component, and some additional registry modifications. I
would be thankful to anyone who can explain what caused the problem, and why
this solution works.

1. Modify "Text Services Framework" component settings:

Language bar setting on the desktop: Hidden
Show additional Language bar icons in the Notification area: Unchecked.
Show text labels on the Language bar: Unchecked.

2. Adde the following registry entries to a component and include it in your
design:

[HKEY_CURRENT_USER\Software\Microsoft\CTF]
"Disable Thread Input Manager"=dword:00000000

[HKEY_CURRENT_USER\Software\Microsoft\CTF\LangBar]
"ShowStatus"=dword:00000003
"Transparency"=dword:000000ff
"Label"=dword:00000001
"ExtraIconsOnMinimized"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\CTF\MSUTB]
"Left"=dword:00000179
"Top"=dword:00000000
"Vertical"=dword:00000000
"ShowDeskBand"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
"ctfmon.exe"="%11%\ctfmon.exe"

Plus run the following script after the end of FBA (to fix entries modified
by FBA), or do the registry modifications manually:

Set WSHShell = WScript.CreateObject("WScript.Shell")
On Error Resume Next
WSHShell.RegWrite "HKCU\Software\Microsoft\CTF\LangBar\Label", 1,
"REG_DWORD"
WSHShell.RegWrite
"HKCU\Software\Microsoft\CTF\LangBar\ExtraIconsOnMinimized", 1, "REG_DWORD"

Freddy

"Gareth Hendry" <ghe...@astra-gamesNOSPAM.com> wrote in message
news:2lRma.323$It3...@newsfep3-gui.server.ntli.net...

[Jon Fincher (MS)]

"Gareth Hendry" <ghe...@astra-gamesNOSPAM.com> wrote in

news:2lRma.323$It3...@newsfep3-gui.server.ntli.net:

My question is - why are you trying to install VS6.0 on an embedded box?

If you're trying to debug, use Remote Debugging, or pump KD output through
NTSD.

If you're trying to make embedded dev systems, you may have a licensing
issue to worry about.

In either case, I don't expect this work at all - the fact that you've
hacked around it is moot.

--
--Jon, MS

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Freddy Ben-Zeev]

Jon,

Installing VS 6.0 on an embedded box does not necessarily mean a licensing
violation - unless you ship an image with it installed. As you can see in
another post on this thread, I managed to solve the problem (after a lot of
experimentation) because it is much easier to debug in Visual Studio than
using remote debugging, and if my embedded system is actually a full PC I
don't see any reason not to take advantage of it. Am I doing anything wrong?

Freddy

"Jon Fincher (MS)" <jonfi_...@microsoft.com> wrote in message
news:Xns935FB3B9D3C7Djo...@157.54.3.22...

[Gordon Smith (eMVP)]

I had the same reaction as Jon initially - "Why would anyone want to ship an
EMBEDDED product with VS 6 on it?"

I then realized - "uhhh, maybe they won't actually SHIP it that way - just
for debugging". Jon suggested using other tools to debug and that's a valid
suggestion. However, why bother learning new tools (assuming those other
tools are new to you) when you have a perfectly reasonable debug tool at
your disposal? My main concern would be "are you bloating your image for
the purpose of including VS 6?"

--Gordon Smith (eMVP)

"Freddy Ben-Zeev" <fre...@guidetech.com> wrote in message
news:uv7Mx$DCDHA...@TK2MSFTNGP12.phx.gbl...

[Jon Fincher (MS)]

"Gordon Smith \(eMVP\)" <Gordon...@nospam.avnet.com> wrote in
news:eR1wOLEC...@TK2MSFTNGP12.phx.gbl:

> I had the same reaction as Jon initially - "Why would anyone want to
> ship an EMBEDDED product with VS 6 on it?"
>
> I then realized - "uhhh, maybe they won't actually SHIP it that way -
> just for debugging". Jon suggested using other tools to debug and
> that's a valid suggestion. However, why bother learning new tools
> (assuming those other tools are new to you) when you have a perfectly
> reasonable debug tool at your disposal? My main concern would be "are
> you bloating your image for the purpose of including VS 6?"

If you're trying to debug an app on an embedded runtime, there are easier
ways than installing the full VS IDE on the embedded system. Remote
debugging works very well with VS 6 and .Net for SDK apps - I'm working on
documenting hte same procedure for .Net apps. The setup is easier, less
of a footprint hit, and you can use the dev machine tools to do the
debugging, so it will work on headless systems as well.

I'll have those steps by the end of this month (I think that was my
commitment).

[alpha]

Freddy,

I'm happy to hear that you've got a successful installation.
Can you post again the method to install the VS6 on XPE.
I missed it because I was on vacation.

Thanks,
Alpha

"Freddy Ben-Zeev" <fre...@guidetech.com> wrote in message
news:uv7Mx$DCDHA...@TK2MSFTNGP12.phx.gbl...