After installation of SafeGuard Easy, computer stops at an empty screen with a blinking cursor

  • Article ID: 104142
  • Updated: 27 Jun 2009


Product
SafeGuard Easy multi-platform 4.5x

Client OS

Windows 2000 Professional SP4, Windows XP SP1 Professional Edition

Server OS

Windows 2000 SP4

Question

The installation of SafeGuard Easy went fine, and the machine is shut down. Upon reboot, the computer stops at an empty screen with a blinking cursor.

Answer

This type of behaviour is quite typical for machines, which support PXE boot. Check the boot order in the BIOS of that machine. Is PXE boot enabled?

a) PXE is not really used
Make sure boot from hard disk comes before PXE boot. This solution will help in those cases where the PXE boot option is enabled, but not used by the customer.

b) PXE is actually used and cannot be disabled
In this case, please contact the vendor of the software distribution / installation tool you are using (e.g. NetInstall).

From our experience, the above behaviour indicates that the implementation of the network boot option does not free up the upper part of the conventional memory. (Conventional memory is always filled from top to bottom).

Make sure your vendor provides a modified boot strap which frees up the conventional memory properly.

In case of NetInstall, please contact the manufacturer and ask for a updated version of PXEDISK.

Some background information regarding b):
The software distribution NetInstall (manufacturer Enteo) instructs the machine to load the file PXEDISK via the network. PXEDISK is a bootstrap command. The bootstrap is loaded into the machine's memory. It decides whether to continue booting from network or whether to boot from the local harddrive. If the latter is the case, the program clears the allocated memory. This type of behaviour is typical for any other software distribution vendors.

Unfortunately, the routine which frees the memory is poorly implemented for some (!) network cards. As a result, the conventional memory is not freed entirely. As SGE kicks in, first thing it will do is to wipe 64k of memory from top to bottom of the conventional memory area. As the bootstrap has not freed the conventional memory properly, parts of the SGE filter driver is written to a memory area where it would not be written to under normal circumstance. As a result, SGE will wipe out parts of its own code and the boot process will end on a black screen with a blinking cursor.

If that is the case, the software vendor of the distribution tool needs to adjust their bootstrap file.

Keywords: enteo, isonet

 
If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent

Comments