XPe weirdness....

[Zapp Brannigan]

Well after a couple of days trying to get XPe to do what we want, I am
almost there.... I do have some weirdness to report thou...

1/ Our problem installing Visual Studio 6 onto XPe (only our
engineering machines)..

Regardless of the configuration of XPe, the VS60WIZ.EXE refused to work.
But get this, there is a really bizarre workaround, that works 100%
for us. When the Visual Studio Setup Wizard starts, use the keyboard to
navigate to the README button, and use Enter to open the readme, then
use Alt+F4 to close the IE Readme page, then use the mouse to select
Next, for us, this always works correcty, however, and deviation
(however minor) from this process causes the Wizard to crap out when
Next is pushed. How weird is this?? This alone has severly undermined
our faith in XPe, as this all works fine in XPPro and XPHome (We tried).....

2/ STOP: Errors and virtual memory...

Today, I wasted a fair few hours building installs that did nothing but
generate a STOP as soon as the FBA runs, (I forget the STOP code, it may
have been 21). It turned out that happened as soon as I enabled a
pagefile in the "Standard PC" component (128Mb fixed size pagefile), as
soon as I switched this off, the problem went, as soon as I switched it
back on, it came back. What gives??? I needed the swapfile during FBA,
as I was getting Out Of Memory errors during component registration. As
it happens, I managed to remove some stuff to make the image smaller,
and I therefore don't need the pagefile at this stage (will enable it
after FBA, before ghosting)...

The whole process is very frustrating, as XPe TD is so slow (P4 2.2Gig,
with 1.3Gig of RAM), it takes 10 minutes at load and save
configurations. Is this Normal? My boss had a fit when I showed him
TDesign.EXE consuming 650Mb of memory is Task Manager!!!

 

[Wayne Taylor]

Hello,

1. I don't understand why you need to do this, can't you just develop your
application on your development machine and transfer the exe to Windows XPe,
there is a component for Visual Basic Runtime files for example.

2. This may be related to trying to get everything in your image to allow
you to run VS6, which in my opinion you don't need to do.

TD does use alot of memory my own uses 194mb with my config loaded (268
components), I guess yours is so high becuase you have alot of components
in. I'm not sure why TD uses so much memory, I suspect it's do with loading
each component it to memory cross checking etc, mayby MS can answer....

Let me know if I can help any more.

 

[Eberhard Schefold]

Wayne Taylor schrieb/wrote:

1. I don't understand why you need to do this, can't you just develop
your application on your development machine and transfer the exe to
Windows XPe, there is a component for Visual Basic Runtime files for
example.

Because auf the XPe peculiarities, it can become necessary to debug the
application running on XPe. But I would suggest remote debugging for that.

 

[Andy Allred [MS]]

I just opened a config with 1200 components in 3 and a half minutes. The
machine is a 2.2GHz with 512MB ram and TD was consuming just over 300MB.

Andy

 

[Zapp Brannigan]

Zapp,
regarding point 1, I have experienced the same problems.. I've also tryed to apply the Fix Q815021 to NTDLL, but I did not obtain results. I think MS descourages the installation of VS 6.0 on XPe, because nobody wants to explain that strange bug.. moreover considering that VS .NET installation gives no problems.
In addiction, did you see the following?

http://groups.google.it/[email protected]&oe=UTF-8&output=gplain

It doesn't work well for me..
I don't know what to do, maybe two brains will be better than one!
Regards!

Michele

Unfortunatly, some of the stuff we develop has to be debugged in situ
and remote debugging or consoles displaying trace statements are nowhere
near enough, we are therefore occasionaly using the full VS98 to step
through code, and make source changes "on the fly".

Did you try the solution I posted, it works 100% here (but the sequence
has to be exactly as described for it to work).