I know this has been discussed before, but I have not seen a satisfactory work-around. This issue is AREV reporting insufficient disk space upon creating a table or copying one. I know that AREV is checking disk space and I also realize the limit of the signed long word that is used to store the free disk space. Is there a work around to this issue.

The stuations under which this has happened are both single and multi user AREV installations. I am very network literate and (in the case of multi user) have checked the usual items like ownership under Novell and user disk space limitations under Novell.

I encountered a message written by someone in the discussion area that talked about a work-around and included a Hyperlink to the document. Unfortunately, this link is now invalid.

Possible solutions include:

* Limiting the space allocated to users of the volume to less than 2 Gb. It may be sufficient to limit the space so that the free space falls under 2 Gb.

* Change the DISKSIZE routine in SYSOBJ. There was a basic version of such a replacement routine posted some time back. I took it and modified it to fit the network we are using. Here it is:

FUNCTION DISKSIZE(DRIVELETTER)
DECLARE SUBROUTINE DSPACE
FREEBYTES=0
A=0
B=0
TOTAL.ALLOCATION.UNITS.ON.DISK=0
DSPACE(DRIVELETTER,FREEBYTES,0,A,B,TOTAL.ALLOCATION.UNITS.ON.DISK)
IF FREEBYTES THEN
   DRIVE.SIZE.IN.BYTES=TOTAL.ALLOCATION.UNITS.ON.DISK * A * B
   REPLY=DRIVE.SIZE.IN.BYTES
   REPLY=ABS(FREEBYTES)
END ELSE
   PCPERFORM 'CHKVOL ]CHKVOL.TXT'
   DISKINFO=XLATE('DOS','CHKVOL.TXT','','X')
   IX1=INDEX(DISKINFO,'Total volume space:',1)
   IX2=INDEX(DISKINFO,'Space remaining on volume:',1)
   TOTAL_SPACE=TRIM(DISKINFOIX1+19,'K')
   TOTAL_SPACE=ICONV(TOTAL_SPACE,'MD0') * 1024
   REMAINING_SPACE=TRIM(DISKINFOIX2+26,'K')
   REMAINING_SPACE=ICONV(REMAINING_SPACE,'MD0') * 1024
   REPLY=TOTAL_SPACE:@FM:REMAINING_SPACE
END
RETURN REPLY

This routine uses the Netware CHKVOL routine to get the appropriate values for disk space.

* If your problem is with COPYTABLE, do the COPYTABLE first to a drive that is not so large, perhaps your local hard disk. Then do a DOS copy to move the .LK and .OV files and edit the REVMEDIA file manually. Actually, I think the problem does not exist with MAKETABLE, so you could do a MAKETABLE and then a DOS copy.

Thanks very much for the information Victor. I will compose a module across multiple versions of AREV and different filing systems to deal with this problem.

View this thread on the forum...