https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl20pg1-g2/m-p/3554319#M42121 Finally we overcame the problem typing the command: "bootworks -dsbios" at the command prompt just after the procedure corruption.<BR />This is the way we are working till now as a workaround and customer is expecting a final solution.<BR /> Mon, 30 May 2005 07:51:18 GMT Peter Loeffel 2005-05-30T07:51:18Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl20pg1-g2/m-p/3554318#M42120 RDP 1.60 / and 2.0 with G1 Server is working<BR />with the G2 servers i got error:<BR />Every time he tried to initialize a new blade the whole procedure was corrupted as soon as the bootworks application was running.<BR />Specifically a crash dump page appears starting with: <BR />"Exiting due to signal SIGVER"<BR />"Page fault at eip=0008908a"<BR /> Mon, 30 May 2005 07:50:08 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl20pg1-g2/m-p/3554318#M42120 Peter Loeffel 2005-05-30T07:50:08Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl20pg1-g2/m-p/3554319#M42121 Finally we overcame the problem typing the command: "bootworks -dsbios" at the command prompt just after the procedure corruption.<BR />This is the way we are working till now as a workaround and customer is expecting a final solution.<BR /> Mon, 30 May 2005 07:51:18 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bl20pg1-g2/m-p/3554319#M42121 Peter Loeffel 2005-05-30T07:51:18Z