Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
FoxPro DOS 2.6 question...
Message
From
17/02/1999 19:00:21
 
 
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00188192
Message ID:
00188701
Views:
25
>>>>>>>I keep getting the error "Insufficient disk space to write to file"...
>>>>>>>
>>>>>>>The file is 60 megs but I've got 5.5 gig free on the drive...
>>>>>>>
>>>>>>>Any ideas what could cause this?
>>>>>>>
>>>>>>
>>>>>>Yep - it has to do with how the DISKSPACE() function is implemented in FPDOS and FPW; ythe number returned is a 32 bit integer; in the case of FPDOS, it wraps around; FPW actually reports negative values above 2GB.
>>>>>>
>>>>>>With Novell volumes, I've used the ability for the operating system to limit the available disk space for the user to work around the problem in the past; I'm not certain how to deal with this in a pure DOS environment, or with local drives running under Win9x.
>>>>>
>>>>>But this is a program that's been running fine for years. I'm only taking out the user interface so that it runs unattended. I haven't changed any of the old code.
>>>>>
>>>>
>>>>That's wonderful, but have you ever had the luxury of having this amount of disk free space before? Try allocating some huge dummy files to pull your free space on the drive down to a number that FPDOS can work with; it may fix your problem.
>>>
>>>Well... that *sounded* promising, but...
>>>
>>>I cut disk space down to 1.7 and still got the error. My next test is to run it on a machine with a true 2 gig hard drive...
>>
>>One other thought; where are your temporary files being written? It's possible, if there are work files involved, that you're running out of temp file space - try setting TMPFILES to a directory on the big drive in CONFIG.FP, or if you specify things individually, SORTWORK at least.
>>
>>>
>>>I'll post the results
>>>
>>>Thanks

Well... I found the problem... the program kept dying on the line SCATTER MEMVAR MEMO... turns out the memo field was FILLED with about 8 meg of gibberish.

I re-copied the "live" file back into my development area and all worked fine...

Thanks to all for your help

Larry
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform