Hang during creating NW partition!

[richard]

I have tried to install NW 3.12 to my PC with a IDE 4.3 harddisk (primary
master). First, I have created a bootable DOS 6.22 partition with fdisk and
format, then type 'install' in DOS prompt, and select to retain the DOS
partition afterwards; then it copied all the things needed for the Dos
partition of NW. After entering the system console, I load ide.dsk for the
harddisk and select those port and interrupt number detected. Then, I go to
create the netware partition; however, once select create the netware
partition to the free space. The server seems to be hanged and no reponse at
all, then, I force it to restart and re-enter into the system console and
back to 'disk option', and it reported that the netware partition has been
created! I then go to 'volume option', and select to create a SYS volume,
however, the screen just flash with a message 'Please wait' for 15 mins or
more without finishing to create SYS volume.

Do I use the wrong driver for the harddisk? or does it really need more time
to finish the job?

Richard

[Barry Schnur]

Could you describe the full system configuration a bit further?

Barry Schnur
Novell Support Connection Sysop

Please post replies ONLY via the Newsgroup

[Felton Green (SysOp)]

Hi

I'd use the ide.exe drivers:

20 Sep 1994 ide.exe 35K IDE driver supports Current Parameters

from:

http://support.novell.com/filefinder/147/index.html

and it's best to use normal drive in the paramaters of the BIOS instead of
LBA.

--
Felton Green (SysOp)
Novell Support Connection Forums

[richard]

Barry, thanks for your response!

The MB used is from Pcchips (however I have forgotten what model it should
be), that I purchased in the fourth quarter last year, Duron 1G, onboard SIS
display chipset, 4.3 G Fujitsu IDE harddisk (primary master). I have
previously gone through some of the posts response from you and known that
the harddisk has better to set LBA off; however, once I tried to turn this
LBA off, fdisk reported that my harddisk volume was only about 504M.
Besides, when I commence to install NW, it prompt me to create the DOS
partition, at this momemt, it reported my DOS paritition was about half size
of the original size, but the free space seems to be reported correctly.

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message
news:73pekugsko3om93vl...@4ax.com...

[Barry Schnur]

OK -- it is possible that the Duron is causing some problems here -- that is a
LOT faster than Netware 3.12 will use. Also, the embedded video can be
setting up a memory conflict as well.

[richard]

Barry, so you meant that I can't sucessfully install NW312 until I replace
my MB to older one? As far as I can still remember that I can sucessfully
install NW5.0 / 5.1 to this PC with the same configuration. Now, I just want
to install NW312 to do some testing!

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:tl1fkuoavvps79r3e...@4ax.com...

[Dave Lunn]

Richard,

Barry might be right here, but you might have put a wrench in the works too.

You need to be sure to start this install using IDE.DSK drivers and not
ISADISK.DSK or what you experienced can come visit you. Even using IDE.DSK
drivers the problem of a drive greater than 1 gig still can rear it's head
and you may have to create a NW partition of only a few hundred meg to
install into. With 3.12 you need only five meg for a the DOS partition and
so should not exceed 528 meg total for both until you have it patched. If
you already have a DOS partition that's larger it's ok, as long as you don't
exceed 1 gig total wih the Netware partition added until you have it patched
of you use IDE.DSK.

Once that install is completed and you have patched the server up to date,
then you have two choices, re-install and repatch using the IDEATA.HAM
drivers so you can access the rest of the drive to create the full size
Netware partition or you need a third party product like Storage Manager fro
http://www.portlocksoftware.com or ServerMagic from
http://www.powerquest.com . You may be able to fins a version 3 or 4 for
server Magic on ebay reasonably. Both are excellent products to resize
partitions. both will work for you. If you are going to be using NW 5.1 or
later and NSS volumes just go get Storage Manager now.
--
Dave Lunn
NSCV Sysop
http://support.novell.com

[Dave Lunn]

Speech impediment in your fingers Felton ? <G> IDE.DSK if he has to D/L it,
ide.EXE will be hard to find on the site.

[Barry Schnur]

>Barry, so you meant that I can't sucessfully install NW312 until I replace
>my MB to older one? As far as I can still remember that I can sucessfully
>install NW5.0 / 5.1 to this PC with the same configuration. Now, I just want
>to install NW312 to do some testing!

Perhaps -- I can't be sure. I have never run 3.12 on anything faster than a
Pentium II 400 since anything faster than that won't do anything for
performance at all. Also, some other folks have reported set up issues trying
newer and faster hardware with 3.12 (after all, 3.12 is 10 years old).

Also, that embedded video -- I avoid that on servers as much as I can for
various reasons. Heck, folks have had some struggles with newer Dell servers
that have embedded video and installing 5x versions of Netware.

[Felton Green (SysOp)]

Hi Dave

Check again... it's listed as ide.exe... at the URL I posted. %^ )

[richard]

Thanks Dave, Barry & Felton for your valuable experience and advices!

I have updated the ide.dsk and it works! I can create the NW partition and
sys vol. without encountering any problems.
However, another problem come.

First, I have tried to create the startup.ncf with the following statement:
"load ide port=1F0 int=E"

Then, I create autoexec.ncf with the following statement:
"file server name LUEN"
"ipx internal net 3D476224"
"load msm31x" ;this is required to load Lan driver
"load ethertsm" ;this is required to load Lan driver
"load fenwsrv port=c800 frame=ethernet_802.2 name=fenwsrv_2_e81" ; Lan
driver
"bind ipx fenwsrv_2_e81 net=CEE71119"
mount sys

when I restart the server, after loading ide driver, it then mount sys vol.
before running autoexec.ncf. It make me feel strange!
Because of mounting sys before loading Lan driver, the Lan driver (fenwsrv),
which is placed in c:\server.312, is reported to be unable to load. I have
tried to troubleshoot by clearing all the statement in autoexec.ncf and left
the startup.ncf unchanged and I found that once ide.dsk was loaded in
startup.ncf , the sys vol will be mounted automatically. If I load ide.dsk
manually, it wouldn't mount sys vol automatically.

Felton, when I come across some posts, you have said that the installed 3.2
Enchanment Pack can be removed in product option. However, when I tried to
remove this pack from product option by pressing del, an error message
"Could not load 32ENH Pack" ! What can I do?

Richard
"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message
news:fzZ19.52$O2....@prv-forum2.provo.novell.com...

[Felton Green (SysOp)]

Hi

The only way to get the sys vol to NOT mount is by launching the server.exe
with the -na option.

Have you loaded the 3.2 enhancement pack?

[Barry Schnur]

>
>when I restart the server, after loading ide driver, it then mount sys vol.
>before running autoexec.ncf. It make me feel strange!

>Because of mounting sys before loading Lan driver, the Lan driver (fenwsrv),
>which is placed in c:\server.312, is reported to be unable to load. I have
>tried to troubleshoot by clearing all the statement in autoexec.ncf and left
>the startup.ncf unchanged and I found that once ide.dsk was loaded in
>startup.ncf , the sys vol will be mounted automatically. If I load ide.dsk
>manually, it wouldn't mount sys vol automatically.

Right, this is true, what you need to do is edit autoexec.ncf so that it
references the DOS path to the LAN driver (Load C:\Server.312\fenwsrv etc.)

[richard]

Thanks Felton & Barry's solution for loading Lan driver!

Since the lan driver can't be loaded from autoexec.ncf, I load all the
dirivers, including disk driver, lan driver and then mount the sys vol
manually. Then, I install the enhancement Pack in product option. During the
installation, everything goes OK! After restarting the server, I load all
the things manually and go to product option and try to remove the
enhancement pack. An error was shown "Could not load 32ENH pack".

Sorry, nearly forget another problem, when I tried to run syscon in a
Chinese win98 workstation with the lastest novell client, an error message
showed that a file (however, I haven't written it down) seems to be
something like that as "BIG5$XXX.OVL" is missing. I think it seems to be
something related to Chinese character (BIG 5) display.

Richard
"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message

news:vV029.158$6g....@prv-forum2.provo.novell.com...

[Barry Schnur]

>Since the lan driver can't be loaded from autoexec.ncf, I load all the
>dirivers, including disk driver, lan driver and then mount the sys vol
>manually.

Again, the lan driver CAN be loaded from autoexec.ncf. Just reference the DOS
path for it.

[Felton Green (SysOp)]

Here is the procedure to load the lan drivers:

Load LAN Drivers

Once the SYSTEM and PUBLIC files are copied, continue the installation
process by loading LAN drivers.

Select LAN drivers for the cabling system and the network boards you
use.

Frame Types for Ethernet Networks

The default Ethernet frame type for NetWare v3.12 is 802.2.

If you have a mixed environment where you have NetWare v3.11 or earlier
that use the 802.3 frame type, you may need to specify both 802.2 and
802.3 frame types.

To do this, you load the LAN driver twice and specify a different frame
type each time the LAN driver is loaded.

A workstation running the 802.3 frame type can't communicate with the
NetWare v3.12 server (which defaults to 802.2) until both frame types
are loaded.

IMPORTANT: Some routers may not support the Ethernet 802.2 frame type.
Check your router's documentation and load the frame type the router
supports.

IMPORTANT: Loading both 802.2 and 802.3 frame types can affect network
speed and performance. Standardize your network on 802.2 if possible.

Procedure

1.Load the drivers with the default frame type.

LOAD LAN_driver <Enter>

Third-party drivers are also included with NetWare v3.12, including
drivers from 3COM®, Cabletron, Datacom, Hewlett Packard®, IBM, Intel®,
Madge, Proteon®, Racal, Standard Microsystems, Thomas-Conrad, and
Ungermann-Bass®.

The LAN drivers are copied to SYS:SYTEM and can be loaded from there.

1a.(Conditional) If you are loading a Novell-supplied LAN driver,
replace LAN_driver with the driver listed in Table 2-4 for your
cabling system and network board.

1b.(Conditional) If you are loading a third-party LAN driver, load the
driver from SYS:SYSTEM or from the diskette that came with the network
board.

For example, if you have an Ethernet cabling system and an NE2000
network board, type

LOAD NE2000 <Enter>

2.Answer the prompts for addresses and interrupts according to the
information you entered on the File Server Worksheet.

3.(Conditional) Load the drivers with another frame type. Type

LOAD LAN_driver FRAME=frame_type <Enter>

Replace frame_type with the frame type for your cabling system and
network board.

For example, if you have an Ethernet cabling system and an NE2000
network board, type

LOAD NE2000 FRAME=ETHERNET_802.3 <Enter>

If the LAN driver has been loaded previously, a message similar to the
following appears:

Do you want to add another frame type for a previously loaded board? n

4.Type "Y" to continue.

5.Select the correct frame type from the confirmation list.

The following message appears:

Previously loaded module was used re-entrantly

For more information, see " Load LAN Driver" in System Administration.

Bind the Protocol to the LAN Driver

The final installation step is to bind the protocol to the LAN driver.

NetWare v3.12 allows protocols other than IPX to function on the
network. The steps below use IPX as an example protocol to bind each LAN
driver in the file server.

Procedure

1.Bind IPX to the LAN driver.

1a.To bind IPX to each LAN driver, type

BIND IPX TO LAN_driver

If you use multiple frame types on the same network board, NetWare v3.12
lists the frame types that are loaded and asks you to select the board
you want to bind IPX to.

You can bind IPX to all those frame types, as long as you give a
different network address to each frame type.

For more on network numbers, see "Network numbering" in Concepts.

1b.If you have loaded the same LAN driver several times (for several
network boards of the same type), select the board to be bound to the
protocol.

1c.To bind a protocol to a driver that is loaded with two or more frame
types for the same network board, see " BIND" in System Administration.

2.Assign the network address.

Each LAN driver must be assigned the network address that identifies the
cabling system it uses to communicate with similar LAN drivers on the
network.

NOTE: This network address is not the same as the internal IPX network
number you assigned to the file server in Step 2.

At the prompt, type the number that enables the LAN driver and network
board in the file server to communicate with the network. The address
must be

A hexadecimal number (base 16: using numbers 0 through 9 and letters A
through F).

One to eight digits.

NOTE: If you use multiple frame types with your LAN drivers, assign a
network address for each frame type.

[Felton Green (SysOp)]

Hi again

Why are you trying to remove the 3.2 enhancement pack?

[richard]

I am now doing a test to see whether the 3.2 enhancement pack can be
removed, because I will help my client to remove his illegal copy of 3.2
enhancement pack. If it is not possible to remove, I will plan to re-install
the server without enhancement pack and patch it using 3.12 patches.

Richard

"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message

news:pP229.202$6g....@prv-forum2.provo.novell.com...

[richard]

I get it and I will try later! Thanks Barry!

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:15dhku8ajo78us1vg...@4ax.com...

[Barry Schnur]

OK -- let us know.

[Felton Green (SysOp)]

Hi

Ok..

[richard]

Barry, I have tried to load the lan driver after mounting SYS vol by
inserting a statement (i.e. "load c:\server.312\fenwsrv
frame=ethernet_802.2") in autoexec.ncf. It works; however, I have tried
another scenerio that I just install NW 312 without patching it with 3.2 EP
and load the same statement after mounting SYS vol.. An error message (i.e.
"loader cannot find public symbol: MSMGetPhysical, load file referenced
undefined public variable, Module Fenwsrv.lan not loaded") resulted. I have
also tried to mount SYS vol after loading Lan driver, it's OK! Therefore, I
would like to ask how can solve this problem, if I am not intended to
install 3.2 EP (because it is the illegal copy). What patch do I need first?

In the previous post, I also mentioned that when I tried to run syscon in a
novell client installed in Chinese Win98, an error message was shown as "The
system was unable to load overlay file Big5$run.ovl, Program Initialization
Failure - execution Terminated". How can I fix this problem?

Thanks!
Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:uvlhkusn7c8si6ueo...@4ax.com...

[Felton Green (SysOp)]

Hi

Have you tried a search add statement in the autoexec.ncf?

i.e;

search add c:\server.312

right after the server name and internal number.

[Barry Schnur]

Understand that the 3.2 EP is a collection of the same patches which you can
download and apply manually to 3.12.

So, if you have a 'new' 3.12 server, you would need to install it, then apply
all the updates we have listed.

Note further, for 331 driver support (and it that is a 10/100 NIC it probably
relies on that), you need at least the CLIB and 312PTD updates plus the later
versions of MSM31X, NBI31X, and Ethernet.nlm.

[richard]

Thanks Barry!

I have read the list of patches that you have mentioned in
http://support.novell.com/filefinder/147/index.html . However, there are far
too many patches need to be applied and the corresponding change shin
autoexec.ncf or startup.ncf. So I would like to ask what are the minimum
patches that I really need to apply so that the server can run normally from
starting.
Here is the patches that I decided to apply in order from frist to last:
1. 312ptd.exe
2. lib312d.exe
3. nwpaup1a.exe
4. 312y2kp2.exe
5. strtl8a.exe

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:nqtjkuc9p7knfltg8...@4ax.com...

[Felton Green (SysOp)]

Hi

It is recommend that you install all updates/patches that pertain to your
system. Only leave out those that are obviously not applicable... i.e.
MAC if you don't have any MACs on your network.

Here is a process that will help things out...

make the following directories on your workstation:

patches
patches\system
patches\system\4\nls -this directory is only for English, your system
may vary

patches\login
patches\public

boot\server.312

Download all the updates and expand them out in the temp directory. Move
the updates to the directory that they will wind up in on the server.

You will have some that require an installation and you can do those
separatly.

[Barry Schnur]

>1. 312ptd.exe
>2. lib312d.exe
>3. nwpaup1a.exe
>4. 312y2kp2.exe
>5. strtl8a.exe
>

That is a decent start for a new server, although in that sequence, you will
likely need to use the manual LSWAP routine we posted many messages ago.

[richard]

Thanks Barry & Felton! I will anyway try to install them all!

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:g96kkuo5kd66bdiik...@4ax.com...

[Barry Schnur]

OK -- I am sure you will let us know the results.

[richard]

Hi, Barry!

I have tried to install most patches to the server and it seems to work!
However, I have not fully tested it to see whether it 'really' works!

Here are the patches that I applied:
CRON.EXE
CLIBAUX1.EXE
LIB312D.EXE
312Y2KP2.EXE
NWPAUP1A.EXE
STUFKEY5.EXE
CDUP5A.EXE
TCOPY2.EXE
TBACK3.EXE
312PTD.EXE
VRP386.EXE
BNDFX4.EXE
SMSUP6.EXE
NW3DFS.EXE
NAM312.EXE
LANDR.EXE
SBACK6.EXE
ATK307.EXE
MON176.EXE
PS3X02.EXE
SYS376.EXE
MAP312.EXE
LOG376.EXE
PU3X01.EXE
IDE.EXE
PS2OPT.EXE

I think you would discover that I haven't applied any things else related to
IPX/SPX or TCPIP protocols because I don't which version of MPR that my
server installed. The article mentioned that those patches, such as
mpr31b.exe, tcp312.exe, ipx660.exe, etc, should not be installed to the
server with version of mpr below 2.0, so I haven't installed these patches!

I would also like to ask what are the file 'big5$run.ovl' used for? I still
can't use syscon in chinese win98 because of missing this file.

I have also tried to load memory in console after running server -na -ns,
and it told me that the registered memory was only 16MB. Previously, I have
tried to register the memory manually according to some posts from you /
Felton; however, it still showed only 16MB. ????

Anyway, thanks again for your precious advices!
Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:dfakkusf86ds94ksb...@4ax.com...

[Barry Schnur]

>ATK307.EXE -- Not needed unless you have Macintosh computers in the mix
>IDE.EXE -- NWPAUP1A replaces this.

>
>I think you would discover that I haven't applied any things else related to
>IPX/SPX or TCPIP protocols because I don't which version of MPR that my
>server installed. The article mentioned that those patches, such as
>mpr31b.exe, tcp312.exe, ipx660.exe, etc, should not be installed to the
>server with version of mpr below 2.0, so I haven't installed these patches!

If it is a newer NIC, you should apply these updates and assume ODI 331

>
>I would also like to ask what are the file 'big5$run.ovl' used for? I still
>can't use syscon in chinese win98 because of missing this file.

Not a clue here -- sorry.

>
>I have also tried to load memory in console after running server -na -ns,
>and it told me that the registered memory was only 16MB. Previously, I have
>tried to register the memory manually according to some posts from you /
>Felton; however, it still showed only 16MB. ????
>

Since you have applied the updates (and you mentioned applying 312PTD before
the CLIB update), you should now use this approach at the server:

The LSWAP.EXE (loader patch) applies updates to server.exe. There are at
least THREE areas where server.exe updates are needed:

1) Memory registration
2) Date handling (which also requires that LIB312D.EXE be in place)
3) Public symbol errors (which manifest when one tries to use current
specification disk and network card drivers).

Here is the procedure to use:

LSWAP EXE
============

The defaults used in the command lines are from Netware 4.1x handling so for
the typical 3.12 server update, if it does update automatically, you will
need to not only run it manually, but make sure that you use the correct path
setting.

Both LSWAP.EXE and LSWAP.NLM use the same command line options. First
option specifies the location to LOADER.EXE.

(DEFAULT:C:\NWSERVER\LOADER.EXE).

The second option specifies location to SERVER.EXE or MSERVER.EXE.

(DEFAULT: C:\NWSERVER\SERVER.EXE).

So, it the typical scenario where you need to run this manually from the DOS
prompt in the C:\Server.312 directory, you need to do the following:

1) Make sure that both LSWAP.EXE and LOADER.EXE are in the Server.312
directory.

2) Then use the following command syntax:

LSWAP C:\SERVER.312\LOADER.EXE C:\SERVER.312\SERVER.EXE

3) When this is done, you should end up with a SERVER.EXE with a new date and
a copy of the old server.exe as SERVER.OLD with the old date.

After you've done this, as a test to see if the memory is being
autoregistered, start the server with:

Server -ns -na (This forces it to run with out your start up files).

Then feed it a name and net number (its not critical what you feed it for
this test).

Then at the console prompt, type: Memory

If it reports 16M - then you will need to use manual memory registration
techniques. If it reports your actual memory (say 32M, 48M or 64M) then
autoregistration will work.

