Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NWDOS 7 & NYB Virus

0 views
Skip to first unread message

Steve Lenaghan

unread,
Aug 25, 2003, 1:02:48 PM8/25/03
to
We use NWDOS7 on a small Telephone Answering Service running under
NWLite and we've had a few hiccups lately. While archiving a disk from
the answering into my windows machine I got an alert that the disk had
the NYB virus. We had our system infected with this several years ago
and thought we got it cleaned up. I have tried some Norton rescue disks
and even hooked up the drives in a window machine to test and I am not
convinced the problem is gone. I tried running the NWDOS resident virus
tester, (it's old but so is NYB) but I get a memory allocation error.
The server is a 486 IBM with 64 meg of memory. I am trying to move
everything onto our NWSB server but there are issues since the answering
program is peer to peer.

I have:

470 K free conventional memory available
10 M Extended available
55 M Extended by XMS available
33 M EMS available

The math is out but that's what MEM says

I also get "File Sharing Conflict reading device NWLITE" sometimes

I don't have any 3rd party memory managers installed (I have Quarterdeck
8.0 which was in when the system was MSDOS 6.x, since removed)

TIA

Steve L.

Dave Lunn

unread,
Aug 25, 2003, 3:42:59 PM8/25/03
to
NYB is a DOS boot sector virus. Go to http://www.sophos.com and d/l Sophos.
It is more cumbersome than other option, but it's free and it works. You
almost certainly will have other boot sector virii as well, I would expect
stealth boot b and c.

--
Dave Lunn
NSF SysOp
http://support.novell.com


Steve Lenaghan

unread,
Aug 26, 2003, 11:56:33 AM8/26/03
to
Nice DOS virus package, but there weren't any viruses, so it must be a memory
setup problem that is giving the same symptoms as I had when the machine was
infected.

Installing NWDOS reduced the problem with the program clocks stopping. In
desperation I put up an extra PC to run the function that used to run on the
server. Now the server is a server and the program runs on its own, and no more
'clock-outs'.
I am getting closer to putting the system on the NWSB server.

It is obvious I have totally screwed up the memory setup for the server. I have
QEMM v8 but have concerns about using it with NWDOS. Your opinion?

TIA

Steve

Dave Lunn

unread,
Aug 26, 2003, 12:46:21 PM8/26/03
to
QEMM 8 is an excellent program and got over almost all the bugs associated
with the 7.x series. It works very well with NWDOS, and in certain very
specific sitautions it can be quite useful.

It has no business on a Netware 4.x server of any sort though

Normally with NWdos patched I use emm386 and dpmi. I find that with PNW i
can get very stable performance and pretty much always load with ~620K
available. So, I don't much use QEMM as you will. I often use PCKWIK with
NWDOS and PNW though because it gives me an extremely fast cache of
configurable size and on a PNW server can really boost performance a lot.

Steve Lenaghan

unread,
Aug 26, 2003, 1:21:41 PM8/26/03
to
Ok, I will gut out the existing memory commands with NWDOS and run QEMM 8
(unless it does it for me) and try that route.

The NWSB boots on MSDOS 6.x and I'm not playing with that machine since
everything runs just fine.

I have 5-6 unopened QEMM 8 for anyone who wants one. Ya hafta read what you're
buying on eBay!

Steve L.

0 new messages