L
Larry Waibel
I do wish that Microsoft would take some responsibility for automating the
import and build processes for creating an XPe target output. After weeks of
working to get the import process to work to import when the repository
already existed I'm now having the build process hang the XP Pro GUI so hard
that I have to power off the system and reboot (and I've never had anything
else that caused me to have to do that!). Here's what I do:
Y:\sdcots\winxpe\gatesbc\sra\src>\sdcots\winxpe\src\cmiexp.wsf
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
CMI Explorer version 3.14.620 (CMI revision 578)
Copyright (C) 1999-2001 Microsoft Corp. All Rights Reserved.
Platform GUID : {B784E719-C196-4DDB-B358-D9254426C38D}
Platform : (not in database)
*dbo xpe-db /ri
Server : xpe-db
Database : MantisSQLDB
Generation : {E3CBAFE0-E0E7-4B47-8670-BE0ACE62AE18}
Open mode : ReadImport (1)
*new cfg config
*cfg=CMI.CreateFromFile("\sdcots\winxpe\gatesbc\sra\src\sra.slx")
*cfg.activate
Starting configuration activation at: 12/12/05 15:39:52...
CFDB: 1.98 secs, 42 reqs. LAB: 1.98 secs, 42 reqs, 0% hits, 0 entries
Activation complete, elapsed time: 6.61 seconds
No errors or warnings
*cfg.build 0, "\sdcots\winxpe\gatesbc\sra\bin"
If I hit enter after this, it'll show:
Starting run-time build at: <date> <time>...
and then the XP Pro GUI is hung! The mouse cursor moves but that's about it.
I can't kill the command shell and I can once get the Task Manager to show
but it doesn't respond to any clicks so I can't try to kill the script.
Is there any way to turn on some kind of output from the script so I can at
least get some idea of where in the script it must be going into a 100% CPU
loop? Or even better, what's the problem with the script and how do I fix
it?
import and build processes for creating an XPe target output. After weeks of
working to get the import process to work to import when the repository
already existed I'm now having the build process hang the XP Pro GUI so hard
that I have to power off the system and reboot (and I've never had anything
else that caused me to have to do that!). Here's what I do:
Y:\sdcots\winxpe\gatesbc\sra\src>\sdcots\winxpe\src\cmiexp.wsf
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
CMI Explorer version 3.14.620 (CMI revision 578)
Copyright (C) 1999-2001 Microsoft Corp. All Rights Reserved.
Platform GUID : {B784E719-C196-4DDB-B358-D9254426C38D}
Platform : (not in database)
*dbo xpe-db /ri
Server : xpe-db
Database : MantisSQLDB
Generation : {E3CBAFE0-E0E7-4B47-8670-BE0ACE62AE18}
Open mode : ReadImport (1)
*new cfg config
*cfg=CMI.CreateFromFile("\sdcots\winxpe\gatesbc\sra\src\sra.slx")
*cfg.activate
Starting configuration activation at: 12/12/05 15:39:52...
CFDB: 1.98 secs, 42 reqs. LAB: 1.98 secs, 42 reqs, 0% hits, 0 entries
Activation complete, elapsed time: 6.61 seconds
No errors or warnings
*cfg.build 0, "\sdcots\winxpe\gatesbc\sra\bin"
If I hit enter after this, it'll show:
Starting run-time build at: <date> <time>...
and then the XP Pro GUI is hung! The mouse cursor moves but that's about it.
I can't kill the command shell and I can once get the Task Manager to show
but it doesn't respond to any clicks so I can't try to kill the script.
Is there any way to turn on some kind of output from the script so I can at
least get some idea of where in the script it must be going into a 100% CPU
loop? Or even better, what's the problem with the script and how do I fix
it?