Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Temp Files on Desktop - FPD2.6
Message
De
06/11/1999 16:55:42
 
 
À
06/11/1999 16:38:10
Information générale
Forum:
Visual FoxPro
Catégorie:
FoxPro 2.x
Divers
Thread ID:
00284262
Message ID:
00288113
Vues:
18
>I was finally out at the client site today. I looked more deeply into how the FPDOS app is set to run.
>
>It turns out that each user logging into the main server gets their own H: drive mapped. That drive contains a folder, \BATCH, containing a startup batch file for starting the FPDOS app. This batch file is directly called by a desktop shortcut. The Start In folder is H:\BATCH.
>
>Batch file contents:
>
>SET S_User = UserName    && environment variable required by app
>O:
>CD O:\MOUNTAIN
>G:\FOXPRO25\FOXPROX SYSSTART -CO:\MOUNTAIN\LINUX\CONFIG.FP
>
>CONFIG.FP contains:
>RESOURCE=C:\
Should be RESOURCE=full path of file, so C:\FOXUSER.DBF would be right if you wanted to use the default FOXUSER. You'll get bit if the same CONFIG.FP gets used by a different (later) Fox version.

>TMPFILES=C:\
>
>
>Everything works perfectly fine, except the tempfiles are showing up on the desktop.

I think that back in FPDOS, it required just a drive designator for TMPFILES; TMPFILES inherited the current relative pathing for the drive in your FPDOS startup context. You could specify actual paths for things like SORTWORK, but it's been a long time since I looked. I'm immensely allergic to using the root, especially of a boot drive, for temporary files, so I'd create a C:\TEMP on each targetr system, add a CD C:\TEMP to the batch (if you're on another drive, this will change the default path for the drive without actually switching to the drive), and I'd use SORTWORK, PROGWORK, etc. directives to specify the C:\TEMP directory.

Better yet, make a workstation-specific CONFIG, so that you don't accidentally smash up the root of the boot drive, and fix up the batch file.
>
>The server is Linux/Samba, the clients are mainly W95 with a few NT4W boxes in the mix. Both client types exhibit this problem.
>
>I agree that the FOXPROCFG environment variable could also be used. However, it was my understanding that using the -C command line switch is more "direct" and would override a FOXPROCFG setting. If I can't think of any other things to try I'll try FOXPROCFG and let you know if it works.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform