Problems after RAM upgrade.

levd,

It looks like the issue may be with the Hardware Abstraction Layer (HAL). I would recommend recreating the image you are deploying after running Microsoft Sysprep, which usually takes care of issues of this sort. Sysprep strips the HAL from the image, and when a Sysprepped image is deployed and the machine boots the first time, it will recreate its HAL. 

Thank you,

Randy

Sounds like hardware to me. I'd try a few things to start feeling around the problem...

1) memtest. Download  the memest iso (www.memtest.org) and give the RAM a burn to check its not a batch of faulty DIMMs
2) BIOS upgrade. Are there upgrades available? If so, give that a shot
3) If memory OK, does sysprep fail with 512MB, 768MB as well as 1GB?

The obvious question also is what error exactly are you getting?

Kind Regards,
Ian./

I would definitely consider Ian's suggestions. Does the error refer to HAL.DLL at any point? 

 Hello all,

There is no clear error notice, something with cannot write to registry.
Im working from home now so i cannot reproduce the error.

Ian,
If you refer to a problem with the memory or an outdated bios version isnt it strange the pc runs fine with the new 1GB memory? The pc runs on an image pushed when it ran at 256mb.
When installing the 1GB the bios gives a notice found 1024kb press F1 to save, and the it runs fine...
Re-imaging the machine gives the problem after the image is pushed in the mini-setup.

Randy,
What are you saying, recreating the image from scatch?
Or take a machine with the placed memory (1GB, which is running fine) and then pulling it from the machine, with the taks "image create task", option "run Microsoft Sysprep on this machine before creating the image" enabled?

LEVD

levd,

I am recommending recreating the image from the original source (256MB RAM), using Sysprep this time, in the manner you specified.

Thank you,

Randy

Either as Randall said, or put one machine back to 256MB.  Push the image to it (just so its clean.)  Then install the 1GB into this machine.  This still works, if I understand what you've said above.  Now, take an image of this machine with the 1GB in it.  Then push this new image (which really ought to be the same, but never can tell) onto another machine that has 1GB and see if that works.

Separately, I'd agree w/the memtest recommendation.  I've often increased memory in a bunch of machines at one time.  Invariably, when dealing w/that many different sticks on that many different machines, a good solid weekend-long test of memory is a good idea.  If you use PXE, just make a DOS boot disk with memtest.exe the default boot option (instead of the boot to local hard drive) and it automatically starts up memtest for me :)

Good luck,
PH

 It does seem to be a HAL-related and also a MICROSOFT Sysprep-related issue unless the Ghost image is corrupted which i doubt. However do we know which hardware the image was originally taken from. Is it from the same make, or closely the same? As a test i would try using the Deploy Anywhere feature coming along with the Ghost Suite 2.5. As the program replaces the HALL to match the destination hardware specifications, the setup manager might run properly afterwards.

In addition I would suggest checking one of the four sysprep requirements:

The reference and destination computers must have compatible HALs. For example, Advanced Programmable Interrupt Controller (APIC)–based MPS (multiprocessor systems) must use the same APIC HAL. A standard HAL Programmable Interrupt Controller (PIC)–based system is not compatible with either the APIC HAL or the MPS HAL.

See the full requirements here:

http://support.microsoft.com/kb/302577

If  would also like to know what command your ordered sysprep to run and what is your answer file doing to have a better understanding of what might occur and when.

Finally, if you haven't hugely configured syprep in your image and need to progress then i would suggest ,as levd did, recreating the image from an upgraded box.  And why not using the Ghost tools to facilitate the job. 

 Hi Levd,

Did you ever get to the bottom of this problem?

Kind Regards,
Ian./