Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

very slow on running program

Original Message
Name: shahram_khatabi
Date: February 12, 2008 at 23:52:36 Pacific
Subject: very slow on running program
OS: Novell
CPU/Ram: P4/256Meg
Comment:
Dear sir/madam
I have set novell 4.11 server on P4 1800 MHz with 256Meg ram.whenever I restart the server all my clients can work with application program on server very slowly for 10 to 20 Minutes then it works normally and the speed changes and running and changing the menus of application program become normal.All clients work with dos 6.22 OS.I don't know where I have not configure the server well because I saw other network administrators work with similarity case(on both hardware and software) but doesn't have this problem.so I avoid from restarting the server az far az I can,because it become slowly for 10 to 20 minutes when my clients work.also during this time the LED of Hard server on and shows that work so much until situation become normal.My application program on server is on foxpro.be happy to help me and hearing from you soon,thanks.(shahram_khatabi@yahoo.com)


Report Offensive Message For Removal


Response Number 1
Name: paulsep
Date: February 13, 2008 at 05:04:05 Pacific
Subject: very slow on running program
Reply: (edit)
Netware servers should only be restarted, if necessary.
The longer a netware server is running, the faster it gets, because netware optimizes a lot of things and a lot of files will be cached into the memory for faster access.
You can check the "Long Term Cache Hits" in the monitor program at the server console.
The value should show 80 percent or higher.
After a reboot, the value is less then 50 percent and rises, the longer the server is up and running.
If this isn't the case, the server needs more memory to increase the speed.
On netware 4.11 the only things you need is fast harddrives and memory (the more, the better).
It's absolutely possible to let 100 clients work an a netware 4.11 server with 133 MHz processor, fast harddisk and a lot of memory installed at the server, without performance issues.
So maybe the Foxpro database is consuming a lot of memory.


Report Offensive Follow Up For Removal

Response Number 2
Name: shahram_khatabi
Date: February 13, 2008 at 23:08:06 Pacific
Subject: very slow on running program
Reply: (edit)
Thanks about your take care.I have to point something more.I work with 25 clients and I see other network insame position that doesn't have this problem.Also when I restart and work with one client user on application program,the server work slowly on application program for 10 to 20 min too(I should mention that I don't have any speed problem on copying files from one drive to another drive,just slowly on any uses application program).Don't you think it's related to some setting like files and buffer about memory on STARTUP.NCF OR AUTOEXEC.NCF that I should intert or correct it?,I see this line on startup.ncf:
SET RESERVED BUFFERS BELOW 16 MEG=200
Is it right that line with 256Meg RAM. on server?.Anything else should I insert?Thanks again about your take care.
(shahram_khatabi@yahoo.com)


Report Offensive Follow Up For Removal

Response Number 3
Name: paulsep
Date: February 14, 2008 at 07:04:05 Pacific
Subject: very slow on running program
Reply: (edit)
I think, if this problem occurs only after a server restart, it's a database issue.
So it seems, that the foxpro has to check the database at startup, or is reindexing the records in the database or something like that.
Are there any log files of the foxpro, you can check for errors.

Maybe the database couldn't close correctly, if there are some workstations still has opend the database, during the server restart.
So this could end up in database errors so that the foxpro has to check the database at every server restart.


Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: very slow on running program

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




DSHUB24 Connection Problems

need help with dsl and dial up

novel 3.12

help mandriva install last straw!

Icon Scaling in Explorer Bar


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC