lswap patch causes problems
Carl K.
doing a core dump (unless I rename server.old back to server.exe).
I can't tell if I need to install another patch before this one or what.
The problem is persistent and it may have something to do with the incorrect
year that I've been getting (as reported in my other thread).
Any ideas?
Carl
Felton Green (SysOp)
You've gotten an update that seems to affect machines like that and since
Novell does not provide support for discontinued products, you'll not see
any solution.
So.. that being said, you should take the changed server.exe and delete it
and restore the server.old to full use.
--
Felton Green (SysOp)
Novell Support Connection Forums
Carl K.
Carl
"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message
news:4on19.3245$n.8...@prv-forum2.provo.novell.com...
Felton Green (SysOp)
Apply the lib312d.exe update and then apply the lswap procedure.
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.
Felton Green (SysOp)
I didn't notice when I responded before...so I didn't say anything.
Thanks
Carl K.
applying the patch in DOS. I've tried it both in DOS and through the NLM in
the console. I've also just copied the files over manually, but to no
avail.
Carl
"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message
news:kZn19.3258$n.8...@prv-forum2.provo.novell.com...
Barry Schnur
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.
Barry Schnur
Novell Support Connection Sysop
Please post replies ONLY via the Newsgroup
Felton Green (SysOp)
Then try the lswap procedure.
Carl K.
I tried again (on the off chance that I could have done something wrong) to
run the LSWAP.EXE from DOS. I did just as you described (which is
essentially the same as the text file included in the download), but alas
still no joy.
Carl
"Barry Schnur" <bsc...@cox.net> wrote in message
news:2f3cku40v52md5fgf...@4ax.com...
Carl K.
times and using several methods. Please don't cut and paste the directions
from the text file, I've followed them already. Over and over. The renamed
server.old exists, but the newly created server.exe fails to boot up all the
way without a core dump.
Carl
"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message
news:Uco19.3266$n.8...@prv-forum2.provo.novell.com...
Felton Green (SysOp)
Carl,
The latest lswap is flawed. You need to use the older version that will
update your server.exe.
If you did not save the older files you can get them from here:
http://support.novell.com/servlet/tidfinder/2936137
Felton Green (SysOp)
http://support.novell.com/servlet/tidfinder/2936137
Felton Green (SysOp)
It's the one I listed in the last message. %^ )
Carl K.
from the link I got from here. I did save the old files (otherwise, I
couldn't have booted at all) so even though I am grateful for the link
below, I don't need it. Can you instead provide a link to this "older
version" of lswap?
Thanks,
Carl
"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message
news:wko19.3272$n.8...@prv-forum2.provo.novell.com...
Carl K.
This fixed both my lswap AND my incorrect year problem.
Bravissimo!!!!!
Carl
"Felton Green (SysOp)" <felton...@bigfoot.com> wrote in message
news:Alo19.3273$n.8...@prv-forum2.provo.novell.com...
Felton Green (SysOp)
Glad we could help. %^ )