[richard]

Thanks Barry!

OK! I will try to see!
If it still won't work, what can I do as well?

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:hogmkuk7vd84i4rpc...@4ax.com...

[Barry Schnur]

Well, perhaps try again <smile>

[Felton Green (SysOp)]

Hi

You need to apply the lswap procedure for the memory most likely.

The possibility that the server.exe in the DOS partition did not get
updated. This the procedure to update the server.exe:

LSWAP EXE
============

The defaults used in the command lines are from NetWare 4.1x handling so

for the typical 3.12 server update, if it does update automatically, you
will need to not only run it manually, but make sure that you use the
correct path setting.

Both LSWAP.EXE and LSWAP.NLM use the same command line options. First
option specifies the location to LOADER.EXE.

(DEFAULT:C:\NWSERVER\LOADER.EXE).

The second option specifies location to SERVER.EXE or MSERVER.EXE.

(DEFAULT: C:\NWSERVER\SERVER.EXE).

So, it the typical scenario where you need to run this manually from the
DOS prompt in the C:\Server.312 directory, you need to do the following:

1) Make sure that both LSWAP.EXE and LOADER.EXE are in the Server.312
directory.

2) Then use the following command syntax:

LSWAP C:\SERVER.312\LOADER.EXE C:\SERVER.312\SERVER.EXE

3) When this is done, you should end up with a SERVER.EXE with a new
date and a copy of the old server.exe as SERVER.OLD with the old date.

After you've done this, as a test to see if the memory is being
autoregistered, start the server with:

Server -ns -na (This forces it to run with out your start up files).

Then feed it a name and net number (it's not critical what you feed it
for this test).

Then at the console prompt, type: Memory

If it reports 16M - then you will need to use manual memory registration
techniques. If it reports your actual memory (say 32M, 48M or 64M) then
autoregistration will work.

[richard]

Hi Barry,

I have tackled most problems during the installation and I have tried to
install ODI33G as well; however, it seems to work not well as a whole, so I
decided not to install finally.

Here, I would like to ask how can I know the total server memory is correct
or not, if I use the manual registration of memory (I have also updated the
server.exe as well using the patch from 312ptd).

Anyway, thanks you and Felton as well!
Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:uqmmkucatb85futfk...@4ax.com...

[Barry Schnur]

>
>Here, I would like to ask how can I know the total server memory is correct
>or not, if I use the manual registration of memory (I have also updated the
>server.exe as well using the patch from 312ptd).
>

Well first, if the patches are in place, the server should autoregister
memory.

At the console prompt, type: Memory

What is reported.

Please post your startup.ncf file as well.

[richard]

Barry, I haven't got the config.txt on hand. However, I have both
startup.ncf & autoexec.ncf .
Here is what the startup.ncf and autoexec.ncf includes:

startup.ncf
;******* PM312 is the NW v3.12 Patch Manager. ********
LOAD C:\SERVER.312\PATCHES\312PTC\PM312
PMLOAD C:\SERVER.312\PATCHES\312PTC\
;** PMLOAD loads all patches in directory specified.**
set auto register memory above 16 megabytes=off
set reserved buffers below 16 meg=300
rem load c:\server.312\mmattrfx.nlm
rem load c:\server.312\nwpaload.nlm
rem load c:\server.312\ideata.ham port=1f0 int=e
rem load c:\server.312\idehd.cdm
rem load c:\server.312\idecd.cdm

autoexec.ncf
file server name LUEN
ipx internal net 3D476224
register memory 1000000 b000000
load c:\server.312\mattrfx.nlm
load c:\server.312\nwpaload.nlm
load c:\server.312\ideata.ham port=1f0 int=e
load c:\server.312\idehd.cdm
load c:\server.312\ideata.ham port=170 int=f
load c:\server.312\idecd.cdm
mount sys
load msm31x
load ethertsm
load c:\server.312\fenwsrv port=c800 frame=ethernet_802.2 name=fenwsrv_2_e81
bind ipx fenwsrv_2_e81 net=CEE71119
load after311

I have altogether 192MB ram. When I checked back the config.txt from one of
previous installation, total server memory seems to be quoted correctly
(i.e. 159.56 MB).

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:mhnrkuo2dv2ktitq3...@4ax.com...

[Barry Schnur]

>
>startup.ncf
>;******* PM312 is the NW v3.12 Patch Manager. ********
>LOAD C:\SERVER.312\PATCHES\312PTC\PM312
>PMLOAD C:\SERVER.312\PATCHES\312PTC\
>;** PMLOAD loads all patches in directory specified.**

*****>set auto register memory above 16 megabytes=off

>set reserved buffers below 16 meg=300
>rem load c:\server.312\mmattrfx.nlm
>rem load c:\server.312\nwpaload.nlm
>rem load c:\server.312\ideata.ham port=1f0 int=e
>rem load c:\server.312\idehd.cdm
>rem load c:\server.312\idecd.cdm

Remark out the command which is turning autoregistration off.

>
>autoexec.ncf
>file server name LUEN
>ipx internal net 3D476224

******>register memory 1000000 b000000

>load c:\server.312\mattrfx.nlm
>load c:\server.312\nwpaload.nlm
>load c:\server.312\ideata.ham port=1f0 int=e
>load c:\server.312\idehd.cdm
>load c:\server.312\ideata.ham port=170 int=f
>load c:\server.312\idecd.cdm
>mount sys
>load msm31x
>load ethertsm
>load c:\server.312\fenwsrv port=c800 frame=ethernet_802.2 name=fenwsrv_2_e81
>bind ipx fenwsrv_2_e81 net=CEE71119
>load after311
>

Remark out the memory registration here.

Then see if you can restart the server and check to see if the full memory is
recognized.

[richard]

OK Barry, I will try to rem them out!

However, I would wonder if manual registration can't work, can
autoregistration work?

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:91srkukthplo8qnjd...@4ax.com...

[Barry Schnur]

Well, what version of DOS is installed? What does config.sys contain?

What sort of motherboard, CPU combination is in the mix.

[richard]

> Well, what version of DOS is installed? What does config.sys contain?

MS-DOS 6.22 and config.sys seems to contain only a statement "lastdrive=z"
and nothing else.

> What sort of motherboard, CPU combination is in the mix.

Pcchips MB, but has forgotten its model name, purchased in the 4th quarter
last year; Duron 1G CPU, 192 MB Ram and on board video display (SIS).

[Barry Schnur]

It is possible that the onboard video display is causing the problem here with
memory handling.

[richard]

Thanks Barry! I have completely solved the problems arisen from the server.
After remarking the line as you described, the memory can be
auto-registered. Anyway, thanks again for your invaluable support!

P.S. I have nearly forgotten that 32M ram was used for video display, so
that the total server memory displayed = 160 M is correct (i.e. 192-32=160).

Richard

"Barry Schnur" <bsc...@cox.net> wrote in message

news:h0atkuk5cevm2gidk...@4ax.com...