🚀 go-pugleaf

Just wanted to thank you all for the replies. You have all helped to make my
life a little easier. I've been messing with this stuff for about three or four
weeks now and its been interresting to say the least.

Thanks again.

One more little thing. I've been messing with netware connect and due to my
limited funds have been using a 14.4 modem on the server since its the only
dos/netware applicable modem I have. I've been trying to remotely connect but
the only other modems I have are 56.6 winmodems. Unfortunetly I have been able
to make a solid connection to the network. I've been told that this is becuase
I'm using a 56.6 to dial into a 14.4. What's your ideas? I'm hoping to upgrade
it this week end to a 36.6.

Thanks.

Brian Williams wrote:

> Bud Durland wrote:
> >
> > daulphin wrote:
> > >
> > > 1. When the server.exe is executed and the system goes through its
> > > display of the NLM's that load and don't load is there anyway to to
> > > create a log file that records what is outputted on the screen. I'm sure
> > > that some of my NLM's aren't loading correctly but it scrolls by to
> > > quickly. Any solution would be great.
> >
> > Netware usually puts LOAD CONLOG very close to the beginning of the
> > AUTOEXEC.NCF.  Unless your AUTOEXEC.NCF is running from the DOS
> > partition, you can mve it up to just past the INTENRLA IPX NUMBER line.
> > CONLOG Creates a log file in SYS:\ETC that contains all the messages
> > sent to the console.  Simply UNLOAD CONLOG, then read the file (named
> > CONSOLE.LOG, I think).  Of cours,e you'll miss messages generated by
> > anything that loads from the STARTUP.NCF.  I've not tried putting a copy
> > of CONLOG.NLM in C:\NWSERVER and loading it in the STARTUP.NCF (it will
> > let you specify a file name, so you can point the log file to the DOS
> > partition). I believe I'd do so with caution, though.
>
> I tried to get it to run in STARTUP.NCF and finally gave up.  It
> autoloads CLIB and STREAMS, and I just couldn't get the whole package to
> go in STARTUP.
> > > 3. Have any of you used Netware Connect? What do you think of it. What
> > > would you recomend instead. Would you use something like Cytrix
> > > Winframe/MetaFrame instead?
> >
> > Never used NWC.  For simple file tranfer I think I'd like ite better
> > than WinFrame.  Remember WinFrame is an NT server that creates a
> > 'virtual machine" for each connection.  We have a WinFrame server that
> > was forced on us as part of a software package.  It is used steadily by
> > 5-7 people everyday.  Only after we upgraded it to a *dual* 400 Mhz P-II
> > with 512MB of RAM and a F/W SCSI Raid was performance acceptable.
>
> We use Netware Connect and it works quite well for Remote LAN Node
> work.  If you need remote control, I would use NWC and add pcAnywhere
> over IPX.
> >
> > > 4. How exactly does one go about Creating a network printer from a
> > > printer attached driectly to a workstation. I would love to just go the
> > > full route and get a little printer server (jet direct device) and do it
> > > that way  but money is my main contraint. I've also heard that by doing
> > > this one could stan to learn alot more.
> >
> > Create the print queue in NDS using NWADMN95.  Create a printer, and
> > make sure it's communications properties are set to "remote parallel".
> > At the workstation running Windows95, navigate to F:\PUBLIC\WIN95 and
> > run NPTR95.  I'll leave it as an exercise for the student to figure out
> > how to make it work from the Startup Group.
> >
>
> You left out the step of creating a Print Server and configuring the
> printer list there, then running PSERVER.NLM.
> --
> Brian Williams
>
> Experience is what you get when you didn't get what you really wanted.
> Support the anti-Spam amendment Join at http://www.cauce.org/
> Hunt spammers with SamSpade!  http://www.blighty.com/products/spade/
> More spam hunting tools: http://www4.ncsu.edu/~aiken/antispam.html