>Roxanne,
>
>I suspected as much. SYS(2020) in FPW 2.6 reported my 2.1GB hard drive correctly. Here's a little something for the AT&t folks to munch on, and tell them bon appetite: C|
>
>If something is hard coded into the EXE, don't forget about the HexEditor that comes with VFP 5.0.
>
>Good Luck,
>
>George


Hey George Guess What... seems SYS(2020) is reporting correctly for 2.1 GB drives and smaller. But with anything bigger is defaulting to 10.2 regardless of what the real size is. I cant see how that matters though, something weird must be hardcoded and this HexEditor thing doesnt look like too munch fun because theres too many generically named *.app files & I dont know where to begin. And sure enough the stand-alone machine did the same thing once all data files were copied over. But still, how in the world could they have programmatically set a disk size limitation that keeps the app from seeing all available space?

;-) Forgive me but I've thrown in the virtual towel and have begun the old braindead process of reformat/re-partition/re-install. If AT&T says the drives cant be bigger than a GB then so be it. Bet I'll be writing my own version of this package someday over the rainbow. How about a virtual pizza since we've ruled out a fedora?