On Metaframe I'll put the temp folder on a drive other than the boot partition because the temp folder is in "my documents and settings ..." for each user. This can quickly fill up the boot partition and cause Windows 2000 Server to be very displeased. Even with the temp folder on another drive, and having changed the environment variables for TEMP and TMP n Windows, referenced memory errors are common. Remove the SET SCRATCH and it works fine (in conjunction with the fixed size page file described below).
Have you tried
SET VAR vTemp = (ENVVAL('TEMP')) SET SCRATCH &vTemp
This will use the local temp directory, usually something like C:\WINDOWS|TEMP
Emmitt Dove <[EMAIL PROTECTED]> wrote:
>Alastair, > >Regarding the crashes, here are a couple of things I've found through >experimentation: > >1. Most important of all, make sure your user has full rights to wherever >the .$$$ files are to be written. If the user has trouble writing the >temporary files R:Base will be very unhappy. Also, I have not had good >luck trying to use the SET SCRATCH feature in a multiuser environment, >particularly on Citrix, with TEMP and TMP pointing to a common folder on >the server, even when EVERYONE had full rights to the folder. > >2. On Windows 2000 and XP, set the virtual memory to 1000 mb for both >minimum and maximum. A typical user with 128 megs of RAM and a virtual >memory setting with 192 mb minimum will encounter a referenced memory error >on the 3rd or 4th mouseclick in our application (first click clears a >splash, 2nd click selects a sub menu, 3rd click selects a program to run, >4th click runs the program - boom.) Setting the min and max both to 1 gig >eliminated the referenced memory errors. > > >>All I have been trying to do is find out what has been causing the numerous >>unexplained crashes I get with R:Base. The biggest improvement in months, >>maybe a year, has been to change the extension for a file that I run from >>.DAT to .$$$. >> >>Most crashes now occur when I first run R:Base so that once it has started >>it's much more stable. However the command file that is run on start-up can >>also be "quit to" numerous times in a session without crashing. >> >>Writing that has just given me an idea - maybe I should "quit to" the file >>at the start. More testing coming up... >> >>Regards, >>Alastair. > >Emmitt Dove >Manager, DairyPak Business Systems >Blue Ridge Paper Products, Inc. >40 Lindeman Drive >Trumbull, CT 06611 >(203) 673-2231 >[EMAIL PROTECTED] >[EMAIL PROTECTED] > >
-- Albert Berry Full Time Consultant to PSD Solutions 350 West Hubbard, Suite 210 Chicago, IL 60610 312-828-9253 Ext. 32
__________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397
Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
Emmitt Dove Manager, DairyPak Business Systems Blue Ridge Paper Products, Inc. 40 Lindeman Drive Trumbull, CT 06611 (203) 673-2231 [EMAIL PROTECTED] [EMAIL PROTECTED]
