Networks

Ask something
Discussion Locked

Novell 4.11 Memory Issue

0 helpful
10 replies

by tbeaird

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Novell 4.11 server that has 256MB memory installed. Bios recognizes this, but Novell does not. When I issue the memory and memory map commands, I receive the following:

VINITA_1:memory
Total server memory: 42,143 Kilobytes

VINITA_1:memory map
System memory map:
0 - 12288 (DOS)
12288 - 124976 (DOS)
124976 - 654336 (Server)
1048576 - 33554432 (Server)
258441216 - 268435456 (Server)

As Novell suggests, I have removed DOS memory managers and used the REGISTER MEMORY command in the autoexec.ncf file. Anyone have any ideas on what is causing this problem? I have support pack 8 installed.

thanks

10 replies

by rogerndgreen

If the BIOS recognises the memory and you have removed ALL memory managers from the config.sys file (you basically want nothing in it at all, apart from country code files) then the following extractfrom a Novell TID (TID2937050)may help:

Troubleshooting
To check which version of LOADER.EXE is currently running type "patches" at the server console. The last line displayed will tell you which revision of LOADER.EXE is running. If the "patches" console command is not recognized, then PK411.NLM is not loaded, and no NetWare "Operating System" (OS) patches are being loaded.

Solutions
Problem 1
If a memory manager (himem.sys) is loaded in DOS, instead of making the BIOS INT 15 E801h call to get the memory information, we read the memory information from the memory manager. Thus, if a memory manager is loaded and we are failing to auto register all of the memory in system, we will need to first remove the memory manager from the system since this is where the incorrect values are coming from. To correct this problem, remove the memory manager from the DOS config.sys file. If the memory manager is needed for some reason on the system, then you will need to find out why the memory manager is failing to get the correct values.This could be caused by either the memory manager or an outdated BIOS. If memory registration succeeds without the memory manager loaded, it would seem that the problem then lies with the memory manager and it will need to be updated. For updates toyour memory manager, contact the software vendor who distributes the version of DOS you are running.

by rogerndgreen

(continued)
Problem 2
If memory registration fails when no memory manager is loaded in DOS, and LOADER.EXE revision 11 or later is loaded, then an updated BIOS will need to be applied. To check the version of LOADER.EXE see the "Troubleshooting" section. It has been found that the latest Acer BIOS "R01-A7" dated 01/05/98, has a problem with the BIOS INT 15 E801h call to get the memory information. The reason why this problem has only been noticed since revision 11 or later of LOADER.EXE, is because of a change put into revision 11. The change was made to comply with the BIOS specification. With revision 11 or later of LOADER.EXE we will try to register the amount of "Configured Memory" and not "Installed Memory" as returned by the BIOS INT 15 E801h call. With the Acer BIOS, the "Installed Memory" is correctly returned but the "Configured Memory" is incorrect. Thus, using a LOADER.EXE revision that takes the "Installed Memory" instead of the "Configured Memory" values will work just fine. Acer has been notified of the problem with their BIOS and is currently working to get the problem corrected. There are many vendors that OEM the Acer motherboards and BIOS, so you will see this problem on these systems as well. Until a new BIOSis released from Acer, a LOADER.EXE with a revision of 10 or earlier will need to be run.

Hope this helps.

Roger

by estebandelatorre

Register memory is a and depends on the memory comsumed by the ide interface.
ALWAYS SET:
AUTO REGISTER MEMORY
IN NETWARE 4.1 and above. This is the only
way to assure that you will not cause memory segmentation problems.
If you are unable to successfully auto register memory, then call your hardware
vendor. You will need to get a system board, BIOS upgrade, that allows the auto register memory functionality to work, or you may need to go with a different system board. Also, be certain that the current OS patches are loaded and that the current LOADER.EXE has been applied to SERVER.EXE.
The number to use in the place of is determined by taking the number of megabytes above 16MB and converting it to hex.
An easy way to calculate the number in hex is to take the number of Megs above 16, convert that to hex and add 5 zeros on the end. Example a server with 256 MB total RAM: 256 - 16 = 240
240 in hex is F0. The entry in the AUTOEXEC.NCF would beREGISTER MEMORY 1000000 F000000

Your startup.ncf should look like this:
Set auto register memory above 16 megabytes=off

Set reserved buffers below 16 meg=200 (optional, device dependent)

Register memory 1000000
Load

etc...

by tbeaird

Roger,
I, unfortunately, cannot determine the loader.exe version without performing a shutdown and reregistration with server.exe. Due to the holidays, this is not possible. Thanks for your suggestions.

edt@bancobgn.com,
I have tried thissuggestion previously. Unfortunately, it did not work. Thanks.

by maxwell edison

Use the REGISTER MEMORY command only if absolutely necessary. Manually registering memory can cause memory fragmentation. Ideally, you should upgrade the system board so that NetWare's automatic memory registration will work.

Before using REGISTER MEMORY, try the following:

Review the CONFIG.SYS or AUTOEXEC.BAT files to make sure nothing is being loaded on the server that prevents memory recognition: sometimes a real mode driver or a memory manager stops NetWare from registering memory above 64 MB.

If your server contains an older network board, such as many ISA and MCA devices, upgrade to a newer board.

If you have access to the World Wide Web, search the knowledge base at http://support.novell.com for Register Memory topics.

REGISTER MEMORY start_address amount

start_address

Specify the hexadecimal address where the memory you're adding will start. This is the amount of RAM your server currently recognizes and addresses.

This number is usually 16 MB (1000000h); however, the default varies depending on the machine type.

To obtain the start address, use the MEMORY command and convert its output to hexadecimal.

amount

Specify an amount of memory, expressed in hexadecimal, that is installed beyond the start address. This number must be divisible by 10h. Up to 1 GB can be registered at one time.

Using REGISTER MEMORY:

NetWare registers all memory that it recognizes according to bus type. On an ISA bus, NetWare recognizes up to 16 MB. Onan EISA or MCA bus, NetWare recognizes all of the memory that is present. On a computer with a Peripheral Component Interconnect (PCI) bus, NetWare 6 recognizes up to 4 GB.

(continued...)

by maxwell edison

.
.
(continued...)

To have the additional memory registered automatically when the server boots, add the REGISTER MEMORY line to the STARTUP.NCF file.

IMPORTANT: Place the REGISTER MEMORY command before the command to load disk drivers in the STARTUP.NCF file so that the registered memory will be available to the SYS: volume.

Failure to register memory before volume Sys is mounted can result in error messages indicating that the cache memory allocator is out of available memory, or that there is insufficient memory to mount volumes.

If the memory does not register, check for the following possible errors:

An incorrect hexadecimal value was specified for start address or amount.

The amount value exceeds the total installed memory. Use the setup or reference diskette that came with the computer to determine the total amount of installed memory.

NOTE: You must avoid memory address conflicts. A conflict occurs if an adapter board uses 16- or 24-bit DMA or Bus-Master DMA.

To resolve this conflict, upgrade to 32-bit bus adapters or use drivers that are modified and certified to compensate for memory-addressing limitations. Or use the machine's configuration program to move system memory around the adapter if the program allows.

In some cases, the ISA (16-bit) host adapter driver must be loaded in memory below 16 MB. To do so, add the following to the startup.ncf file:

LOAD disk_driver

REGISTER MEMORY amount of memory to add

256 MB 16 MB = 1000000h 240 MB = F000000h

Good luck,

Maxwell

This discussion is closed to new replies.