Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Memory Allocation Error

Created: 10 Nov 2010 | 3 comments
bosworthj's picture
0 0 Votes
Login to vote

I have an HP Probook 6550b that I am trying to image.  I was able to pull an image from it okay, but now when I try to push the image to my other 18 laptops I am getting the memory allocation error right after the command where it changes the computer name.

Change computer name to 1cc1dea34ac0

Memory Allocation Error

Cannot Load Command, System halted

I create my network boot disks on a floppy and then I use the hp drive key boot utility to put that floppy disk on a bootable USB drive.  I have tried to boot with the floppy disk in a usb floppy drive and I get the same error. 

I am using Boot disk creator version number 6.8.8297  I have done this with countless other machines and it works fine.  It seems to be someting with this particular model.  I even got a new driver for the network card and tried that.  It seems intermitent that it does work.  I have two of the laptops that I was able to image but that was after having gotten this error message the first 20 times I tried.

 

Thanks,

Comments

bosworthj's picture
10
Nov
2010
0 Votes 0
Login to vote

Memory Allocation Error

Just a quick addition, it seems that the error is popping up in the process of running the aname.exe command.  I added a couple cls commands to the startnet.bat file and it jumps to a clear screen after the netbind.com command, runs the aname.exe command, output on the screen says it has changed the computer name, but then it never gets to the tcptsr.exe command which is next.

Tomek S's picture
23
Nov
2010
0 Votes 0
Login to vote

I have exactly the same issue

I have exactly the same issue on VMWARE ESXi 4.1 and Altiris 6.8. Actually I am not getting any error - the VM just freezes in the moment it executes aname.exe

Phyrant's picture
06
Dec
2010
0 Votes 0
Login to vote

RDeploy ?

I've seen this problem with a couple models of Dells but only when using RDeploy to pull or push an image. Changed the job to use Ghost and works fine all the time.