27 replies
by mikez1017
by mikez1017
by mikez1017
by phil
by mikez1017
by phil
by mikez1017
One possible cause is that the initial DOS start-up is screwing things up. Novell had this suggestion...
Troubleshooting
- Remove anything in the DOS startup files (config.sys and autoexec.bat).
- simplify the Netware bootup NCF files (IOstart, MSstart, MSauto, IOauto).
- remove SET parameters like Register memory and Start and end memory unclaimed blocks...
- configure the system correctly (EISA config, Hardware conflicts)
- remove boards that would have boot precedence (e.g. Virus scanner board)
Cause
HIMEM.SYS and SMARTDRV.EXE somehow influenced the way Netware is able to register the memory correctly.
Give that a shot...
Al Franco, II
Another hint...
Make sure that you are calling REGISTER MEMORY command before the MOUNT ALL command in Startup.NCF
by mikez1017
Remove or comment ANY entries in your config.sys, leave only Files=40, Buffers=80.
Do the same in autoexec.bat, leave only Echo on, cd nwserver and server.exe
Boot the server and edit your startup.ncf
Remove any line that contains "REGISTER MEMORY" , save and quit
Load servman and verify that under memory, the value: Auto Register Memory Above 16 Megabytes=ON and restart the server.
email me if this does not work, due to in this case you should register the memory manually (a very old board???)
by mikez1017
by techdictator
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.
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 to your memory manager, contact the software vendor who distributes the version of DOS you are running.
by techdictator
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 BIOS is released from Acer, a LOADER.EXE with a revision of 10 or earlier will need to be run.
by techdictator
Additionally:
Config.sys should be empty or at least everything remmed out.
Autoexec.bat should only run server.exe or mserver.exe it should load, run, or execute nothing else!
by mikez1017
by shellyewton
I have ran into the same situation.
What I found worked for me was manually registering the memory in the Autoexec.ncf file. The command register memory must be executed before mount all. Also, don't forget to put in the correct hexadecimal number amount after register memory. (example: register memory 1000000 F000000 for 256)You must also make some changes to the Startup.ncf file. There should not be any memory loads in this file, however the commands..set reserved buffers below 16 meg=300, and set auto register memory above 16 megabytes=off will help. The reserved buffers will aid in keeping your cache buffers to an optimal level while loading nlms and you do not want the auto register memory on if you are manually registering it in autoexec.ncf.You must down the server and bring it back up to reflect these changes.
Good luck.
by mikez1017
CONFIG.SYS file
If a memory manager ( like 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.
No memory managers should be instaled during normal server operations!!!
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 to your memory manager, contact the software vendor who distributes the version of DOS you are running
Any DOS version grater than 5.0 is OK
by mikez1017
by techdictator
by mikez1017
by mikez1017
by techdictator
by mikez1017
by mikez1017
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending