Edbengineerror insufficient disk space

edbengineerror insufficient disk space

Known BDE Bugs. Insufficient Disk Space. The BDE has a bug where, if that space left to the next 4GB barrier is less than the BDE needs for the current. The error 'Insufficient Disk Space' is misleading - it actually means that there has been a general failure to write to the database. Problem Description. The computer where the Common Files are located has insufficient space on the hard drive; or.

Opinion: Edbengineerror insufficient disk space

Error-23 pioneer p5000mp
ORACLE DEFERRED TRANSACTION ERRORS
Networkerror 403 forbidden
Edbengineerror insufficient disk space
Sabre squadron error message
# Lines

.

Ron Schusterwrote on 31-Aug-2012:

I believe this is a well-known error in the BDE. This error occurs when the available space
on a disk drive is at a 4GB boundary. The only workaround offered was to use additional space on
the disk until this boundary is passed. Did Borland/InPrise/CodeGear/Embarcadero ever come out with an official fix for this problem?

13

   .

Leslie Milburnreplied on 31-Aug-2012:

27

     .

John MacDonaldreplied on 27-Jun-2014:

Hello Leslie:
    My guess is that it does not matter if you are using dbase of paradox files right?
    pnews ?
    Sorry to ask such a specific question. Where do I find out more information regarding the patch / fix?
    John
40

       .

Leslie Milburnreplied on 27-Jun-2014:

69

         .

Frank M. Cookreplied on 30-Jun-2014:

(snip)

the older versions installed in Common Files\Borland while the newer one
        installs in Common Files\Borland Shared. you can install the new one
        without removing the old one but you'll want to use BDEAdmin to tell it aiwa bmz-k1 roll error
        use the cfg file in the BDE directory under Borland Shared.
        --
18

INTRODUCTION

This article describes a new setting in the following versions of Windows:

  • Windows 8.1 Enterprise and Windows 8.1 Pro

  • Windows 8 Enterprise and Windows 8 Pro

  • Windows 7 Ultimate and Windows 7 Enterprise

  • Windows Vista Ultimate, Windows Vista Enterprise

This setting helps protect confidential data in a pagefile when BitLocker Drive Encryption (BDE) is enabled.

More Information

The Windows 8.1, Windows 8, Windows 7, and Windows Vista memory-management system includes a feature that automatically manages the system pagefile. The memory-management system typically puts the pagefile on the same volume as the operating system (OS). However, if this volume does not have sufficient space, the pagefile may be relocated to another local volume on which more disk space is available. This relocation may cause data-confidentiality issues when BDE is used to protect the OS volume. Specifically, information may be disclosed if the pagefile's new location is on a volume that is not encrypted by BDE.

To reduce this threat, BDE automatically creates the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\PagefileOnOsVolumeThis subkey lets you direct the memory-management system to put the pagefile only on the BDE-protected OS volume. Specifically, if you set this subkey to a value of 1, the OS volume is the only volume that the Session Management Sub System (SMSS) will consider as a location for the pagefile. If there is insufficient space on the OS edbengineerror insufficient disk space, SMSS will create a smaller pagefile on this volume.

When BDE is enabled, the PagefileOnOSVolume setting is automatically created, and it is set to a value of 1. However, BDE will not create the PagefileOnOsVolume registry entry if the following registry subkey is not set to the default value of ?:\pagefile.sys:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\PagingFilesNote When BDE is disabled, edbengineerror insufficient disk space, the PagefileOnOSVolume setting remains. Disabling BDE does not delete or disable the PagefileOnOSVolume setting.

This functionality gives administrators control over how BDE and the memory-management system manage the pagefile. We recommend that you enable Encrypting File System (EFS) encryption of the pagefile if the following conditions are true:

  • The BDE default PagefileOnOSVolume registry setting is not used.

  • The pagefile is not located on a BDE-protected volume.

Borland Database Engine (BDE) Notes

  • BDE and Windows 7, 32 and 64 bits

http://alexandrecmachado.blogspot.com/2012/01/bde-and-windows-7-32-and-64-bits.html

  • Configuring BDE for Windows 7

http://www.willneumann.net/2008/09/configuring-bde-for-windows7/

  • Steps to Reinstall BDE on a Workstation

http://www.tsrconsult.com/wp-content/uploads/2011/09/TSR-Consulting-Timeslips-Reinstalling-BDE.pdf

http://www.shiprush.com/product_documentation/private-omnirush/bde_discussion.htm

  • What is optimum BDE setting for SHAREDMEMLOCATION?

Shared Memory Location
Shared Memory Conflicts

  • The machine acting as the data file server must have LOCAL SHARE set to TRUE in BDEADMIN.EXE. The location of this setting is Tab->Configuration->System->INIT

Known BDE Bugs

The BDE has a bug where, if that edbengineerror insufficient disk space left to the next 4GB barrier is less than the BDE needs for the current operation then you will get the 'insufficient disk space' error.

Insufficient disk space
File or directory does not exist
file: X:\datapath\_QSQL000.dbf
Table does not exist

Current resolution: Add some files to the drive or clean out a bunch of old ones to get away from the current 4GB barrier. There is, reportedly, a software patch available for the BDE but we have not yet tested it.

Delphi BDE Notes

http://borland.public.bde.narkive.com/8DqYdBWc/rebuild-and-old-mdx-file

http://www.swissdelphicenter.ch/en/showcode.php?id=1350


Board index » delphi » BDE error "Insufficient disk space"


Hi.
BDE version is 5.01  (BDE Administrator, Help
AuthorMessage

David Scav
#1 / edbengineerror insufficient disk space src="http://www.databaseteam.org/styles/serenity/imageset/icon_topic_latest.gif" width="9" height="9"> Paradox 8 - Restructure Gives Insufficient Disk Space


I have a Windows NT v4 Terminal Server (SP5) with Paradox 8 (SP1)
installed. The file server is Windows 2000.

When I attempt to restructure a table on the file server using Paradox
8 from the Terminal Server, I get the error:

Insufficient Disk Space

The table I want to restructure is 110MB (211MB including indexes).
The stuff I was able to turn up on Deja says that you need plenty runtime error 132
space on:
   1) Drive where table is
   2) PRIV directory
   3) Windows TEMP directory

There is 60 Gigs of free space on the drive that contains the file to
be restructured. On my Terminal Server, the boot drive (which contains
PRIV and the Windows TEMP directory), edbengineerror insufficient disk space, has 1.9 Gig free space.

Any ideas would be greatly appreciated.



Sun, 30 Nov 2003 22:14:37 GMT

Liz
#2 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space

David,

I suppose it's possible that the BLOCK SIZE need to be bigger
(110MB is nearing the limit of the smallest block size setting).

To change the block size on an existing table:

1. Exit all BDE apps
2. Open the BDE and change the block size setting (configuration
tab)
3. Create a new table with the same structure as the old
4. Add data from old table to new table
5. Rename as needed
6. Reset the block size setting in the BDE (if desired)

PLEASE BACK UP DATA FIRST.

I'm not sure this is the problem, but it's possible.

Liz

Quote:


> I have a Windows NT v4 Terminal Server (SP5) with Paradox 8 (SP1)
> installed. The file server is Windows 2000.

> When I attempt to restructure a table on the file server using Paradox
> 8 from the Terminal Server, I get the error:

> Insufficient Disk Space

> The table I want to restructure is 110MB (211MB including indexes), edbengineerror insufficient disk space.
> The stuff I was able to turn up on Deja says that you need plenty of
> space on:
>    1) Drive where table is
>    2) PRIV directory
>    3) Windows TEMP directory

> There is 60 Gigs of free space on the drive that contains the file to
> be restructured. On my Terminal Server, the boot drive (which contains
> PRIV and the Windows TEMP directory), has 1.9 Gig free space.

> Any ideas would be greatly appreciated.



Sun, 30 Nov 2003 23:34:45 GMT

David Scav
#3 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space

Quote:


>I suppose it's possible that the BLOCK SIZE need to be bigger
>(110MB is nearing the limit of the smallest block size setting).
>I'm not sure this is the problem, but it's possible.

The blocksize for this file is already set to 16K.


Mon, edbengineerror insufficient disk space, 01 Dec 2003 02:17:13 GMT

Liz
#4 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space
David,

Is the BLOCK SIZE in the BDE set to that?  In theory, it
shouldn't matter, but perhaps when doing a restructure it looks
at the setting in the BDE.  Anywho, check and test - should be
quick and easy.

The only other thing I can think of is if one of the server
directories has a size limit (as server dirs so often do) and so
while the _disk_ has plenty of room, the dir does not.

Sorry, no other ideas edbengineerror insufficient disk space to mind.

Liz

Quote:


> >I suppose it's possible that the BLOCK SIZE need to be bigger
> >(110MB is nearing the limit of the smallest block size setting).

> >I'm not sure this is the problem, 1309 error code mac it's possible.

> The blocksize for this file is already set to 16K.



Mon, 01 Dec 2003 03:06:54 GMT

David Scav
#5 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space

Quote:


>Is the Dcom got error 2147942405 SIZE in the BDE set to that?  In theory, it
>shouldn't matter, but perhaps when doing a restructure it looks
>at the setting in the BDE.  Anywho, check and test - should be
>quick and easy.

Blocksize in the BDE is set to 2048. Tools / Table Repair show the
table blocksize as 16K (which is correct, since this table grows over
time and at one point had lots of records in it).

Quote:

>The only other thing I can think of edbengineerror insufficient disk space if one of the server
>directories has a size limit (as server dirs so often do) and so
>while edbengineerror insufficient disk space _disk_ has plenty of room, the dir does not.

No directory size limits on our servers.

One other bit of info is that I can successfully restructure this
table from a Win98 client with no "insufficient disk space" errors
Free space on the Win98 boot drive [TEMP and PRIV directories] is less
than on the NT Terminal Server  -973MB.

Very strange indeed.



Sat, 06 Dec 2003 05:25:48 GMT

Liz
#6 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space
David,

Did you try setting the BLOCK SIZE to 16K and then doing your
restructure?  If not, that would be the first thing I would try -
just to eliminate it as a possibility (or identify it as the
problem).

Liz

Quote:


> >Is the BLOCK SIZE in the BDE set to that?  In theory, it
> >shouldn't matter, but perhaps when doing a restructure it looks
> >at the setting in the BDE.  Anywho, check and test - should be
> >quick and easy.

> Blocksize in the BDE is set to 2048. Tools / Table Repair show the
> table blocksize as 16K (which is correct, since this table grows over
> time and at one point had lots of records in it).

> >The only other thing I can think of is if one of the server
> >directories has a size limit (as server dirs so often do) and so
> >while the _disk_ has plenty of room, the dir does not., edbengineerror insufficient disk space.

> No directory size limits on our servers.

> One other bit of info is that I can successfully restructure this
> table from a Win98 client with no "insufficient disk space" errors
> Free space on the Win98 boot drive [TEMP and PRIV directories] is less
> than on the NT Terminal Server  -973MB.

> Very strange indeed.



Sat, 06 Dec 2003 07:36:45 GMT

David Scav
#7 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space

Quote:


>Did you try setting the BLOCK SIZE to 16K and then doing your
>restructure?  If not, that would be the first edbengineerror insufficient disk space I would try -
>just to eliminate it as a possibility (or identify it as the
>problem).

Do you mean the BDE blocksize on the machine ?

Because the table blocksize is already 16K.



Sat, 20 Dec 2003 22:13:49 GMT

Liz
#8 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space
David,

Yes, the BDE block size setting.  This setting is what's used for
new tables, and I'd want to rule out the possibility that the
restructure is using that setting rather than the source table's
500 internal server error httpd.conf size.

Liz

Quote:


> >Did you try setting the BLOCK SIZE to 16K and then doing your
> >restructure?  If not, that would be the first thing I would try -
hitachi raw read error >just to eliminate it as a possibility (or identify it as the
> >problem). edbengineerror insufficient disk space Do you mean the BDE blocksize on the machine ?

> Because the table blocksize is already 16K.



Sat, 20 Dec 2003 23:05:33 GMT

Sedge Simon
#9 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space
We've seen this problem with restructures and queries. What solved it
was to empty the trashcan. The BDE and Windows seem to disagree about
how to manage disk space as the temporary files needed for these
operations are deleted, and a "full" trashcan cause this semi-bogus
error message.

--
Sedge

Posted via dBforums, http://dbforums.com



Tue, 30 Dec 2003 00:04:45 GMT

Clayfi
#10 / 12

 Paradox 8 - Restructure Edbengineerror insufficient disk space Insufficient Disk Space
Been having this annoying problem too.

Fixed it by placing the pdxtable on a smaller harddrive.

Seems that the BDE has problems with large harddrives, this was under
w2k adv.server, so that may be part of the culprit.



Sat, 03 Jan 2004 07:48:04 GMT

Clayfi
#11 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space
Hej Liz & David,

Well, I've set the blocksize to 32k, and like I stated, the only
solution was to use a physically smaller harddisk. Seems like a
BDE/Win2k problem. Hope this can help you guys!!



Thu, 08 Jan 2004 21:07:21 GMT

Clayfi
#12 / 12

 Paradox 8 - Restructure Gives Insufficient Disk Space

Hi again,

Just thought I'd follow up on these insufficient disk space errors, edbengineerror insufficient disk space.

Today the same problem occured on the 'smaller' harddisk. This was
while edbengineerror insufficient disk space BDE intensive application was running on the w2k server.

Again the solution was similar (with the other application still
running).
I changed to using the other 'larger' disk. This fixed the problem.
(Both disks have several gigabytes available).

So it in't the actual size of the disk, edbengineerror insufficient disk space, maybe something with the
internal buffering? Have no idea, have a cure, edbengineerror insufficient disk space, but it only works
temporarily! Hope someone can shed more light on this annoyance.



Sat, 17 Jan 2004 23:23:08 GMT 

Repair your computer now.

  • Step 1: Download and install ASR Pro
  • Step 2: Open the program and click "Scan PC"
  • Step 3: Click "Repair now" to start the repair process
  • Speed up your computer today with this easy and free download.

    Sometimes your computer may display an error message stating bde 2501 vista. This problem can be caused by a number of reasons. Error 2501 means “there is not enough disk space to complete this operation.” Errors can usually be fixed by changing some of the defaults 3ds max 2013 x64 a license error the BDE, edbengineerror insufficient disk space, which sometimes include increasing sharedmemsize, edbengineerror insufficient disk space, minbufsize, maxbufsize, or changing the location of shared memory as needed.

    I have a small Datasnap web hosting server written in Delphi 2007, most of which access the BDE. This works tricky on Windows 2000 and XP, edbengineerror insufficient disk space then from time to time (actually relatively regularly) on Vista I get your current error message:

    Fixed error when trying to initialize Borland Database Engine (error 250 $ 1)

    Closing anything that is using the BDE solves this problem (although sometimes you need to help “kill the process” on the data binding server to terminate it).

    This is getting more and more tedious as more and more of our customers use Vista as their “server”. Anyone have any suggestions?

    When using software that uses the Borland Database Engine (BDE), you may receiveone of the following error messages:

    An error occurred while creating the Borland kernel initialization (error $ 2501)

    An error occurred while initializing derectx vreation error Borland database engine (error $ 210D)

    An error may occur while using the application. The error is most likely caused by insufficient shared memory available in the market for use by the database engine. Therefore, increasing the shared memory for the BDE will most likely fix the error.

    1. Open the control panel.
    2. Find and open edbengineerror insufficient disk space BDE Administrator.
    3. Expand the configuration.
    4. Extend the system.
    5. Typically open an INIT definition.
    6. Modify and enter each of our SHAREDMEMLOCATION and SHAREDMEMSIZE values ​​according to the amount of physical knowledge (RAM) available to the computer, based on the table below. Readabilitydatatable = “1”>
      Physical
      SHARED MEMORY SIZE SHARED MEMORY SIZE
      2 Go 0x2BDE 2048 4 Go 0x5BDE < / td> 4096 8 Go 0x7BDE 8192

    org% 2f2000% 2fsvg% 27% 20width% 3d% 27481% 27% 20height% 3d% 27423% 27% 20viewbox% 3d% 270% 200% 20481% 20423% 27% 3e% 3crect% 20width% 3d% 27481% 27% 20height% 3d% 27423% 27% 20fill-opacity% 3d% 220% 22% 2f% 3e% 3c% 2fsvg% 3e “>

    gb 0x5bde 4096 8 LK is a Tech Journey Technical Writer with Network Related System Learning Admin … He has over 15 years of experience in the digital and technical world. Connect LK through Tech Journey on Facebook, Twitter, or edbengineerror insufficient disk space width="40" height="30">error mysql_query line height="30">

    Edbengineerror insufficient disk space - seems

    Contact US

    INTELLIGENT WORK FORUMS
    FOR COMPUTER PROFESSIONALS

    Thanks. We have received your request and will respond promptly.

    Log In

    Come Join Us!

    Are you a
    Computer / IT professional?
    Join Tek-Tips Forums!

    • Talk With Other Members
    • Be Notified Of Responses
      To Your Posts
    • Keyword Search
    • One-Click Access To Your
      Favorite Forums
    • Automated Signatures
      On Your Posts
    • Best Of All, It's Free!

    Join Us!

    *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

    Posting Guidelines

    Promoting, selling, recruiting, coursework and thesis posting is forbidden.

    Students Click Here

    Tek-Tips Posting Policies

    Contact US

    Insufficient disk space., BDE Error Cat:Code: [37:3], BDE: 500 ...

    Insufficient disk space., BDE Error Cat:Code: [37:3], BDE: 500 ...

    koom(TechnicalUser)

    (OP)

    Hi,

    One of our sales reps got the following error listed 3 times  when he tried to sync once:


    Insufficient disk space.
     
    Context: appendFrom: c:\goldmine\Sync\WizProf\42771287\USER\In\Working\MailBox
    C:\GoldMine\GMBase\MailBox
     
    1: File: C:\DOCUME~1\user\LOCALS~1\Temp\INMEM000.REM
     
    BDE Error Cat:Code: [37:3]
    BDE: 500 [9/6/1998]  GoldMine: 6.60.40707
     
    User: USER  
    Window:
    Template:
    Details:
    FILENAME: C:\DOCUME~1\user\LOCALS~1\Temp\INMEM000.REM


    I know the INMEM000.REM file is a temporary file that is created and is supose to be deleted when its eithe done syncronizing or when you close goldmine. (the file is created by Borland Database Engine (BDE)).

    the error happens on his laptop. The size of our database directory on the server is only 21MB.
    The log file says everything went fine, but the user got the errors (on his side..).

    I wonder if any one can give me some direction in how to solve this?

    Thank you for Any help you can provide!!
    --Koomo

    Red Flag Submitted

    Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
    The Tek-Tips staff will check this out and take appropriate action.

    INTRODUCTION

    This article describes a new setting in the following versions of Windows:

    • Windows 8.1 Enterprise and Windows 8.1 Pro

    • Windows 8 Enterprise and Windows 8 Pro

    • Windows 7 Ultimate and Windows 7 Enterprise

    • Windows Vista Ultimate, Windows Vista Enterprise

    This setting helps protect confidential data in a pagefile when BitLocker Drive Encryption (BDE) is enabled.

    More Information

    The Windows 8.1, Windows 8, Windows 7, and Windows Vista memory-management system includes a feature that automatically manages the system pagefile. The memory-management system typically puts the pagefile on the same volume as the operating system (OS). However, if this volume does not have sufficient space, the pagefile may be relocated to another local volume on which more disk space is available. This relocation may cause data-confidentiality issues when BDE is used to protect the OS volume. Specifically, information may be disclosed if the pagefile's new location is on a volume that is not encrypted by BDE.

    To reduce this threat, BDE automatically creates the following registry subkey:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\PagefileOnOsVolumeThis subkey lets you direct the memory-management system to put the pagefile only on the BDE-protected OS volume. Specifically, if you set this subkey to a value of 1, the OS volume is the only volume that the Session Management Sub System (SMSS) will consider as a location for the pagefile. If there is insufficient space on the OS volume, SMSS will create a smaller pagefile on this volume.

    When BDE is enabled, the PagefileOnOSVolume setting is automatically created, and it is set to a value of 1. However, BDE will not create the PagefileOnOsVolume registry entry if the following registry subkey is not set to the default value of ?:\pagefile.sys:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\PagingFilesNote When BDE is disabled, the PagefileOnOSVolume setting remains. Disabling BDE does not delete or disable the PagefileOnOSVolume setting.

    This functionality gives administrators control over how BDE and the memory-management system manage the pagefile. We recommend that you enable Encrypting File System (EFS) encryption of the pagefile if the following conditions are true:

    • The BDE default PagefileOnOSVolume registry setting is not used.

    • The pagefile is not located on a BDE-protected volume.

    Borland Database Engine (BDE) Notes

    • BDE and Windows 7, 32 and 64 bits

    http://alexandrecmachado.blogspot.com/2012/01/bde-and-windows-7-32-and-64-bits.html

    • Configuring BDE for Windows 7

    http://www.willneumann.net/2008/09/configuring-bde-for-windows7/

    • Steps to Reinstall BDE on a Workstation

    http://www.tsrconsult.com/wp-content/uploads/2011/09/TSR-Consulting-Timeslips-Reinstalling-BDE.pdf

    http://www.shiprush.com/product_documentation/private-omnirush/bde_discussion.htm

    • What is optimum BDE setting for SHAREDMEMLOCATION?

    Shared Memory Location
    Shared Memory Conflicts

    • The machine acting as the data file server must have LOCAL SHARE set to TRUE in BDEADMIN.EXE. The location of this setting is Tab->Configuration->System->INIT

    Known BDE Bugs

    The BDE has a bug where, if that space left to the next 4GB barrier is less than the BDE needs for the current operation then you will get the 'insufficient disk space' error.

    Insufficient disk space
    File or directory does not exist
    file: X:\datapath\_QSQL000.dbf
    Table does not exist

    Current resolution: Add some files to the drive or clean out a bunch of old ones to get away from the current 4GB barrier. There is, reportedly, a software patch available for the BDE but we have not yet tested it.

    Delphi BDE Notes

    http://borland.public.bde.narkive.com/8DqYdBWc/rebuild-and-old-mdx-file

    http://www.swissdelphicenter.ch/en/showcode.php?id=1350


    AuthorMessage

    David Scav
    #1 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    I have a Windows NT v4 Terminal Server (SP5) with Paradox 8 (SP1)
    installed. The file server is Windows 2000.

    When I attempt to restructure a table on the file server using Paradox
    8 from the Terminal Server, I get the error:

    Insufficient Disk Space

    The table I want to restructure is 110MB (211MB including indexes).
    The stuff I was able to turn up on Deja says that you need plenty of
    space on:
       1) Drive where table is
       2) PRIV directory
       3) Windows TEMP directory

    There is 60 Gigs of free space on the drive that contains the file to
    be restructured. On my Terminal Server, the boot drive (which contains
    PRIV and the Windows TEMP directory), has 1.9 Gig free space.

    Any ideas would be greatly appreciated.



    Sun, 30 Nov 2003 22:14:37 GMT

    Liz
    #2 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    David,

    I suppose it's possible that the BLOCK SIZE need to be bigger
    (110MB is nearing the limit of the smallest block size setting).

    To change the block size on an existing table:

    1. Exit all BDE apps
    2. Open the BDE and change the block size setting (configuration
    tab)
    3. Create a new table with the same structure as the old
    4. Add data from old table to new table
    5. Rename as needed
    6. Reset the block size setting in the BDE (if desired)

    PLEASE BACK UP DATA FIRST.

    I'm not sure this is the problem, but it's possible.

    Liz

    Quote:


    > I have a Windows NT v4 Terminal Server (SP5) with Paradox 8 (SP1)
    > installed. The file server is Windows 2000.

    > When I attempt to restructure a table on the file server using Paradox
    > 8 from the Terminal Server, I get the error:

    > Insufficient Disk Space

    > The table I want to restructure is 110MB (211MB including indexes).
    > The stuff I was able to turn up on Deja says that you need plenty of
    > space on:
    >    1) Drive where table is
    >    2) PRIV directory
    >    3) Windows TEMP directory

    > There is 60 Gigs of free space on the drive that contains the file to
    > be restructured. On my Terminal Server, the boot drive (which contains
    > PRIV and the Windows TEMP directory), has 1.9 Gig free space.

    > Any ideas would be greatly appreciated.



    Sun, 30 Nov 2003 23:34:45 GMT

    David Scav
    #3 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    Quote:


    >I suppose it's possible that the BLOCK SIZE need to be bigger
    >(110MB is nearing the limit of the smallest block size setting).
    >I'm not sure this is the problem, but it's possible.

    The blocksize for this file is already set to 16K.


    Mon, 01 Dec 2003 02:17:13 GMT

    Liz
    #4 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    David,

    Is the BLOCK SIZE in the BDE set to that?  In theory, it
    shouldn't matter, but perhaps when doing a restructure it looks
    at the setting in the BDE....  Anywho, check and test - should be
    quick and easy.

    The only other thing I can think of is if one of the server
    directories has a size limit (as server dirs so often do) and so
    while the _disk_ has plenty of room, the dir does not...

    Sorry, no other ideas come to mind.

    Liz

    Quote:


    > >I suppose it's possible that the BLOCK SIZE need to be bigger
    > >(110MB is nearing the limit of the smallest block size setting).

    > >I'm not sure this is the problem, but it's possible.

    > The blocksize for this file is already set to 16K.



    Mon, 01 Dec 2003 03:06:54 GMT

    David Scav
    #5 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    Quote:


    >Is the BLOCK SIZE in the BDE set to that?  In theory, it
    >shouldn't matter, but perhaps when doing a restructure it looks
    >at the setting in the BDE....  Anywho, check and test - should be
    >quick and easy.

    Blocksize in the BDE is set to 2048. Tools / Table Repair show the
    table blocksize as 16K (which is correct, since this table grows over
    time and at one point had lots of records in it).

    Quote:

    >The only other thing I can think of is if one of the server
    >directories has a size limit (as server dirs so often do) and so
    >while the _disk_ has plenty of room, the dir does not...

    No directory size limits on our servers.

    One other bit of info is that I can successfully restructure this
    table from a Win98 client with no "insufficient disk space" errors
    Free space on the Win98 boot drive [TEMP and PRIV directories] is less
    than on the NT Terminal Server  -973MB.

    Very strange indeed.....



    Sat, 06 Dec 2003 05:25:48 GMT

    Liz
    #6 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    David,

    Did you try setting the BLOCK SIZE to 16K and then doing your
    restructure?  If not, that would be the first thing I would try -
    just to eliminate it as a possibility (or identify it as the
    problem).

    Liz

    Quote:


    > >Is the BLOCK SIZE in the BDE set to that?  In theory, it
    > >shouldn't matter, but perhaps when doing a restructure it looks
    > >at the setting in the BDE....  Anywho, check and test - should be
    > >quick and easy.

    > Blocksize in the BDE is set to 2048. Tools / Table Repair show the
    > table blocksize as 16K (which is correct, since this table grows over
    > time and at one point had lots of records in it).

    > >The only other thing I can think of is if one of the server
    > >directories has a size limit (as server dirs so often do) and so
    > >while the _disk_ has plenty of room, the dir does not...

    > No directory size limits on our servers.

    > One other bit of info is that I can successfully restructure this
    > table from a Win98 client with no "insufficient disk space" errors
    > Free space on the Win98 boot drive [TEMP and PRIV directories] is less
    > than on the NT Terminal Server  -973MB.

    > Very strange indeed.....



    Sat, 06 Dec 2003 07:36:45 GMT

    David Scav
    #7 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    Quote:


    >Did you try setting the BLOCK SIZE to 16K and then doing your
    >restructure?  If not, that would be the first thing I would try -
    >just to eliminate it as a possibility (or identify it as the
    >problem).

    Do you mean the BDE blocksize on the machine ?

    Because the table blocksize is already 16K.



    Sat, 20 Dec 2003 22:13:49 GMT

    Liz
    #8 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    David,

    Yes, the BDE block size setting.  This setting is what's used for
    new tables, and I'd want to rule out the possibility that the
    restructure is using that setting rather than the source table's
    block size.

    Liz

    Quote:


    > >Did you try setting the BLOCK SIZE to 16K and then doing your
    > >restructure?  If not, that would be the first thing I would try -
    > >just to eliminate it as a possibility (or identify it as the
    > >problem).

    > Do you mean the BDE blocksize on the machine ?

    > Because the table blocksize is already 16K.



    Sat, 20 Dec 2003 23:05:33 GMT

    Sedge Simon
    #9 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    We've seen this problem with restructures and queries. What solved it
    was to empty the trashcan. The BDE and Windows seem to disagree about
    how to manage disk space as the temporary files needed for these
    operations are deleted, and a "full" trashcan cause this semi-bogus
    error message.

    --
    Sedge

    Posted via dBforums, http://dbforums.com



    Tue, 30 Dec 2003 00:04:45 GMT

    Clayfi
    #10 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    Been having this annoying problem too.

    Fixed it by placing the pdxtable on a smaller harddrive.

    Seems that the BDE has problems with large harddrives, this was under
    w2k adv.server, so that may be part of the culprit..



    Sat, 03 Jan 2004 07:48:04 GMT

    Clayfi
    #11 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    Hej Liz & David,

    Well, I've set the blocksize to 32k, and like I stated, the only
    solution was to use a physically smaller harddisk. Seems like a
    BDE/Win2k problem. Hope this can help you guys!!



    Thu, 08 Jan 2004 21:07:21 GMT

    Clayfi
    #12 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    Hi again,

    Just thought I'd follow up on these insufficient disk space errors.

    Today the same problem occured on the 'smaller' harddisk. This was
    while another BDE intensive application was running on the w2k server.

    Again the solution was similar (with the other application still
    running).
    I changed to using the other 'larger' disk. This fixed the problem.
    (Both disks have several gigabytes available).

    So it in't the actual size of the disk, maybe something with the
    internal buffering? Have no idea, have a cure, but it only works
    temporarily! Hope someone can shed more light on this annoyance.



    Sat, 17 Jan 2004 23:23:08 GMT 
    About...).
    BDEAdmin Config./Drivers/Native/Paradox shows block size 2048,
    but individual tables have different block sizes, the tables (source and
    destination) that cause this error have block size 32768.   (Isn't the BDE
    setting just a default, with no other meaning?)

    Database is a Paradox db on a shared network drive.  Database desktop
    version = 7.0.

    Error happens in just one win2000 machine in batchmove.Execute.
    There are some 15 other computers running on win2k or NT4, and none of them
    fails with this operation.  These computers have the same BDE version, and
    the Delphi-program is the same one.

    When using a database on a local drive this batchmove works ok even on this
    machine.

    Now I suspect there's something wrong with the BDE installation, and it
    will be probably reinstalled in near future. (Which is not in my hands.)
    We'll see then. Anyway, some setting must different on this computer than
    on the others.

    Users have no administrative privileges on their computers; this has caused
    BDE-problems before (which should be fixed now);  could some readonly file
    or registry branch have this effect?

    -  Petri

    John Herbster (TeamB) <herb-sci1_at_sbcglobal.net> wrote in article
    <[email protected]>...

    Quote

    > "pete" <[email protected]> wrote
    > > What might cause the BDE-error "Insufficient disk space",
    > > when there really is no shortage of disk space?

    > Pete, I would do some research here:
    > http://tinyurl.com/em5r short for
    > http://groups.google.com/groups?q=%22Insufficient+disk+space%22+block+si
    > ze
    > What version of the BDE are you using?
    > What kind of tables are you using (i.e. Paradox)?
    > If Paradox, what BlockSize are you using (BDEAdmin)?
    > Regards, JohnH

    Board index » delphi » BDE error "Insufficient disk space"


    Hi.
    BDE version is 5.01  (BDE Administrator, Help edbengineerror insufficient disk space

    Edbengineerror insufficient disk space - excellent words

    About...).
    BDEAdmin Config./Drivers/Native/Paradox shows block size 2048,
    but individual tables have different block sizes, the tables (source and
    destination) that cause this error have block size 32768.   (Isn't the BDE
    setting just a default, with no other meaning?)

    Database is a Paradox db on a shared network drive.  Database desktop
    version = 7.0.

    Error happens in just one win2000 machine in batchmove.Execute.
    There are some 15 other computers running on win2k or NT4, and none of them
    fails with this operation.  These computers have the same BDE version, and
    the Delphi-program is the same one.

    When using a database on a local drive this batchmove works ok even on this
    machine.

    Now I suspect there's something wrong with the BDE installation, and it
    will be probably reinstalled in near future. (Which is not in my hands.)
    We'll see then. Anyway, some setting must different on this computer than
    on the others.

    Users have no administrative privileges on their computers; this has caused
    BDE-problems before (which should be fixed now);  could some readonly file
    or registry branch have this effect?

    -  Petri

    John Herbster (TeamB) <herb-sci1_at_sbcglobal.net> wrote in article
    <[email protected]>...

    Quote

    > "pete" <[email protected]> wrote
    > > What might cause the BDE-error "Insufficient disk space",
    > > when there really is no shortage of disk space?

    > Pete, I would do some research here:
    > http://tinyurl.com/em5r short for
    > http://groups.google.com/groups?q=%22Insufficient+disk+space%22+block+si
    > ze
    > What version of the BDE are you using?
    > What kind of tables are you using (i.e. Paradox)?
    > If Paradox, what BlockSize are you using (BDEAdmin)?
    > Regards, JohnH

    INTRODUCTION

    This article describes a new setting in the following versions of Windows:

    • Windows 8.1 Enterprise and Windows 8.1 Pro

    • Windows 8 Enterprise and Windows 8 Pro

    • Windows 7 Ultimate and Windows 7 Enterprise

    • Windows Vista Ultimate, Windows Vista Enterprise

    This setting helps protect confidential data in a pagefile when BitLocker Drive Encryption (BDE) is enabled.

    More Information

    The Windows 8.1, Windows 8, Windows 7, and Windows Vista memory-management system includes a feature that automatically manages the system pagefile. The memory-management system typically puts the pagefile on the same volume as the operating system (OS). However, if this volume does not have sufficient space, the pagefile may be relocated to another local volume on which more disk space is available. This relocation may cause data-confidentiality issues when BDE is used to protect the OS volume. Specifically, information may be disclosed if the pagefile's new location is on a volume that is not encrypted by BDE.

    To reduce this threat, BDE automatically creates the following registry subkey:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\PagefileOnOsVolumeThis subkey lets you direct the memory-management system to put the pagefile only on the BDE-protected OS volume. Specifically, if you set this subkey to a value of 1, the OS volume is the only volume that the Session Management Sub System (SMSS) will consider as a location for the pagefile. If there is insufficient space on the OS volume, SMSS will create a smaller pagefile on this volume.

    When BDE is enabled, the PagefileOnOSVolume setting is automatically created, and it is set to a value of 1. However, BDE will not create the PagefileOnOsVolume registry entry if the following registry subkey is not set to the default value of ?:\pagefile.sys:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\PagingFilesNote When BDE is disabled, the PagefileOnOSVolume setting remains. Disabling BDE does not delete or disable the PagefileOnOSVolume setting.

    This functionality gives administrators control over how BDE and the memory-management system manage the pagefile. We recommend that you enable Encrypting File System (EFS) encryption of the pagefile if the following conditions are true:

    • The BDE default PagefileOnOSVolume registry setting is not used.

    • The pagefile is not located on a BDE-protected volume.

    برنامه نویس > Native Code > برنامه نویسی در Delphi > مباحث عمومی دلفی و پاسکال > Patch for BDE 'Insufficient disk space' problem. (4Gb multiples


    PDA

    View Full Version : Patch for BDE 'Insufficient disk space' problem. (4Gb multiples



    m-khorsandi

    دوشنبه 03 مرداد 1384, 16:00 عصر

    This unit is a patch for the famous 4Gb BDE Bug. It is build to fix the 'Insufficient disk space'-error which can occur while using BDE when the disk free space is near to a multiple of 4Gb. For more information please see BDE report# 7089 on Quality Central.
    The reason for the error in BDE is aparently a bug in idapi32.dll while computing free disk space. Idapi32.dll is using the api function called GetDiskFreeSpaceA exported by kernel32.dll.
    The solution is to 'patch' GetDiskFreeSpaceA in kernel32.dll for the current process, every call to this function is redirected to a new routine (NewGetDiskFreeSpaceA).

    The source code of the patch is included. If you use another programming language (i.e. not Delphi), a precompiled DLL (FIX4GBug.dll) is also included. (If you can compile the included unit, then you do not need to distribute the DLL)


    vBulletin® v4.2.5, Copyright ©2000-1401, Jelsoft Enterprises Ltd.

    Database Utilities for Paradox and dBase

    PdxEditor for Paradox and dBase tables


    Update: 2022-07-18
    32-bit single exe file for 32- and 64-bit Windows.
    Largely a Borland Database Desktop replacement, this Paradox (level 3.5, 4, 5 and 7) and dBase (level III+, IV, 5 and 7) table editor and analyzer lets you read, edit and extract combined and calculated data from any Paradox and dBase tables as well as rename and resize fields, and for Paradox also to modify table language drivers. Other table modifications within the scope of associated SQL query language (Borland Local SQL).
    Basic Excel & CSV export as well as universal CSV import. Help on Local SQL (the BDE SQL implementation) available as HTMLHelp as well as WebHelp.
    Application link >>
    Associated Local SQL WebHelp: See below.

    BDE Local SQL WebHelp recompilation


    Update: 2020-06-18

    Compatible with any standard browser.
    As the original Borland Local SQL manual has been available in the obsolete WinHelp format only, not compatible with Windows 10, this has been recompiled into the more modern OS independent WebHelp format needing only a standard browser to display.
    Recompilation is independent and of no responsibility of the original issuers Borland/Inprise Corporation.

    View: Local SQL WebHelp manual
    Download for offline use: LocalSQL WebHelp or HTMLhelp
    For use with PdxEditor: unpack in .\Help subdirectory.

    Is BDE installed?


    Update: 2018-06-18
    Single exe file for 32- and 64-bit Windows.
    To test if your PC has Borland Database Engine at all and if it is correctly configured.

    Download: BDEtest.zip
    unpack, drop and run from anywhere (except C:\ and C:\Program Files).

    BDE configurator

    Update: 2018-10-16
    Single exe file for 32- and 64-bit Windows.
    For the general adaption of BDE to be used with Windows after Windows XP, the settings file (usually IDAPI32.cfg) should be stored outside the C:\Program Files and the C:\ root directories.
    You may choose e.g. "C:\Data\BDE\Config" once and for all.
    Using Paradox/paradox files after Windows XP you should likewise change the standard location of the Paradox NetFile directory (NET DIR) to be located outside the C:\Program Files and C:\ root directories.
    Paradox NET DIR location is accessed via the BDE Administrator (Windows Control Panel: BDE Administrator\ Configuration\ Driver\ Native\ Paradox).
    You may choose e.g. "C:\Data\BDE\NetDir" once and for all.
    (Some applications may however wisely manage their use of NetFile as an independent per session setting avoiding the possible general conflicts about NetDir location.)

    Needs Administrator privileges as it accesses the Registry root key HKEY_LOCAL_MACHINE for some of the BDE configuration settings (just like the BDE Administrator app).

    For ad hoc changes of default database driver and table level, the BDE Configurator might be the most convenient tool:
    Download: BDEconfig.zip
    unpack, drop and run from anywhere.

    BDE - the Borland Database Engine

    If using the BDE, first of all an admin user must move the configuration file (usually IDAPI32.CFG) outside the folder C:\Program Files (or equivalent according to your language locale), as Windows from version Vista and onwards will not allow applications storing or altering data in this folder and below nor at the C root.
    Second, the Paradox NetFile directory also should be directed to some location outside the C root (C:\) or C:\Program Files directory.
    If so configured, the BDE still serves trustworthyly even with the later versions of Windows, 32- and 64-bit, including Windows 10.
    For creating new tables on a Windows system you should use one of the ANSI language drivers, e.g. 'WEurope' ANSI.

    Needs Administrator previleges as it accesses the Registry root key HKEY_LOCAL_MACHINE for some of the BDE configuration settings. Use "Run as administrator".

    Missing the BDE?

    • Download and run BDE installer:
      BDE-install.zip (v.5.2.0.2)
      (execute installer in "Run as Administrator" mode)
    • Modified BDE installer preventing "Insufficient disk space." error when running SQL on large datasets. IDAPI32.dll modified acc. to Rick Kelly with included BDEKER32.dll. This fully replaces the original installer.
      Download: BDE-install-m.zip (v.5.2.0.2)
    • Each of the BDE installers above may be run in command line mode as:
      BDE-install.exe /T   (test mode)
      BDE-install.exe /M  (manual mode)
      BDE-install.exe /X   (extract mode)

    Borland Database Desktop 7 (DBD)

    If you really, really need the original 1996 Borland Database Desktop - here it is.

    Application link >>

    Contact US

    INTELLIGENT WORK FORUMS
    FOR COMPUTER PROFESSIONALS

    Thanks. We have received your request and will respond promptly.

    Log In

    Come Join Us!

    Are you a
    Computer / IT professional?
    Join Tek-Tips Forums!

    • Talk With Other Members
    • Be Notified Of Responses
      To Your Posts
    • Keyword Search
    • One-Click Access To Your
      Favorite Forums
    • Automated Signatures
      On Your Posts
    • Best Of All, It's Free!

    Join Us!

    *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

    Posting Guidelines

    Promoting, selling, recruiting, coursework and thesis posting is forbidden.

    Students Click Here

    Tek-Tips Posting Policies

    Contact US

    Insufficient disk space., BDE Error Cat:Code: [37:3], BDE: 500 ...

    Insufficient disk space., BDE Error Cat:Code: [37:3], BDE: 500 ...

    koom(TechnicalUser)

    (OP)

    Hi,

    One of our sales reps got the following error listed 3 times  when he tried to sync once:


    Insufficient disk space.
     
    Context: appendFrom: c:\goldmine\Sync\WizProf\42771287\USER\In\Working\MailBox
    C:\GoldMine\GMBase\MailBox
     
    1: File: C:\DOCUME~1\user\LOCALS~1\Temp\INMEM000.REM
     
    BDE Error Cat:Code: [37:3]
    BDE: 500 [9/6/1998]  GoldMine: 6.60.40707
     
    User: USER  
    Window:
    Template:
    Details:
    FILENAME: C:\DOCUME~1\user\LOCALS~1\Temp\INMEM000.REM


    I know the INMEM000.REM file is a temporary file that is created and is supose to be deleted when its eithe done syncronizing or when you close goldmine. (the file is created by Borland Database Engine (BDE)).

    the error happens on his laptop. The size of our database directory on the server is only 21MB.
    The log file says everything went fine, but the user got the errors (on his side..).

    I wonder if any one can give me some direction in how to solve this?

    Thank you for Any help you can provide!!
    --Koomo

    Red Flag Submitted

    Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
    The Tek-Tips staff will check this out and take appropriate action.

    AuthorMessage

    David Scav
    #1 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    I have a Windows NT v4 Terminal Server (SP5) with Paradox 8 (SP1)
    installed. The file server is Windows 2000.

    When I attempt to restructure a table on the file server using Paradox
    8 from the Terminal Server, I get the error:

    Insufficient Disk Space

    The table I want to restructure is 110MB (211MB including indexes).
    The stuff I was able to turn up on Deja says that you need plenty of
    space on:
       1) Drive where table is
       2) PRIV directory
       3) Windows TEMP directory

    There is 60 Gigs of free space on the drive that contains the file to
    be restructured. On my Terminal Server, the boot drive (which contains
    PRIV and the Windows TEMP directory), has 1.9 Gig free space.

    Any ideas would be greatly appreciated.



    Sun, 30 Nov 2003 22:14:37 GMT

    Liz
    #2 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    David,

    I suppose it's possible that the BLOCK SIZE need to be bigger
    (110MB is nearing the limit of the smallest block size setting).

    To change the block size on an existing table:

    1. Exit all BDE apps
    2. Open the BDE and change the block size setting (configuration
    tab)
    3. Create a new table with the same structure as the old
    4. Add data from old table to new table
    5. Rename as needed
    6. Reset the block size setting in the BDE (if desired)

    PLEASE BACK UP DATA FIRST.

    I'm not sure this is the problem, but it's possible.

    Liz

    Quote:


    > I have a Windows NT v4 Terminal Server (SP5) with Paradox 8 (SP1)
    > installed. The file server is Windows 2000.

    > When I attempt to restructure a table on the file server using Paradox
    > 8 from the Terminal Server, I get the error:

    > Insufficient Disk Space

    > The table I want to restructure is 110MB (211MB including indexes).
    > The stuff I was able to turn up on Deja says that you need plenty of
    > space on:
    >    1) Drive where table is
    >    2) PRIV directory
    >    3) Windows TEMP directory

    > There is 60 Gigs of free space on the drive that contains the file to
    > be restructured. On my Terminal Server, the boot drive (which contains
    > PRIV and the Windows TEMP directory), has 1.9 Gig free space.

    > Any ideas would be greatly appreciated.



    Sun, 30 Nov 2003 23:34:45 GMT

    David Scav
    #3 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    Quote:


    >I suppose it's possible that the BLOCK SIZE need to be bigger
    >(110MB is nearing the limit of the smallest block size setting).
    >I'm not sure this is the problem, but it's possible.

    The blocksize for this file is already set to 16K.


    Mon, 01 Dec 2003 02:17:13 GMT

    Liz
    #4 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    David,

    Is the BLOCK SIZE in the BDE set to that?  In theory, it
    shouldn't matter, but perhaps when doing a restructure it looks
    at the setting in the BDE....  Anywho, check and test - should be
    quick and easy.

    The only other thing I can think of is if one of the server
    directories has a size limit (as server dirs so often do) and so
    while the _disk_ has plenty of room, the dir does not...

    Sorry, no other ideas come to mind.

    Liz

    Quote:


    > >I suppose it's possible that the BLOCK SIZE need to be bigger
    > >(110MB is nearing the limit of the smallest block size setting).

    > >I'm not sure this is the problem, but it's possible.

    > The blocksize for this file is already set to 16K.



    Mon, 01 Dec 2003 03:06:54 GMT

    David Scav
    #5 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    Quote:


    >Is the BLOCK SIZE in the BDE set to that?  In theory, it
    >shouldn't matter, but perhaps when doing a restructure it looks
    >at the setting in the BDE....  Anywho, check and test - should be
    >quick and easy.

    Blocksize in the BDE is set to 2048. Tools / Table Repair show the
    table blocksize as 16K (which is correct, since this table grows over
    time and at one point had lots of records in it).

    Quote:

    >The only other thing I can think of is if one of the server
    >directories has a size limit (as server dirs so often do) and so
    >while the _disk_ has plenty of room, the dir does not...

    No directory size limits on our servers.

    One other bit of info is that I can successfully restructure this
    table from a Win98 client with no "insufficient disk space" errors
    Free space on the Win98 boot drive [TEMP and PRIV directories] is less
    than on the NT Terminal Server  -973MB.

    Very strange indeed.....



    Sat, 06 Dec 2003 05:25:48 GMT

    Liz
    #6 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    David,

    Did you try setting the BLOCK SIZE to 16K and then doing your
    restructure?  If not, that would be the first thing I would try -
    just to eliminate it as a possibility (or identify it as the
    problem).

    Liz

    Quote:


    > >Is the BLOCK SIZE in the BDE set to that?  In theory, it
    > >shouldn't matter, but perhaps when doing a restructure it looks
    > >at the setting in the BDE....  Anywho, check and test - should be
    > >quick and easy.

    > Blocksize in the BDE is set to 2048. Tools / Table Repair show the
    > table blocksize as 16K (which is correct, since this table grows over
    > time and at one point had lots of records in it).

    > >The only other thing I can think of is if one of the server
    > >directories has a size limit (as server dirs so often do) and so
    > >while the _disk_ has plenty of room, the dir does not...

    > No directory size limits on our servers.

    > One other bit of info is that I can successfully restructure this
    > table from a Win98 client with no "insufficient disk space" errors
    > Free space on the Win98 boot drive [TEMP and PRIV directories] is less
    > than on the NT Terminal Server  -973MB.

    > Very strange indeed.....



    Sat, 06 Dec 2003 07:36:45 GMT

    David Scav
    #7 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    Quote:


    >Did you try setting the BLOCK SIZE to 16K and then doing your
    >restructure?  If not, that would be the first thing I would try -
    >just to eliminate it as a possibility (or identify it as the
    >problem).

    Do you mean the BDE blocksize on the machine ?

    Because the table blocksize is already 16K.



    Sat, 20 Dec 2003 22:13:49 GMT

    Liz
    #8 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    David,

    Yes, the BDE block size setting.  This setting is what's used for
    new tables, and I'd want to rule out the possibility that the
    restructure is using that setting rather than the source table's
    block size.

    Liz

    Quote:


    > >Did you try setting the BLOCK SIZE to 16K and then doing your
    > >restructure?  If not, that would be the first thing I would try -
    > >just to eliminate it as a possibility (or identify it as the
    > >problem).

    > Do you mean the BDE blocksize on the machine ?

    > Because the table blocksize is already 16K.



    Sat, 20 Dec 2003 23:05:33 GMT

    Sedge Simon
    #9 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    We've seen this problem with restructures and queries. What solved it
    was to empty the trashcan. The BDE and Windows seem to disagree about
    how to manage disk space as the temporary files needed for these
    operations are deleted, and a "full" trashcan cause this semi-bogus
    error message.

    --
    Sedge

    Posted via dBforums, http://dbforums.com



    Tue, 30 Dec 2003 00:04:45 GMT

    Clayfi
    #10 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    Been having this annoying problem too.

    Fixed it by placing the pdxtable on a smaller harddrive.

    Seems that the BDE has problems with large harddrives, this was under
    w2k adv.server, so that may be part of the culprit..



    Sat, 03 Jan 2004 07:48:04 GMT

    Clayfi
    #11 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space
    Hej Liz & David,

    Well, I've set the blocksize to 32k, and like I stated, the only
    solution was to use a physically smaller harddisk. Seems like a
    BDE/Win2k problem. Hope this can help you guys!!



    Thu, 08 Jan 2004 21:07:21 GMT

    Clayfi
    #12 / 12

     Paradox 8 - Restructure Gives Insufficient Disk Space

    Hi again,

    Just thought I'd follow up on these insufficient disk space errors.

    Today the same problem occured on the 'smaller' harddisk. This was
    while another BDE intensive application was running on the w2k server.

    Again the solution was similar (with the other application still
    running).
    I changed to using the other 'larger' disk. This fixed the problem.
    (Both disks have several gigabytes available).

    So it in't the actual size of the disk, maybe something with the
    internal buffering? Have no idea, have a cure, but it only works
    temporarily! Hope someone can shed more light on this annoyance.



    Sat, 17 Jan 2004 23:23:08 GMT