Critical TD Bug - Anyone got a workaround??

[Guest]

We are up against a critical (actually a pair of) Target Designer bugs.
Wondering if anyone here knows a workaround. It's stopping us shipping
product... :-(

The problem is, our project is quite large, having a (almost) complete XP
functionality with only a few things like Media Player and the games removed.
The project file is 41MB in size. This has never been a problem (aside from
the long loading and saving times). However, today I needed to add support
for a new PC type, so I created the PMQ file, and imported it into the
project, it went in OK, added about 10 device drivers, and not much else.
When I come to save the SLX project file, I now get "

Not enough storage space is available to complete this request" error
message,

followed by:

"An error occured while saving D:\SYSTEM DISK\Version 03\Xpe Target Designer
Files\FullXP.slx. Please check permissions on the file and folder as well as
the available disk space on the storage colume."

I have checked the suggestions made, and everything is fine, there are well
over 100Gb os free space on the volume in question, and permissions are fine.
I cannot save the file to ANY location, so I think this is a red herring
error message.

Anyone seen this, or know a workaround? I can build a image, but cannot
save the project file. Saving to XML works find however, but then you
encounter the bug where everything becomes a unreleased component next time
you open the project, generating 1000's of warnings...

Need some help here... !!!

 

[JC]

Did you try doing a "Save As" instead of just saving the slx?

I have not seen this one before, but "save as" and give it a different
location should work...

HTH,
JC

 

[Black Shuck]

Did you try doing a "Save As" instead of just saving the slx?

I have not seen this one before, but "save as" and give it a different
location should work...

HTH,
JC

Tried that, did not make a difference. Tried saving it to both local
HDD and network locations, nothing worked.. :-( It's also 100%
repeatable here, as If I don't safe the project, close it all down, and
reopen TD and re-import the PMQ, I am always left with the same problem.

 

[Guest]

You are running into a known bug with TD. The first step to resolving this is
to close Target Designer and start a new instance. Don't reuse the same
instance of Target Designer without closing or you will hit this error. The
other step is to save the project in phases. I am also building a very large
image and my solution was:

1) close td and start again.
2) import pmq and add most of the desired components.
3) Save, shutdown again and start again
4) add the last of my components and now this project will save.

 

[KM]

Mark,

Yes, this is a known issue indeed.
I don't think Microsoft would fix XPe Tools bugs (they focus on LH/LHE now).

One workaround (will require you to gain some CMI knowledge first) - use CMI Explorer tool (VALUEADD folder on XPe CD) to work on
the project. It won't fix the problem completely but will remove TD VB Script problems from the picture and, of course, will free up
some RAM.

 

[KM]

Mark,

Forgot to ask - how did you manage to get the (almost) complete XP functionality in your image?
There are some known templates but I am wondering about your approach?

 

[Guest]

In my case I created a number of components for each of the major sections:

Management group - all management compoments
Multimedia/graphics - all multimedia and graphics
system services
font group
etc.

Added those to my image and ended up with a full xpe image about 900meg. I
didn't include all drivers in my image. Of course when I tried to save this
monster I got nasty errors which required my workaround described above.

 

[KM]

Ok. I understand.

Then I possible workaround for you (although you may still see that TD bug sometimes). You can try using XPProEmulation.slx project
from www.xpefiles.com (Development Utilities/Main). It is already saved and contains virtually any software components from XPe
database.

 

[Black Shuck]

Mark,

Forgot to ask - how did you manage to get the (almost) complete XP functionality in your image?
There are some known templates but I am wondering about your approach?

I used the XPPro emulation SLX from XPEFiles as a starting point, and
removed a few unnecessary bits and bobs.

 

[Black Shuck]

Mark,

Yes, this is a known issue indeed.
I don't think Microsoft would fix XPe Tools bugs (they focus on LH/LHE now).

This is bad news, as the XPe Tools are a pretty critical component in
using XPe...

 

[Guest]

Just to clarify. Black Shuck = Mark Gillespie@Home (posting via usenet,
rather than at work using Passport)

 

[Leonid]

TD is very "memory hungry" application. The big project requires big memory
resources on development machine.
For example, I have my laptop with 512 MB RAM. TD eats all memory + part of
page file. Then I installed 1 GB RAM.
Now TD eats 1 GB RAM (with the same project).
In any case adding more RAM to development machine may solve some "save" and
"save as" bugs in TD.

\Leonid

Mark,

Yes, this is a known issue indeed.
I don't think Microsoft would fix XPe Tools bugs (they focus on LH/LHE now).

One workaround (will require you to gain some CMI knowledge first) - use

CMI Explorer tool (VALUEADD folder on XPe CD) to work on

the project. It won't fix the problem completely but will remove TD VB

Script problems from the picture and, of course, will free up

 

[KM]

Leonid,

"TD eats 1 GB RAM"? Wow.. I hav never seen such memory consumption by TD.
With the biggest version of the XPProEmulation project the RAM usage was ~500-600Mb.
SQL Server RAM usage was getting up to 200-300Mb at most.

KM

 

[Leonid]

Hi, Konstantin
You are right. I mean TD + SQL server on same machine. BTW how to limit SQL
server RAM usage. Are there settings to configure SQL RAM usage to be
controlled?

Thanks
\Leonid

 

[KM]

Leonid,

I don't really know why you'd need that except you are running the SQL on a server machine and want to free up some memory for other
apps (server apps) there.

Anyway, run this SQL script (use SQL Query Console or Enterprise Manager or anything you prefer);

SP_CONFIGURE 'max server memory', 128
RECONFIGURE
GO

If will set the max limit amount of memory that SQL Server takes to 128Mb.

If you want to read more about this, see this link: http://www.sql-server-performance.com/awe_memory.asp

KM

 

[Leonid]

Thanks a lot for tip.
\Leonid

Leonid,

I don't really know why you'd need that except you are running the SQL on

a server machine and want to free up some memory for other

 

[Guest]

Quick update. Found a workaround.

It seems the script that adds the components via the import PMQ function is
causing the corruption, if you avoid this, things work.

This means, if you do the following, you can work around the large project
save problem (it's slightly more convoluted, but bearable).

Import the PMQ, Save the log to disk, close your project without saving
(Important), reopen the project, and add the devices from the logfile
manually (copy and paste descriptions from the log to the search window.)
Dependancy Check, and then bobs your uncle...

 

[KM]

Mark,

I can't tell you whether it is a good fix or not but I am pretty sure that my big XPe projects which exposed the problem weren't
started with PMQ import. :-(
(e.g., XPProEmulation)