![]() | |
#41
| |||
| |||
|
|
On Oct 23, 10:42*am, Tony Gravagno address.is.in.po... (AT) removethis (DOT) com.invalid> wrote: dtsig wrote: According to refman.pdf "The stream is returned as a pointer to a character or 0 if an error occurred. *system(0) contains the error number." When we open an os level file with the %fopen command we get an error of 27 streamFrom = (char*)%fopen(fileReadFrom, oFlag) if streamFrom = 0 then err = system(0) ; debug My question is ... where is the definition of the error numbers returned? ... I have looked at the unix.h table but have not found anything. Hi Dave, you're close. You're now working in C world so the data is in a place familiar to C developers, ERRNO.H. In D3, that's dm,bp,unix.h, errno.h. *There you'll see error 27 is EFBIG, which is "File too large". *Aside from trying to read a file that's over 2GB in size, I'm not sure what would cause this in D3. Maybe trying to read a host OS file that's larger than the 100MB VME blob? Or possibly just more than your available overflow frames. Please let us know if you find out what tripped this. *I do occasional work with these functions and information is tough to find. Regards, T No .. it is the size and the fact that PICK is to current sw what old IBMPC sw was to 32bit <G Another attempt to do real world stuff with the tools at hand. Will work out a way with better tools to resize things to that PICK can handle it <g Thanks for the quick reply |
#42
| |||
| |||
|
|
Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues |
#43
| |||
| |||
|
|
Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues |
#44
| |||
| |||
|
|
Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues |
#45
| |||
| |||
|
|
Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues |
#46
| |||
| |||
|
|
Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues |
#47
| |||
| |||
|
|
Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues |
#48
| |||
| |||
|
|
Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues |
#49
| |||
| |||
|
|
Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues |
#50
| |||
| |||
|
|
dtsig wrote: On Oct 23, 10:42*am, Tony Gravagno address.is.in.po... (AT) removethis (DOT) com.invalid> wrote: dtsig wrote: According to refman.pdf "The stream is returned as a pointer to a character or 0 if an error occurred. *system(0) contains the error number." When we open an os level file with the %fopen command we get an error of 27 streamFrom = (char*)%fopen(fileReadFrom, oFlag) if streamFrom = 0 then err = system(0) ; debug My question is ... where is the definition of the error numbers returned? ... I have looked at the unix.h table but have not found anything. Hi Dave, you're close. You're now working in C world so the data is in a place familiar to C developers, ERRNO.H. In D3, that's dm,bp,unix.h, errno.h. *There you'll see error 27 is EFBIG, which is "File too large". *Aside from trying to read a file that's over 2GB in size, I'm not sure what would cause this in D3. Maybe trying to read a host OS file that's larger than the 100MB VME blob? Or possibly just more than your available overflow frames. Please let us know if you find out what tripped this. *I do occasional work with these functions and information is tough to find. Regards, T No .. it is the size and the fact that PICK is to current sw what old IBMPC sw was to 32bit <G Another attempt to do real world stuff with the tools at hand. *Will work out a way with better tools to resize things to that PICK can handle it <g Thanks for the quick reply Have fun blaming D3 for this here and in the U2 forum, but if you do some research you'll find people everywhere have the same issues (Google "fopen 2gb"). Can we take a step back and discuss what it is that you're trying to read from a 2gb file? *As we've discussed before this might not be the right approach to the business problem you're trying to solve. T |
![]() |
| Thread Tools | |
| Display Modes | |
| |