Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
strangeness
1 view
Skip to first unread message
James W. Howell
Aug 31, 1994, 9:47:00 AM8/31/94
to
Hi PIB,
I'm at a total loss on what this might be, I have a user who when he
first turns on his machine and then starts Nupop it shows "trying to
establish connection" and then the machine reboots by itself, and then when
he tries to run Nupop again after the warm boot, it works ok. He has other
network applications that he runs (gopher, news, etc...), that work fine the
first time after power up. The machine is a IBM ValuePoint 486, 8 M RAM,
lots of hard disk, etc, with a Western Digital card attached to a Novell net
via ethernet. I've had him try running it with /NOEMS, and erasing the
MLIST.STM file in the in.mbx, but that didn't help. Any help would be
appreciated.
Jim
I'm at a total loss on what this might be, I have a user who when he
first turns on his machine and then starts Nupop it shows "trying to
establish connection" and then the machine reboots by itself, and then when
he tries to run Nupop again after the warm boot, it works ok. He has other
network applications that he runs (gopher, news, etc...), that work fine the
first time after power up. The machine is a IBM ValuePoint 486, 8 M RAM,
lots of hard disk, etc, with a Western Digital card attached to a Novell net
via ethernet. I've had him try running it with /NOEMS, and erasing the
MLIST.STM file in the in.mbx, but that didn't help. Any help would be
appreciated.
Jim
James W. Howell
Cornell Information Technologies - Network Resources Collaboration Systems
Phone: (607)-255-9369 Email: jw...@cornell.edu
Eric C Hagberg
Aug 31, 1994, 10:07:30 AM8/31/94
to
Memory management conflict. Emm386 doesn't "see" the net card when it first
boots, as it hasn't been initialized, so it uses a part of upper memory that
it thinks is available. It isn't, and when NUPop goes to use that space...
well, you've seen what happens.
boots, as it hasn't been initialized, so it uses a part of upper memory that
it thinks is available. It isn't, and when NUPop goes to use that space...
well, you've seen what happens.
Take a look at the amount of upper memory that emm386 reports as usable on
cold boot, run NUPop, and look at what emm386 reports this time. The number
will be smaller now.
You need to exclude the part of upper memory from emm386's grasp.
-ech
+-------------------------------------------------------+
Eric Hagberg Phone: 212-746-4622
User Services Manager Fax: 212-746-8322
Office of Academic Computing Cornell Medical College
0 new messages