Where can I get some Config.fp help ?? 1

[FoxEgg]

Is there an URL which has the various settings....

Cheers John Fox

 

[tcitjh]

What exactly is the issue?

Most of the setting are in the FoxPro manuals!

 

[rgbean]

John,
These settings are also documented in the help file. Assuming you have FP DOS 2.x, look at the "Configuring FoxPro" topic near the beginning of the help topics. Most everything you need to know about CONFIG.FP is there.

If there is something specific you are unsure of, please ask about it.

Rick

 

[FoxEgg]

Dear tcitjh

Here is the problem...

Running Win 2000... I use the batch file (below) for a DOS based program (FoxPro Dos) to point the lpt1: port to the print server (george) and to set the screen to full screen and to load and run the DOS program (which is on another machine mapped as x

The network is CAT5, switch a high speed NetGear, 100Mhz network cards and all machines ping each other at less than 1ms. Windows routines (also mapped; no batch file) are fast. I have both TCP/IP and Netbeui active... (and a fixed IP address (which W2000 seems to like).

The PROBLEM IS:

loading the dos program is slow and printing to george is slow...

The QUESTION IS:

Is there something else I can try to do to speed this up ?

The Batch file is"

#cmd
rem @ echo off
cls
x:/
net use lpt1: \\george\george-p1 /PERSISTENT:YES
mode con: cols=80 lines=25
rem
x:\foxpro ortho.prg -t
net use lpt1: /delete
c:/
exit
[/b]

So I tried a number of solutions.... I made


files=50
buffers=50

in the config.sys file

nope... no help

It still took 32 seconds to print from the FOXPRO

BUT (and I think this is a clue for those smarter than I...) as soon as I exited the FOXPRO... the document printed IMMEDIATELY.... ie if I closed the app within 2 seconds of printing a page then it printed right then ....

IS THIS A CLUE ????

So is it a print spooler problem ? I changed the settings from print spooler to print immediately ... NO change

Then I looked further


Additional clues (maybe)
I added

[IFSMGR]
printbuftime=1

to the system.ini NO Help

I went to the dos command .. went to x: issued a dir>prn: command... went like a rocket

Aha (he thinks)..... its actually the foxpro slowing things down.... tried the command

print x:anyfile.xyz from dos command is fast

but printing from inside foxpro is still slow.....

So I have worked out that it is a FOXPRO setting that seems to be causing the slow printing...

So I though I'd review config.fp for clues to speed up printing... hence the question.

Sorry for long answer, but my girls (office staff) would appreciate an answer so that they caould print faster.

Regards

John Fox

 

[rgbean]

John,
I guess I'd first ask why you are running a .PRG file? This requires loading up the entire development environment and if this isn't (legally) installed on each of your user's systems, bringing all that code down from the network is going to take a while. Does your CONFIG.FP (which I assume is also on the network but would be better if local) at least point to the local systems for the following:
resource=c:\foxtemp\foxuser
help=OFF
TALK=OFF
tmpfiles=c:\foxtemp
sortwork=c:\foxtemp
editwork=c:\foxtemp
progwork=c:\foxtemp

It might start quicker if you created an .EXE and installed the FP runtimes on the local system (assuming you bought the distribution kit).

When running FPD under windows, it a well known fact that IF your code uses the SET PRINTER TO ... statement, that you'll need to include a
SET PRINTER TO && clear for release to Window's spooler
SET PRINTER TO && 2nd is sometimes required (never hurts)

to release the print job. (Either from a REPORT ... TO PRINTER, or a SET DEVICE TO PRINTER.)

Rick

 

[FoxEgg]

Dear Rick,

First thanks for the time in replying, I very much appreciate it.

why you are running a .PRG file? This requires loading up the entire development environment and if this isn't (legally) installed on each of your user's systems, bringing all that code down from the network is going to take a while.

I have purchased a full version FPD (years ago).. I have successfully run this app via the .prg (via a shortcut) on Win 3.11 and Win 98 and both were veryfast.

So why is the samee app (even via a .prg) slow on Win 2000 ???

Does your CONFIG.FP (which I assume is also on the network but would be better if local) at least point to the local systems for the following:
resource=c:\foxtemp\foxuser
help=OFF
TALK=OFF
tmpfiles=c:\foxtemp
sortwork=c:\foxtemp
editwork=c:\foxtemp
progwork=c:\foxtemp

My config.fp contains CATMAN=OFF (and that is it !!!)

It might start quicker if you created an .EXE and installed the FP runtimes on the local system (assuming you bought the distribution kit).

Was already running (under W98) without an .exe (although I agree with your point)

When running FPD under windows, it a well known fact that IF your code uses the SET PRINTER TO ... statement, that you'll need to include a
SET PRINTER TO && clear for release to Window's spooler
SET PRINTER TO && 2nd is sometimes required (never hurts)

to release the print job. (Either from a REPORT ... TO PRINTER, or a SET DEVICE TO PRINTER.)


Once again, the code ran well in Win 98 without the
SET PRINTER TO
command

But I could certainly look at it

I just do not understand why it is that it runs slower under Win2000..

Thanks again Rick......

John Fox

 

[tilltek]

My experience is that a once a printer (any printer) is shared, spooling is ON no matter what you set it to. In other words. all the printer settings like "RAW", "print direct to port", "spool msdos jobs" and so on mean nothing once you share any printer.
My system needs to not only print, but open a cash drawer via the printer so spooling is deadly (cash drawer opens 20 seconds after you walk away), I now use an auto print share box on all machines that need to share a printer.

 

[wtotten]

Foxpro does have a problem "releasing" print jobs. Issuing a second SET PRINT TO usually works. Novell has a feature to ENDCAPTURE (ENDCAP) or ypou can set the TIMEOUT in the Netware client to spool a job afetr x number of seconds. See if your network client or your OS has such a feature.

Bill

 

[FoxEgg]

Thanks Tilltek

I too would prefer a direct connection.... but Office geography does not permit.... furthermore we have had networked printers before.... (OR HAVE WE ???)

STOP brain storm....STOP I think you are right... as I think back, this slowness has only come from the time we have used networked printers...

So I read and tried the

SET PRINTER TO
SET PRINTER TO

suggestion to release the spooler and it STILL didn't work.

{actually I use set prin on and then set prin off commands in the app}

I am convinced the delay is in FPD not in the 2000 DOS environment...

Time to rewrite the app in VFP

John Fox

 

[clogic]

Just bring it into FPW 2.6

And ... SET PRINT ON/OFF is NOT the same as the SET PRINTER TO command ...

ON/OFF turns print on and off ... TO directs to a printer and then closes that 'connection'.

I suggest you follow all the very good advice above ...

SET PRINT ON
{your print stuff}
SET PRINT OFF
SET PRINTER TO
SET PRINTER TO

Best of luck, Steven S
Professional Foxpro developer for DOS/Windows/Unix platforms since 1989.

 

[FoxEgg]

Dear All

You were all right... Problem is solved

I added a

SET PRINTER TO
SET PRINTER TO

To follow all the SET PRIN OFF commands

It worked very well; sorry I was so dumb in not learning what you were telling me....


One residual problem:

I found one section of my program where the printing was still slow.. It turned out that I had accidentally programmed out a

??CHR(27)+"E"

escape code for the printer. (I manually write all printer code in PCL5) Once the escape code was returned, all aspects of the program are working well.

I and my office team are very grateful for your assistance....

I am learning VFP7....(I am still dumb, but still trying)


Thanks to all... fantastic help.

John Fox
jfox@orthopaedicassociates.com.au

 

[Guest_imported]

I have problem with Set Key To in Foxpro DOS 2.6, when exist very much record and execute Set key to Win98 crashed