Re: XP x 3+clipper=SLOW



i had a similar problem.

they were causeb by the "commit" command.

no problems working local on w95-winMe, no problems on most
win XP systems working local or on networkdrives, but in some
contsellations the problem occured.

removed the "commit" command from the do....while-loop and placed it
behind the loop....

:-))


"Klas Engwall" <klas.engwall@xxxxxxxxxxxxx> schrieb im Newsbeitrag
news:4377c30c.1323262590@xxxxxxxxxxxxxxxxxxxxxx
> jmilovic,
>
>>1. The slowness i am having is that when opening some dbf, and yes when
>>seeking, reading, writing... I tryed copying a local copy of exe file
>>but that doesnt help, maybe a little when loading exe.
>>Cpu usage is 1-5% (i use oslib)
>>
>>2. I had the problem on "server" when i used mapped drive, now with
>>subst-ed drive works fine.
>
> Hmmm, it sounds like there is something wrong with how the network is
> set up on the "server" and that the Clipper app is just the victim of
> something going on deeper down in XP. Look at drivers and protocols
> for example. Is there anything you don't need that can be turned off?
> Any extra protocols besides TCP/IP? And check if the performance is
> identical if you let one of the workstations take the role of server
> (with mapping vs substing locally and mapping over the network).
>
> What happens if you copy a large collection of files to the C: drive
> from a mapped drive and from a substed drive respectively using the
> command line or Explorer? Any difference there?
>
> IIRC there was a change introduced in XP SP2 that affected write
> performance, but I can't remember the exact details and I haven't
> personally seen that problem. Perhaps someone else can jump in.
>
> You might also want to take a look at Nick Ramsay's networking page at
> http://www.witzendcs.co.uk/html/nt_networking.html
>
> The registry settings affected by Nick's reg files are not primarily
> speed related, but they are considered "required" for systems where
> Clipper applications and similar file sharing apps are run. So it is
> generally a good idea to apply them. They _do_ solve som other common
> problems.
>
> Regards,
> Klas
>
> -------
> klas dot engwall at engwall dot com
>
> http://www.engwall.com/clipper/
>
> The LFN Library for Clipper
> The LanMan Library for Clipper
> The NFPAT1A Timeslice release patch for the Nanforum Toolkit


.



Relevant Pages

  • Re: Dial-up clients drop connections
    ... Both products physically synchronize with the respondent modem, authenticate, attempt to "talk to the network", then drop the connection. ... Extreme cases may warrant the removal of the TCP/IP protocol..With the NetShell utility, you can reset the TCP/IP stack to restore it to its state that existed when the operating system was installed. ... When you run the reset command, it rewrites pertinent registry keys that are used by the Internet Protocol stack to reach the same result as the removal and the reinstallation of the protocol. ...
    (microsoft.public.windowsxp.general)
  • Re: networking problem
    ... > Static IP address configuration in Windows XPe environment HOWTO ... > To be able to be pingable with one ethernet card in your target machine, ... > Network Command Shell ... > Command Shell Interface Context ...
    (microsoft.public.windowsxp.embedded)
  • RE: Network Not Working in Linux ; Works in Windows Why ?
    ... Have you enabled the NIC cards and/or do you have the correct drivers loaded ... Network Not Working in Linux; ... I am giving the outputs of the following command for assitance. ...
    (RedHat)
  • internet ip to local ip with pix
    ... pix inside 10.112.2.241 ... Is 10.2.2.2 inside or outside the network? ... You would need a 'static' command, and you would need a 'route' ... to the outside interface by using the access-group command. ...
    (comp.dcom.sys.cisco)
  • Re: [Info-Ingres] commit question
    ... The next block has been turned into a rollback ... hence the next command executed is the rollback and not the commit. ... The situation we had was that the "modify to truncate" command succeeded ...
    (comp.databases.ingres)

Loading