|
|
 Up |
|
|
  |
Author: Random CRandom C Date: Jul 22, 2008 05:43
Hi guys,
I need to install a fresh copy of my XPe tools to hand over to my
assistant. We got him his own FP2007 install disks, and all seemed to
install fine, but it locks the machine up completely while trying to
build an image - even tiny ones.
I'm working on a fresh install of XP on my own desktop here (I'll be
passing the machine on to him along with the job), and the SP2 tools
work fine still on the other disk, but on the fresh one, or on the
assistant's own PC, no dice. I've tried SQL Server 2000 Dev Edition
instead of MSDE, I've tried just installing SP1, I've tried installing
from my own personal SP1 CDs. None of it makes a spit of difference -
import a PMQ, resolve dependencies, and build - and it'll lock the
machine solid, usually to the point of stopping the clock, though the
mouse...
|
| Show full article (1.05Kb) |
|
| | 5 Comments |
|
|
Author: Ralph A. Schmid, dk5rasRalph A. Schmid, dk5ras Date: Jul 22, 2008 06:44
Random C gmail.com> wrote:
>None of it makes a spit of difference -
>import a PMQ, resolve dependencies, and build - and it'll lock the
>machine solid, usually to the point of stopping the clock, though the
>mouse can still move, when the build gets to about 99%% done.
Check the hardware, maybe just something simple like an overheating
CPU or defective memory. Depending on the image the RAM is much more
used than in normal office joby, so maybe the error only shows up
then.
-ras
|
| |
|
| | no comments |
|
|
|
|
|
Author: Random CRandom C Date: Jul 23, 2008 05:57
On Jul 22, 2:44 pm, "Ralph A. Schmid, dk5ras" radio-link.net>
wrote:> Random C gmail.com> wrote:>>None of it makes a spit of difference -
>>import a PMQ, resolve dependencies, and build - and it'll lock the
>>machine solid, usually to the point of stopping the clock, though the
>>mouse can still move, when the build gets to about 99%% done.
>
> Check the hardware, maybe just something simple like an overheating
> CPU or defective memory. Depending on the image the RAM is much more
> used than in normal office joby, so maybe the error only shows up
> then.
>
If it's the hardware why is it a) happening on two machines b) not
happening on the old install? I installed the new windows to a
secondary hard drive without touching the original install, because we
cannot be...
|
| Show full article (0.82Kb) |
| no comments |
|
|
Author: Random CRandom C Date: Jul 23, 2008 06:01
On Jul 22, 11:09 pm, "Sean Liming \(MVP\)" sjjmicro.com>
wrote:> You will want to have allot of RAM in the development system - 2GB is what I
> recommend for XPe development. Porcessing power is also important.
Yeah thanks Sean, it's the same machine with a core2 processor and 2GB
RAM I've been using for over a year. It's just with a fresh install on
a fresh OS it doesn't work.
I've tried SQL server developer edition and MSDE, doesn't make any
difference, and as I said, I've also tried it on another machine.
I *have* got it working on a third install on the one machine, but I...
|
| Show full article (2.42Kb) |
| no comments |
|
|
|
|
|
Author: Random CRandom C Date: Aug 15, 2008 03:19
Welll... the clean install worked for a while, and was handed over to
my replacement, and my install nuked as I'm leaving.
Obviously, it stopped working. We think it's something to do with
Windows Update, but what I have no idea. Has anyone else seen anything
like this?
|
| |
| no comments |
|
|
