04 Jul 15 21:36, you wrote to Mike Luther:

 MikeL>> use at least one 'blank line' at the end of the CONFIG.SYS file to
 MikeL>> solve some strange error problems in some systems.

 EV> When a software program is set up to expect something and it isn't
 EV> there, it causes software to BURP!

 MikeL>> As well DOS operations under OS/2 cannot 'normally' handle more
 MikeL>> than a 2GB file partition as far as I know under a lot of DOS
 MikeL>> stuff I still use.

 EV> That would take more partitions than there are file letters on a 250GB
 EV> HDD.

yup! it takes C thru L to do 2Gig partitions on a 40Gig drive... if one
goes that way...

 EV> But I have read in this echo of a work-around but I can't recall what
 EV> it was called right now.

yep... on OS/2 there's a special "driver" that is loaded in the
DOS tasks... it is called 2gbfix.com... it is little more than a TSR...
what it does is to intercept the calls to the drive space checking
routines... if they report negative numbers (because of the signed number
rollover), then it alters the response so that it returns 2gb or less than
2gb so that the DOS program will see a valid positive number instead of an
invalid negative one...

the largest value available for older DOS programs is stored in a longint
(aka long integer)... a longint is a signed integer 32bits in length making
it 4 bytes in size... it has the range of -2,147,483,648 to 2,147,483,647,
or -2^31 to 2^31-1... when the value reaches the maximum positive value, it
rolls over to the bottom most value and keeps on incrementing as before...
once the value passes 2gb, it is negative and will remain negative for
another 2gb of counting until it reaches zero and goes positive again...
there is no unsigned 32bit storage capability for large values in old DOS
programs...

)\/(ark

... Split your coffee? Call a Chemist!
---