Bruce, Thanks for the explanation. I will change my settings to the C:\TEMP and see what happens. I may in the near future do as Javier suggested and show my DAT file and get some help there. The only thing that might prevent that is how badly I want my ego to be bruised. I have not even set up my users in an actual application, just a form within RBASE.
Ah! I may as well give you folks a good laugh and post it right here now. CONNECT Labor SET TIMEOUT 60 CLS EDIT USING KayParkMainMenu DISCONNECT EXIT RETURN James Belisle -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruce Chitiea Sent: Wednesday, April 06, 2011 2:15 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: I/O problems James: > I am very unfamiliar with how the temp files affect things. > Since the settings I now have, C:\Doucuments and settings\Jim\Local > Settings\Temp are on C: drive, how does going to C:\TEMP make a > difference? Only a partial explanation but it goes something like this: 1. Every program running on a Windows operating system from Win NT forward requires a 'login' to the operating system; 2. Every USERNAME login operates under a very specific list of access permissions which define what the logged-in user can do on the system with the programs running under his/her name; 3. Windows is designed to allow multiple human operators to access a machine under individual login names; 4. Windows provides segmented, 'secured' storage for each user within the C:\Documents and settings... structure. So in this example, user 'Jim' can't see files belonging to user 'Bruce': -- C:\Documents and settings\JIM\... -- C:\Documents and settings\BRUCE\... So, 'temp' and 'scratch' files stored in the 'temp' folders within these structures are created and maintained ONLY for programs started under the logins 'Jim' or 'Bruce'. And here's the rub: Windows creates its own 'users' for programs under-the-covers, so to speak. 'Administrator' is one such 'user'. You saw many instances of 'svchost' in the process list. Many of these 'users' provide services to programs started under logins 'Jim' and 'Bruce'. These processes many need a 'system-wide' location for temp files, completely independent of (and protected from) whatever's going on with individually logged-in programs. Since R:Base uses system-wide resources, outside of those dedicated to any single-user's login, you really want to point your R:Base temp and scratch files to either: C:\Temp or C:\Windows\Temp >From long habit, I stay out of the C:\Windows path as much as possible so my money is on C:\Temp. Well, not really 'C:'. And that's where we get personal. DEEP WEEDS Temporary file creation and deletion causes fragmentation of hard drives. Spreading temp files across a fragmented drive slows the system down. You really want your operating system and program setups to change as little as possible while simplifying backup and maintenance. So I partition the hard drive like this: C:\ Windows and application programs only D:\ 1-2 GB reserved for Temp files and Virtual Memory (topic for another day) E:\ Data files This satisfies all my goals: C:\ Changes as little as possible D:\ Fragmentation is just not a big deal E:\ I can backup the path E:\*.* and get everything. Gotta go. bruce chitiea safesectors inc.
